Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Environments

#35

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.

Reported by Matt Todd · April 30th, 2008 @ 12:25 AM

State: resolved
Milestone: Release 0.6.0
Assigned to: Matt Todd Matt Todd

Activity

  1. Matt Todd
    Matt Todd
    • 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]

    http://github.com/mtodd/halcyon/...

    May 12th, 2008 @ 05:37 AM

  2. Matt Todd
    Matt Todd

    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::Config class. This is still a problem and probably deserves its own ticket.

    May 12th, 2008 @ 05:41 AM

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.