chore: new build process

[hacdias]

Please read #399 before any of the following conversations.

[hacdias]

It should be everything on dist, even the checksums and *.zip.

[eine]

Sure. I replaced it with dist/*.*. This will include CHANGELOG.md and config.yaml too. Is it ok?

$ ls dist/*.*
dist/CHANGELOG.md                        dist/linux-armv5-filebrowser.tar.gz
dist/config.yaml                         dist/linux-armv6-filebrowser.tar.gz
dist/darwin-amd64-filebrowser.tar.gz     dist/linux-armv7-filebrowser.tar.gz
dist/dragonfly-amd64-filebrowser.tar.gz  dist/netbsd-386-filebrowser.tar.gz
dist/filebrowser_0.0.0_checksums.txt     dist/netbsd-amd64-filebrowser.tar.gz
dist/freebsd-386-filebrowser.tar.gz      dist/openbsd-386-filebrowser.tar.gz
dist/freebsd-amd64-filebrowser.tar.gz    dist/openbsd-amd64-filebrowser.tar.gz
dist/linux-386-filebrowser.tar.gz        dist/solaris-amd64-filebrowser.tar.gz
dist/linux-amd64-filebrowser.tar.gz      dist/windows-386-filebrowser.zip
dist/linux-arm64-filebrowser.tar.gz      dist/windows-amd64-filebrowser.zip

$ tree dist
dist
├── CHANGELOG.md
├── config.yaml
├── darwin-amd64-filebrowser.tar.gz
├── dragonfly-amd64-filebrowser.tar.gz
├── filebrowser_0.0.0_checksums.txt
├── freebsd-386-filebrowser.tar.gz
├── freebsd-amd64-filebrowser.tar.gz
├── linux-386-filebrowser.tar.gz
├── linux-amd64-filebrowser.tar.gz
├── linux-arm64-filebrowser.tar.gz
├── linux-armv5-filebrowser.tar.gz
├── linux-armv6-filebrowser.tar.gz
├── linux-armv7-filebrowser.tar.gz
├── netbsd-386-filebrowser.tar.gz
├── netbsd-amd64-filebrowser.tar.gz
├── openbsd-386-filebrowser.tar.gz
├── openbsd-amd64-filebrowser.tar.gz
├── solaris-amd64-filebrowser.tar.gz
├── windows-386-filebrowser.zip
├── windows-amd64-filebrowser.zip
├── darwin_amd64
│   └── filebrowser
├── dragonfly_amd64
│   └── filebrowser
├── freebsd_386
│   └── filebrowser
├── freebsd_amd64
│   └── filebrowser
├── linux_386
│   └── filebrowser
├── linux_amd64
│   └── filebrowser
├── linux_arm_5
│   └── filebrowser
├── linux_arm_6
│   └── filebrowser
├── linux_arm64
│   └── filebrowser
├── linux_arm_7
│   └── filebrowser
├── netbsd_386
│   └── filebrowser
├── netbsd_amd64
│   └── filebrowser
├── openbsd_386
│   └── filebrowser
├── openbsd_amd64
│   └── filebrowser
├── solaris_amd64
│   └── filebrowser
├── windows_386
│   └── filebrowser.exe
└── windows_amd64
    └── filebrowser.exe

[eine]

The current tagging/CI proposal is as follows:

• Some maintainer/user needs to manually tag a commit in filebrowser/frontend (which is a submodule of filebrowser/filebrowser).
• Then, he/she executes build/release.sh in filebrowser/filebrowser:
  • If the requested tag/semver exists in frontend, it is checked out. If not, it exits.
  • The version is substituted in filebrowser/filebrowser/filebrowser.go.
  • A commit is added.
  • The commit is tagged.
  • The tag is pushed.

When a tag is pushed to filebrowser/filebrowser, if the test stage in travis-ci is successful, a deployment stage is executed. In this one, the release binaries are built with goreleaser and rice-box is pushed to filebrowser/caddy with build/push_ricebox.sh:

• A branch named update-rice-box is created from master.
• assets/rice-box.go is replaced.
• A commit is added.
• The commit is tagged.
• The branch and tag are pushed to filebrowser/caddy.

A maintainer is required in order to merge/squash/rebase this single commit to master.

---

Furthermore, a PR could be automatically created by using the GitHub REST API: https://developer.github.com/v3/pulls/#create-a-pull-request. However, although creating the PR is quite easy, handling the authentication seems to be not so straightforward: https://developer.github.com/v3/auth/. Therefore, I prefer to keep it apart from this PR.

---

@hacdias, please let know if you find any pending work to be done here.

[hacdias]

Awesome!

[hacdias]

🚀🚀 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 🚀🚀

Huge thanks! 😄

[hacdias]

@1138-4eb could you just take a look at why it failed deploying? https://travis-ci.com/filebrowser/filebrowser/jobs/138442868#L584

[eine]

Sure. I'll check it now.

EDIT

It is fixed. It was a quite stupid error on my side: travis-ci/travis-ci#7641