Note: On Windows, both projects need to be checked out with, git config core.autocrlf input or they won't build correctly.
One of our dependencies is @eurofurence/reg-component-library, which we only publish to the private GitHub packages
registry.
To configure access, obtain a GitHub personal access token with read:packages scope permissions. With that, do
echo "//npm.pkg.github.com/:_authToken=${GITHUB_TOKEN}" >> ~/.npmrc
npm install -g gatsby-cli
gatsby telemetry --disable
npm install
cp .example.env.development .env.development
Edit this new file and fill in the env vars with the test env information.
npm start
Then point your browser to http://localhost:8000/register
You can run locally together with one or more of the backend services (most likely you'll want at least reg-attendee-service and reg-payment-service).
See the instructions here, as well as the readme's of the backend services.
Then you can use the system exactly as it is installed on the server by pointing your browser to http://localhost:10000/register
This also lets you avoid any CORS issues because everything is coming from the same domain.
In gatsby-config.js, set the correct pathPrefix. Then do
PREFIX_PATHS=true npm run build
This will generate a full static version of the site into public, which you can then tar.gz and upload to the server
for roll-out with a script similar to this one (assuming you have ssh-agent running and have access):
# build application with prefix paths as configured
PREFIX_PATHS=true npm run build
# upload and roll out
tar czf public.tgz public
scp public.tgz [email protected]:projects/
ssh [email protected] -t "bash -l -c 'scripts/update-app.sh'"
rm -f public.tgz