-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update install page with link to binaries #34
Comments
we can have them ready anytime you like, we just need to decide how often to rebuild them and how. If it's manual, we can easily build and push to www.cockroachlabs.com. If it's automated, we may be better off putting them in AWS. |
Should we distribute i386 and amd64 binaries? On Mon, Feb 8, 2016 at 2:21 PM, marc notifications@github.com wrote:
|
According to a note in CONTRIBUTING.md, we only support 64-bit builds. I'm not sure what the issue is, but it seems safe to go 64-bit only. |
Good to know we're ready whenever. @jess-edwards and I are planning to do a soft-release of the docs as early as next week, so can you guys choose a location, push them there, and post links here by Monday or Tuesday? |
ok, finally getting back to this. I'll be tweaking various S3 paths and naming schemes, so I'll probably be breaking some of my nightly scripts, but here's a proposal for the ultimate goal:
The download page will simply link to the fixed binary name (the redirect should take care of going to the right one). eg: |
ok, the redirect doesn't work so well with cloudfront. I may have to write to the final filename right away (eg: upload directly to s3://binaries.cockroachdb.com/cockroach.linux-amd64.tgz). The only issue here is what happens when concurrent circle-ci runs step all over each other. S3 will usually drop one of them but can sometimes result in an empty file. |
@jseldess: the binaries are up and will be refreshed for every commit to master that passes the tests. |
Excellent. Thanks very much, @mberhault! I'll add those links in today. |
we'll also need to change the instructions. the downloads tar gzipped tarballs, so people will need to do the following:
no chmod needed. |
@mberhault, when I extract the tarball, the directory created is called @bdarnell suggested that we should be doing the opposite: extracting the tarball should create a directory with the same name as the tarball, but the binary in that directory should just be |
ok. will do. |
Renamed the binary per suggestions. We now have: Leaving open since this about docs, not the binaries themselves. |
oh, and it may take a little while for the new binaries to be effective, cloudfront caching is a little pesky. |
Thanks, Marc. |
Jseldess/download binary - fixes issue #34
Resolved with PR #113 |
Clarified starter upgrades commands.
For OS X and Linux, Download the Binary needs a valid link.
@bdarnell, @mberhault: When do you think OS X and Linux binaries will be ready, and where will we host them for user download?
The text was updated successfully, but these errors were encountered: