Switch from Cloudflare Pages to DigitalOcean on monorepo / next.js apps

DaviPtrs commented 1 month ago

2 scenarios:

Use the digital ocean build environment like shown below (only if it's not fucked up like on Cloudflare Pages) https://docs.digitalocean.com/products/app-platform/how-to/deploy-from-monorepo/ https://github.com/digitalocean/sample-monorepo https://docs.digitalocean.com/products/app-platform/reference/buildpacks/nodejs/ https://www.youtube.com/watch?v=PmFtK01G_A8
Use our own build environment (with cicd pipelining) For that option I'm considering Drone CI, because it's open source and it has support for adding features as a extension. Github Actions is absolutely awful for conditional path pipelines and Circle CI is better but far beyond being good. https://www.drone.io/ https://www.youtube.com/watch?v=-VfJq2UKYCE https://github.com/meltwater/drone-convert-pathschanged

TODO list from the old task:

[x] Update package maneger to pnpm, PR with new code: https://github.com/agicommies/commune-ts/pull/26
[x] Build optimizations for single projects builds
[ ] Cashing
[x] PostgresSQL Database
[x] Make CI / lint, format and typecheck work on PRs (.github allready set on repo)

DaviPtrs commented 1 month ago

For now we're using the built in build environment but already found a bug

The build environment often "loses" the next binary

The current workaround is to force rebuild while clearing the build cache

DaviPtrs commented 1 month ago

Summary

We are using Drone CI for most deployments, while others are still being built in the Digital Ocean build environment. All deployments handled by Drone CI are being built as Docker images and then the Digital Ocean app is pointing to the branch Docker tag (main for production and dev for development).