> We have a init file that can be used for Hetzner instances. > > zotonic/cloud-init/zotonic-cloudinit.yml at master ยท zotonic/zotonic > <https://github.com/zotonic/zotonic/blob/master/cloud-init/zotonic-cloudinit.yml> > github.com > <https://github.com/zotonic/zotonic/blob/master/cloud-init/zotonic-cloudinit.yml> > [image: apple-touch-icon-180x180-a80b8e11abe2.png] > <https://github.com/zotonic/zotonic/blob/master/cloud-init/zotonic-cloudinit.yml> > <https://github.com/zotonic/zotonic/blob/master/cloud-init/zotonic-cloudinit.yml> > > TIL about cloud-init, looks interesting!
> We have still to update it for Ubuntu 22 - currently you can do an upgrade > after installation. > > What we often do is: > > - The above script > - Checkout the website repo on the correct branch into ~zotonic/ > - Symlink from ~zotonic/zotonic/apps_user/ to the website repo > - We also make sure that there is a local priv/zotonic_site.config or that > in priv/config.d/ there is a config with the local information. > - Just run Zotonic from ~zotonic/zotonic with "bin/zotonic start" > > You can also add this start command to the startup scripts of the server, > so that after reboot the site will start. > > As the site is now checked out from git, a deploy is just a click on the > update button in /admin/status > > We periodically just update zotonic from upstream, also with git pull. > Normally this can be done as a hot code upgrade, otherwise a quick stop, > pull, make, start will do the trick. > > The above is the lazy and low-tech approach. > Sounds right for our typical use case, as we don't have mission-critical websites. Thank you Carlo -- --- You received this message because you are subscribed to the Google Groups "Zotonic developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/zotonic-developers/CABVJJr-9J9Hk7xkNVtScaSu-Oqn_DrETd7%2BAa%2BXjS8MP6swFig%40mail.gmail.com.
