Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • W Weather
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • Metrics
  • Weather
  • Issues
  • #11086
Closed
Open
Created Feb 27, 2014 by Trac@tracbot

handling different settings

For testing Weather locally, a few changes need to made to the django-settings for it to behave well. There seems to two ways of handling multiple settings (development, testing and production)1 and they are described below:

  1. Settings module -> This helps in clearly separating different settings for differed phases of development but it seems like a overkill for Weather. Moreover, Karsten suggested that changes made here should affect current Weather when its deployed.

  2. Create a local-setting file -> the file will house all the custom settings for testing, but it won't be version controlled.

Let me know what you guys think.

Trac:
Username: feverDream

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking