Namespace VS App Platform
complete
Mohammad Rafivulla
Need some documentation describing the differences between namespaces and app platform in the view of "Functions" service (implying the service not the literal word). I just started with serverless and It has become really confusing to develop DO's functions. I think the confusion arised because the CLI creates a namespace to deploy functions, whereas there should be a way to deploy to app platform without pushing every small thing to GitHub.
While this was okay but now when I'm in need of adding a BUILD ONLY env var, I can do it easily on the App Platform, but I can't seem to do it on Namespaces. It just strengthens my confusion between Namespace and App platform
Brian Boucheron
complete
Brian Boucheron
Thanks for the feedback about our Functions and App Platform docs. You've identified an area that is definitely tricky to explain.
- Here are our docs on deploying Functions projects to App Platform:
The only way to do this is through a repository. This can be set up using
doctl
(https://docs.digitalocean.com/products/app-platform/how-to/manage-functions/) but yes, it's not the same deploy process as doctl serverless ...
commands.- Without using App Platform, Functions does not support build-only environment variables. The build process for Functions is detailed here:
- You mention that "there should be a way to deploy to app platform without pushing every small thing to GitHub". One workflow that folks have found productive is to use the Functions product and doctl serverless ...CLI workflow when developing and prototyping, and then committing and pushing finalized changes to a repo for App Platform deploy.