Skip to content

chronhq/backend

Folders and files

NameName
Last commit message
Last commit date
Feb 5, 2023
Feb 15, 2022
Feb 15, 2022
Mar 23, 2020
Feb 5, 2023
Mar 26, 2020
Jan 13, 2023
Nov 18, 2018
Nov 22, 2019
Jan 24, 2019
Feb 14, 2023
Nov 18, 2018
Oct 25, 2018
Jan 13, 2023
Oct 15, 2019
Jun 3, 2019
Mar 12, 2020
Apr 1, 2020
Apr 1, 2020
Feb 5, 2023
Feb 5, 2023
Mar 20, 2020
Jan 13, 2023
Nov 15, 2018
Jan 13, 2023

Repository files navigation

Chron Backend

Build Status Requirements Status Codacy Badge

Getting Started

For API authentication to work, a Firebase service account key is required. Create a new project and obtain a key as described in the docs, saving it as config/firebase.json.

Docker

# Clone the repo
git clone https://github.com/chronhq/backend
cd backend

# Create env files, remember to update accordingly
cp django.env.sample django.env
cp postgres.env.sample postgres.env
cp mbtiles.env.sample mbtiles.env
cp auth.env.sample auth.env  # from console.firebase.com

# Build and start the docker containers
make run

# Navigate to http://localhost/
# 502 error means postgres is starting, try again in a few seconds

Local

# Clone the repo
git clone https://github.com/chronhq/backend
cd backend

# Create and activate virtual environment
virtualenv venv
source venv/bin/activate # *nix
venv/Scripts/activate # win
pip install -r config/requirements.txt

cd project
python manage.py runserver # must be executed from the project directory

Production Setup

make run_prod can be used to configure the containers for a production setup.

About

Backend for database. Python, Django, Postgres + PostGIS

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published