cloudron-setup has no documentation for "provider" options

[girish]

There is also a more elaborate tutorial style article here - https://www.digitalocean.com/community/tutorials/how-to-install-web-apps-using-cloudron-on-ubuntu-18-04

[FalconFour]

Woohoo! Yep, I set it up with the "generic" option. Almost immediately ran into an issue with the installer backgrounding a text-UI yes/no prompt that it never answered (so it hung), with the UI written into the log file hovering over the "no" box... but... after Ctrl+C'ing out of it and trying again, it worked.

Now I'm stuck trying to get cert set up. Let's Encrypt seems not to be responding... just hangs at "renewing certs" and visibly 1% on the progress bar forever. Hmm...

[girish]

OK, we got this sorted out

[jdaviescoates]

@girish said in cloudron-setup has no documentation for "provider" options:

Today, we don't use that flag at all but it's still there in case we need to put in some hacks

Does this mean (I think it does), given my Cloudron server appears to be running fine, that it makes zero difference that when installing on my Hetzner Cloud VPS I used generic instead of hetzner as the provider? (at the time I didn't realise Hetzner were in the list!)?

Or might there be some reason why I should delete and start again and next time specify that Hetzner is the provider?

[nebulon]

It does not make much difference for most cases, the provider flag is there to be able to do provider specific quirks and code paths, where applicable. We had more in the past though and at the moment it is not really used, but we keep it to be able to put some back if need be. As an example the backend to get the public IP address used to be provider specific as for example EC2 had its own way to determine that compared to DigitalOcean.

[scooke]

FWIW, https://cloudron.io/get.html does make it clear what the provider is:

Install Cloudron on your server

Create a fresh Ubuntu Bionic 18.04 x64 server and run these commands

wget https://cloudron.io/cloudron-setup
chmod +x ./cloudron-setup
./cloudron-setup --provider [digitalocean,ec2,generic,ovh,...]
A domain is required to install Cloudron.

I guess you could change the --provider option to --vps_provider to make it more clear. But it's pretty clear, especially for anyone who has already provisioned themselves a VPS, I would think. I'm just thinking that changing it will most likely end up with someone else not liking it, and then you change it, and then someone else.... TBH, do you really want to start replicating all the Digital Ocean tutorials here? That said, you all show incredible patience and a helpful attitude with all the questions that come your way. Good job!

[jdaviescoates]

@nebulon said in cloudron-setup has no documentation for "provider" options:

It does not make much difference for most cases

Thanks, I gathered that.

But what I'm asking about is my specific case, not the general case.

For someone like me, who has used Hetzner cloud to install their Cloudron server, is there any benefit or advantage to have used:

./cloudron-setup --provider hetzner

Instead of

./cloudron-setup --provider generic

I used that latter because at the time I didn't realise Hetzner was included in the list of potential providers. Does it matter/ make any difference?

Would there by any benefit to me starting again from scratch any using --provider hetzner instead? If so, I wouldn't mind doing that given you've made the process so simple. But if it doesn't make any difference I'll just leave things as they are.

Out of interest, where can I find the full list of providers?

Many thanks!

[nebulon]

As said, currently it does not make a difference, but it might in the future. Instead of reinstalling, you can just adjust the value stored in the database by running the following on your server:

mysql -uroot -ppassword box -e "UPDATE settings SET value='{\"provider\":\"hetzner\"}' WHERE name='sysinfo_config'"

Please note that adjusting database values like this is highly dangerous, as there is no value validation happening, so don't attempt to change anything else If we hit common use-cases to change values, we will add a UI to change it in the dashboard.

[jdaviescoates]

@nebulon said in cloudron-setup has no documentation for "provider" options:

currently it does not make a difference

@nebulon said in cloudron-setup has no documentation for "provider" options:

you can just adjust the value stored in the database by running the following on your server:
mysql -uroot -ppassword box -e "UPDATE settings SET value='{"provider":"hetzner"}' WHERE name='sysinfo_config'"

OK great, thanks.

[thetomester13]

Reviving this old thread - sorry!

I just reran the ./cloudron-setup script (both with and without a provider argument). In both cases, at the end of the install, it does still wait for user input in order to reboot the server and boot up Cloudron properly. Which, if one were trying to automate this entire process ( ... : -) makes it quite difficult. Could there be a way to pass an argument where the install script automatically reboots the server at the end of the install without waiting for the user's input?

[fbartels]

@thetomester13 have a look at https://forum.cloudron.io/topic/5236/request-a-cli-flag-to-skip-the-reboot-y-n-question-on-cloudron-installation/7

[thetomester13]

@fbartels yep, that's what I was looking for! My search queries fail me again. Thanks

[girish]

@thetomester13 said in cloudron-setup has no documentation for "provider" options:

I just reran the ./cloudron-setup script (both with and without a provider argument)

The provider argument is not used anymore. The original intent was to have some VPS specific setup if needed during installation and upgrades but we have never needed to use it,

[thetomester13]

@girish got it. Just wanted to make sure I try a few things before I pinged the forum

[martin]

@thetomester13 I came across this question after recently installing on Oracle Cloud, and thought I ought to put something in for the argument. I put in "OCI", saw it had been written to a file somewhere, but apart from that it all just worked so I forgot about it!