[Seaside] Seaside application deployment/migration/update
tulipe.moutarde at gmail.com
Tue May 3 19:46:02 UTC 2011
I'm about to release my first real world Seaside app but I'm a bit
How do you update your code and deal with model changes ?
My first guess would be "upload an mcz file in a folder and load it from
the image (on a regular basis or by manually triggering an action in the
admin section of my web application)."
Do you have any other way to do it ? How do handle big changes in your
models ? Do you use some sort of migration ?
An other problem for me is how do you deal with multiple environments ?
I'm used to have a development, a staging and a production environment.
In dev for example, I want to use S3 in staging and prod but not in dev.
Is there any convention/approach in this field ?
I use migrations, Vlad the deployer and Rails.env everyday in ruby/rails
and I wonder how to tackle them in Smalltalk/Seaside...
More information about the seaside