On 02/04/2009, at 11:30 PM, edgarsmolow wrote:
> > An alpha version of my first Pylons app is on my workstation in > development mode. I want to deploy the app to our web server so our > customer can view it and provide feedback. Pylons 0.9.7 has been > installed on the web server. > > 1. Is the best procedure for deploying the app to create a Python egg > and a config file, and copy them to the web server? That's the procedure we use for production deployments. In fact, we have an internal "pypi" clone, so we deploy our production release eggs to that and then easy_install -U on the live servers to install or update. But copying the eggs is just as good. > > [The common method of deployment where Pylons was NOT used is to copy > a slew of files to the web server, carefully placing them in specific > directories. Later updates are a matter of copying (overwriting) one > or more files to web server.] [Urgh!] > > 2. To update the application on the web server, do I create a new egg > & config file, copy (overwrite) to the web server, and restart Paste? easy_install -U the new egg, update the config file if required, then restart Paste. Make sure to switch off debug mode; and it would be recommended not to run paster with "--reload" so that paste doesn't restart itself before you're ready. 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
