pyramid 1.2.6 - problem deploying first production project
Since I'm new to pyramid python (started both Friday), I'm not sure if I found a bug or am doing something wrong. I didn't modify the MANIFEST.in file, but these 7 files are not deployed when I install the egg. CHANGES.txt MANIFEST.in README.txt development.ini production.ini setup.cfg setup.py The above 7 files are listed in the deployed EGG-INFO/SOURCES.txt file. Didn't notice until I looked for the deployed production.ini I need to specify in my .wsgi file. MANIFEST.in appears fine: include *.txt *.ini *.cfg *.rst recursive-include custapp *.ico *.png *.css *.gif *.jpg *.pt *.txt *.mak *.mako *.js *.html *.xml I'm using: python: 2.6.5 with virtualenv on Ubuntu 10.04 LTS pyramid: 1.2.6 scaffold: pyramid_starter Is this problem normal, or a bug, or am I doing something wrong? I already took a look at http://docs.python.org/distutils/sourcedist.html#the-manifest-in-template Thanks in advance and congrats on creating a fast flexible framework! -- You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
Re: deploying to production?
Chris Miles wrote: paster serve is a reasonable option. Like I said, mod_wsgi is preferred for me as it simplifies service control. Yes, there's a lot to be said for that... Most systems already know how to start and stop Apache... Is there a good how-to anywhere on serving with mod_wsgi? Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: deploying to production?
On May 26, 1:57 am, Chris Withers ch...@simplistix.co.uk wrote: Chris Miles wrote: paster serve is a reasonable option. Like I said, mod_wsgi is preferred for me as it simplifies service control. Yes, there's a lot to be said for that... Most systems already know how to start and stop Apache... Is there a good how-to anywhere on serving with mod_wsgi? Did you try the web site? Start with: http://www.modwsgi.org/ http://code.google.com/p/modwsgi/wiki/InstallationInstructions http://code.google.com/p/modwsgi/wiki/IntegrationWithPylons http://code.google.com/p/modwsgi/wiki/DeveloperGuidelines http://code.google.com/p/modwsgi/wiki/VirtualEnvironments Graham --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
deploying to production?
Hey All, As a total newbie to Pylons I thought I'd ask some questions about deployment: - which bits of a Pylons project do you version control? * - how do you build all the other bits? * - what do people use to serve their sites? Is whatever paster serve blah.ini using suitable for serving to the wide world or does it need to be proxied through something like Apache? - if using paster serve, how do people wire it so that it starts at machine startup and stops at machine shutdown? - is paster serve the recommended option? If not, what is? cheers, Chris * I'd like to be using buildout for things wherever possible, the following is what I have so far: [buildout] parts = pylons develop = myproj [pylons] recipe = zc.recipe.egg eggs = Pylons PasteScript myproj -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: deploying to production?
On Wed, May 20, 2009 at 02:28:52PM +0100, Chris Withers wrote: - which bits of a Pylons project do you version control? * I version control anything that isn't automatically regenerated. That includes the Paster templates and boilerplate code (since it's rarely boilerplate when I'm done!) - how do you build all the other bits? * I push my releases to a git repository that is accessible from my production server where I checkout and build an egg in the production virtualenv. For a long time, I built out of my working directly, but a recent feature mis-merge broke me of that bad habit :). - what do people use to serve their sites? Is whatever paster serve blah.ini using suitable for serving to the wide world or does it need to be proxied through something like Apache? - if using paster serve, how do people wire it so that it starts at machine startup and stops at machine shutdown? - is paster serve the recommended option? If not, what is? I'd say I seem to be in the minority, based on the discussions here, but I use Apache+FastCGI. Never have any deployment problems. I restart Apache when I deploy a new version, which might annoy some people (I could kill my fcgi processes, but just don't usually bother). I do try to be the first hit so I see the initial load time! * I'd like to be using buildout for things wherever possible, the following is what I have so far: I have not used buildout, so I can't really comment. -- Ross Vandegrift r...@kallisti.us If the fight gets hot, the songs get hotter. If the going gets tough, the songs get tougher. --Woody Guthrie --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: deploying to production?
On May 20, 6:28 am, Chris Withers ch...@simplistix.co.uk wrote: Hey All, As a total newbie to Pylons I thought I'd ask some questions about deployment: - which bits of a Pylons project do you version control? * It's been a while since I started a new Pylons project from scratch, but I think everything that's generated by paster create plus the modules you add minus anything that's generated (the data directory comes to mind). - how do you build all the other bits? * python setup.py install Actually, I use Paver to build minified JS files and things like that, but the standard install command can still be used. - what do people use to serve their sites? Is whatever paster serve blah.ini using suitable for serving to the wide world or does it need to be proxied through something like Apache? It's unlikely that you'd want to expose the Paste server directly to the world. Paste server behind a proxy is a good choice though. - if using paster serve, how do people wire it so that it starts at machine startup and stops at machine shutdown? supervisord.org or runit or perhaps daemontools (runit is like daemontools but written in Python; supervisor can be installed by any user). - is paster serve the recommended option? If not, what is? I don't know if there's an officially recommended option, `but paster serve` is a good choice, at least for my needs. cheers, Chris * I'd like to be using buildout for things wherever possible, the following is what I have so far: [buildout] parts = pylons develop = myproj [pylons] recipe = zc.recipe.egg eggs = Pylons PasteScript myproj -- Simplistix - Content Management, Zope Python Consulting -http://www.simplistix.co.uk --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: deploying to production?
Previously Chris Withers wrote: * I'd like to be using buildout for things wherever possible, the following is what I have so far: [buildout] parts = pylons develop = myproj [pylons] recipe = zc.recipe.egg eggs = Pylons PasteScript myproj myproj should depend on Pylons and PasteScript, so don't list them here. You will need to use dependent-scripts = true to get bin/paster generated. If you want to deploy using mod_wsgi you can use the collective.recipe.modwsgi buildout recipe. Wichert. -- Wichert Akkerman wich...@wiggy.netIt is simple to make things. http://www.wiggy.net/ It is hard to make things simple. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: deploying to production?
On 20/05/2009, at 11:28 PM, Chris Withers wrote: As a total newbie to Pylons I thought I'd ask some questions about deployment: - which bits of a Pylons project do you version control? * The whole package source that paster creates, minus any autogen fluff like .egg-info dir. - how do you build all the other bits? * My preference is to run a private pypi-like package repository within the environment. We configure the project package dependencies correctly (setuptools-style) and host any private packages, including the pylons project, in the private repository. For deployment we can then just configure .pydistutils.cfg to point to our local package repository and use easy_install. Local packages are fetched from the local repository, the rest (like Pylons, etc) from PYPI. - what do people use to serve their sites? Is whatever paster serve blah.ini using suitable for serving to the wide world or does it need to be proxied through something like Apache? I prefer serving Pylons apps using Apache/mod_wsgi, usually in daemon mode. Works nicely, service configuration is centralised and avoids all the hassles around starting up shutting down separate applications. If mod_wsgi isn't available or isn't working for some reason, the next preference is paster serve behind Apache/mod_proxy. - if using paster serve, how do people wire it so that it starts at machine startup and stops at machine shutdown? Depends on the system. On Solaris I use the very clever SMF. - is paster serve the recommended option? If not, what is? paster serve is a reasonable option. Like I said, mod_wsgi is preferred for me as it simplifies service control. Cheers, Chris Miles --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
