Initial commit

Author: nmoroze

.dockerignore

@@ -0,0 +1,13 @@
+*.pyc
+*.swp
+*.swo
+i.*.swp
+.*.swo
+.webassets-cache
+.sass-cache/
+private
+delete_db.py
+env/
+.env
+node_modules/
+.DS_Store

.gitignore

@@ -0,0 +1,18 @@
+*.pyc
+*.swp
+*.swo
+i.*.swp
+.*.swo
+.webassets-cache
+.sass-cache/
+private
+delete_db.py
+env/
+test_db
+.env
+node_modules/
+.DS_Store
+__pycache__
+.cache/
+Cog
+.vscode/

CONTRIBUTING.md

@@ -0,0 +1,64 @@
+Contributing
+============
+
+All kinds of contributions to Cog are greatly appreciated. For someone
+unfamiliar with the code base, the most efficient way to contribute is usually
+to submit a [feature request](#feature-requests) or [bug report](#bug-reports).
+
+If you want to dive into the source code, you can submit a [patch](#patches) as
+well. Working on [existing issues][issues] is super helpful!
+
+Feature Requests
+----------------
+
+Do you have an idea for an awesome new feature for Cog? Please [submit a
+feature request][issue]. It's great to hear about new ideas.
+
+If you are inclined to do so, you're welcome to [fork][fork] Cog, work on
+implementing the feature yourself, and submit a patch. In this case, it's
+*highly recommended* that you first [open an issue][issue] describing your
+enhancement to get early feedback on the new feature that you are implementing.
+This will help avoid wasted efforts and ensure that your work is incorporated
+into the code base.
+
+Bug Reports
+-----------
+
+Did something go wrong with Cog? Sorry about that! Bug reports are greatly
+appreciated!
+
+When you [submit a bug report][issue], please include relevant information such
+as Cog version, operating system, configuration, error messages, and steps to
+reproduce the bug. The more details you can include, the easier it is to find
+and fix the bug.
+
+Patches
+-------
+
+Want to hack on Cog? Awesome!
+
+If there are [open issues][issues], you're more than welcome to work on those -
+this is probably the best way to contribute to Cog. If you have your own
+ideas, that's great too! In that case, before working on substantial changes to
+the code base, it is *highly recommended* that you first [open an issue][issue]
+describing what you intend to work on.
+
+Patches should be submitted as Github pull requests.
+
+Any changes to the code base should follow the style and coding conventions
+used in the rest of the project. The version history should be clean, and
+commit messages should be descriptive. Please run the included tests to ensure
+that nothing has broken, and, if applicable, we recommend writing tests for
+any new features you add!
+
+---
+
+If you have any questions about anything, feel free to [ask][email]!
+
+_Thanks to Anish Athalye for letting us borrow this contribution guide from [Gavel](https://github.com/anishathalye/gavel)._
+
+[issue]: https://github.com/techx/cog/issues/new
+[issues]: https://github.com/techx/cog/issues
+[fork]: https://github.com/techx/cog/fork
+[email]: mailto:[email protected]
+[gavel]: https://github.com/anishathalye/gavel

DEVELOPMENT.md

@@ -0,0 +1,27 @@
+# Development
+
+## Setup
+- Set up a Python2
+[virtualenv](http://python-guide-pt-br.readthedocs.io/en/latest/dev/virtualenvs/)
+to manage Python dependencies 
+- Source your virtualenv 
+- Run `pip install -r requirements.txt` to install all dependencies 
+- Install [PostgreSQL](https://www.postgresql.org/download/) to run a database locally
+  - If you're using Mac, install *Postgres.app* from
+  [here](https://www.postgresql.org/download/) 
+- Set three environment variables: 
+  - `DATABASE_URL` points to the URL of a development database,
+which has to be set up using Postgres on your system. A sample `DATABASE_URL`
+could look like `postgres://username:password@localhost/cog`. 
+  - `QUILL` is the URL to your Quill instance for auth. 
+  - `SECRET` needs to be the same JWT secret used in your Quill instance. 
+- Run `python initialize.py` 
+  - This initializes the database - run it if you make any changes to the models and
+  are fine with overwriting data.
+
+## Running 
+- Run `make run` 
+- The site will be visible at `localhost:8000`
+
+## Tests 
+- Run `make test` to run all tests

Dockerfile

@@ -0,0 +1,14 @@
+FROM python:2
+
+ARG APP_PATH=/hardware-checkout
+
+WORKDIR $APP_PATH
+
+ADD requirements.txt $APP_PATH
+RUN pip install -r requirements.txt
+
+ADD . $APP_PATH
+
+EXPOSE 8000
+CMD ["gunicorn", "--bind", ":8000", "-k", "geventwebsocket.gunicorn.workers.GeventWebSocketWorker", "hardwarecheckout:app"]
+