One more related question.
What is the recommended way of packaging and distributing TG2
application. ? (Any tutorial pointers ?)
Ideally would like to have a one step installation process that
a. -- installs TG2 (controlled components)
b. -- install the application
c. -- do the initial setup and configuration required.
Here is what we are thinking for each of this...
a. Use the EggBasket/Easyeaster. ( I need to understand more here)
b. create a egg for our application and put it in the basket ??
How do we tell tg2 deploy an application from egg ? some paster
command
c. Modify websetup.py for doing adding seed data.
Modify setup.py to load additional dependencies.
python setup.py
paster setup-app config file ?
d. Where would data upgrade fit in ?
Would really appreciate some thoughts / pointer to get this
streamlined.
Thanks
/Jd
On Aug 6, 4:31 pm, Jd <[email protected]> wrote:
> On Aug 4, 6:31 am, "Diez B. Roggisch" <[email protected]> wrote:
>
>
>
> > On Tuesday 04 August 2009 02:50:05 Jd wrote:
>
> > > From what I gather, TG2 installation puts together a bunch of cool
> > > projects together in the right way for them to be extremely useful. We
> > > have chosen it for our project.
>
> > > Now the problem is that we would like to freeze these components that
> > > it come with. Everytime I install a new tg2env and TG2 in from the
> > > instructions, I get different version of the stuff. Also these seem to
> > > differ on different linux distributions (CentOS, Fedora, Ubuntu etc)
>
> > > We would like to have one environment that refers to specific
> > > versions of the underlying components.
>
> > > What we would like to see is...
> > > -- TG2.0 --> component1 (v2.2), component2 (4.5.3)
> > > -- TG2.1 --> component1 (v2.3), component2 (4.5.3)
>
> > > Is my understanding off ?
> > > Any suggestions or more explanation on how things are put
> > > together ?
>
> > You can achieve this by creating a custom index-page that you restrict
> > easy_install to use when fetching eggs to install. For that, put a line like
>
> > [easy_install]
> > find_links =http://eggbasket.office.ableton.com/versionset/81
> > allow_hosts = eggbasket.office.ableton.com
>
> > into setup.cfg parallel to setup.py in your project.
>
> > We do so by having a customizied EggBasket that supports a thing we call
> > versionsets. And a commandline-tool called Easterbunny that uploads a
> > virtualenv as whole, making it one of those versionsets.
>
> > This works extremely smooth for us for a year now.
>
> > Other options also exist, zc.buildout works also AFAIK, but I never toyed
> > around with that.
>
> > diez
>
> Thanks for the response.
> - I will need to probably read up on egg files and packaging.. I am
> not too familiar in that area.
> - Will also look up tools suggested by you.
> -- Version set sound like the right way to do things. I am assuming
> that it allows you to "label" a setup of component with specific
> versions as a single unit. Is this something you can share ? Also is
> Easterbunny something you wrote ? Could not spot it in my search.
>
> /Jd
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
