Skip to content
Implementing what I've learned and trying new things in an app for managing teams
TypeScript Python CSS Shell HTML Dockerfile JavaScript
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


🎺 🎺 🎺

An app for teams, allowing them to write and share meeting minutes.

I started this project to implement what I've learned over the past few years, and to explore new technologies and libraries that interest me.


You can find instructions on setting up the frontend and backend for local development here, as well as a rough guide to the codebase.

Contributions are welcome! You can make a contribution by forking this repository, committing your changes on a new branch and opening a pull request. Please be respectful in your interactions with other contributors.

Alternatively, you can open an issue if you find a problem that needs to be fixed.


The frontend is a React application.

Setting up the frontend

To develop on the frontend you will need Yarn (as well as Node).

To set up the frontend, install its dependencies and start the development server.

cd mellophone/frontend
yarn start

You'll probably want to have the backend running at the same time as well. You can run this is in a new terminal window. You will need to have Docker Compose installed. If you'd like you can read more about the how the backend is set up.

# Initialise and start the backend Django/Postgres servers
docker-compose run dev pipenv sync
docker-compose run dev pipenv run migrate
docker-compose up dev

Below are some common commands you might run. Remember you will need to be in the frontend root (/mellophone/frontend). You might wish to consult the yarn docs or the package.json itself

Command Action
yarn Install dependencies (and ensure all dependencies are up to date with yarn.lock)
yarn start Run a development server (located at http://localhost:300)
yarn build Create a production build (if you want to run the backend with a static frontend)
yarn test Run tests against the frontend code
yarn lint Run code style and type checks
yarn lint --write Run code style and type checks, fixing where possible

The frontend codebase

The frontend is bootstrapped using Create React App and is located in the mellophone/frontend directory.

Most components are written using TypeScript and styled with CSS Modules.

  • src/
    Frontend code is housed here. You can see the React root here (App.tsx, index.tsx) and files used in development (setupTests.ts, setupProxy.ts types.ts).
    • components/
      React components such as buttons, inputs and forms are here.
      Components like <Button/> and <Input/> extends to their standart HTML counterparts, adding styling and making sure they are labelled.
      More complex components might implement a form or display information, depending on props for the data and callbacks (ie a network request, Redux action).
    • ducks/
      The application's Redux store, roughly following the re-ducks pattern.
    • network/
      Network requests to the backend are abstracted as async functions.
      These bundles of requests are loaded into the app's context and can be accessed with the useNetwork() hook. This context can be replaced in a testing runtime.
    • pages/
      These are higher level components that integrate components, ducks, and network logic into page-level views.
      Each component in this folder corresponds to a route within the application, like /account or /teams/123/meetings.
    • utils/
      General purpose functions that don't belong to any of the above directories. See each invidual files for their purposes.

Tests are run using Jest with React Testing Library, and are colocated with their applicable file in a __tests__ subdirectory.
If you're testing components from the pages/ directory, you can use src/utils/TestRenderer.tsx to replace network functions or to set the Redux store to a particular state.


The backend is a Django application.

Setting up the backend

To set up the backend you will need Docker Compose installed.

Before starting the development server, you will need to install dependencies and run database migrations.
To save the hassle of running/compiling the frontend, you can run the scripts/ script to have it installed for you.

docker-compose run dev pipenv sync --dev
docker-compose run dev pipenv run migrate
docker-compose run dev sh scripts/

You can now start up the development server.

docker-compose run dev

Below are some common commands you might run. You might also wish to consult the pipenv docs and the Pipfile itself for further information.

Make sure you're running your commands inside the development container (docker-compose run dev ${YOUR COMMAND}).

Command Action
pipenv sync Install runtime dependencies (and ensure they are up to date with Pipfile.lock)
pipenv sync --dev As above, but also include development dependencies, such as linting/testing libraries
pipenv run migrate Apply new migrations to the database (must be running at this time)
pipenv run server Run the Django development server (located at http://localhost:8000)
pipenv run lint Format backend code
pipenv run lint --check Check backend code formatting
pipenv run test-unit Run tests against the backend
pipenv run test-e2e Run an end-to-end test using Selenium

The backend codebase

This repository is set up as a Django project, with the backend API as the mellophone/backend application.

  • The root directory how many default files for Django, like the database tables ( and the API routes (
    • controllers
      Defines the behaviour for a certain route. They interpret parameters/data from the incoming request and call the applicable services.
    • migrations
      Holds Django-defined instructions for migrating/rolling back the database schema.
    • services
      Defines logic for accessing with application objects (users, teams, meetings).
      To relate it to the controller-service-repository pattern, these mix the service and repository layer.
      Try to keep logic for accessing Django models to an appropriately named file (for example, services/ is responsible for the User model).

Tests for the backend at the moment only focus on the services, and are located in the services/tests directory.
I'll be looking at adding tests in future for API routes in future, but for now there is only the basic end-to-end Selenium test in mellophone/

You can’t perform that action at this time.