Smirl / switches

A webpage of switches that don't do anything at all

switches

A web page of switches that don't do anything at all

Installation and Running

We can use docker to get a production like environment locally.

docker-compose up

Create the database. This only needs to be done the once not everytime you run the app.

docker-compose exec app sh

from switches import db
db.create_all()
exit()

In production we should use something better like gunicorn. gunicorn will also be installed when you ran pip install -r so you can try that too.

(venv)$ gunicorn switches:app --log-file - --log-level debug --port 5000

Go to http://localhost:5000/ to see your hard work

Heroku

This has been deployed to heroku and you can see the master branch at http://intense-depths-2389.herokuapp.com. The Procfile runs the gunicorn server with some logging. Heroku deployment uses postgresql not sqlite3. This is configured with the DATABASE_URL environment variable which is set in heroku. For development sqlite3 is fine and you do not need to install the psycopg2 python package.

How it works

The switches.py file is the web server which has different "web pages". These are all of the functions which have @app.route on them. The Switch model is a database table basically. Your database is just the one file called switches.sqlite3 which create_all made for you.

The templates/index.html is a jinja2 template (AKA a html file with some curly brackets in it). The flask app populates the template when the page is loaded. The javascript at the bottom changes the page once it has been loaded. We add some click handlers to the delete button and the toggle switch.