Skip to content

Conversation

@danamlewis
Copy link
Contributor

Includes:

  1. Minor edits and revisions of links, language, etc.
  2. Added section (3b) how to do multiple wifi setup (for hotspot and home, suggested) from a Mac
  3. Added note about console cable and good how-to link for using that with Mac
  4. Edited watchdog section to run now, w/ @channemann's notes from his gist on that step

@ghost
Copy link

ghost commented Sep 10, 2015

This looks so awesome! :-) Thank you so much for polishing and making the install instructions Bette!

Because my initial install instructions had *.lan instead of the correct *.local extension for SSHing, the *.lan needs to be replaced in multiple places.

I'm not on a computer right now to correct it but it is a quick fix: replacing the *.lan with *.local everywhere it is located by searching with control/command (depending on operating system) for .lan.

Thank you again for the very nice work!

@danamlewis
Copy link
Contributor Author

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!

@channemann
Copy link
Contributor

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
I would change the wording here; the lack of cables doesn't make it headless, it's the lack of a display.

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)
If the user's SSID or password has a special character, an escape will be required; alternatively, I believe you can use single ticks (') instead of double ticks (") to enclose those two parameters.

https://github.com/openaps/docs/pull/4/files#diff-143c9a69795855e2aff56388ae86ae53R74
The user doesn't actually need to set their phone up as a hotspot to do this (which is alluded to later). It is good to test all of the networks they added, however, so testing both the iOS hotspot and the other wifi networks (home, etc) would be good.

https://github.com/openaps/docs/pull/4/files#diff-143c9a69795855e2aff56388ae86ae53R79
Probably want to expand on this a bit.

@danamlewis
Copy link
Contributor Author

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.

@channemann
Copy link
Contributor

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
chris.hannemann@gmail.com

On Sep 9, 2015, at 7:58 PM, Dana Lewis notifications@github.com wrote:

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.


Reply to this email directly or view it on GitHub.

@scottleibrand
Copy link
Contributor

Yes, we should encourage people to use single quotes (') instead of double
quotes (") to enclose passwords, as some characters (like ! and others)
have special meaning at the linux command line and will not be properly
passed on to the password script if they're only enclosed in double
quotes. That's a really annoying problem to troubleshoot, so single quotes
are safest.

On Wed, Sep 9, 2015 at 8:03 PM, Chris Hannemann notifications@github.com
wrote:

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
chris.hannemann@gmail.com

On Sep 9, 2015, at 7:58 PM, Dana Lewis notifications@github.com wrote:

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.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHub
#4 (comment).

@danamlewis
Copy link
Contributor Author

@bewest ping for reviewing this PR, so @Alimazaheri can give to Ed to test after it's merged into docs.

@msrcgm
Copy link
Contributor

msrcgm commented Sep 11, 2015

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.


Reply to this email directly or view it on GitHubhttps://github.com//pull/4#issuecomment-139452763.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe worth considering, a lot of docs use verbiage "type" instead of "do"?

@bewest
Copy link
Member

bewest commented Sep 13, 2015

Looks pretty good, lot of nice tweaks and fixes, thanks!
Looks good to me, please merge. :-)

danamlewis added a commit that referenced this pull request Sep 13, 2015
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.
@danamlewis danamlewis merged commit a9408ce into openaps:master Sep 13, 2015
@msrcgm
Copy link
Contributor

msrcgm commented Sep 13, 2015

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:

Merged #4#4.


Reply to this email directly or view it on GitHubhttps://github.com//pull/4#event-408141859.

@danamlewis
Copy link
Contributor Author

Ready for you to try. This view is probably easiest to look at:
http://openaps.gitbooks.io/building-an-open-artificial-pancreas-system/content/docs/Setup/rpi.html

On Sun, Sep 13, 2015 at 1:35 PM, msrcgm notifications@github.com wrote:

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.com<mailto:
notifications@github.com>> wrote:

Merged #4#4.


Reply to this email directly or view it on GitHub<
https://github.com/openaps/docs/pull/4#event-408141859>.


Reply to this email directly or view it on GitHub
#4 (comment).

Dana Lewis | http://www.twitter.com/danamlewis |
http://www.linkedin.com/in/danalewis
"Doing something for someone else is more important than anything you would
do for yourself."

scottleibrand pushed a commit that referenced this pull request Nov 19, 2015
danamlewis pushed a commit that referenced this pull request Jan 28, 2016
bewest referenced this pull request in bewest/docs Mar 26, 2016
danamlewis pushed a commit that referenced this pull request Apr 7, 2017
scottleibrand pushed a commit that referenced this pull request Jul 4, 2017
Link to raw version of openaps-bootstrap.sh
dirkgastaldo added a commit to dirkgastaldo/docs that referenced this pull request Nov 29, 2017
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.
danamlewis pushed a commit that referenced this pull request Nov 30, 2017
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.
danamlewis pushed a commit that referenced this pull request May 17, 2018
dougboss added a commit to dougboss/docs that referenced this pull request Nov 25, 2019
"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 ?
@dougboss dougboss mentioned this pull request Nov 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants