public inbox for [email protected]
help / color / mirror / Atom feedFrom: Andreas 'ads' Scherbaum <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: New blog - who dis?
Date: Mon, 4 Sep 2023 14:47:25 +0200
Message-ID: <CAMDzVO9do0WroHM-Mto3gmYbHUVE6LncpRONZc=1-m0=uVQbtg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAMDzVO9mer4V8OON7KhynDwE267oZr6BiF-9=gc22dzLmsxWDw@mail.gmail.com>
<[email protected]>
On Mon, Sep 4, 2023 at 1:00 PM Alvaro Herrera <[email protected]>
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
--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: New blog - who dis?
In-Reply-To: <CAMDzVO9do0WroHM-Mto3gmYbHUVE6LncpRONZc=1-m0=uVQbtg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox