# Setting up RomM for development ## Option 1: Using Docker If you prefer to use Docker for development, you can set up RomM using the provided Docker Compose configuration. This method simplifies the setup process by encapsulating all dependencies within Docker containers. ### Environment setup #### Create the mock structure with at least one rom and empty config for manual testing ```sh 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/config.yml ``` #### Copy env.template to .env and fill the variables ```sh cp env.template .env ``` ```dotenv ROMM_BASE_PATH=/app/romm DEV_MODE=true ``` #### Build the image ```sh docker compose build # or `docker compose build --no-cache` to rebuild from scratch ``` #### Spin up the Docker containers ```sh docker compose up -d ``` And you're done! You can access the app at `http://localhost:3000`. Any changes made to the code will be automatically reflected in the app thanks to the volume mounts. ## Option 2: Manual setup ### Environment setup #### - Create the mock structure with at least one rom and empty config for manual testing ```sh 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/config.yml ``` #### - Copy env.template to .env and fill the variables ```sh cp env.template .env ``` #### - Install system dependencies ```sh # https://mariadb.com/docs/skysql-previous-release/connect/programming-languages/c/install/#Installation_via_Package_Repository_(Linux): sudo apt install libmariadb3 libmariadb-dev libpq-dev # Build and configure RAHasher (optional) # This is only required to calculate RA hashes # Users on macOS can skip this step as RAHasher is not supported git clone --recursive https://github.com/RetroAchievements/RALibretro.git cd ./RALibretro git checkout 1.8.0 git submodule update --init --recursive sed -i '22a #include ' ./src/Util.h make HAVE_CHD=1 -f ./Makefile.RAHasher cp ./bin64/RAHasher /usr/bin/RAHasher ``` #### - Install python dependencies You'll need uv installed ```sh curl -LsSf https://astral.sh/uv/install.sh | sh ``` Then create the virtual environment and install the dependencies using uv: ```sh uv venv source .venv/bin/activate uv sync --all-extras --dev ``` #### - Spin up the database and other services ```sh docker compose up -d ``` #### - Run the backend _Migrations will be run automatically when running the backend._ ```sh cd backend uv run python3 main.py ``` ### Setting up the frontend #### - Install node.js dependencies ```sh cd frontend # npm version >= 9 needed npm install ``` #### - Create symlink to library and resources ```sh mkdir assets/romm ln -s ../romm_mock/resources assets/romm/resources ln -s ../romm_mock/assets assets/romm/assets ``` #### - Run the frontend ```sh npm run dev ``` ## Setting up the linter We use [Trunk](https://trunk.io) for linting, which combines multiple linters and formatters with sensible defaults and a single configuration file. You'll need to install the Trunk CLI to use it. ### - Install the Trunk CLI ```sh curl https://get.trunk.io -fsSL | bash ``` Alternative installation methods can be found [in their docs](https://docs.trunk.io/check/usage#install-the-cli). On commit, the linter will run automatically. To run it manually, use the following commands: ```sh trunk fmt trunk check ``` **Failing to install and run the linter will result in a failed CI check, which won't allow us to merge your PR.** ## Test setup ### - Create the test user and database with root user ```sh docker exec -i romm-db-dev mariadb -uroot -p < backend/romm_test/setup.sql ``` ### - Run tests _Migrations will be run automatically when running the tests._ ```sh cd backend # path or test file can be passed as argument to test only a subset uv run pytest [path/file] # or run the following command to run all tests # the -vv switch increases the verbosity of the output, providing more detailed information during test execution. uv run pytest -vv ```