Installation procedure fragmentation + failing

[GregPeden]

Documentation currently indicates two different installation methods

Docs website (https://coasts.dev/docs#installing):

curl -fsSL https://coasts.dev/install | sh
coast daemon install

The readme.md (https://github.com/coast-guard/coasts?tab=readme-ov-file#installation):

eval "$(curl -fsSL https://coasts.dev/install)"

When I try to install by either means, I have this result per the screenshot:

It seems the installation goes to a different folder than the coast command expects it to be.

I am attempting to install v0.1.37 in Ubuntu via WSL2 on Windows 11.

[jamiesunderland]

ah, that is silly of us. sorry. Should be the website docs one.

eval "$(curl -fsSL https://coasts.dev/install)"

[jamiesunderland]

#131

[GregPeden]

Yeah but neither one worked.

[dahyman91]

@GregPeden what shell do you use? The problem with the old command was that you would have to start a new session, but the new one (eval) should source the config immediately.

[dahyman91]

In fairness the logic to add coasts to your path was never tested on linux, so that could be the problem. Once you let me know what shell you're using I can text on my linux machine/update the script if needed.

[dahyman91]

Puling up my linux machine now to test

[GregPeden]

@GregPeden what shell do you use? The problem with the old command was that you would have to start a new session, but the new one (eval) should source the config immediately.

Yeah I am using Ubuntu within a WSL2 terminal.

I actually was able to install the release build of Coast a couple weeks ago using the two-line method in the docs.

The latest release worked just fine but the command itself isn't working.

[dahyman91]

The install itself looks like it completed fine. Can you try running ~/.coast/bin/coast help and let me know what you get? That'll tell us whether it's a PATH issue or something else.

I'm committing a copy of the install script to the repo so you have something to work against directly.

[dahyman91]

@GregPeden

https://github.com/coast-guard/coasts/blob/main/external/install.sh

[GregPeden]

Yes it installed fine and the long-form command call works but the aliased command doesn't.

Yes I could fidget to fix it myself manually but I mean to highlight that the as-prescribed install solution isn't doing it.

[dahyman91]

Thank you! Noted and we'll put some love into non-MacOs installation in the coming days.

[jamiesunderland]

@GregPeden I'm going to try to fix this with virtual-box tonight. I'm not sure it will match your exact setup but will do my best

[GregPeden]

Yeah... and I don't know for sure that my setup isn't unique somehow, but I haven't done anything in particular to make my environment unique. I'm pretty sure that Ubuntu in WSL is really common, though.