Skip to content

Latest commit

 

History

History
212 lines (122 loc) · 7.29 KB

CONTRIBUTING.md

File metadata and controls

212 lines (122 loc) · 7.29 KB
Raw

Contributing to the OpenUnited Platform

We are thrilled that you are considering contributing to the OpenUnited platform. We welcome your ideas, code, and enthusiasm.

In addition to reading this guide and getting your local development environment setup, please also join us on Discord.

This guide is designed to help you understand how you can contribute to OpenUnited effectively, and it outlines the best practices and expectations we have for our contributors.

Setting Up Your Development Environment

Firstly, please fork this repo to your own account. Then, git clone your forked version of the repo locally and change to the platform directory and copy .env.example to .env.

git clone [email protected]:<your-username>/platform.git
cd platform
cp .env.example .env

Installing Makefile

Install Makefile e.g. Makefile for mac

Database Set Up

We recommend using PostgreSQL for your database.

By default, the OpenUnited platform will look for a database named ou_db and use postgres as both the username and password. This is set in your .env file and can be overriden of course.

The make setup command you run later on will create this database for you automatically by calling the reset_database.py script.

In case you don't already have PostgreSQL running locally, the end of this guide you can see some helpful tips for installing PostgreSQL with and without Docker.

Running the OpenUnited Platform

You need to set a value for DJANGO_SECRET_KEY in your .env file, this is used for cryptographic signing.

You can generate a unique value for DJANGO_SECRET_KEY using this website and set the value on the .env file.

After that, run the following commands:

python3 -m venv env
source env/bin/activate
pip install -r requirements.txt
export DJANGO_SETTINGS_MODULE=apps.common.settings.development

For end-to-end tests, the OpenUnited platform uses Playwright. If you don't have Playwright installed, please do so. See installing Playwright

Setup the database and load fixtures / sample data:

make setup

Finally, start the server:

make run

Then navigate to: http://localhost:8000/ in your browser.

Customizations

If you want to extend your local development, create a local.py in apps/common/settings. Import base.py or development.py and make sure to export it:

export DJANGO_SETTINGS_MODULE=apps.common.settings.local

It is advised to put this line into your bash configuration.

How to Make a Contribution

Before moving on, please make sure that the project is run locally on your machine without any problem.

Here's a quick rundown on how you can make a contribution:

  1. Find an issue that you are interested in addressing or a feature that you would like to add.
  2. Create a new branch for your fix using git checkout -b branch-name-here
  3. Make the appropriate changes for the issue you are trying to address or the feature that you want to add.
  4. Use git add insert-paths-of-changed-files-here to add the file contents of the changed files.
  5. Commit your changes. The commit messages should follow this format.
  6. Push the changes to the remote repository using git push origin branch-name-here and submit a pull request.
  7. Wait for the pull request to be reviewed by a maintainer.
  8. Make changes to the pull request if the reviewing maintainer recommends them.
  9. Celebrate your success after your pull request is merged!

Making Changes

Every change that is made needs to be formatted according to Black. You can run black . before pushing your changes but it is recommended to use an extenstion that runs this command every time you save a file. For VS Code, you can install the extension in here.

  • If your changes introduces a new feature, make sure to include the necessary tests such as unit tests, integration tests etc.
  • If your changes modifies the existing implementation, make sure to extend and/or modify the tests.
  • If your changes requires an update on the documentation, please update the documentation accordingly.

NOTE: If your work includes changes in the front-end, make sure to run watch_css_changes.sh script during the development. Otherwise, the styles might not apply.

PostgreSQL Without Docker

Before cloning and running the project, make sure to have PostgreSQL install on your machine. You can either download and install PostgreSQL or you can use the Docker image of PostgreSQL.

You can download the latest version of PostgreSQL here. Follow the instructions and install it.

Using Docker for PostgreSQL

You can also pull the image of PostgreSQL. It is assumed that you have Docker install on your machine. After that, you can pull it with this command:

docker pull postgres

Running OpenUnited with Docker

Make sure you have docker install on your machine.

cp .env.example .env
cp docker.env.example docker.env

# create a network named as platform_default
docker network create platform_default

docker compose --env-file docker.env up --build

Run the tests:

docker-compose --env-file docker.env exec platform sh -c "python manage.py test"

Then navigate to: http://localhost:8000/ in your browser.

Notes: Docker Networking

  • For linux machine you can set the network_name=host in docker.env
  • For docker desktop in Mac or Windows you can set the custom network network_name=custom_network_name in docker.env. (N.B. If you facing issue like network custom_network_name not found, you have to create it like docker network create custom_network_name )

Not working? Please double-check your settings and if you still continue to experience problems, create an issue detailing your problem.

Docker Compose Notes

  • If you want to have auto-reload during development and use ipdb/pdb/breakpoint add following to docker-compose.yml > services > platform
services:
  platform:
    # ...
    volumes:
      - .:/code/
    # ...
    stdin_open: true
    tty: true
  • After adding ipdb/pdb/breakpoint, you can check container id by docker ps and attach it to debug docker attach <container-id>

Make commands

  • Install Makefile e.g. Makefile for mac

  • Run the server

    make run

  • Run tests

    make test

  • Run tests with coverage

    make cov

  • Run tests with HTML coverage

    make cov_html

  • Run migrations and migrate

    make migrate

  • Create superuser

    make admin

  • Seed data to specific app

    make seed app="app_name"

  • To setup the app with initial data from fixtures. Note that this command will reset the database.

    make setup

  • Dump data from the database to the application fixture.

    make dumpdata

  • Generate the tailwindcss

    make tailwindcss

  • Format the fixtures located in each app.

    make format_fixtures

Pre-commit installation

  • Install pre-commit hook

    pre-commit install

    Result: pre-commit installed at .git/hooks/pre-commit