adding spin to path

[macolso]

Signed-off-by: MacKenzie Olson 48335676+macolso@users.noreply.github.com

Content must go through a pre-merge checklist.

Pre-Merge Content Checklist

This documentation has been checked to ensure that:

• The title, template, and date` are all set
• File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep '^M' | wc -l and expect 0 as a result)
• Has passed bart check
• Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)
• Headings are using Title Case
• Code blocks have the programming language set to properly highlight syntax and the proper copy directive
• Have tested with npm run test and resolved all errors

[macolso]

Added to PATH. @mikkelhegn would be good to get your review given 822

[mikkelhegn]

I'm a little concerned with this as it might break a flow which is deliberately very hard to break. Not sure if everyone can run the sudo command. Can we somehow make it optional by adding it in a quote section or but it in the "Learn more".

I think the real way to solve this is through spinframework/spin#641 and then make the quickstart use those.

[mikkelhegn]

Let me know if I'm too much of a chicken :-)

[macolso]

I'm aligned with that thought process - we may lose some users who don't have the ability to run sudo if we put PATH in the mainstream directions.

I really like how Nomad's UI on their install options . We should do something like once spinframework/spin#641 is completed

[mikkelhegn]

@tpmccallum ☝🏻

[itowlson]

rustup seems to be able to add the Rust tooling to PATH without sudo, by installing into ~/.cargo, then adding . "$HOME/.cargo/env" to .bashrc (which in turn adds ~/.cargo/bin to PATH). Makes the installer a bit more complicated of course...

[karthik2804]

Handlebars does not support multiline strings. Therefore the line breaks must be represented using \n

[macolso]

Going to hold off merging until we have a complete installation story