You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the docs here, we suggest rebuilding nginx. But @lognaturel says that with .2, nginx will just need to be restarted: "The logic to put the certs in the right place and everything is in the command that’s run at container start time." In general: "settings changes should not require rebuilds."
@lognaturel: "I think we’ll want to document for folks who use their own infrastructure that we now publish images."
If provider has a region concept, use a region-agnostic URL, the region will be requested
Must use an HTTPS URL
No rebuild needed when changing config, just stop and restart
If using a custom database, might have to add pgrowlocks extension manually
Audit log events only if there were blobs to process, otherwise nothing; use the CLI to check if it can run; there should be a log event for each day during which files were uploaded
In the docs here, we suggest rebuildingIn general: "settings changes should not require rebuilds."nginx
. But @lognaturel says that with .2,nginx
will just need to be restarted: "The logic to put the certs in the right place and everything is in the command that’s run at container start time."The text was updated successfully, but these errors were encountered: