MIME-Version: 1.0
References: 
 <CAMDzVO9mer4V8OON7KhynDwE267oZr6BiF-9=gc22dzLmsxWDw@mail.gmail.com>
 <20230904105958.s45oaei7x3te37e4@alvherre.pgsql>
In-Reply-To: <20230904105958.s45oaei7x3te37e4@alvherre.pgsql>
From: "Andreas 'ads' Scherbaum" <ads@pgug.de>
Date: Mon, 4 Sep 2023 14:47:25 +0200
Message-ID: 
 <CAMDzVO9do0WroHM-Mto3gmYbHUVE6LncpRONZc=1-m0=uVQbtg@mail.gmail.com>
Subject: Re: New blog - who dis?
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: pgsql-www@lists.postgresql.org, planet@postgresql.org
Content-Type: multipart/alternative; boundary="000000000000894b7c060487ead5"
Archived-At: 
 <https://www.postgresql.org/message-id/CAMDzVO9do0WroHM-Mto3gmYbHUVE6LncpRONZc%3D1-m0%3DuVQbtg%40mail.gmail.com>
Precedence: bulk

--000000000000894b7c060487ead5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 4, 2023 at 1:00=E2=80=AFPM Alvaro Herrera <alvherre@alvh.no-ip.=
org>
wrote:

> Hello,
>
> On 2023-Sep-04, Andreas 'ads' Scherbaum wrote:
>
> > I plan to migrate my blog to a new software platform, which
> > will also change the URLs which appear in the RSS feed. There
> > is no convenient way to keep the old URLs in place.
> >
> > Most importantly, this will affect Planet PostgreSQL, which
> > suddenly might see about 150 "new" blog postings.
> >
> > Is there a recommended way how to deal with such a move?
>
> Each post in the blog has a "guid" unique identifier, which is usually
> the same as the URL, but some platforms let you set up something
> different.  If you can "migrate" your posts to the new platform while
> keeping the GUIDs, that would be best -- they would not be seen as new
> posts.  The actual URLs don't actually matter.
>

The guid in my case is the full URL of the posting, including the domain.
I would need to break and fix quite a few things to port this guid over to
the new system, and I can easily miss something before going live.

I'd rather not go down this path.


> If your platform doesn't let you do this, I think PlanetPostgres would
> mark the new posts as hidden anyway, because of the volume (but pester
> everyone along the way).  That way only future new posts (actually new
> posts) would be syndicated, but everything would appear duplicate in the
> admin interface.
>

Will it work if I disconnect the old blog from Planet, then move the
software
and apply the blog again? Will this ingest all previous postings on the
feed, or just the new ones?


> > Did someone do such a move before, what is your experience?
>
> It's usually a pretty noisy things to do, from the moderators point of
> view.
>

That's exactly what I want to avoid.


Thanks

--=20
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project

--000000000000894b7c060487ead5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Sep 4, 2023 at 1:00=E2=80=AFP=
M Alvaro Herrera &lt;<a href=3D"mailto:alvherre@alvh.no-ip.org">alvherre@al=
vh.no-ip.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">Hello,<br>
<br>
On 2023-Sep-04, Andreas &#39;ads&#39; Scherbaum wrote:<br>
<br>
&gt; I plan to migrate my blog to a new software platform, which<br>
&gt; will also change the URLs which appear in the RSS feed. There<br>
&gt; is no convenient way to keep the old URLs in place.<br>
&gt; <br>
&gt; Most importantly, this will affect Planet PostgreSQL, which<br>
&gt; suddenly might see about 150 &quot;new&quot; blog postings.<br>
&gt; <br>
&gt; Is there a recommended way how to deal with such a move?<br>
<br>
Each post in the blog has a &quot;guid&quot; unique identifier, which is us=
ually<br>
the same as the URL, but some platforms let you set up something<br>
different.=C2=A0 If you can &quot;migrate&quot; your posts to the new platf=
orm while<br>
keeping the GUIDs, that would be best -- they would not be seen as new<br>
posts.=C2=A0 The actual URLs don&#39;t actually matter.<br></blockquote><di=
v><br></div><div>The guid in my case is the full URL of the posting, includ=
ing the domain.</div><div>I would need to break and fix quite a few things =
to port this guid over to</div><div>the new system, and I can easily miss s=
omething before going live.</div><div><br></div><div>I&#39;d rather not go =
down this path.<br></div><div><br></div><div><br></div><div>=C2=A0<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex">
If your platform doesn&#39;t let you do this, I think PlanetPostgres would<=
br>
mark the new posts as hidden anyway, because of the volume (but pester<br>
everyone along the way).=C2=A0 That way only future new posts (actually new=
<br>
posts) would be syndicated, but everything would appear duplicate in the<br=
>
admin interface.<br></blockquote><div><br></div><div>Will it work if I disc=
onnect the old blog from Planet, then move the software</div><div>and apply=
 the blog again? Will this ingest all previous postings on the</div><div>fe=
ed, or just the new ones?<br></div><div><br></div><div><br></div><div>=C2=
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
&gt; Did someone do such a move before, what is your experience?<br>
<br>
It&#39;s usually a pretty noisy things to do, from the moderators point of<=
br>
view.<br></blockquote><div><br></div><div>That&#39;s exactly what I want to=
 avoid.<br></div><div><br></div></div><div class=3D"gmail_quote"><br></div>=
<div class=3D"gmail_quote">Thanks<br clear=3D"all"></div><br><span class=3D=
"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_sign=
ature"><div dir=3D"ltr"><div><div dir=3D"ltr"><span><span style=3D"white-sp=
ace:pre">				</span></span>Andreas &#39;ads&#39; Scherbaum<br>German Postgr=
eSQL User Group<br>European PostgreSQL User Group - Board of Directors<br>V=
olunteer Regional Contact, Germany - PostgreSQL Project<br></div></div></di=
v></div></div>

--000000000000894b7c060487ead5--