Firenado

Latest version: v0.9.5

Safety actively analyzes 629908 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 8 of 8

0.1.5.0

September 01, 2016

We are pleased to announce the release of Firenado 0.1.5.0.

On this release the build was improved in order to provide extra requirements.

Right now it is possible to install redis and sqlalchemy using extra requirements with pip or on the requirements file.

Python 2.6 and 3.2 are not supported on this version to comply with Tornado 4.4.1.

Here are the highlights:

Refactoring
- Depreciate python 2.6 and 3.2. 118
- Change application file from application.py to app.py. 120

New Features
- Create the static maps component. 57
- Add optional requirements to setup.py. 119

Bug Fixes
- Fix managment command help. 13
- Six is not being installed by setup.py. 121
- Sqlalchemy connection is missed when database service restarts or the connection is renewed. 127

0.1.4

April 9, 2016

We are pleased to announce the release of Firenado 0.1.4.

On this release the focus was to get the framework refactored to be more "Pythonic".

This version fixes couple bugs and introduce a way to set the application static_path via configuration.

Here are the highlights:

Refactoring
- Package refactoring to move code from **init**.py's. 109

New Features
- Added static_path to the config file. 104

Bug Fixes
- A disabled session still needs a session type. 91
- The service by decorator is broken. 107
- The initialize method runs just if the component has a file defined. 103

0.1.3

January 31, 2016

We are pleased to announce the release of Firenado 0.1.3.

On this release yml config files will be used by default but yaml files will be
considered also.

Services can be served by other services and couple more minor features were
added to the framework.

No bug fixes were covered on this release.

Here are the highlights:

New Features
- Served_by decorator can be used by another service. 91
- Components can add ui_modules to an application. 85
- Tornado application debug mode added. 84
- Config files can be used with yml and yaml. Yml is default. 83
- Firenado was prepared to start with application types. Tornado is default. 41
- A Firenado Tornado application can be set to start listening on a unix socket. 38

0.1.2

October 30, 2015

Hotfix release to solve a severe bug that was preventing firenado command to un.

Here are the highlights:

New Features
- Added root path to the assets component. 77

Bug Fixes:
- Firenado doesn't run because core.management.tasks was not shipped on 0.1.1. 76

0.1.1

October 28, 2015

We are pleased to announce the release of Firenado 0.1.1. Now we start to support Python 3 and have fixed some bugs fixed.

The project CI is being tracked by travis and tests are being added to the project.

Here are the highlights:

New Features
- Python 3 support
- Added installation capabilities to the framework.

Migration from iFlux to Firenado
- Security (It will be decided if this module still be needed on 0.1.2).

Bug Fixes:
- Firenado requirements are not wired to the setup script. 52
- When Redis connection fails application exits without warning. 58
- Deadlock with the string generation on the util package. 64

0.1

September 28, 2015

This was a complete rewrite from the iFlux framework an here are the highlights:

New Features
- Yaml based configuration files

Migration from iFlux to Firenado
- Data tools
- Modules
- Session
- Services

Migration changes:
- Configuration
- Command line tool

Page 8 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.