An experiment in "deep web" content management
All content must be accesed using an appropriate access code. Once screens are unlocked they are stored in the session. If a user wants to save thier findings they can register as a member.
Uses:
Docker is the prefered way to run a local development environment. Everything is automated using Make.
Copy the local .env.example to .env and fill in the correct vars for your setup
cp ./.envs/local/.env.example ./.envs/local/.env
To build the image, make and run migrations, and run the dev server, use:
make run
The first time you run the app you'll want to create a superuser
make manage createsuperuser
If you want to run the tests:
make test
To run a django mangement command use make manage. For example:
make manage shell
To format your code with black:
make format
The app is able to use the Twilio api to do OTP login via SMS. See Twilio Verification API for more details.
For development there is a local SMS provider that doesn't depend on Twilio. To use it set SMS_PROVIDER to local. The correct auth code is sent to the logs. Use it to login.
Notifications for new messages are sent via SMS using Twilio. See Twilio SMS API for more details.
For development use the local SMS provider by setting SMS_PROVIDER to local.
A Postgress DB should be running on localhost:5432.
PgAdmin web app should be runing on localhost:5050.
After you log in to PgAdmin you can access the DB by adding a new server with Mantaience DB set to your POSTGRES_DB, host set to andrewbbs-postgres, and our username and password set to the same ones you set in your .env
- DevOps
- add make targets for production
- add continuous deployment via workflows
- move certs to volumes
- Reduce size of django image?
- run tests in github workflow
- App
- Add view and edit member details
- Add view member list
- Message system
- Add admin send to all feature
- Add reply to message feature
- Message pagination
- Link in in SMS?
- Encrypted Messaging
- Alerts for new joins