Explicitly document --features and their dependencies in Getting Started Guide

[katrinabrock]

I'm happy to submit a PR for this soon.

Problem Description

"A Note on Installing diesel_cli" is helpful, but could be way more helpful to make install painless.

Two main things

1. Possible arguments to --features (backends) should be explicitly listed. Maybe there is a cargo way to figure out what they are? Even if there is, it would be nice to explicitly list them in the getting started guide to make it rust-beginner friendly.

2. For each backend, it would be nice to list the exact package name needed for various OS package managers (brew, apt-get, dnf, do we need to cover Windows?)

Checklist

• I have already looked over the issue tracker for similar issues.

[killercup]

Yes please! I'm not sure I'd put all that in the Getting Started guide, though. Maybe add a new document about all the feature toggles Diesel has? The 3 backends are the relevant ones for the CLI, and a good start; but the same document could also talk about the features you need to enable in diesel (and diesel-codegen) to get DateTime, JSON, etc. support.

[katrinabrock]

For a guide to installing dependencies, do we need to cover windows or just Mac and common Linux flavors?

[killercup]

Eventually, we should cover every platform our users use. :) But we can absolutely start out with just Mac and Debian, for example!

…

Am 14.08.2017 um 00:08 schrieb katrinabrock ***@***.***>: For a guide to installing dependencies, do we need to cover windows or just Mac and common Linux flavors? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.