Skip to content

Updated .profile section for clarity #87

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
scottleibrand merged 13 commits into from
Feb 11, 2016
Merged

Updated .profile section for clarity #87

Changes from all commits
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
9d123a5
Updated to make .profile setup more clear
Feb 11, 2016
3c1fd2b
Update vizualization.md
Feb 11, 2016
80deb33
Update vizualization.md
Feb 11, 2016
0794ee8
Update vizualization.md
Feb 11, 2016
322d3ee
Update vizualization.md
Feb 11, 2016
c79c034
Update vizualization.md
Feb 11, 2016
4822993
Update vizualization.md
Feb 11, 2016
988a5f2
Update vizualization.md
Feb 11, 2016
d4f746d
Update vizualization.md
Feb 11, 2016
e94123e
typo
Feb 11, 2016
e324752
Removed env in cron as we suggest .profile above
Feb 11, 2016
8afcb68
Roll back last change
Feb 11, 2016
997ffb0
Update vizualization.md
Feb 11, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions docs/Automate-system/vizualization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,16 +23,17 @@ Next, on your Nightscout website, go to the Settings (3 horizontal bars) in the

To be able to upload data, OpenAPS needs to know the URL for your Nightscout website and the hashed version of your API_SECRET password, which you have entered as one of your Nightscout configuration variables. Two environment variables, NIGHTSCOUT_HOST and API_SECRET, are used to store the website address and the password, respectively.

To obtain the hashed version of the API_SECRET, go to http://www.sha1-online.com/ (keep the default sha-1) and hash your API_SECRET. For example, if your enter "password" (without quotes), the hashed version returned will be 5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8.
To obtain the hashed version of the API_SECRET, run the following ```echo -n "<API_SECRET>" | shasum``` and replace ```<API_SECRET>``` with what you set up in Nightscout. For example, if your enter ```echo -n "password" | shasum```, the hashed version returned will be 5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8. Run it with your password and save the hashed key that is output for the next step.

In your Raspberry PI terminal window, you may now define the two environment variables as follows:
In your terminal window, you may now define the two environment variables. This is done by adding them to your .profile in your home directory. The .profile runs each time the system starts and will ensure these variables are set for future use on the command line.

```nano ~/.profile``` and add the following at the end of the file below any other content that may already be there:
```
$ export NIGHTSCOUT_HOST="https://<your Nightscout address>"
$ export API_SECRET="<your hashed password>"
NIGHTSCOUT_HOST=https://<your Nightscout address>; export NIGHTSCOUT_HOST
API_SECRET=<your hashed password>; export API_SECRET
```

These variables will stay defined as long as the current terminal session remains active. Note that it is important to enter https:// (not http://) in front of your Nightscout address. To have these variables defined each time you login, you may include the two `export` lines (without quotes) in the .profile file, which is in your home directory.
Now run ```source /etc/profile``` to enact the changes we've just made without restart the machine

### Configuring and Uploading OpenAPS Status

Expand Down