romm/DEVELOPER_SETUP.md

Environment setup

Mocking RomM structure

- Create the mock structure with at least one rom and empty config for manual testing

mkdir -p romm_mock/library/roms/switch
touch romm_mock/library/roms/switch/metroid.xci
mkdir -p romm_mock/resources
mkdir -p romm_mock/assets
mkdir -p romm_mock/config
touch romm_mock/config.yml

Setting up the backend

- Copy env.template to .env and fill the variables

cp env.template .env

- Install system dependencies

# https://mariadb.com/docs/skysql-previous-release/connect/programming-languages/c/install/#Installation_via_Package_Repository_(Linux): 
sudo apt install libmariadb3 libmariadb-dev pipx

- Install python dependencies

You'll need poetry installed

https://python-poetry.org/docs/#installing-with-the-official-installer

WARNING: Until poetry 1.8.0 version is released, poetry needs to be installed with the new non-package-mode feature branch:

pipx install --suffix _npm git+https://github.com/radoering/poetry.git@non-package-mode

More info: https://github.com/python-poetry/poetry/pull/8650

Then create the virtual environment

# Fix disable parallel installation stuck: $> poetry_npm config experimental.new-installer false
# Fix Loading macOS/linux stuck: $> export PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring
poetry_npm install --sync

- Spin up mariadb in docker

docker-compose up -d

- Run the backend

*Migrations will be run automatically when running the backend.

cd backend
poetry_npm run python3 main.py

- Start a worker

cd backend
poetry_npm run python3 worker.py

Setting up the frontend

- Install node.js dependencies

cd frontend
# npm version >= 9 needed
npm install

- Create symlink to library and resources

mkdir assets/romm
ln -s ../backend/romm_mock/resources assets/romm/resources
ln -s ../backend/romm_mock/assets assets/romm/assets

- Run the frontend

npm run dev

Test setup

- Create the test user and database with root user

docker exec -i mariadb mariadb -u root -p<root password> < backend/romm_test/setup.sql

- Run tests

*Migrations will be run automatically when running the tests.

cd backend
# path or test file can be passed as argument to test only a subset
poetry_npm run pytest [path/file]