Different Profiles for development and production

> Seaside has configurations that can be used to change application
>  settings quickly.
>
>   http://www.shaffer-consulting.com/david/Seaside/Configurations/index.html
>
>  A question to Seaside Configuration users: Would it make sense to make
>  configurations more powerful, so that they can be defined in
>  dispatchers to affect multiple applications (in other words so that
>  they are inherited along the dispatcher tree)?
>
>  Lukas
>
>  --
>  Lukas Renggli
>  http://www.lukas-renggli.ch
>
>
> _______________________________________________
>  seaside mailing list
>  [hidden email]
>  http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

>
> I've made squeak to read a simple text file in the image path
> with some configs.
> Is just reading text that when compiled instantiates a
> dictionary with the
> (basic) values I configure from there. So I just clone the
> image and start it there with it's own values.
>
> Cheers,
>
> Sebastian
> PD:  Welcome to the seaside. Refresh your mind !

>>
>
> I kind of do the same thing, I keep all my config data on the file  
> system in
> text files and use my own config system rather than Seaside's.  I  
> don't like
> keeping config info in the image, it's too much of a hassle.  I keep  
> three
> profiles, dev, prod, test, with a file in the root that determines  
> which
> profile is used (easily toggled).  Inside the directory for a  
> profile, each
> setting is stored in a separate file where the filename is the  
> setting name
> and the file contents are the value.

> >>
> >
> > I kind of do the same thing, I keep all my config data on the file
> > system in text files and use my own config system rather than
> > Seaside's.  I don't like keeping config info in the image, it's too
> > much of a hassle.  I keep three profiles, dev, prod, test,
> with a file
> > in the root that determines which profile is used (easily
> toggled).  
> > Inside the directory for a profile, each setting is stored in a
> > separate file where the filename is the setting name and the file
> > contents are the value.
>
>
> ... And I'm just the other way ;-)
>
> I create configuration classes and then I zip up the folder
> with the images and send them to my designers... they know
> how to use the web interface to make changes that are needed
> for db access or resource pathing, and don't have to look for files.
>
>
> - Brian

> -----Mensaje original-----
> De: [hidden email]
> [mailto:[hidden email]] En nombre
> de Ramon Leon
> Enviado el: Viernes, 29 de Febrero de 2008 11:14
> Para: 'Seaside - general discussion'
> Asunto: RE: [Seaside] Different Profiles for development and
> production
>
> > >>
> > >
> > > I kind of do the same thing, I keep all my config data on
> the file
> > > system in text files and use my own config system rather than
> > > Seaside's.  I don't like keeping config info in the
> image, it's too
> > > much of a hassle.  I keep three profiles, dev, prod, test,
> > with a file
> > > in the root that determines which profile is used (easily
> > toggled).  
> > > Inside the directory for a profile, each setting is stored in a
> > > separate file where the filename is the setting name and the file
> > > contents are the value.
> >
> >
> > ... And I'm just the other way ;-)
> >
> > I create configuration classes and then I zip up the folder
> > with the images and send them to my designers... they know
> > how to use the web interface to make changes that are needed
> > for db access or resource pathing, and don't have to look for files.
> >
> >
> > - Brian
>
> OK, but how do you easily move configs between images?  
> What's nice about
> files of course is it makes it much easier to share configs
> between images
> and/or edit config from a shell, which matters to me since I manage my
> production servers via ssh.  I think Unix/Linux proved long
> ago that plain
> text configuration files worked better than custom binary
> formats (like
> Windows) and since switching to Linux, I've come to
> appreciate that approach
> much much more.
>
> Ramon Leon
> http://onsmalltalk.com
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside