Dev

[audiefile]

No description provided.

[scottleibrand]

I think the /var/www stuff should live outside pebble.sh. I have a cron job to copy www/openaps.json to /var/www/ on the box running apache, but not on the Pi's (where I'm using SimpleHTTPServer).

[audiefile]

Out of curiosity, why separate /var/www and pebble.sh and have a cron job to copy? Why SimpleHTTPServer over apache?

[scottleibrand]

Mainly because I didn't think it was necessary to have "set up Apache" be part of the installation. SimpleHTTPServer comes with Python, so didn't require any additional packages...
My opinion on this isn't all that strong, so if anyone else has a perspective (or wants to do the work to document their preferred way of doing it), please share. 
-Scott

On Tue, Oct 6, 2015 at 6:54 PM -0700, "Rachel Sandlain" [email protected] wrote:

Out of curiosity, why separate /var/www and pebble.sh and have a cron job to copy? Why SimpleHTTPServer over apache?

—
Reply to this email directly or view it on GitHub.

[audiefile]

Fair enough. I'm not sure why I set up apache anymore. I've had a bunch of
half implemented ideas and I think apache was part of one. Since I had it
already, I figured why not just use that. The raspberry pi documentation
has write up on apache also. It's interesting to know why people do things
the way they do - you can learn so much that way.
Rachel

On Tue, Oct 6, 2015 at 10:45 PM Scott Leibrand [email protected]
wrote:

Mainly because I didn't think it was necessary to have "set up Apache" be
part of the installation. SimpleHTTPServer comes with Python, so didn't
require any additional packages...
My opinion on this isn't all that strong, so if anyone else has a
perspective (or wants to do the work to document their preferred way of
doing it), please share.
-Scott

On Tue, Oct 6, 2015 at 6:54 PM -0700, "Rachel Sandlain" <
[email protected]> wrote:

Out of curiosity, why separate /var/www and pebble.sh and have a cron job
to copy? Why SimpleHTTPServer over apache?

—
Reply to this email directly or view it on GitHub.

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