[bitwarden_rs] update guide to fix cargo build issue

[pxlfrk]

Hi!

in #609 @luto told me that Uberspace will support Rust in the Version 7.6.2, which is indeed correct - but only the stable release channel. Bitwarden_rs depends on the nightly release channel, so as described right now in the guide cargo build -j 1 --release --features sqlite will fail.

Compiling pear_codegen v0.1.4
error: failed to run custom build command for pear_codegen v0.1.4

Caused by:
process didn't exit successfully: /home/passres/bitwarden_rs/target/release/b uild/pear_codegen-eb17718987529976/build-script-build (exit code: 101)
--- stderr
Error: Pear requires a 'dev' or 'nightly' version of rustc.

Therefore I re-added the rust-installation section to the guide to fix this issue.

Another solution would be to include also the nightly and/or dev release channels to the default uberspace installation.

Looking forward for your Feedback to solve this issue.

[luto]

sigh 😅 do you have any recommendations on which of the nightly releases to provide? is it fine to provide the latest nightly that actually builds the relevant tools as a "nightly" channel?

[pxlfrk]

As far as i can tell i would recomment using rustup for this guide as it's mentioned in the official setup documentation; the latest nightly-release-channel should also work. At least i think so..

[pxlfrk]

cc #708 for further information.

[jonmz]

cc #708 for further information.

Oh, thanks, I just scrolled through the open issues regarding bitwarden, not through open PRs. Tbh I am not really keen on providing nightly builds unless absolutely necessary, and for that I would like to get at least some basic understanding why a nightly build (even one from 2018) is needed for Pear but a stable build from 2020 would not do it... we are strictly sticking with stable versions on other programming languages as well. If possible I would prefer Rust being no exception, but will keep this PR open for now.

[pxlfrk]

I absolutely agree with you, in theory the stable release should work fine. I'd prefer waiting for the result of the issue you referenced.

[luto]

postponed until we've got some replies in the issue.

[luto]

This should be fixed in a future bitwarden/pear release: SergioBenitez/Pear#23 (comment). Thanks for the PR, though!