Slowly rolling-out automatic updates, but allowing manual updates immediately, seems a great idea to me.

@jdaviescoates I would love that too It has been awaiting review for a while You can go ahead and try it right now !

@christiaan There is absolutely no need to be on the official docker.io paid apps thing. It has to be a specific docker image for cloudron (see https://cloudron.io/documentation/custom-apps/tutorial/ )

As long as your re-touching the onboarding flow, I have a small suggestion : add a password.

More precisely, when the terminal tells you to go to the IP of your server on your browser, anyone who gets there before could basically take over the server, and could even reset the flow so you don't even notice. I know, the window of opportunity is small. It should basically be impossible as long as you go to the IP in question right then. But still...

A one-time password shown in the terminal, that the web interface would ask you for before allowing you to proceed with the setup would be pretty easy for the user, and would completely solve the issue.

(I must note that I have not gone through the setup and onboarding in a long time, what I am saying may be completely obsolete)

I'm actually working on it, in a package with a bunch of other stuff in the same app so it can actually be useful (Transmission to download stuff, SickChill to auto-download TV Shows, and a custom file manager). I'd love feedback if you want to check it out : https://git.cloudron.io/mehdi/river/

I'm the co-founder and CTO of a startup specialized in data encryption : https://seald.io if anyone's interested

@girish I have already done major work for jellyfin in my river app, like ldap integration & such. We should coordinate to avoid duplicate work

@JOduMonT Nop, the private registry thing is more when you build app yourself and do not want to push them to the public docker hub. Like a private proprietary custom app or something.

@will Yeah, it's a real pain .. I think the only way is to either upload them 1 by 1 trhough the web interface, or use SFTP or something ... That's exactly why I created River ( https://git.cloudron.io/mehdi/river/ )

Or use the cloudron CLI with the cloudron exec command !

@ultraviolet

On the desktop app side, I cannot find an option to connect its library to a remote server I don't think it's possible.

@ultraviolet take a look at https://cloudron.io/documentation/custom-apps/manifest/#capabilities

This mechanism is already used for some apps (at least OpenVPN, which also needs a capability for networking stuff). The MLOCK capability is currenlty not one of the possibilties, but it would be trivial to add to a future version of cloudron

@jdaviescoates After reading the arguments about why they recommend a bare-metal server ( on https://freeswitch.org/confluence/display/FREESWITCH/Performance+Testing+and+Configurations#PerformanceTestingandConfigurations-RecommendedConfigurations ), it seems to me that running it in cloudron (that means in a container) if cloudron itself is installed on a bare metal machine would be perfectly acceptable, as the kernel and its clock are shared between the host and containers.

@jdaviescoates said in Video/screencast tutorial suggestions:

although such videos existing would no doubt help with marketing - if only because it would show how easy it is

That's my thinking

@girish said in Video/screencast tutorial suggestions:

How to setup Cloudron on an internal/home network

It depends on who you want to target precisely with these videos, but I would suggest to start with the basic : how to install on a normal VPS / dedicated server, how to set up DNS for a few of the most popular providers ...

@nebulon Take a look at https://www.meilisearch.com/ . It looks very good ! Also https://blog.meilisearch.com/how-to-integrate-a-relevant-search-bar-to-your-documentation/

I think the point of this proposal could be attained more easily if the team was more aggressive about pushing "unstable" apps to the store.

I guess right now they are a bit careful about which ones they do publish, to avoid unnecessary support requests... I am not sure how to solve this issue

@JOduMonT Nop, the private registry thing is more when you build app yourself and do not want to push them to the public docker hub. Like a private proprietary custom app or something.

@scooke If there are really a lot of these lines in a very short time, maybe one of your apps is under DDoS attack ? Or someone is trying to brute-force a password ?

@JOduMonT It is possible, just configure cloudron certificate provider to Let'sEncrypt Wildcard.

(My 2 cents : switch providers. If they are this incompetent, it does not bode well..)