Process of getting into the AppStore
-
Whats the process of bringing applications into the App Store for third party developers?
@philkunz Check out the Tutorial -> https://docs.cloudron.io/packaging/tutorial/
-
As above :
- package them
- add entry in App Wishlist describing what and why it's great
- share a github/lab repo for review of code
- if @staff think it addresses a need and is capable of maintenance and support as an app store app, they will get back to you
Many app store apps started as custom apps, got reviewed, then accepted/adopted
-
What @timconsidine said is correct. Currently, the app library is like a curated selection of apps we are able to maintain updates for. Given that in our experience most support issues from users are app related and not actually Cloudron platform related (things we develop), we are a bit conservative adding new packages, since in the end we have to jump in and fixup broken instances. This in fact is where we have to spend most of our support time.
-
G girish moved this topic from Support on
-
@nebulon I get that. For about 150 Euro a year you can't really have someone working on individual instances. What I kinda would like to see is Cloudron being able to subscribe to alternative app catalogues, that have the same update mechanics as the current Cloudron apps. With Custom apps, the problem is scaling solutions. Say we have customers we would like to deploy a Cloudron instance for, and then deploy our apps in addition to Cloudron maintained apps. I basically have to setup the clients firewall to allow our CI to push an update to the cloudron instance within the client's network. On top, it is hard to give control to maybe clientside IT admins in terms of delaying updates etc. What would be nice, if there was a private registry option that would allow for cloudron side triggered updates. It would also be fine if it was a paid for cloudron.io hosted option, a little bit like a managed Digital Ocean image registry, that can be subscribed to by Cloudron users, with a clear message that there is 0 support by the cloudron team, but only support by the maintainer of the custom registry...
-
What is the app you've packaged @philkunz ?
Despite what's already been said, so far I don't think I've ever seen @girish or @nebulon say "sorry, we're not going to add this app to the app store" apart from when it is an app that is clearly no longer maintained upstream.
Generally, if someone does the work to package an app for Cloudron, they'll add it to the app store.
-
@nebulon I get that. For about 150 Euro a year you can't really have someone working on individual instances. What I kinda would like to see is Cloudron being able to subscribe to alternative app catalogues, that have the same update mechanics as the current Cloudron apps. With Custom apps, the problem is scaling solutions. Say we have customers we would like to deploy a Cloudron instance for, and then deploy our apps in addition to Cloudron maintained apps. I basically have to setup the clients firewall to allow our CI to push an update to the cloudron instance within the client's network. On top, it is hard to give control to maybe clientside IT admins in terms of delaying updates etc. What would be nice, if there was a private registry option that would allow for cloudron side triggered updates. It would also be fine if it was a paid for cloudron.io hosted option, a little bit like a managed Digital Ocean image registry, that can be subscribed to by Cloudron users, with a clear message that there is 0 support by the cloudron team, but only support by the maintainer of the custom registry...
