c91ffe1e58
* Add migration script for tag relations table * Expand hierarchical filter features Expand the features of the hierarchical multi input filter with support for using a relations table, which only has parent_id and child_id columns, and support adding an additional intermediate table to join on, for example for scenes and tags which are linked by the scenes_tags table as well. * Add hierarchical filtering for tags * Add hierarchical tags support to scene markers Refactor filtering of scene markers to filterBuilder and in the process add support for hierarchical tags as well. * List parent and child tags on tag details page * Support setting parent and child tags Add support for setting parent and child tags during tag creation and tag updates. * Validate no loops are created in tags hierarchy * Update tag merging to support tag hierarcy * Add unit tests for tags.EnsureUniqueHierarchy * Fix applying recursive to with clause The SQL `RECURSIVE` of a `WITH` clause only needs to be applied once, imediately after the `WITH`. So this fixes the query building to do just that, automatically applying the `RECURSIVE` keyword when any added with clause is added as recursive. * Rename hierarchical root id column * Rewrite hierarchical filtering for performance Completely rewrite the hierarchical filtering to optimize for performance. Doing the recursive query in combination with a complex query seems to break SQLite optimizing some things which means that the recursive part might be 2,5 second slower than adding a static `VALUES()` list. This is mostly noticable in case of the tag hierarchy where setting an exclusion with any depth (or depth: all) being applied has this performance impact of 2,5 second. "Include" also suffered this issue, but some rewritten query by joining in the *_tags table in one pass and applying a `WHERE x IS NOT NULL` filter did seem to optimize that case. But that optimization isn't applied to the `IS NULL` filter of "exclude". Running a simple query beforehand to get all (recursive) items and then applying them to the query doesn't have this performance penalty. * Remove UI references to child studios and tags * Add parents to tag export * Support importing of parent relationship for tags * Assign stable ids to parent / child badges * Silence Apollo warning on parents/children fields on tags Silence warning triggered by Apollo GraphQL by explicitly instructing it to use the incoming parents/children values. By default it already does this, but it triggers a warning as it might be unintended that it uses the incoming values (instead of for example merging both arrays). Setting merge to false still applies the same behaviour (use only incoming values) but silences the warning as it's explicitly configured to work like this. * Rework detecting unique tag hierarchy Completely rework the unique tag hierarchy to detect invalid hierarchies for which a tag is "added in the middle". So when there are tags A <- B and A <- C, you could previously edit tag B and add tag C as a sub tag without it being noticed as parent A being applied twice (to tag C). While afterwards saving tag C would fail as tag A was applied as parent twice. The updated code correctly detects this scenario as well. Furthermore the error messaging has been reworked a bit and the message now mentions both the direct parent / sub tag as well as the tag which would results in the error. So in aboves example it would now show the message that tag C can't be applied because tag A already is a parent. * Update relations on cached tags when needed Update the relations on cached tags when a tag is created / updated / deleted so these always reflect the correct state. Otherwise (re)opening a tag might still show the old relations untill the page is fully reloaded or the list is navigated. But this obviously is strange when you for example have tag A, create or update tag B to have a relation to tag A, and from tags B page click through to tag A and it doesn't show that it is linked to tag B. |
||
|---|---|---|
| .github | ||
| .idea | ||
| docker | ||
| docs | ||
| graphql | ||
| pkg | ||
| scripts | ||
| static | ||
| ui | ||
| vendor | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .goreleaser.yml | ||
| .gqlgenc.yml | ||
| .travis.yml.disabled | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| go.mod | ||
| go.sum | ||
| gqlgen.yml | ||
| main.go | ||
| main_test.go | ||
| revive.toml | ||
| tools.go | ||
README.md
Stash
Stash is a locally hosted web-based app written in Go which organizes and serves your porn.
- It can gather information about videos in your collection from the internet, and is extensible through the use of community-built plugins for a large number of content producers.
- It supports a wide variety of both video and image formats.
- You can tag videos and find them later.
- It provides statistics about performers, tags, studios and other things.
You can watch a SFW demo video to see it in action.
For further information you can read the in-app manual.
Installing stash
via Docker
Follow this README.md in the docker directory.
Pre-Compiled Binaries
The Stash server runs on macOS, Windows, and Linux. Download the latest release here.
Run the executable (double click the exe on windows or run ./stash-osx / ./stash-linux from the terminal on macOS / Linux) and navigate to either https://localhost:9999 or http://localhost:9999 to get started.
Note for Windows users: Running the app might present a security prompt since the binary isn't yet signed. Bypass this by clicking "more info" and then the "run anyway" button.
FFMPEG
If stash is unable to find or download FFMPEG then download it yourself from the link for your platform:
The ffmpeg(.exe) and ffprobe(.exe) files should be placed in ~/.stash on macOS / Linux or C:\Users\YourUsername\.stash on Windows.
Usage
Quickstart Guide
- Download and install Stash and its dependencies
- Run Stash. It will prompt you for some configuration options and a directory to index (you can also do this step afterward)
- After configuration, launch your web browser and navigate to the URL shown within the Stash app.
Note that Stash does not currently retrieve and organize information about your entire library automatically. You will need to help it along through the use of scrapers. The Stash community has developed scrapers for many popular data sources which can be downloaded and installed from this repository.
The simplest way to tag a large number of files is by using the Tagger which uses filename keywords to help identify the file and pull in scene and performer information from our stash-box database. Note that this data source is not comprehensive and you may need to use the scrapers to identify some of your media.
CLI
Stash runs as a command-line app and local web server. There are some command-line options available, which you can see by running stash --help.
For example, to run stash locally on port 80 run it like this (OSX / Linux) stash --host 127.0.0.1 --port 80
SSL (HTTPS)
Stash can run over HTTPS with some additional work. First you must generate a SSL certificate and key combo. Here is an example using openssl:
openssl req -x509 -newkey rsa:4096 -sha256 -days 7300 -nodes -keyout stash.key -out stash.crt -extensions san -config <(echo "[req]"; echo distinguished_name=req; echo "[san]"; echo subjectAltName=DNS:stash.server,IP:127.0.0.1) -subj /CN=stash.server
This command would need customizing for your environment. This link might be useful.
Once you have a certificate and key file name them stash.crt and stash.key and place them in the same directory as the config.yml file, or the ~/.stash directory. Stash detects these and starts up using HTTPS rather than HTTP.
Customization
Themes and CSS Customization
There is a directory of community-created themes on our Wiki, along with instructions on how to install them.
You can also make Stash interface fit your desired style with Custom CSS snippets and CSS Tweaks.
Support (FAQ)
Answers to other Frequently Asked Questions can be found on our Wiki
For issues not addressed there, there are a few options.
- Read the Wiki
- Check the in-app documentation (also available here
- Join the Discord server, where the community can offer support.
Compiling From Source Code
Pre-requisites
- Go
- Revive - Configurable linter
- Go Install:
go get github.com/mgechev/revive
- Go Install:
- Packr2 - Static asset bundler
- Go Install:
go get github.com/gobuffalo/packr/v2/packr2 - Binary Download
- Go Install:
- Yarn - Yarn package manager
- Run
yarn install --frozen-lockfilein thestash/ui/v2.5folder (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
macOS
TODO
Windows
- Download and install Go for Windows
- Download and install MingW
- Search for "advanced system settings" and open the system properties dialog.
- Click the
Environment Variablesbutton - Under system variables find the
Path. Edit and addC:\Program Files\mingw-w64\*\mingw64\bin(replace * with the correct path).
- Click the
NOTE: The make command in Windows will be mingw32-make with MingW.
Commands
make generate- Generate Go and UI GraphQL filesmake 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 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 fmt-ui- Formats the UI source code.make ui- Builds the frontend and the packr2 filesmake packr- Generate packr2 files (sub-target ofui. Use to regenerate packr2 files without rebuilding UI)make vet- Rungo vetmake lint- Run the lintermake fmt- Rungo fmtmake fmt-check- Ensure changed files are formatted correctlymake it- Run the unit and integration testsmake validate- Run all of the tests and checks required to submit a PRmake ui-start- Runs the UI in development mode. Requires a running stash server to connect to. Stash port can be changed from the default of9999with environment variableREACT_APP_PLATFORM_PORT.
Building a release
- Run
make generateto create generated files - Run
make uito compile the frontend - Run
make buildto 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 stashappdev/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>