On Dec 22, 8:22 am, "Dmitrii 'Mamut' Dimandt" <[EMAIL PROTECTED]>
wrote:
> David King wrote:
> >> I don't know what the status is on ErlyWeb 0.7, but I would really
> >> really really love to see a config directory (a la Rails') where all
> >> the
> >> necessary site configuration could be placed (database connectivity,
> >> environment, production/testing/debug, routes - oh I'd love a routes
> >> configuration)
>
> > I've moved all of my configuration into a myapp.app file, and then I
> > start yaws in embedded mode with this information so that I don't need
> > a yaws.conf or any other configuration files. It simplifies starting
> > and changing configuration, and then everything is in one file.
>
> embedded mode might no be suitable for production environment
>
why not ? What if it was called "power mode" ? Unless you have just a
minimal setup or you like to hack yaws, you have to run in embedded
mode or how else do you run other OTP servers withing the same VM ?
> > As for routes, I know rails thinks that this is a configuration, but
> > it's not, it's business logic; it's deciding how your application will
> > behave. We already have a way to modify "routes" via
> > myapp_app_controller:hook/1. Maybe we need some syntactic sugar in
> > there, but otherwise I like it the way it is.
>
> Yes, I thought about hook/1. Syntactic sugar would've been great for
> specifying routes.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"erlyweb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
