Devon Mackay 71965eaeaf Add abililty to use system python
Moving virtual environments between systems is problematic... and
unnecessary when creating container images. These modifications allow
the ability to install app dependencies into the system python, and use
that instead of a virtual environment.
2018-07-01 19:15:40 -04:00
2018-06-04 17:13:24 -04:00
2018-07-01 19:15:40 -04:00
2018-06-12 15:52:01 -04:00
2018-05-30 13:57:11 -04:00
2018-06-28 10:24:20 -04:00
2018-06-04 22:36:20 -04:00
2018-06-18 10:42:07 -04:00
2018-06-26 10:31:39 -04:00
2018-06-14 13:53:18 -04:00
2018-05-23 08:50:39 -04:00
2018-06-26 10:31:39 -04:00
2018-05-24 12:27:41 -04:00
2018-06-28 10:24:20 -04:00

ATST

Build Status

Installation

script/setup

The setup script installs pipenv, which is what this application uses to manage its dependences and virtualenv. Instead of the classic requirements.txt file, pipenv uses a Pipfile and Pipfile.lock, making it more similar to other modern package managers like yarn or mix.

To enter the virtualenv manually (a la source .venv/bin/activate):

pipenv shell

If you want to automatically load the virtual environment whenever you enter the project directory, take a look at direnv. An .envrc file is included in this repository. direnv will activate and deactivate virtualenvs for you when you enter and leave the directory.

Additionally, ATST requires a redis instance for session management. Have redis installed and running. By default, ATST will try to connect to a redis instance running on localhost on its default port, 6379.

Running (development)

To start the app and watch for changes:

DEBUG=1 script/server

Testing

To run unit tests:

script/test

or

python -m pytest

Notes

tornado templates are like mustache templates -- add the following to ~/.vim/filetype.vim for syntax highlighting:

:au BufRead *.html.to set filetype=mustache
Description
No description provided
Readme 17 MiB
Languages
Python 48.6%
HTML 43.1%
JavaScript 3.7%
SCSS 3.7%
Shell 0.8%
Other 0.1%