#bottle.py

I have been using the micro-framework called bottle.py, and starting to write fairly complicated applications on top of it. So I have been able to put together a relatively clean structure based that serves my maintainability issues This setup uses redis, memcached, and mako as the templating language. Lets assume the application name is project. project/ project/main.py - This is the core application file that loads up bottle and the plugins project/INSTALL - This is the readme and simple installation instructions project/middlewares.py - This is the middlewares that you maybe using in your bottle.py application project/views.py - This contains all the views that you will create, you can also split it further based on your application object types project/utils.py - This is the utility library project/static_views.py - This is a temporary view for serving the static assets of your application in the development. This should never be used in the production setup and be replaced with either a CDN or Nginx or varnish or apache to serve them directly. project/templates/ - This is the mako templates directory project/static/ - This is the static file directory This is a very manageable structure that has evolved over time and works pretty well for me to start off new project pretty easily. In the next article, I will publish an actual mini application with the additional features like HTML5 boilerplate integration in addition to a core bootstrap for the templating structure as well.

I have been using the micro-framework called bottle.py, and starting to write fairly complicated applications on top of it. So I have been able to put together a relatively clean structure based that serves my maintainability issues This setup uses redis, memcached, and mako as the templating language. Lets assume the application name is project. project/ project/main.py - This is the core application file that loads up bottle and the plugins project/INSTALL - This is the readme and simple installation instructions project/middlewares.py - This is the middlewares that you maybe using in your bottle.py application project/views.py - This contains all the views that you will create, you can also split it further based on your application object types project/utils.py - This is the utility library project/static_views.py - This is a temporary view for serving the static assets of your application in the development. This should never be used in the production setup and be replaced with either a CDN or Nginx or varnish or apache to serve them directly. project/templates/ - This is the mako templates directory project/static/ - This is the static file directory This is a very manageable structure that has evolved over time and works pretty well for me to start off new project pretty easily. In the next article, I will publish an actual mini application with the additional features like HTML5 boilerplate integration in addition to a core bootstrap for the templating structure as well.

Problem: I want ONE bottle project to display different pages for: - http://foo.est.im - http://bar.est.im These should be separate Bottle apps. There's [an ugly hack](http://permalink.gmane.org/gmane.comp.python.bottle.general/730) from the official maillist, I think I can make it better. The secret is to create a customized WSGI app: from fnmatch import fnmatch from bottle import Bottle, default_app, run foo = Bottle() foo.hostnames = ['foo.est.im'] @foo.route('/') def hello(): return 'hello!' bar = Bottle() bar.hostnames = ['bar.est.im'] @bar.route('/') def hi(): return 'hi~' @route('/') def index(): print 'hello world' def application(environ, start_response): for app in [foo, bar]: hostnames = getattr(app, 'hostnames', []) if filter(lambda x:fnmatch(hostname, x), hostnames): return app(environ, start_response) return default_app()(environ, start_response) Then run this motherfucker: from django.utils import autoreload def dev_server(): run(application, host='0.0.0.0', port=8002, debug=True) autoreload.main(dev_server)

I hope this tiny simple little code example will help someone out in the future so they don't have to go digging for information like this.

@bottle.route('/') def index(): bottle.response.content_type = 'text/plain' return ("=== API REFERENCE ===\n" + "\n".join(x['rule'] for x in bottle.app().routes))