Web service voor het LED-display
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
led-display/{{cookiecutter.app_name}}
Steven Loria c1a76b484d
Switch to MIT license
5 years ago
..
assets Update boostrap to 4.1.1 6 years ago
requirements Bump itsdangerous 6 years ago
tests Use environment variables for configuration 6 years ago
{{cookiecutter.app_name}} Reverting alignment 6 years ago
.env.example Use environment variables for configuration 6 years ago
.eslintrc created travis: npm run lint and npm run build 7 years ago
.gitignore Use environment variables for configuration 6 years ago
.isort.cfg Add a lint command with flake8 and isort 9 years ago
.travis.yml Remove sudo: in .travis.yml 5 years ago
LICENSE Switch to MIT license 5 years ago
Pipfile Bump flake8 from 3.7.3 to 3.7.4 in /{{cookiecutter.app_name}} 5 years ago
Procfile Rename repo_name -> app_name 11 years ago
README.rst Use environment variables for configuration 6 years ago
autoapp.py Use environment variables for configuration 6 years ago
package.json Switch to MIT license 5 years ago
requirements.txt Rename repo_name -> app_name 11 years ago
setup.cfg Bump flake8-docstring 7 years ago
webpack.config.js Fix eslint errors and switch to babel-preset-env 7 years ago

README.rst

===============================
{{ cookiecutter.project_name }}
===============================

{{ cookiecutter.project_short_description}}


Quickstart
----------

Run the following commands to bootstrap your environment ::

git clone https://github.com/{{cookiecutter.github_username}}/{{cookiecutter.app_name}}
cd {{cookiecutter.app_name}}
{%- if cookiecutter.use_pipenv == "yes" %}
pipenv install --dev
{%- else %}
pip install -r requirements/dev.txt
{%- endif %}
cp .env.example .env
npm install
npm start # run the webpack dev server and flask server using concurrently

You will see a pretty welcome screen.

Once you have installed your DBMS, run the following to create your app's
database tables and perform the initial migration ::

flask db init
flask db migrate
flask db upgrade
npm start


Deployment
----------

To deploy::

export FLASK_ENV=production
export FLASK_DEBUG=0
export DATABASE_URL="<YOUR DATABASE URL>"
npm run build # build assets with webpack
flask run # start the flask server

In your production environment, make sure the ``FLASK_DEBUG`` environment
variable is unset or is set to ``0``.


Shell
-----

To open the interactive shell, run ::

flask shell

By default, you will have access to the flask ``app``.


Running Tests
-------------

To run all tests, run ::

flask test


Migrations
----------

Whenever a database migration needs to be made. Run the following commands ::

flask db migrate

This will generate a new migration script. Then run ::

flask db upgrade

To apply the migration.

For a full migration command reference, run ``flask db --help``.


Asset Management
----------------

Files placed inside the ``assets`` directory and its subdirectories
(excluding ``js`` and ``css``) will be copied by webpack's
``file-loader`` into the ``static/build`` directory, with hashes of
their contents appended to their names. For instance, if you have the
file ``assets/img/favicon.ico``, this will get copied into something
like
``static/build/img/favicon.fec40b1d14528bf9179da3b6b78079ad.ico``.
You can then put this line into your header::

<link rel="shortcut icon" href="{{ "{{" }}asset_url_for('img/favicon.ico') {{ "}}" }}">

to refer to it inside your HTML page. If all of your static files are
managed this way, then their filenames will change whenever their
contents do, and you can ask Flask to tell web browsers that they
should cache all your assets forever by including the following line
in your ``settings.py``::

SEND_FILE_MAX_AGE_DEFAULT = 31556926 # one year