chore - fly deployment #11
Conversation
apps/certbot-service/README.md
Outdated
|
|
||
| 3. Set the appropriate environment variables and secrets for the app "postgres-new-certbot" (see `.env.example`) in fly.io UI (available in Bitwarden as a secure note "fly.io postgres.new cerbot .env") | ||
|
|
||
| 4. Setup [cron-manager](https://github.com/fly-apps/cron-manager?tab=readme-ov-file#getting-started) to run the certbot service every 2 weeks with the following `schedules.json`: |
There was a problem hiding this comment.
Can we use this approach to schedule machines so that we don't need a separate cron manager instance running?
There was a problem hiding this comment.
Let's investigate this approach once we have the POC deployed and working. I wanted to use this option but as you can read in the thread, the docs is lacking and finding the right command incantations seems not trivial.
But I'm definitely open to switch to it if we can make it works. 😄
| @@ -22,5 +22,5 @@ cpu_kind = 'shared' | |||
| cpus = 1 | |||
|
|
|||
| [mounts] | |||
| source = "postgres-new-data" | |||
| source = "postgres_new_data" | |||
There was a problem hiding this comment.
Wondering if a volume is really necessary vs. just a directory on the ephemeral VM we treat as a cache? As soon as you attach a volume on Fly, auto scaling doesn't work (or only works for as many volumes as you manually create since volumes are 1-to-1 to a machine).
There was a problem hiding this comment.
Yeah it's not necessary, I'll find a way of deleting the cache in another PR 👍
What kind of change does this PR introduce?
chore
What is the current behavior?
we can only run db-service locally
What is the new behavior?
we can deploy db-service