Re: [Oship] [288] OKAY! I really can't seem to make oship/etc be ignored
on 3-2-2009 22:07 svn@openehr.org wrote:
Revision: 288 Author: tim.cook Date: 2009-02-03 21:07:37 +0000 (Tue, 03 Feb 2009) Log Message: ----------- OKAY! I really can't seem to make oship/etc be ignored in SVN. We'll just have to tell people to delete the directory after checking out the code and before running 'grokproject oship'. Grrrrr totally unprofessional but I can't seem to manage it tonight.
Huh? When I checked out revision 276 earlier tonight, I had no /etc. /etc was only created after the command 'grokproject oship'.
With the instructions you gave before, I had OSHIP installed (also needed to answer a question about replacing startup.py, which I answered 'y').
Nevertheless, I don't like the installation procedure like this. There are too many steps involved, where things can break. Especially the final staps when the server has started (create a Grok application called 'Oship', mind the capital, click on it, etc.)
We need something like virtualenv --no-site-packages oshipenv cd oshipenv source bin/activate (oshipenv)easy_install oshipproject (oshipenv)oshipproject oshipdemo ...answer the questions about the admin-account and its password (oshipenv)cd oshipdemo (oshipenv)bin/paster serve etc/deploy.iniNo downloading of zc.buildout and/or grokproject (I think that in fact zc.buildout is included with grokproject already), nor answering questions about overwriting.
So, we need to create an oshipproject egg and have it published on PyPi, right?
I'll send you the console output for my installation with rev 276 off-list. Roger