Build - huntrsoftware.com

Downloads are currently unavailable for local builds: Releases are built and published to the production site by hand until they can be worked into the automated deployment pipeline. Local builds produced by following this guide will be missing downloads.

Step 1 - Clone the site and all associated projects

Before you can build the huntrsoftware.com site, you need the project docs which aren't stored in the site repo; they need to be generated locally.

Clone the site and all associated Huntr Software projects.

git clone https://codeberg.org/HuntrSoftware/huntrsoftware-site.git
git clone https://codeberg.org/HuntrSoftware/Layers.git
git clone --recursive https://codeberg.org/HuntrSoftware/vortex.git
git clone --recursive https://codeberg.org/HuntrSoftware/docuriser.git
git clone https://codeberg.org/HuntrSoftware/fetch.git

mkdir nodeyou && cd nodeyou
git clone --recursive https://codeberg.org/HuntrSoftware/nodeyou.git
git clone https://codeberg.org/HuntrSoftware/nodeyou-api.git
git clone https://codeberg.org/HuntrSoftware/ny-service-agent.git
git clone https://codeberg.org/HuntrSoftware/ny-profile-api.git
cd ..

The site's Docuriser configuration expects the project directories in the following structure (the root somewhere/ directory can be any name, stored anywhere you like):

somewhere/
├── docuriser/
├── fetch/
├── huntrsoftware-site/
├── Layers/
├── nodeyou/
│   ├── nodeyou/
│   ├── nodeyou-api/
│   ├── ny-service-agent/
│   └── ny-profile-api/
└── vortex/

Step 2 - Build Docuriser

You can use either a separate copy of Docuriser (e.g. an installed binary) or build the cloned source copy.

cd docuriser
cmake -B build
cmake --build build -j
cd ..

It's safe to use the same source copy as the site build since Docuriser checks out each tagged project version in isolation, leaving the local source copies alone.

Step 3 - Build the site

Navigate to the site directory, build all projects, and finish with the site build.

Currently, the site itself, Fetch, and the node.you projects are all unreleased. For now, they are generated with the --working-tree flag.

cd huntrsoftware-site
../docuriser/bin/docuriser-cli build projects/layers/.docuriser-project
../docuriser/bin/docuriser-cli build projects/vortex/.docuriser-project
../docuriser/bin/docuriser-cli build projects/docuriser/.docuriser-project
../docuriser/bin/docuriser-cli build projects/site/.docuriser-project 0.0 --working-tree
../docuriser/bin/docuriser-cli build projects/fetch/.docuriser-project 0.0 --working-tree
../docuriser/bin/docuriser-cli build projects/nodeyou-app/.docuriser-project 0.0 --working-tree
../docuriser/bin/docuriser-cli build projects/nodeyou-api/.docuriser-project 0.0 --working-tree
../docuriser/bin/docuriser-cli build projects/nodeyou-service-agent/.docuriser-project 0.0 --working-tree
../docuriser/bin/docuriser-cli build projects/nodeyou-profile-api/.docuriser-project 0.0 --working-tree
../docuriser/bin/docuriser-cli site build .docuriser-site

After the site build processes, the output can be found under build/site/.