pleroma/otp: invite-only by default; fix tzdata write-permission crash loop

Default pleroma_signup_open to "false" and add pleroma_invites_enabled
"true" as a default (there was none before, every instance had to set it
explicitly). Two of three live instances were already overridden to
invite-only; open registration by default is what let haskell.social get
hit by spam/harassment in the first place.

Point tzdata's :data_dir at a writable, per-instance directory instead of
its own root-owned lib path. Without this, tzdata_release_updater crashes
every few seconds trying to write its update-poll marker file under
/opt/pleroma/lib, which the pleroma user can't write to.

1 files changed, 6 insertions, 0 deletions

diff --git a/pleroma/otp/templates/config.exs.j2 b/pleroma/otp/templates/config.exs.j2
index eb1be5b..6f09ec8 100644
--- a/pleroma/otp/templates/config.exs.j2
+++ b/pleroma/otp/templates/config.exs.j2
@@ -60,6 +60,12 @@ config :pleroma, :frontend_configurations,
   pleroma_fe: %{theme: "{{pleroma_fe_theme}}"}
 {% endif %}
 
+# /opt/pleroma/lib is root-owned, but the tzdata dep writes an update-poll
+# marker file under its own priv dir at runtime; pointing it at a writable,
+# per-instance dir avoids tzdata_release_updater crash-looping every few
+# seconds on "could not write to .../tzdata-<version>/priv/latest_remote_poll.txt".
+config :tzdata, :data_dir, "{{pleroma_data_dir}}/{{pleroma_instance}}/tzdata"
+
 config :logger,
   backends: [{ExSyslogger, :ex_syslogger}]