PSA - env file now requires both a Terms and Privacy URL to be set
I've fought hard the last few days to get my deploy up and running. Eventually I figured out that I needed to explicitly set TERMS_URL and PRIVACY_URL or loomio would not proceed past the account creation.
James Kiesel Mon 18 Jun 2018 8:06PM
Hmmm in my opinion we shouldn't be requiring those things for the app to function, since if you're hosting a private-to-LAN instance, or maybe something that isn't going to touch the EU, you don't actually need those things.
It strikes me that it's a sensible default to have them populated to something though (all things considered we'd rather you host Loomio with a privacy policy than not), but using ours probably isn't the right sensible default, since our privacy policy will be different from the one for a private host. (for example, our policy says 'Loomio team members may access your email address', which is false and misleading for a private host)
I think I'm leaning towards 'the app works without it, but it shows a warning to site admins to populate it if it's not there'
Robert Guthrie Mon 18 Jun 2018 8:26PM
This is a bug, it was my intention that these are not required. Thanks for raising this, I'll look into it.
Steve Couch Mon 18 Jun 2018 9:23PM
Yeah, didn't think it was intended, but very glad to help out.
Robert Guthrie Wed 20 Jun 2018 4:26PM
Ok this is fixed in master and stable now. (latest docker images are building as a type) Thanks for letting me know.
Steve Couch · Mon 18 Jun 2018 8:04PM
All you need to do is add this to the bottom of your env file:
TERMS_URL="https://www.loomio.org/terms_of_use"
PRIVACY_URL="https://www.loomio.org/privacy"
I think the GDPR reorganizing caused some issues. Coffeescript's implicit returns meant that without those two variables set, loomio would not proceed with processing a new user (maybe this was the intention!).