search

CaptainFact / captain-fact

📚 Documentation, wiki and community discussions
https://captainfact.io
67 stars 7 forks source link

Move all services to render.com #124

Closed Betree closed 3 years ago

Betree commented 4 years ago

If implemented, it will resolve https://github.com/CaptainFact/captain-fact/issues/16

Motivation

We currently use two services for hosting CaptainFact:

With Scaleway we get a good computing power for a decent price (8 x 64bit cores, 32GB ram and 300SSD disk for ~25€/m), however:

I've recently experimented with https://render.com. It's a great service that provides the simplicity of Netlify to do continuous deployment with the entire stack. Their pricing is very affordable, to migrate the entire stack we'd need:

Migration plan

Test migration

Move staging server with the same steps as prod migration, but without moving the DB.

Need to check:

Production migration

We can eventually move frontend before or later, it doesn't impact the migration.

Estimated time to complete: 4 hours

Betree commented 4 years ago

Turns out this is not as easy as I expected, we need to review our build system. I'll probably revisit after https://github.com/CaptainFact/captain-fact-api/issues/40.

Betree commented 4 years ago

Our main server is going down by the end of the year (see the email below) so we'll have to prioritize this issue.

I've started moving the build to mix release in https://github.com/CaptainFact/captain-fact-api/pull/226, which should help to make the move smoother.

We're also going to need a reverse proxy (we are currently using traefik). Two options:

Email from Scaleway:

image

Betree commented 3 years ago

Done