Updating raspberry pi setup instructions#4
Conversation
Reverse merge to remove the sync issue @bewest found
|
Good catch! I thought I got most of them, but found a few tucked away in various places - all .lan fixed to .local now, thanks @diabeticgonewild! |
|
Good stuff. I have a few notes and touch-ups; certainly not all need to be addressed in this PR. https://github.com/openaps/docs/pull/4/files#diff-143c9a69795855e2aff56388ae86ae53R3 The numbering system breaks the markdown formatting once you hit 3 because of the paragraph breaks. Might be best to move away from a formatted numbered list. https://github.com/openaps/docs/pull/4/files#diff-143c9a69795855e2aff56388ae86ae53R51 (and similar) https://github.com/openaps/docs/pull/4/files#diff-143c9a69795855e2aff56388ae86ae53R74 https://github.com/openaps/docs/pull/4/files#diff-143c9a69795855e2aff56388ae86ae53R79 |
|
Awesome comments. I spent 20 minutes battling with the list formatting...almost called it quits and called in the troops @bewest but thought I got it working. Guess not. Ben, help please! Or suggest better formatting to use in lieu of the lists I botched? Re: SSID section, I was able to get it to run with double ticks to enclose the parameters. Would love for you to make any of those additional adds or mods per your comments, those all sound good to me. |
|
If it makes you feel better, I struggled with that exact list when I was first putting it all into a gitbook as well (and eventually just gave up). I'm sure we can come up with something less crazy. I recall having difficulty with a work password that started with a ! when using the double ticks, but perhaps I had something else messed up as well. I'll roll the other stuff into a future edit. Chris Hannemann
|
|
Yes, we should encourage people to use single quotes (') instead of double On Wed, Sep 9, 2015 at 8:03 PM, Chris Hannemann notifications@github.com
|
|
@bewest ping for reviewing this PR, so @Alimazaheri can give to Ed to test after it's merged into docs. |
|
I'll have my pi tomorrow and will attempt the set up Saturday night. Sent from my iPhone On Sep 10, 2015, at 10:00 PM, Dana Lewis <notifications@github.commailto:notifications@github.com> wrote: @bewesthttps://github.com/bewest ping for reviewing this PR, so @Alimazaheri can give to Ed to test after it's merged into docs. — |
There was a problem hiding this comment.
Maybe worth considering, a lot of docs use verbiage "type" instead of "do"?
|
Looks pretty good, lot of nice tweaks and fixes, thanks! |
Updated raspberry pi setup instructions. Ready for @msrcgm to test! Please make notes as you go for anywhere the instructions don't seem clear (and ask in real time on gitter so folks can help you get through those spots in the meantime) and we'll be able to update them more.
|
File should I attempt? Or wait for further revision. Sent from my iPhone On Sep 13, 2015, at 1:29 PM, Dana Lewis <notifications@github.commailto:notifications@github.com> wrote: — |
Link to raw version of openaps-bootstrap.sh
Dana, I am attempting to get the #s to go in sequence. What's happening is when we insert an image or code between numbered lines it breaks the sequence and the numbering restarts at #1 (rather than openaps#4, for example). I found a solution here: github/markup#1084 You insert spaces to get the image code block one space beyond where your text begins, four spaces here, until you get to number 10, and then I'm guessing you have to insert five spaces. I could be wrong. The list in the Workflow section should end with openaps#11. If it doesn't you can reject this PR.
Dana, I am attempting to get the #s to go in sequence. What's happening is when we insert an image or code between numbered lines it breaks the sequence and the numbering restarts at #1 (rather than #4, for example). I found a solution here: github/markup#1084 You insert spaces to get the image code block one space beyond where your text begins, four spaces here, until you get to number 10, and then I'm guessing you have to insert five spaces. I could be wrong. The list in the Workflow section should end with #11. If it doesn't you can reject this PR.
"If you are using Jubilinux 0.3.0 (Debian Stretch) or the Raspberry Pi, please skip to openaps#4. If you are using Jubilinux 0.2.0 (Debian Jessie), you will need to manually initialize bluetooth. (click here to expand instructions)" There is no step 4 that I can find ... What are the steps for Jubilinux 0.3.0 ?

Includes: