Create .env files for backend and frontend. See examples and ask your local boffin for details.
Current node version is 18.16.0.
Run npm ci in the each of the root, backend and frontend directories to install dependencies.
Create separate shells for the database container, backend and frontend:
cd backend
docker-compose upcd frontend
npm run devcd backend
npm run migrate
npm run devIf the database doesn't seem to do anything, ie. no messages after the initial ones after running docker compose up and the database queries are not getting through, run docker compose down and try again. You can always run the database container in detached mode (-d) but then you won't see the logs live.
If you have used a development database with an older version of PostgreSQL and you want to keep your data, you will need to migrate it to the new version. See here for instructions.
Run npm run prettier in the root directory before committing. The commit runs hooks to check this as well as some linters, type checks etc.
Using pre-built librdkafka to speed up backend development
By default, node-rdkafka builds librdkafka from the source. This can take minutes on a bad day and can slow development down quite considerably, especially when you're working with different branches with different dependencies and need to run npm ci often. However, there's an option to use the version installed locally.
Do this in some other directory than the project one:
wget https://github.com/edenhill/librdkafka/archive/v2.0.2.tar.gz -O - | tar -xz
cd librdkafka-2.0.2
./configure --prefix=/usr
make && make installYou may have to do some of that as root. Alternatively, you can install a prebuilt package - see here for more information.
Set the env BUILD_LIBRDKAFKA=0 when doing npm ci or similar on the backend to skip the build.