Using a cloud-init startup script for new VM / VPS deployments
-
Most of the founders of these hosts are active on Twitter too, worth some tweets @mentioning the platform and founders handles, they often respond.
-
@marcusquinn Ah darn, okay good to know. I ran some tests too and couldn't get it to work at all (almost as if the startup script didn't run), but have further testing I want to do.
I currently use LunaNode and made them aware of Cloudron a while back when I posted on supporting automatic LunaNode DNS via their API (and linked them to it as well).
I'll maybe reach out to them too after I've run some more tests on getting a startup script to work for their VMs to boot with installing Cloudron (and if I get one that works of course I'll share it here too).
-
@d19dotca We are already on DO and AWS market place. We are working with the linode guys at https://github.com/linode/Marketplace-Apps/pull/13. We are also in touch with upcloud. If you know folks at LunaNode, we will happily work with them to get a 1-click image or equivalent.
-
@girish I just looked at what you did for Linode on GitHub, and that may actually help as itβs a similar script to what I tried in my tests but not the same so Iβm maybe missing some of what you did there. Specifically referring to the cloudron-stackscript.sh file. Iβll try that out.
Thanks for sharing the GitHub link.
-
I recently signed-up to netcup (thinking of perhaps having my backups stored there instead of on Hetzner where my primary VPS is - although I also pay Hetzner for their native backup solution too for good measure, and occasionally run a snapshot as well) and I noticed that I could choose for Cloudron to be automatically installed, and so I did. But I've not actually even gone to the relevant url/ IP to complete the installation yet as not sure which url to use for it
(and just not got around to it).
Saying that, the UX of Hetzner is so much better than Netcup (they weirdly and confusingly make you pay 6 months up front even though you can cancel at any time and be refunded down to the hour) that I actually found the whole process of doing it manually on Hetzner easier!
-
FYI - I was able to get this to work with the following startup script which I borrowed from the Linode StartStack on GitHub.
#!/bin/bash set -eu wget https://cloudron.io/cloudron-setup chmod +x cloudron-setup ./cloudron-setup --provider generic
It worked after a while, I think before I just wasn't waiting long enough for it and was also looking in the wrong area for the logs of the startup script.
Happy this works now. I'll keep this in my repertoire to save some time if I ever need to spin-up a new Cloudron quickly.
-
@MooCloud_Matt Yes that's true too, but that wasn't what I wanted to achieve in this case.
I was specifically trying to teach myself how to use a cloud-init script / boot script, it was a learning project. Always trying to learn new things.