Environments
Reported by Matt Todd | April 30th, 2008 @ 12:25 AM | in Release 0.6.0
Provide for (slightly) different behaviors depending on environments, like where to put logs, which database to use (undecided as Halcyon is ORM-agnostic and has very little specific DB code, though it couldn't hurt), whether to provide automatic class reloading, etc.
Comments and changes to this ticket
-
Matt Todd May 12th, 2008 @ 05:37 AM
- State changed from “new” to “resolved”
(from [08cf8650bf861533a37cd30a074191df2314b74b]) Added Halcyon.environment configurable attribute, including tests. Defaults to the development environment. Also updated app init templates to include configuration and initialization, along with documentation. [#35 state:resolved]
-
Matt Todd May 12th, 2008 @ 05:41 AM
Need to address when the environment is set manually and is interpreted as a string by the YAML load process because the environment should always be a symbol. (Ummm, that sounds like a spec that would fail in that case.)
This should be addressed by the greater flexibility of the planned
Halcyon::Configclass. This is still a problem and probably deserves its own ticket.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Matt Todd