It's a bit odd because these binaries are different than what you get from our releases.

These binaries don't embed the site (which isn't a biggie), but more importantly, aren't signed. This is particularly terrible for macOS users, who will get a warning that pops up essentially claiming this is a virus.

@kylecarbs@deansheather I recall there being a limitation with regard to signing the slim binaries in the build process. Was this arcodesign limitation and can we work around it?

So I have an idea but perhaps this can't work for some reason I'm not aware of:

1. Build slim binary for darwin (like normal)
2. Sign the binary
3. Use Go(!) to create a zip (archive/zip) of the darwin binary
4. Sign and notarize the zip file (+ store xattrs generated on the zip?)
5. Delete the zip
6. Zstd compress slim binaries (like normal)
7. Allow requesting/bin/coder-darwin-arm64.zip which transparently compresses the binary (again, using Go for reproducible bitstream), if needed attach xattrs

Perhaps xattrs aren't needed, in which case that part can be ignored.

That sounds pretty complicated. We should just link to the GitHub release page instead and hide this link if it's a dev build.

Users shouldn't be using the binaries we include in the server as they are not fully featured.

I've read your linked issue and agree that this is a good usecase for this, but I don't think this should be merged without changes to slim binaries to differentiate them from full server binaries. I will open a PR today to:

• hide theserver command on slim binaries
• mention slim binary in the version command output
• replace theserver command with a command that prints an error

Ideally though we should just separate the CLI binary from the server binary like I suggested in#3188

Deferring my review to either@kylecarbs@deansheather or@mafredri

I'll review this after I merge#5747

I liked the idea, but maybe, we could simplify it by adding a "Download" menu item in the User Dropdown Menu at the topbar and the download menu item redirect the user to the GitHub releases page. Thoughts?

@BrunoQuaresma

A link in the user dropdown menu makes sense to me

Any preferences in how I determine whether we're in an airgapped environment?

(With the goal of linking to the current page that "Install Coder CLI" does if not airgapped and linking to the binaries directly if airgapped?)

@normana10 I think we don't have a way for that rn, so I think you can just ignore the air-gapped network use case for now since other parts of the app rely on the user having network access like the documentation links. But I appreciate your concern.

Awkward becausemy use-case is the air-gapped use-case

I can throw a flag/environment variable into the backend if we think that is a decent solution?

(As a side note, GitLab having offline/air-gapped docs hosted locally is sometimes alifesaver in an air-gapped environment. Just an interesting thought)

@normana10 that is good to know. We have an open issue to offline docs#5466. I think we can use an option as we do for the other deployment settings.

@BrunoQuaresma how about when you click download, a modal is opened (or you're redirected to a page) where we describe:

We recommend downloading the fully-featured vX.X.X [1] release for your platform from GitHub:
[Click here to download from GitHub]

Alternatively, you can download a version of coder without the server functionality from this instance:

• [coder-darwin-arm64]
• ...

• [1] Specifying version here because we should link to the same release the server is running.

(I spent literally 0 time trying to write good text, if this is implemented, do a better job than me. 😄)

@mafredri this looks good!

Though hats off to the Coder team, Coder has been a breeze to setup in my air-gapped env and theOffline Deployment Docs arechef's kiss

And I say that having set upa bunch of other software that didn't like to play ball offline

(Back on topic)

I also think so long as it'svery obvious like the button saying "Download CoderCLI" I (as a user) wouldn't have any expectation that the binary I download would be able to run a Coderserver

My main goal is just easing new devs into getting port forwarding setup so they can VNC using a client like TigerVNC (NoVNC doesn't serve the use-case well enough due to the cumbersome copy/pasting)

Do we think something like this:

Where "Download Coder Server" links to the GitHub release for the corresponding version and "Coder CLI" opens something like this (where we allow you to download the bundled binary):

(Assuming I apply Dean's changes and revert theSSHButton.tsx back to the way it was)

Thoughts?

@normana10 it is looking good! I would make a few changes to make it look a tiny better like using a single button with a Download icon and opening a dialog/modal as@mafredri suggested here#5738 (comment). I think with the dialog we can explain better why to use from an instance or from Git Hub. As a user, I would question why downloading the server doesn't show the OS list as the download CLI does.

Thanks for thinking about this@normana10 and coming up with new ideas. One issue with having a "download server" and "download CLI" is that we're currently not promoting the use of the non-GitHub release binary and we don't have a game-plan for how we wish to do it. Internally we're calling it slim (non-GitHub) and fat (GitHub) binary, but it's more like slim and normal. We'd prefer for the GitHub release to be used and calling it "server" is kind of misleading and directs people towards using slim binary instead (because of "oh I don't want the server").

@normana10 please, let us know if you need any help/assistance from our side!

This Pull Request is becoming stale. In order to minimize WIP, prevent merge conflicts and keep the tracker readable, I'm going close to this PR in 3 days if there isn't more activity.

This Pull Request is becoming stale. In order to minimize WIP, prevent merge conflicts and keep the tracker readable, I'm going close to this PR in 3 days if there isn't more activity.

This Pull Request is becoming stale. In order to minimize WIP, prevent merge conflicts and keep the tracker readable, I'm going close to this PR in 3 days if there isn't more activity.