Better to be more verbose. Some pain-points I had when setting-up linksight
[ ] Setting-up postgresql with the proper role without accepting passwords is a bit difficult. I suggest to have a standard, recommended way of doing this (create a new user role, creating a database for linksight, granting privileges to said role, and updating the config file to trust)
[ ] Update keys in the template .env file. The master codebase looks for GOOGLE_OAUTH2_KEY, but the template environment file has SOCIAL_AUTH_GOOGLE_OAUTH2_KEY. I wouldn't have found out that this is a problem if I didn't check the logs in flower-error.log. There were also some missing keys not provided in our template (FLOWER_OAUTH2_REDIRECT_URI)
[ ] Add a FAQ section for setting-up linksight. Things to ensure in their local configurations, possible questions and solutions.
Better to be more verbose. Some pain-points I had when setting-up linksight
trust).envfile. Themastercodebase looks forGOOGLE_OAUTH2_KEY, but the template environment file hasSOCIAL_AUTH_GOOGLE_OAUTH2_KEY. I wouldn't have found out that this is a problem if I didn't check the logs inflower-error.log. There were also some missing keys not provided in our template (FLOWER_OAUTH2_REDIRECT_URI)