Manually tag the commit that is going to be used in filebrowser/frontend.
When the tag is pushed, Travis will detect it and execute the following procedures:
Run through the linters to check if the code is alright.
Build the frontend and the backend, generating
If the commit is not tagged, we will push the latest
filebrowser/filebrowser docker image to hub.docker.com/r/filebrowser/filebrowser.
If the commit is tagged, then:
Build the release artifacts for all supported platforms and a new docker image (see
.goreleaser.yml for more information).
The artifacts are published to GitHub Releases.
The tagged docker image is published to hub.docker.com/r/filebrowser/filebrowser.
rice-box.go is committed, tagged and then pushed to a branch on filebrowser/caddy which must then be merged by a maintainer.