Closed Rutvikrj26 closed 5 months ago
This belongs together with the "ENABLE_FILE_DOWNLOADS_OPTION" setting. Put it there, not at the end of the file.
Please try to explain what these settings are for, say something like "The following settings determine the options that can be selected for a newly-submitted project, on the 'Project Access' page. These settings do not affect existing published projects."
The default (in .env.example) must be to enable all access policies, so that we can test them.
Always end text files with a line feed character.
Thankyou for your comments @bemoody!
I have implemented the changes suggested by you.
- This belongs together with the "ENABLE_FILE_DOWNLOADS_OPTION" setting. Put it there, not at the end of the file.
Can you please expand on this a bit - why it belongs there. I could not directly see a pattern in the example env file that would suggest this.
Thanks!
Thanks Rutvik, looks good to me.
Can you please expand on this a bit - why it belongs there. I could not directly see a pattern in the example env file that would suggest this.
I think this is a fair question. If we have expectations for structure, we should outline them somewhere (e.g. perhaps in a comment at the top of the file).
This PR is a followup to #2204 where the access policies are getting restricted. This adds the configuration setting to the .env.example with usage instructions and it's effects on the platform.