[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #11086 [Tor Weather]: handing different settings
#11086: handing different settings
---------------------------------------+---------------------
Reporter: feverDream | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Tor Weather | Version:
Keywords: weather-rewrite, settings | Actual Points:
Parent ID: | Points:
---------------------------------------+---------------------
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. [[BR]]
2. Create a local-setting file -> the file will house all the custom
settings for testing, but it won't be [[BR]]version controlled.
Let me know what you guys think.
[1]: !http://www.rdegges.com/the-perfect-django-settings-file/
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11086>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs