I think there is a good use case for exposing a custom URL mapping via Nginx that doesn't necessarily go to a container on the local system.
This has use cases for a single (sub)domain providing proxy and load balancing services, as well as cluster management down the road.
As of now, the default nginx.conf loads all .conf files from applications/ directory.
Unless there is anything in the code that wipes out all conf files instead of only individual ones, adding a custom on there for a custom use case won't cause problems for other apps and won't be overwritten on upgrades.
If you want to feel safer, keep the custom .conf elsewhere and use a symlink from the applications/ directory.
@d19dotca I guess that depends exactly on what you want to use the cloudron cli for. A workflow could look like the following:
change/update version of a package in the app
commit the change to git (you could edit and commit directly in e.g. gitea or gitlab)
this automatically triggers the ci platform
this one could do some verification
create the updated docker image
deploy it to your cloudron
The simples form of this could be a post-commit hook in your git hosting tool.
Just got some basic tests up and running for Homepage! You can find the repo here. It packages version 0.9.6 of homepage-cloudron. I hope to soon add a background color option to the config as well for the more minimalist crowd.
@girish what do you think the chances are of publishing this on the store?
Not to mention that if your software is closed source you do not need to publish it for all cloudron users if only you want to use it. With a bit of technical knowledge you can build apps yourself (see the link from @mehdi), push it to a private registry and then use the cloudron cli to install it yo your instance.
I am actually hosting a few apps on my Cloudron that I am just building locally (Bitwarden for example before it was available as an official app).
If you don't make your app official you are of course on the hook for maintaining it, but you still benefit from the user management of Cloudron, automatic ssl and backups/easy restore.
Learn docker. This is the base deployment tool for Cloudron. No need to learn compose/swarm etc.
Take some time to learn Heroku. Also see 12 factor app. A lot of ideas for Cloudron app deployment are inspired from these two PaaS concepts. Heroku can deploy lots of different frameworks/stacks, so just pick one you are comfortable with.
And then the tutorial link above should be easy to follow. Without knowing 1 & 2, the tutorial can be hard to understand.