[Zope3-Users] Re: Getting started with a zope 3 install as eggs
Jesper Petersen wrote: Thanks for your replies Philipp and Brandon, Things are more clearly now :) So zopeproject _only_ deals with setting up the environment for you, when you run buildout eggs actually get installed. And, I don't need zopeproject on my hosting machine at all, I just test and develop on my personal machine and when ready, I install it as an egg on the host and run it. Pretty much. Typically, the sandbox that zopeproject generates is checked in to a version-control system and then deployed on the server, or on other developers' machines for testing. To "revive" such a checked-in sandbox (generate scripts, download dependency eggs, etc.), you'd use buildout. zopeproject is indeed out of the loop at this point. Now I have the boring task of converting my old webapp done in 3.3.1 to an egg with all dependencies. Is there a way that can aid me in adding dependencies? Grep for imports. Or use zope.dependencytool or zope.importtool (no idea what the difference between those is). As it is now I see this in front of me.. 1. Look at all imports to see what I need 2. Add them in configure.zcml with 3. Add them in setup.py Yup. I can also see 'file="meta.zcml"' in some includes, how would I know when to specifically include a file or not? Having to look at the zope tree for files seems kind of awkward. zopeproject pretty much gives you the standard set of meta.zcml includes. Also, say that I use zope.foo.bar, how would I know wether to include zope.foo or zope.foo.bar as a dependency? I could do a simple search on pypi for this but it seems kind of time consuming. Normally you'd only have to include zope.foo. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: Getting started with a zope 3 install as eggs
Thanks for your replies Philipp and Brandon,Things are more clearly now :) So zopeproject _only_ deals with setting up the environment for you, when you run buildout eggs actually get installed. And, I don't need zopeproject on my hosting machine at all, I just test and develop on my personal machine and when ready, I install it as an egg on the host and run it. Now I have the boring task of converting my old webapp done in 3.3.1 to an egg with all dependencies. Is there a way that can aid me in adding dependencies? As it is now I see this in front of me.. 1. Look at all imports to see what I need 2. Add them in configure.zcml with 3. Add them in setup.py I can also see 'file="meta.zcml"' in some includes, how would I know when to specifically include a file or not? Having to look at the zope tree for files seems kind of awkward. Also, say that I use zope.foo.bar, how would I know wether to include zope.foo or zope.foo.bar as a dependency? I could do a simple search on pypi for this but it seems kind of time consuming. Lots of questions :) Thanks for your time Jesper On 11/5/07, Brandon Craig Rhodes <[EMAIL PROTECTED]> wrote: > > "Jesper Petersen" <[EMAIL PROTECTED]> writes: > > > I've looked a bit at zopeproject, but I'm still wondering if it's > > possible to still install zope as eggs without zopeproject (if that > > even makes sense). > > If I understand both "zopeproject" and your question (and I'm less > confident about whether I understand your question), then this might > be the answer you need: The "zopeproject" script is *not* designed to > install Zope. That is, it's not, once you've developed your Zope > project in one place, the way you "make Zope appear" on the actual > hosting server so that your application can run. > > Instead, "buildout" is how you get Zope installed most of the time. > Your "setup.py" for your application is what will list Zope as a > dependency, and will result in its being fetched and installed before > you run your application. > > So what's the point of "zopeproject"? It's just there to write your > first "setup.py" and "buildout.py", to create your "src/" directory > for you, and get things set up for development. But once you've > started your project, you'll never need "zopeproject" again; you can > immediately uninstall it if you want! :-) So you'll never need it > installed on a "production box", only on development boxes where you > first create projects out of nothing. > > Let me know whether this answer was helpful, or a statement of the > obvious that is beside the actual point of your question. :-) > > -- > Brandon Craig Rhodes [EMAIL PROTECTED] > http://rhodesmill.org/brandon > ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: Getting started with a zope 3 install as eggs
"Jesper Petersen" <[EMAIL PROTECTED]> writes: > I've looked a bit at zopeproject, but I'm still wondering if it's > possible to still install zope as eggs without zopeproject (if that > even makes sense). If I understand both "zopeproject" and your question (and I'm less confident about whether I understand your question), then this might be the answer you need: The "zopeproject" script is *not* designed to install Zope. That is, it's not, once you've developed your Zope project in one place, the way you "make Zope appear" on the actual hosting server so that your application can run. Instead, "buildout" is how you get Zope installed most of the time. Your "setup.py" for your application is what will list Zope as a dependency, and will result in its being fetched and installed before you run your application. So what's the point of "zopeproject"? It's just there to write your first "setup.py" and "buildout.py", to create your "src/" directory for you, and get things set up for development. But once you've started your project, you'll never need "zopeproject" again; you can immediately uninstall it if you want! :-) So you'll never need it installed on a "production box", only on development boxes where you first create projects out of nothing. Let me know whether this answer was helpful, or a statement of the obvious that is beside the actual point of your question. :-) -- Brandon Craig Rhodes [EMAIL PROTECTED] http://rhodesmill.org/brandon ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: Getting started with a zope 3 install as eggs
Jesper Petersen wrote: Hi Christian, I've looked a bit at zopeproject, but I'm still wondering if it's possible to still install zope as eggs without zopeproject (if that even makes sense). Sure, you can do that. Nobody's stopping you. It's just that zopeproject gives you a head start with the sandbox. It's all about getting the environment primed and installing the most common eggs. From there you can take it anywhere you like. Will zopeproject become _the_ way of developing in the future? Dunno. I've primarily developed as a replacement tool for the tarball-centric mkzopeinstance script, because I didn't want to type all that boiler plate all the time. I use it in trainings, quite successfully. Note that it's offspring from grokproject, which we've been using to set up Grok-based sandboxes for much longer now. I think the basic principle is well-established now. I have a hosting situation that is a bit unclear when it comes to running zopeproject because they use good old instances. I have a discussion with them at the moment so I hope I get this sorted out :) A zopeproject-generated sandbox is like an instance, except that it also installs the Zope eggs, and therefore is self-contained (the eggs can still be shared among multiple sandboxes, though). If you can host instances, you should be able to host buildout-driven sandboxes (because that's what zopeproject generates) too. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: Getting started with a zope 3 install as eggs
Hi Christian,I've looked a bit at zopeproject, but I'm still wondering if it's possible to still install zope as eggs without zopeproject (if that even makes sense). Will zopeproject become _the_ way of developing in the future? Because I don't see a reason using a tarball install when you can't smoothly install those nice zope packages (e.g lovely.tag) that depend on the eggversion of zope. I have a hosting situation that is a bit unclear when it comes to running zopeproject because they use good old instances. I have a discussion with them at the moment so I hope I get this sorted out :) On 10/31/07, Christian Klinger <[EMAIL PROTECTED]> wrote: > > Jesper, > > do you know zopeproject > > http://cheeseshop.python.org/pypi/zopeproject/0.4.1 > > with the help of zopeproject you will get > a buildout where you can specifiy further > dependencies in your application. > > HTH > > Christian > > > Good afternoon list, > > I currently have a Zope 3.3.1 installation (tarball) and have written > > some code that uses zc.catalog > > and hurry.query. These two were installed as eggs and work fine (I used > > zc.catalog 1.1 because > > later versions required a lot of zope eggs) > > > > I'd like to use more packages but I see that most of the new stuff today > > > require eggs from the > > 'eggified' version of Zope.. > > > > So I figure I just might as well switch to all eggs and join the future. > > I want this to go as smooth as > > possible. Not sure how to get started though. > > > > > > 1. Which package to easy_install to get Zope 3? And when you've got it > > installed can you say that > > > > you actually run a certain version of Zope any longer? > > > > > > 2. If I install everything as eggs, how do I actually create, configure > > and run instances? Or do I > > actually keep my old 3.3.1 install alongside the new eggs? > > > > 3. Any other suggestions? > > > > Greatly appreciate any answers bringing some clarity to this > > Regards > > Jesper > ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: Getting started with a zope 3 install as eggs
Jesper, do you know zopeproject http://cheeseshop.python.org/pypi/zopeproject/0.4.1 with the help of zopeproject you will get a buildout where you can specifiy further dependencies in your application. HTH Christian Good afternoon list, I currently have a Zope 3.3.1 installation (tarball) and have written some code that uses zc.catalog and hurry.query. These two were installed as eggs and work fine (I used zc.catalog 1.1 because later versions required a lot of zope eggs) I'd like to use more packages but I see that most of the new stuff today require eggs from the 'eggified' version of Zope.. So I figure I just might as well switch to all eggs and join the future. I want this to go as smooth as possible. Not sure how to get started though. 1. Which package to easy_install to get Zope 3? And when you've got it installed can you say that you actually run a certain version of Zope any longer? 2. If I install everything as eggs, how do I actually create, configure and run instances? Or do I actually keep my old 3.3.1 install alongside the new eggs? 3. Any other suggestions? Greatly appreciate any answers bringing some clarity to this Regards Jesper ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
