Skip to content

KSG-IT/ksg-nett

This branch is 1 commit ahead of, 51 commits behind develop.

Folders and files

NameName
Last commit message
Last commit date
Nov 2, 2023
Aug 5, 2022
Nov 2, 2023
Nov 2, 2023
Mar 10, 2023
Jan 3, 2019
Nov 9, 2023
Nov 9, 2023
Aug 2, 2022
Jan 27, 2023
Dec 4, 2022
Nov 9, 2023
Jan 6, 2023
Jan 15, 2023
Aug 19, 2023
Jul 13, 2023
Jul 27, 2023
Jan 3, 2023
Aug 16, 2023
Oct 31, 2023
Jul 20, 2021
Feb 6, 2021
Feb 28, 2021
Nov 9, 2023
Mar 8, 2018
May 2, 2021
Apr 2, 2022
Aug 18, 2017
Aug 16, 2023
Aug 2, 2022
Feb 15, 2018
Jan 12, 2023
Dec 3, 2022
Dec 3, 2022
Aug 21, 2017
Nov 29, 2023
Nov 29, 2023
Jun 15, 2022
Sep 28, 2022
Nov 4, 2022
Oct 16, 2022
Oct 15, 2020

Repository files navigation

KSG-nett backend

Build Status

Overview

This repository contains the source code for KSG's web page. The project is written in Django exposing a graphQL API using graphene. KSG-nett is a two-part webapplication, this being the backend and requires a fucntioning frontend instance to be running. Follow the link and the quickstart section over there in addition to here to get everything up and running.

Quickstart

Dependencies are managed with poetry. To run the code do the following

  1. Make sure you have python 3.8 available on the computer
  2. install poetry on your computer
  3. Install Weasyprint (make sure to follow instructions thoroughly before going on to the next step)
  4. Clone and Navigate to this folder
  5. Install the dependencies by running poetry install
  6. Migrate the database with poetry run python manage.py migrate
  7. Run the projects by running poetry run python manage.py runserver

Other dependencies

We use black as a code formatter. We enforce this with the use pre-commit. Make sure to have this installed locally otherwise code formatting will not be automaically applied.

Branch formatting guidelines

Usually tasks are assigned through Shortcut stories, with a story type which is either a feature, bug or chore, and a story id. This is used to track progress on the task throughout development. A given branch will automatically get tracked if the branch includes sc-<story-id> anywhere in its name.

  • Our branches follows a convention of story-type/sc-<story-id>/branch-name

So a story which is a bug type, with an id of 666 and a title of "Dashboard renders wrong data" would be named bug/sc-666/dashboard-renders-wrong-data or similar.