DevOps: deployment with fly.io

[evereq]

See https://fly.io. Make it possible to quickly deploy Gauzy into Fly.io infra. See https://fly.io/docs/languages-and-frameworks/dockerfile for the best way to make it (I think). Plus we have to use https://fly.io/docs/postgres

[evereq]

1. For a more powerful token that can manage multiple applications, run flyctl auth token.
2. GitHub Actions: https://fly.io/docs/app-guides/continuous-deployment-with-github-actions/
3. Secrets management: https://fly.io/docs/reference/secrets
4. Terraform - https://github.com/fly-apps/terraform-provider-fly

[evereq]

Posted question in https://community.fly.io/t/is-fly-still-pursuing-one-click-app-deployments/2611/10?u=ever

[evereq]

See https://github.com/triggerdotdev/fly.io for example of full project deployment into Fly.io

[evereq]

Some commands we run manually:

• Open terminate in .fly\applications folder and run all commands from either api or webapp subfolders

• To (re)deploy app, run command flyctl deploy for each app

• Create Volumes for API public and data folder (Note: public volume is not in use yet because can't attach multiple for now):

flyctl volumes create api_data --region lax --size 1
flyctl volumes create api_public --region lax --size 1

• Scale machine type for API

cd api
flyctl scale vm shared-cpu-2x

• Scale count of machines (to 1 for now because we don't need more for demo and we are using SQLite):

cd api
flyctl scale count 1

cd webapp
flyctl scale count 1

• Scale memory for API (min 2GB RAM required)

cd api
flyctl scale memory 2048

• Scale memory for WebApp:

cd webapp
flyctl scale memory 512

[evereq]

NOW:

• we have Gauzy UI deployed to https://ever-gauzy-webapp.fly.dev
• we have Gauzy API deployed to https://ever-gauzy-api.fly.dev/api

Note: wait up to ~1 min for instance to power on for the first request due to inactivity timeout!

TODOs:

• when @superfly adds support for multiple volumes we need to fix issue with screenshots that did not save correctly in between app restarts (of course can be fixed also if we switch to another S3 compatible storage for screenshots and other blobs)

• put somewhere button "Deploy with Fly.io" and create a Wiki page that describes step by step how to do it (similar to https://github.com/triggerdotdev/fly.io readme)

• we provisioned the machine for PostgreSQL in Fly.io, but did not try to use it yet. That would be required if someone want to use fly.io for live hosting.