Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Server migration - status, discussion
gaekwad wrote #313798:
…I don’t want to spoil the surprise!
you little devil, you .. .cheers!
PS Digital Ocean!
So we are now officially into TxP 2.0. TxP is now all grown up and has shed its old roots. 2018. Congratulations to all the Devs and a big Thank You!
Last edited by bici (2018-09-03 16:50:37)
…. texted postive
Offline
Re: Server migration - status, discussion
bici wrote #313799:
So we are now officially into TxP 2.0.
Well, actually we’re into http/2, TLS 1.3 (with TLS 1.2 fallback), IPv6 (with IPv4 fallback), and a lot more scope to run some very neat things in future. Happy days!
Offline
Re: Server migration - status, discussion
It looks like textpattern.com has migrated successfully. DNS changes should roll out over the coming hours/days. There are some small snags on caching which will be rectified in the coming days.
Otherwise, all systems go! Please report any issues in this thread, bearing in mind you may need to clear your cache before you can see the new server.
This leaves the following properties to migrate:
- Textpattern RPC server for legacy installations (this needs some attention first, uptime/availability is essential)
- Textpattern forum (this is a sizeable job)
- TXP magazine (some preflight tasks to complete first)
Offline
Re: Server migration - status, discussion
Great stuff Pete! The new server also helps with what I have planned for the Thenes and Plugins sites, which would not run on the old server.
PS. We need to discuss moving the docs site to .com suffix which will complete that migration. I’ll need to look into Github’s recent allowance of HTTPS for custom domains – which also means we won’t need Cloudflare’s services essentially.
Offline
Re: Server migration - status, discussion
Cool! I hope you’ve had your Asahi by now!
philwareham wrote #313810:
I’ll need to look into Github’s recent allowance of HTTPS for custom domains – which also means we won’t need Cloudflare’s services essentially.
Can you explain that, please? On another site, we’re debating whether to keep Cloudflare and I know too little about that.
TXP Builders – finely-crafted code, design and txp
Offline
Re: Server migration - status, discussion
philwareham wrote #313810:
PS. We need to discuss moving the docs site to .com suffix which will complete that migration. I’ll need to look into Github’s recent allowance of HTTPS for custom domains – which also means we won’t need Cloudflare’s services essentially.
Totally fine – we can whack it on the roadmap, no worries. I’ve got some time tonight if it’s easy to do, and honestly I have about 3x safe levels of caffeine in my system from earlier on so the timing’s good.
Offline
Re: Server migration - status, discussion
jakob wrote #313811:
Cool! I hope you’ve had your Asahi by now!
Not yet, but it’s coming. I decided to postpone until the whole job is done. I’m a terrible beer drinker, I have maybe 5 a year maximum.
Offline
Re: Server migration - status, discussion
Hi Jakob, we only now use Cloudflare on Textpattern sites to enforce HTTPS on the docs site (which is a Jekyll powered GitHub Pages site). Up until very recently you couldn’t have a custom domain pointing to a GitHub Pages site and have it run as HTTPS – so we use Cloudflare as a middleman to incept requests and rewrite to HTTPS.
Now GitHub do allow custom domains with HTTPS natively I can get rid of this service.
Cloudflare is still very good in my opinion and their caching is excellent – but Pete’s server build is also very fast so instead of handing our DNS to a third party (which occasionally can be subject to outages and attacks) we can simply drop their services here without any performance impact.
Offline
Re: Server migration - status, discussion
Thanks for the eloquent explanation, Phil!
TXP Builders – finely-crafted code, design and txp
Offline
Offline
Re: Server migration - status, discussion
NicolasGraph wrote #313822:
FYI, on the main textpattern.com domain, the Documentation and Themes menu items are still linked to the .io extension.
Hi Nicolas! The documentation is currently living on .io (so that is correct), but will soon move to .com instead. There is some work happening today and during this week, philwareham and I are continuing with behind-the-scenes work to consolidate and simplify some things.
Edit: now moved to docs.textpattern.com
Last edited by gaekwad (2018-09-04 15:06:13)
Offline
Re: Server migration - status, discussion
Docs are now at docs.textpattern.com. We still need to redirect any traffic that goes to docs.textpattern.io, but that will happen during this week.
Offline
Re: Server migration - status, discussion
philwareham wrote #313825:
Docs are now at docs.textpattern.com. We still need to redirect any traffic that goes to docs.textpattern.io, but that will happen during this week.
Done.
I’m tail-ing the log files, but it looks like anything hitting docs.textpattern.io transfers quickly and seamlessly to an equivalent URL on docs.textpattern.com with a 301 redirect as the cherry on the frosting on the cake.
Offline
Re: Server migration - status, discussion
Hi again,
Thanks for your work on the migration.
I just noticed that any search on the forum renders a 404 error because it is searching on the .com domain while the forum is still on the .io.
Last edited by NicolasGraph (2018-09-05 09:11:26)
Offline
Re: Server migration - status, discussion
NicolasGraph wrote #313832:
Hi again,
Thanks for your work on the migartion.
I just noticed that any search on the forum renders a 404 error because it is still searching on the .com domain.
Oh, yes. The forum is partway migrated (I’ve update some of the codebase for the new home). This will be fixed as the site moves to the new server very soon.
Offline