5.0 KiB
Building from Source
Pre-requisites
- Go
- GolangCI - A meta-linter which runs several linters in parallel
- To install, follow the local installation instructions
- Yarn - Yarn package manager
- Run
yarn install --frozen-lockfile
in thestash/ui/v2.5
folder (before running make generate for first time).
- Run
NOTE: You may need to run the go get
commands outside the project directory to avoid modifying the projects module file.
Environment
Windows
- Download and install Go for Windows
- Download and extract MingW64 (scroll down and select x86_64-posix-seh, dont use the autoinstaller it doesnt work)
- Search for "advanced system settings" and open the system properties dialog.
- Click the
Environment Variables
button - Under system variables find the
Path
. Edit and addC:\MinGW\bin
(replace with the correct path to where you extracted MingW64).
- Click the
NOTE: The make
command in Windows will be mingw32-make
with MingW. For example make pre-ui
will be mingw32-make pre-ui
macOS
- If you don't have it already, install the Homebrew package manager.
- Install dependencies:
brew install go git yarn gcc make node ffmpeg
Linux
Arch Linux
- Install dependencies:
sudo pacman -S go git yarn gcc make nodejs ffmpeg --needed
Ubuntu
- Install dependencies:
sudo apt-get install golang git gcc nodejs ffmpeg -y
- Enable corepack in Node.js:
corepack enable
- Install yarn:
corepack prepare yarn@stable --activate
Commands
make pre-ui
- Installs the UI dependencies. Only needs to be run once before building the UI for the first time, or if the dependencies are updatedmake generate
- Generate Go and UI GraphQL filesmake fmt-ui
- Formats the UI source codemake ui
- Builds the frontendmake build
- Builds the binary (make sure to build the UI as well... see below)make docker-build
- Locally builds and tags a complete 'stash/build' docker imagemake lint
- Run the linter on the backendmake fmt
- Rungo fmt
make it
- Run the unit and integration testsmake validate
- Run all of the tests and checks required to submit a PRmake server-start
- Runs an instance of the server in the.local
directory.make server-clean
- Removes the.local
directory and all of its contents.make ui-start
- Runs the UI in development mode. Requires a running stash server to connect to. Stash server port can be changed from the default of9999
using environment variableVITE_APP_PLATFORM_PORT
. UI runs on port3000
or the next available port.
Local development quickstart
- Run
make pre-ui
to install UI dependencies - Run
make generate
to create generated files - In one terminal, run
make server-start
to run the server code - In a separate terminal, run
make ui-start
to run the UI in development mode - Open the UI in a browser
http://localhost:3000/
Changes to the UI code can be seen by reloading the browser page.
Changes to the server code requires a restart (CTRL-C
in the server terminal).
On first launch:
- On the "Stash Setup Wizard" screen, choose a directory with some files to test with
- Press "Next" to use the default locations for the database and generated content
- Press the "Confirm" and "Finish" buttons to get into the UI
- On the side menu, navigate to "Tasks -> Library -> Scan" and press the "Scan" button
- You're all set! Set any other configurations you'd like and test your code changes.
To start fresh with new configuration:
- Stop the server (
CTRL-C
in the server terminal) - Run
make server-clean
to clear all config, database, and generated files (under.local/
) - Run
make server-start
to restart the server - Follow the "On first launch" steps above
Building a release
- Run
make pre-ui
to install UI dependencies - Run
make generate
to create generated files - Run
make ui
to compile the frontend - Run
make build
to build the executable for your current platform
Cross compiling
This project uses a modification of the CI-GoReleaser docker container to create an environment
where the app can be cross-compiled. This process is kicked off by CI via the scripts/cross-compile.sh
script. Run the following
command to open a bash shell to the container to poke around:
docker run --rm --mount type=bind,source="$(pwd)",target=/stash -w /stash -i -t stashapp/compiler:latest /bin/bash
Profiling
Stash can be profiled using the --cpuprofile <output profile filename>
command line flag.
The resulting file can then be used with pprof as follows:
go tool pprof <path to binary> <path to profile filename>
With graphviz
installed and in the path, a call graph can be generated with:
go tool pprof -svg <path to binary> <path to profile filename> > <output svg file>