BlastOff helps accelerate Pylons application development by generating a project with a number of pre-configured dependencies.
Installation
Use pip:
$ pip install BlastOff
or use setuptools:
$ easy_install BlastOff
or old school, download the package from http://pypi.python.org/pypi/BlastOff, unpack it and run (as root if required):
$ python setup.py install
Usage
Create a new Pylons project from the BlastOff template with:
$ paster create -t blastoff AppName
You will be prompted for a few options.
SQLAlchemy database URL:
Enter sqlalchemy_url (The SQLAlchemy URL of the database) ['sqlite:///%(here)s/development.db']:
Specify the database URL that will be used by SQLAlchemy. Defaults to an SQLite database. For PostgreSQL use something like:
postgres://user:pass@hostname/dbname
SchemaBot database schema version control:
Enter use_schemabot (Enable database schema version control using SchemaBot) [True]:
If True then SchemaBot will be used to automatically manage the SQLAlchemy database schema.
Email confirmation to activate new user accounts:
Enter email_confirmation (True/False: New users must click activation link from confirmation email) [True]:
If True the application will be configured to send a confirmation email to the user upon registration. The email will contain a link for activating the account before it can be used. If False no activation confirmation will be configured so users will be able to login immediately after registering.
Create a default user:
Enter default_user (Default username to create, password will match username (leave blank for no default user)) ['']:
To have a default user created when the database is set up enter the username here.
After creation the Pylons app is ready to be used.
To ensure all the application dependencies are installed you can run this command from the application directory:
$ python setup.py develop
Before starting the app the database needs to be set up (i.e. tables created). This is done by using the standard Pylons command:
$ paster setup-app development.ini
If the SchemaBot option was enabled then a BlastOff generated project will use SchemaBot to manage database schema changes. The initial tables will be created by SchemaBot, the default user inserted if that option was selected, and the database marked as schema version 1. See model/__init__.py within the application source for more information.
To run the application use the standard Pylons command:
$ paster serve --reload development.ini
Point your browser at the URL http://127.0.0.1:5000/
The generated project contains model and functional tests that can be run using the “nosetests” command (requires the Nose package to be installed).
Documentation
For more information see the BlastOff wiki at http://bitbucket.org/chrismiles/blastoff/wiki/Home or the Pylons documentation at http://pylonshq.com/
Metadata
Release files for BlastOff 0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| BlastOff-0.2.tar.gz | 68.5 kB | Without provenance | Details for BlastOff-0.2.tar.gz |
Release files / BlastOff-0.2.tar.gz
| Download URL | BlastOff-0.2.tar.gz |
|---|---|
| Size | 68.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00ff2e4e3087da2c9765e28324d33fcc84f102e7e8b880869093980b1b41cd74
|
|
BLAKE2b-256 checksum How to use checksums |
c9409a5a850b414d8d19235dbc9610626bdc189b3cd0df31f65b26780c3331e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for BlastOff 0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.