Restructure project directory!

[danriti]

@whiskeylover:

I wish to restructure the project directory to use a layout that is common in web applications:

/ (project top level)
/docs
/toast (web application level)
+--> /assets
+--> /tests
+--> *.py
'--> *.html

So with this layout, the folders have the following purpose:

• project top level - This is where files live that are essential to the project. This includes gitignores, build scripts, READMEs, documentation folders, etc
• web application level - This is where files live that are related to the web application. This helps encapsulate alot of code one level deeper then the top, making the top level not as overwhelming and gives nice organization (i.e. tests will contain tests related to the web app)

I also want to remove the venv from the repo, as this is something that should stay local to each development environment.

Let me know your thoughts on this and we can discuss =)

[whiskeylover]

I was thinking of moving the HTMLs outside of the project to a new project. If we want to have the HTMLs served by the Flask server, we'd need to put them in the "templates" folder and all assets in the "static" folder.

What do you think?

[danriti]

We really only need a single repo for this, so how about this change:

/ (project top level)
/docs
/toast (web application level)
+--> /tests
+--> *.py
'--> /public
     +--> /assets
     '--> *.html

With this structure, you get the following benefits:

1. You can host the public directory using Apache as the root directory. This allows really fast serving of our static pages.
2. You don't expose any of the python web app, as it's a level up
3. Flask app/server runs completely seperate

Thoughts?

[whiskeylover]

This looks great.

Where do we plan to host this? We need a host that allows us to configure Apache and stuff.

[danriti]

Dreamhost should allow us to do everything we want, as I've done similar setups in the past. I'll add a new issue to investigate and do a proof of concept.