Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-1849

Improve configurations infrastructure

        Details

        • Type: Improvement
        • Status: Closed (View Workflow)
        • Priority: Major
        • Resolution: Done
        • Affects Version/s: None
        • Fix Version/s: None
        • Labels:
        • Story Points:
          0.25
        • Epic Link:
        • Sprint:
          Summer 2019 Sprint 9, Summer 2019 Sprint 10, Summer 2019 Sprint 11, Summer 2019 Sprint 12

          Description

          Make settings.py more flexible to support dev, test, and prod environments.

            Attachments

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              ann.loraine Ann Loraine added a comment -

              Make django log location configurable.

              Show
              ann.loraine Ann Loraine added a comment - Make django log location configurable.
              Hide
              Permalink
              ann.loraine Ann Loraine added a comment -

              https://bitbucket.org/aloraine/appstore/branch/IGBF-1849-LogConfig#diff

              Show
              ann.loraine Ann Loraine added a comment - https://bitbucket.org/aloraine/appstore/branch/IGBF-1849-LogConfig#diff
              Hide
              Permalink
              ann.loraine Ann Loraine added a comment - - edited

              Goal: Enable setting Django log file name and path in settings.ini rather than always writing to debug.log in the django directory, as done previously.

              On deployment:

              • Write Django log file to the same location as the web server logs because this is probably where a deployer would naturally look for application logs. In our current Ubuntu setup, this is /var/log/apache2.
              • The Django log file should be saved to a location that is writable by user:group www-data:www-data. This saves an extra step of making this file writable by this user.

              To test:

              • Check that the file is getting written in the expected place.
              • Check that Django fails to start if the log file cannot be written in the designated place.
              • Check what happens when DEBUG setting is True or False.
              Show
              ann.loraine Ann Loraine added a comment - - edited Goal: Enable setting Django log file name and path in settings.ini rather than always writing to debug.log in the django directory, as done previously. On deployment: Write Django log file to the same location as the web server logs because this is probably where a deployer would naturally look for application logs. In our current Ubuntu setup, this is /var/log/apache2. The Django log file should be saved to a location that is writable by user:group www-data:www-data. This saves an extra step of making this file writable by this user. To test: Check that the file is getting written in the expected place. Check that Django fails to start if the log file cannot be written in the designated place. Check what happens when DEBUG setting is True or False.

                People

                • Assignee:
                  ann.loraine Ann Loraine
                  Reporter:
                  ann.loraine Ann Loraine
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: