This sounds okay ... I'd be inclined to have you also include a sandbox or QA stone in your setup, that is either a copy of the production db, or a db filled with test data, that you would use to validate your update process/code before each release to production ... better safe debugging in a sandbox, than sorry debugging in a production db:)
I have another project coming up, and I have free reign over the tech stack. I am gonna use Pharo, but I'd like to spend my up front time on this project figuring out the things I usually wait until the end to do. One of these issues is setting up gemstones.
I would like to use GsDevKit_home, but I want to make sure that the use case I am envisioning is in keeping what this package is set up to do.
My vision is something like:- Deploy a stone to remote production server.- Develop in the latest version of Pharo on my local machine, keeping my project in git.- When it's time to deploy, ��use tODE client to tell the production server to grab the latest code, and we're done.
Does this sound reasonable?
Also, one thing that I find invaluable in troubleshooting applications written using relational databases is to be able to be able to just dump the production database and load it up on my local machine. Is this possible using gemstones?
Good you are thinking along the same lines ... You can take a
snapshot of an extent in a running stone using the tODE command
`bu snapshot` (run `man bu` in a tODE shell ) for more details,
then using the GsDevKit_home bash script, $GS_HOME/bin/newExtent (
`$GS_HOME/bin/newExtent -h` for more details) you can install the
snapshot from production into a local sandbox stone ...
For future questions about GsDevKit_home and GemSTone, please the
GLASS mailing list[1][2]. There are a number of folks in the wild
that are using the develop in Pharo, deploy in GemStone model so
you'll benefit from having those folks weigh in with their
approaches as well, without cluttering the Pharo newsgroup with
GemStone information. Also there are few more GemTalk employees
that monitor the GLASS list and can weigh in with their knowledge
as well :)
Dale
Thanks!
----
peace,
sergio
photographer, journalist, visionary
Public Key:��http://bit.ly/29z9fG0
#BitMessage��BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
http://www.codeandmusic.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101