On a new installation, Stash will default to 'blobs' (which relative to the CWD of /, becomes '/blobs').
In our recommended installation, this is NOT mapped and as a result will NOT be persistent across the container being removed or updated.
So by default, we are populating blob data which will be deleted, likely leaving to some confused new users.
This should also be noted for existing installations to make this a persistent path.
* Bump Go to 1.17, refactor build/x86_64 Dockerfile to make better use of multi-stage
* Bump to 1.17 from 1.16
* Bump packr version, provide needed legacy env var
* Add apple silicon support, fix macos build chain
* Update unused travis ci
* Fix to avoid creating generated folder inside data folder.
This Fix is to avoid that ```generated``` folder will be created inside the movie /video files forder which leads to see the generated clips of the movies in SCENES.
* Update docker-compose.yml
Added generated volume , removed transcoded as it wasn't needed.
All volumes remain with relative paths as suggested.
Co-authored-by: bnkai <48220860+bnkai@users.noreply.github.com>
* Stealing good ideas from DockSTARTer
* Pushing an example WIP
* Actually ran and debugged container and it works now.
TODO: We need configurability for this to be more useful.
* Prepped docker-compose for if we get these envvars coded in.
* Removed unnecessary start.sh
* Removed env.example
* Fixed internal directory to conform more.
Resovles https://github.com/stashapp/stash/pull/44#issuecomment-485060195
* Logging options need quotes.
* I decided to use architecture tags since go-releaser can do multiple architectures.
* Compose version version: '3.4'
* No relative pathing on container side of volume
ChilledSlim