1. Pyramid Deployment and Maintenance Carlos de la Guardia Plone Conference 2011

2. So, your application is ready and looking good

3. Time to deploy it and see how it holds up

4. Deployment with NginX More information at: http://docs.pylonsproject.org/projects/pyramid_cookbook/dev/deployment/nginx.html upstream myapp-site { server 127.0.0.1:5000; server 127.0.0.1:5001; } server { server_name example.com; access_log /home/example/env/access.log; location / { proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_connect_timeout 60s; proxy_send_timeout 90s; proxy_read_timeout 90s; proxy_buffering off; proxy_pass http://myapp-site; proxy_redirect off; } }

5. Deployment with Apache and Mod_WSGI We need to create an app that will call our application with configuration. Then we set up apache to call this app. More information at: http://docs.pylonsproject.org/projects/pyramid/1.2/tutorials/modwsgi/index.html #pyramid.wsgi from pyramid.paster import get_app application = get_app('/mydir/modwsgi/env/myapp/production.ini', 'main') #apache.conf WSGIApplicationGroup %{GLOBAL} WSGIPassAuthorization On WSGIDaemonProcess pyramid user=cguardia group=staff threads=4 python-path=/mydir/modwsgi/env/lib/python2.6/site-packages WSGIScriptAlias /myapp /mydir/modwsgi/env/pyramid.wsgi <Directory /mydir/modwsgi/env> WSGIProcessGroup pyramid Order allow,deny Allow from all </Directory>

7. We already discussed mod_wsgi. If you are sure that you need something else, people on our mailing lists have reported success with uWSGI and gUnicorn.

8. If you are using ZODB with paster, consider using Jove to manage multiple sites and settings consistently: https://github.com/Pylons/jove

9. Other approaches include using gevent, twisted or eventlets.

10. Putting all your eggs in the same basket

12. Create an egg directory using a GitHub site and generate the index with the same script.

13. Install a PyPI clone like ClueReleaseManager, and configure your .pypirc file to point at the clone. Use setuptools to upload.

14. Jarn.mkrelease can be used to commit, tag and upload in one step: $ mkrelease -d mypypi src/my.package

16. Recipes are used to define what each part of the buildout will install and/or setup. There are many available recipes on PyPI.

17. A buildout can have different configurations. For example, deployment and production.

18. Buildout can be used to setup a Pyramid application and it's dependencies easily.

19. Sample buildout [buildout] parts = myapp mkrelease Develop = src/mypackage index = http://example.github.com/myapp/staging/index/ [myapp] recipe = zc.recipe.egg eggs = some_dependency mypackage interpreter = py [mkrelease] recipe = zc.recipe.egg eggs = jarn.mkrelease scripts = mkrelease

21. We can use supervisor to control our pyramid applications, either alone or together with other applications or services.

22. A very easy way to configure it is to simply add the supervisor egg to our buildout and include a configuration file.

23. Sample supervisor configuration [inet_http_server] port= 127.0.0.1:9001 [supervisord] logfile= %(here)s/var/supervisord.log logfile_maxbytes= 50MB logfile_backups= 10 loglevel= info pidfile= %(here)s/var/supervisord.pid [rpcinterface:supervisor] supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface [supervisorctl] serverurl= http://127.0.0.1:9001 [program:core] command = %(here)s/bin/paster serve %(here)s/src/inav2_core/development.ini redirect_stderr = true

24. Useful maintenance tools

26. Importing web application code from a command line script will not work when it depends on a request.

27. Pyramid offers a facility for generating an environment similar to what the application would get from a real request.

28. This makes it possible to easily write scripts for tasks like updating databases, create sample content or initialize application services.

31. app

32. root

33. registry

34. closer

35. Exception logging with pyramid_exclog [loggers] keys = exc_logger [handlers] keys = exc_handler [formatters] keys = exc_formatter [logger_exc_logger] level = ERROR handlers = exc_handler qualname = exc_logger [handler_exc_handler] class = handlers.SMTPHandler args = (('localhost', 25), 'from@example.com', ['to@example.com'], 'myapp Exception') level = ERROR formatter = exc_formatter [formatter_exc_formatter] format = %(asctime)s %(message)s

37. File system level backup

38. Continuous archiving

39. Do not forget about staging

41. It's important to be able to quickly deploy changes to staging before trying them in production.

42. Ideally, multiple branches could be deployed separately.

43. Take a look at octomotron: https://github.com/chrisrossi/octomotron

45. Monitoring

46. Failover

47. Replication

48. Automated deployment

49. More...

51. Mission-critical application used by organizations such as Open Society Foundations and Oxfam.

52. 5000+ users (no anonymous access).

53. More than 75,000 Pages of content.

54. Nearly 100,000 lines of code.

56. Buildout for environment creation.

57. Custom package index stored on GitHub.

58. 1 App Server, 1 DB Server.

59. Uses ZODB with RelStorage and PGTextIndex.

60. Deployment is done with a Python script that creates a parallel environment, backs up and evolves data, then restarts the instance.

61. Thank You! Email: [email_address] IRC: #pyramid, #pylons http://groups.google.com/group/pylons-devel

62. Goodbye!