> 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.
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.
It could look like (with the understanding that this my not be
syntactically correct):
Ewc=do_ewc(A,fun(A1,[posts | Rest]) ->
{ewc,posts,index,[A,Rest]};
(A1,[users | Rest]) ->
{ewc,users,show,[A,Rest]};
(A1, [some_complicated_url | Rest]) ->
do_lots_of_processing(Rest);
(A1,[page,Page]) ->
{page,Page};
(A1,Other) ->
get_initial_ewc(A1)
end).
This would be pretty easy to write.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
