Publish Linux packages to Packagecloud#13
Conversation
| formats: | ||
| - deb | ||
| - rpm | ||
| - apk |
There was a problem hiding this comment.
Packagecloud does not appear to accept Alpine packages. I therefore decided to just stop building them for now, as we have no good story for how to install them. Also, Alpine is not a very common distro outside of docker images (to my knowledge).
| go install github.com/timescale/tiger-cli/cmd/tiger@latest | ||
| ``` | ||
|
|
||
| ### Direct binary download |
There was a problem hiding this comment.
I decided to remove the "Direct binary download" section, as macOS binaries installed via this method will currently be quarantined and prevented from opening via Gatekeeper.
If/when we have code signing and notarization sorted out (see #11), we can consider bringing this option back. But I'd rather not encourage users to do it if it won't work on all operating systems.
cevian
left a comment
cevian
left a comment
There was a problem hiding this comment.
LGTM - one suggestion for manual install instructions in comments. I totally agree with the decision to make this a separate repo
2 participants
This is a follow-up to #9. It wires up the release pipeline to push Linux packages to a new
tiger-clirepo in Packagecloud. I decided to make a new repo, rather than reuse the existingtimescaledbrepo, because Tiger CLI seemed pretty distinct from TimescaleDB and the other related packages that are currently in there (and because I didn't want to start polluting that repo with my testing 😅). But I'm totally open to reusing the timescaledb repo if that's what people think is best (should be an easy swap) - just let me know.See the installation instructions in the README for information on how to configure the repository and install packages. Note that I have not yet tested this myself (I plan to test Ubuntu soon, but I don't have easy access to the other Linux distros at the moment).