Elasticsearch frontend with advanced OSINT analytics capabilities including sentiment display, nickname/information tracing, live and scheduled rule creation with webhook endpoints. https://pathogen.is
Go to file
2022-07-29 22:22:22 +01:00
app Implement aliases 2022-07-29 22:22:22 +01:00
core Implement aliases 2022-07-29 22:22:22 +01:00
docker Pass through local settings file to mount 2022-07-29 22:22:22 +01:00
.gitignore Remove lib from gitignore 2022-07-21 13:46:55 +01:00
.pre-commit-config.yaml Make isort compatible with Black 2022-07-21 13:51:06 +01:00
docker-compose.yml Pass through local settings file to mount 2022-07-29 22:22:22 +01:00
manage.py Run formatting 2022-07-21 13:45:13 +01:00
pyproject.toml Make TS lowercase in table 2022-07-21 13:51:17 +01:00
README.md Fix typo in documentation 2022-07-21 13:47:52 +01:00
requirements.txt Make project docker-ready 2022-07-29 22:22:22 +01:00

Neptune

Django app to handle to manage subscriptions to products using Stripe, and implementation of the products themselves.

Setting up the environment

Create the virtual environment, enable it, and install the dependencies.

$ python3 -m venv env
$ source env/bin/activate
(env) $ pip install -r requirements.txt

Local settings

You'll need to copy the app/local_settings.example.py file to app/local_settings.py. The project won't start otherwise.

$ cp app/local_settings.example.py app/local_settings.py

Running database migrations

Now we need to run the database migrations in order to get a working database.

(env) $ python manage.py migrate

Creating a superuser

In order to access Django admin, we need a superuser.

(env) $ python manage.py createsuperuser
Username: t2
Email address: t2@google.com
Password: 
Password (again): 
Superuser created successfully.

Running the server

(env) $ python manage.py runserver 8001
Starting development server at http://127.0.0.1:8001/
Quit the server with CONTROL-C.

As you've guessed, you can access it at http://127.0.0.1:8001/

Troubleshooting

Sometimes Django is difficult.

django.db.utils.OperationalError: no such table: core_user

This means you haven't yet run the migrations. See above.

Updating the models

If you make changes to the database models, you will need to create new migrations. Do this like so:

(env) $ python manage.py makemigrations

Afterwards, we can apply them as normal.

(env) $ python manage.py migrate