Skip to content

AriHrannar/Politikus

Repository files navigation

Build Status

Django React/Redux Base Project

This repository includes a boilerplate project used for all Seedstars Labs applications. It uses Django as backend and React as frontend.

We build on the shoulders of giants with the following technologies:

Frontend

Backend

  • Django
  • Django REST framework Django REST framework is a powerful and flexible toolkit for building Web APIs
  • Django REST Knox Token based authentication for API endpoints
  • WhiteNoise to serve files efficiently from Django
  • Prospector a complete Python static analysis tool
  • Bandit a security linter from OpenStack Security
  • pytest a mature full-featured Python testing tool
  • Mock mocking and testing Library
  • Responses a utility for mocking out the Python Requests library

Readme Notes

  • If the command line starts with $, the command should run with user privileges
  • If the command line starts with #, the command should run with root privileges

Retrieve code

  • $ git clone https://github.com/seedstars/django-react-redux-base.git
  • $ cd django-react-redux-base
  • $ git submodule init
  • $ git submodule update
  • $ ./scripts/get_static_validation.sh

Remember that when you copy this repository for a new project you need to add the scripts external module using:

  • $ git submodule add https://github.com/Seedstars/culture-scripts scripts

NOTE: This is only needed in case you copy this code to a new project. If you only clone or fork the repository, the submodule is already configured

Installation

Main Project

We use Docker as a development environment. For production, we leave you to set it up the way you feel better, although it is trivial to extrapolate a production environment from the current docker-compose.yml.

Running

Run Docker development server

  • $ docker-compose up

Accessing a container

You can access shell in a container

  • $ docker exec -i -t <CONTAINER_NAME_OR_ID> /bin/bash

E.g.

  • $ docker ps # get the name from the list of running containers
  • $ docker exec -i -t djangoreactreduxbase_frontend_1 /bin/bash

Accessing the database

The database can be accessed @localhost:5433

  • $ psql -h localhost -p 5433 -U djangoreactredux djangoreactredux_dev

Testing

To make sure the code respects all coding guidelines you should run the statics analysis and test scripts before pushing any code.

Frontend (javascript tests)

  • $ ./scripts/test_local_frontend.sh

Backend (django/python tests)

  • $ docker exec -i -t djangoreactreduxbase_backend_1 /bin/bash scripts/test_local_backend.sh

Static analysis

Frontend (javascript static analysis)

  • $ ./scripts/static_validate_frontend.sh

Backend (django/python static analysis)

  • $ docker exec -i -t djangoreactreduxbase_backend_1 /bin/bash scripts/static_validate_backend.sh

Screenshots

Here are some screenshots of the boilerplate project.

Screenshot01

Screenshot02

Gotchas

  • This project uses NodeJS v6.x (stable) and the corresponding version of npm
  • The npm development server takes longer than the django server to start, as it has to install the npm dependencies (if not already installed) and fire webpack. This means that after the django server starts, you should wait that webpack finishes compiling the .js files.
  • If your IDE has builtin language support for python with auto-imports (e.g. PyCharm), you can create a virtualenv and install the py-requirements.
  • If you are annoyed by docker creating files belonging to root (which is Docker's intended behaviour), you can run # chown -hR $(whoami) . before firing up the server.
  • While testing the backend, if you have a local virtualenv, you can run the static validation without running a docker container.
  • While testing the backend, if you have a local virtualenv and a local database configured with the dev settings, you can run the tests without running a docker container.

Contributing

We welcome contributions from the community, given that they respect these basic guidelines:

  • All Tests & Static Analysis passing;
  • 100% code coverage;

Prior to any pull-request, we advise to open an issue. This is because, although we are happy to merge your code, we must make sure the changes don't impact our way of doing things, thus resulting on a declined PR, and your time wasted.

If you want to tackle any open issue, well..... Just go for it! :)