[DevOps] Make it possible to deploy to DigitalOcean App Platform and Droplets

[evereq]

Droplets

• https://docs.servicestack.net/do-github-action-mix-deployment
• https://gist.github.com/danieltorscho/c104c23e97c840f09fd9a186ec092b28
• https://www.digitalocean.com/community/questions/how-to-deploy-using-github-action
• https://github.com/digitalocean/sample-nodejs
• https://github.com/digitalocean/droplet-1-clicks
• https://medium.com/nerd-for-tech/deploy-your-nodejs-application-to-a-digital-ocean-droplet-step-by-step-guide-3f6f928f776

DigitalOcean App Platform

• https://github.com/marketplace/actions/digitalocean-app-platform-deployment
• https://github.com/digitalocean/sample-golang-docr-github-action
• https://docs.digitalocean.com/products/app-platform/getting-started/sample-apps/docker and https://github.com/digitalocean/sample-dockerfile

[evereq]

https://github.com/ever-co/ever-gauzy/pull/7591

[evereq]

Setup on Droplets

1. Create 3 separate Droplets for each env, e.g. ever-do-demo, ever-do-stage, and ever-do-prod. Make sure each Droplet is at least 2GB RAM.
2. Set GitHub Secrets DO_DROPLET_DEMO_HOST, DO_DROPLET_STAGE_HOST and DO_DROPLET_PROD_HOST to values of IPs of your relevant Droplets
3. Add Droplet names to Trusted sources for Redis and PostgreSQL DB
4. Define GitHub Secrets DO_DROPLET_USERNAME (default value in DO is root) and DO_DROPLET_KEY (use SSH Private key that used when you added public SSH Key to DO)

[evereq]

Setup on the DigitalOcean App Platform

1. Make sure GitHub Secret DIGITALOCEAN_ACCESS_TOKEN is set to your DigitalOcean access token that has enough privileges to create/update DigitalOcean App Platform applications.
2. Our existing GitHub actions are used to create 3 separate "Apps" in DigitalOcean, one for each environment, e.g. ever-gauzy-demo, ever-gauzy-stage and ever-gauzy-prod
3. Check .github/workflows/deploy-do-app-platform-demo.yml, .github/workflows/deploy-do-app-platform-stage.yml and .github/workflows/deploy-do-app-platform-prod.yml
4. Each GitHub action creates or updates a separate DO App and assigns a custom Domain name to each env (see APP_DOMAIN env var)
5. You can define the type of instance (size) in the INSTANCE_SIZE env var (see possible values in the following link) and count in the INSTANCE_COUNT env var. We recommend using 1 instance in the demo env and at least 2 instances in the stage env. Make sure you are using a professional instance size and at least 2 instances for prod environment.
6. Important to make sure DEMO env var is set to false for prod environment. We also recommend to set ADMIN_PASSWORD_RESET to false for production.
7. As with any other setup of our platform, make sure API_BASE_URL is set to the URL on which you would like to have API exposed and CLIENT_BASE_URL should be set to the URL on which you will have client-side UI loaded.
8. You can also research .do/app.yaml file that is used as a template to define the DO App Platform application. Important to note that you will have to configure services/image/registry_type ,services/image/registry, and services/image/repository to use your own DigitalOcean or DockerHub Container Registry, please refer to DO documentation about those parameters.

[evereq]

Added Wiki https://github.com/ever-co/ever-gauzy/wiki/Gauzy-Self%E2%80%90Hosted-Setup-in-DigitalOcean