Cloudron Forum

For what it's worth, the terms of service have been updated. Not that it matters. As with everything on the internet, it's buyer beware and use at your own risk. For my part I'm comfortable with the underlying protocol and the role Bluesky (a public-benefit company) is playing in developing it and the reference implementations for it.

They have released a PDS (docker image) that will federate with their sandbox network. Federation with the production network will come after a period of time.

https://github.com/bluesky-social/pds

Federation still depends on three services hosted by Bluesky. Eventually it should be possible to consume these ATProto services from other providers, but for now Bluesky is the only one offering them.

SMTP-Mailer is configured automatically and working for me when I send the test email. However, a number of Contact Form plugins that were advertised as working with SMTP-Mailer weren't actually sending an email. Some failed silently, and some helpfully showed an error to the user.

I did finally find one. Completely free. I'm not connected to them in any way. Just leaving this here in case anyone else runs into the same problem.

https://wordpress.org/plugins/simple-basic-contact-form/

@sfeldkamp

Well, I tried the digital oceans ones and they didn't work either. Maybe I will have to create a new server and restore backups instead.

https://docs.cloudron.io/guides/upgrade-ubuntu-18/

https://www.digitalocean.com/community/tutorials/how-to-upgrade-to-ubuntu-18-04

These are different. Which should I follow? I've tried the cloudron guide a couple of times with no luck. Is it safe to upgrade following the digitalocean guide (I am hosted on digital ocean).

@girish

oh, man. My bad for not reading the docs on that one. Thanks for the help.

@nebulon said in Gitea - Package Updates:

Full changelog

https://github.com/go-gitea/gitea/pull/13058

This change in 1.13.0 broke my repo by causing my existing git hook to fail. Git Hooks tab is now hidden by default.
I can't successfully push to origin because the hook fails.

I updated run/gitea/app.ini manually to restore it by adding

[custom]
DISABLE_GIT_HOOKS = false

However, this is not durable for a restart. I was depending on the Git Hooks feature of Gitea to push to mirror my repository to the GitHub Pages app repo to publish it.

Is it possible to default this value to true instead in the app? Or otherwise provide a way to toggle it that will be durable across versions and installs?