Skip to content
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

Closed
piraz opened this issue May 30, 2015 · 1 comment
Closed

Create the basic Tornado infrastructure #3

piraz opened this issue May 30, 2015 · 1 comment
Assignees
Labels
Milestone

Comments

@piraz
Copy link
Contributor

piraz commented May 30, 2015

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.

@piraz piraz added the core label May 30, 2015
@piraz piraz self-assigned this May 30, 2015
@piraz piraz added this to the firenado 0.0.1 milestone May 30, 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
As classes are loaded from the config in runtime a funciton was
introduced to conf to help with this task.

Used the function to load modules during the application bootstrap.

Refs: #3 #15.
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
@piraz
Copy link
Contributor Author

piraz commented Sep 9, 2015

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.

@piraz piraz closed this as completed Sep 9, 2015
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant