-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create the basic Tornado infrastructure #3
Comments
piraz
referenced
this issue
in piraz/firenado
Jun 7, 2015
piraz
added a commit
that referenced
this issue
Jun 13, 2015
piraz
added a commit
that referenced
this issue
Jul 3, 2015
piraz
added a commit
that referenced
this issue
Jul 24, 2015
The skeleton application will be the functional test for basic features shipped by the framework. Refs: #3
It looks this issue as just a "wildcard" ticket to stick to general commits. The "better" structure from iFlux goal was reached so we can close this issue. |
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Review the iFlux Tornado infrastructure and write down a better on Firenado.
As long Firenado may be serving other's web frameworks the structure we put here must be flexible and customize-able enough to support other options.
Tornado still be used as the default option on Firenado.
The text was updated successfully, but these errors were encountered: