quad
/
quadfile
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README.md 

In hopes of avoiding confusion related to issue #2
This commit is contained in:
Dominik V. Salonen 2017-11-19 22:11:56 +01:00 committed by GitHub
parent 63c55c777e
commit 4d1d923fa4
1 changed files with 18 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@ -28,11 +28,26 @@ Recommended:
# Using the thing # Using the thing
## Test deployment
* Clone the repo somewhere * Clone the repo somewhere
* ``pip install -r requirements.txt``
* Do ``cp conf.py.sample conf.py`` * Do ``cp conf.py.sample conf.py``
* Edit ``conf.py`` so that the information is correct * Edit ``conf.py`` so that the information is correct
* `sqlite3 files.db < schema.sql` * ``sqlite3 files.db < schema.sql``
* If possible, make it listen on ``127.0.0.1`` and then use something like nginx as a reverse proxy for security purposes. Using gunicorn and the WSGI entry point is even better if you know how to do that.
* ``chmod +x run.py`` and then ``./run.py`` * ``chmod +x run.py`` and then ``./run.py``
* ??? * ???
* PROFIT (Hopefully) * PROFIT (Hopefully)
## Production deployment
* Clone the repo somewhere
* Set up a virtual environment for QuadFile
* ``pip install -r requirements.txt``
* Do ``cp conf.py.sample conf.py``
* Edit ``conf.py`` so that the information is correct
* ``sqlite3 files.db < schema.sql``
* ``gunicorn wsgi:app -w 4 --bind 127.0.0.1:8282 --log-file $HOME/quadfile.log`` (Use supervisor to run it on boot if needed)
* Configure nginx and proxy_pass it to gunicorn
* ???
* PROFIT (Hopefully)