Hi Sergio,<br><br>you might want to have a look at this:<br><a href="http://www.experiencedwebprogramming.com/2008/11/11/monticello-update-within-a-live-environment/">http://www.experiencedwebprogramming.com/2008/11/11/monticello-update-within-a-live-environment/</a><br>
<br>It describes how to update your code from within your webapp. So it won't be necessary to have visual access to your image.<br><br>Maybe it helps a bit.<br>The post is not based on the newest application build by Lukas called Gopher. Using Gopher would let the code look a little more easy. But I guess you can get the point.<br>
<br>See comments further below.<br><br><div class="gmail_quote">2010/2/23 sergio_101 <span dir="ltr"><<a href="mailto:sergiolist@village-buzz.com">sergiolist@village-buzz.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
currently, my workflow for a project in development goes something like this..<br>
<br>
developers work on the app / design in their editors on development<br>
versions of the app.. running on their machines..<br>
<br>
as changes are made, they commit their changes to the repository..<br>
<br>
they then deploy them via capistrano to the live server..<br>
<br>
the server restarts with the new changes..<br>
<br>
this continues until the project is deployed for real..<br>
<br>
once this happens.. work is pretty much the same, with each person<br>
running a database of their own for testing and the production<br>
database doing its thing..<br>
<br>
my question is.. will we be working the same way with seaside?<br>
<br>
when you make changes and upload everything via monticello, can you<br>
just attach to your production image and have it pull all new changes?<br>
<br>
how are conflicts settled?<br>
<br>
is the live data subject to any weirdness?<br></blockquote><div><br>When there is any conflict you have to make sure to solve it before you update your live/production/whatever image. But remember you have two options of updating your code: On the one hand you can do a simple "update" simply speaking: it adds the new code to the exisiting one. Or you load the latest Monticello-File which updates the whole code and no conflicts should happen then.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
ie.. if we have a 'person' class, and we add 'address2' to the person<br>
class.. are the previous 'person'-s still okay?<br></blockquote><div><br>Thing is: You should handle the the situation when the value of address2 is not set at older Persons. But if it is only about changing the attributes I don't see any problem at all. Happens to me all the time :)<br>
In those cases I prefer working with late bindings e.g. When you take a look at the accessor of "address2" you could do something like <br><br>^address ifNil: [address2 := 'Default address']<br>That ensures that every created object of Person can access and work with the new attribute regardless if it was nil or not.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
thanks!<br>
<br>
--<br>
<br>
----<br>
peace,<br>
sergio<br>
photographer, journalist, visionary<br>
<br>
<a href="http://www.coffee-black.com" target="_blank">http://www.coffee-black.com</a><br>
<a href="http://www.painlessfrugality.com" target="_blank">http://www.painlessfrugality.com</a><br>
<a href="http://www.twitter.com/sergio_101" target="_blank">http://www.twitter.com/sergio_101</a><br>
<a href="http://www.facebook.com/sergio101" target="_blank">http://www.facebook.com/sergio101</a><br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</blockquote></div><br>Hth,<br>Peter<br clear="all"><br>-- <br><a href="http://www.peter-osburg.de">www.peter-osburg.de</a><br><a href="http://www.experiencedwebprogramming.com">www.experiencedwebprogramming.com</a><br><a href="http://www.mix-rss.com">www.mix-rss.com</a><br>