Sushi is application package builder. Enough to create same package structure every time. Create custom recipes for Flask, Django, etc...

Sushi work like a package manager, Homebrew for example. You have to add a least one cookbook to your in order to have some recipes available.

And of course you can very easily create your own cookbook cause they are __Github__ repositories.

• Deploy the same everytime
• Make specific recipe for Flask, Django, ...
• Use helpers to not waste time
• Auto virtualenv for best dev
• Auto git init your package
• And more !

Sushi support helper(extensions) and there are easy to create. There are already some extension, like git, license.

pip install sushi

If it's the first time your run Sushi, your cookbook is certainly empty. You can easily learn a basic recipe like that:

Sushi » sushi cookbook-add socketubs/sushi-recipes
==> Add socketubs/sushi-recipes cookbook
Cloning into 'socketubs/recipes'...
remote: Counting objects: 126, done.
remote: Compressing objects: 100% (84/84), done.
remote: Total 126 (delta 46), reused 108 (delta 28)
Receiving objects: 100% (126/126), 44.95 KiB, done.
Resolving deltas: 100% (46/46), done.
==> Done

First recipe ~~~~~~~~~~~

List all recipes available on my cookbook:

Sushi » sushi all
==> Recipes available
socketubs/recipes/advanced
socketubs/recipes/basic
socketubs/recipes/django
socketubs/recipes/flask
socketubs/recipes/helper

And learn the basic one for example.

Sushi » sushi learn basic
==> Learn given recipe
==> Done

Deploy it !

Tests » sushi craft MyApp --recipe=basic
==> Craft your project
  => Recipe: basic
==> Call helpers
==> Done

Take a look at your configuration file: ~/.sushi/sushi.conf.

If you want to create your own recipe, you have to create a pull request on my cookbook or create your own cookbook on __Github__.

Recipes are simple folder archives with a basic structure but with Jinja2 code inside your files.

This is a tree sample of my advanced recipe:

tree advanced
advanced
├── .gitignore
├── README.md
├── __app__
│   ├── __init__.py
│   ├── cli.py
│   ├── core.py
│   └── logger.py
├── bin
│   └── __app__
└── setup.py

All files will be parsed by __Jinja2__ and all tags listed below will be replaced.

There is just one keyword to know for filename: __app__ will be replace by your formatted module name.

And for file rendering:

And every values you can add to your configuration file under settings section.

Create your own helpers [REWRITE] -----------------------

Helpers are Sushi extensions, they will be run after complete rendering of your recipes.

You module name must be sushi_ext_name and it will be call like that sushi_ext_name.run(dst), wich dst is the path where recipe will be renderer.

Your helper can use sushi.core api like that:

>>> from sushi.core import conf
>>> conf.get('settings', 'license')
'agpl-v3'
>>> conf.get('paths', 'sushi_recipes')
'/Users/socketubs/.sushi/recipes'
>>> from sushi.env import get_env
>>> get_env('my_package')
{'username': 'socketubs',
 'license_content': u'http://www.opensource.org/licenses/agpl-v3.html',
 'hour': 21, 'day': 2, 'minute': 0, 'month': 9, 'second': 4, 'year': 2012,
 'firstname': '## Set firstname',
 'lastname': '## Set lastname',
 'module': 'my_package',
 'date': '2012-09-02 21:00',
 'name': 'my_package',
 'license': 'agpl-v3',
 'email': '## Set email'}

And of course conf object is ConfigParser, so you can ask your helper users to set variables in their configuration file.

There is one sushi recipe for helper that you can found here.

You can find two examples on Github.

• Sushi-git
• Sushi-license

License is AGPL3. See LICENSE.