Add setup guides #18

Merged
mhfowler merged 3 commits from setup-guides into main 2021-03-29 13:41:54 +00:00
mhfowler commented 2021-03-29 09:19:43 +00:00 (Migrated from github.com)

I created a setup section, and within that section

  • quick_deployment.md
  • install_from_debian.md

I also added a brief section to quick_deployment.md that includes how to connect to the internet, once you've installed PeachCloud via a disc image.

I created a setup section, and within that section - quick_deployment.md - install_from_debian.md I also added a brief section to quick_deployment.md that includes how to connect to the internet, once you've installed PeachCloud via a disc image.
mycognosist (Migrated from github.com) approved these changes 2021-03-29 13:28:08 +00:00
mycognosist (Migrated from github.com) left a comment

So nice to have both setup pathways documented like this!

There are a couple of tiny formatting changes I'd like to see but I'll probably review the entire set of documentation and make all of those changes at once. That will offer a good opportunity to ensure consistency across the docs :)

So nice to have both setup pathways documented like this! There are a couple of tiny formatting changes I'd like to see but I'll probably review the entire set of documentation and make all of those changes at once. That will offer a good opportunity to ensure consistency across the docs :)
mhfowler commented 2021-03-29 13:43:51 +00:00 (Migrated from github.com)

@mycognosist for writing docs that sounds like a good workflow to me. Where when I write stuff you can review for major changes, but then for formatting go back through everything separate from the PR. I mean I'm still happy to hear feedback of formatting things, but it also just sounds more ergonomic to make separate PRs instead of comments and then changes for documentation

@mycognosist for writing docs that sounds like a good workflow to me. Where when I write stuff you can review for major changes, but then for formatting go back through everything separate from the PR. I mean I'm still happy to hear feedback of formatting things, but it also just sounds more ergonomic to make separate PRs instead of comments and then changes for documentation
Sign in to join this conversation.
No description provided.