![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Moving along in fits and starts...
Nov. 14th, 2013 11:09 pmIn between some errands and some smaller jobs, I figured out what needed to be done to set up local cloud storage with a Raspberry Pi, an old USB drive, and some open source code from the ownCloud project.
Everything went very well following the narrative on a page at instructables.com, up until I got to Step 4, in which I was to download and install the ownCloud software.
The trick had to do with the fact that the ownCloud web address in the instructions was no longer valid, so in the end, I crossed my fingers and added the ownCloud repository for Debian 7.0 to the repositories in place on my copy of Raspbian "wheezy" and invoked apt-get.
It worked.
Everything went very smoothly until I forgot to specify the USB drive as the place to store my cloud files. My attempt to fix that pretty much hosed my configuration, which was bad news, but the configuration was pretty easy to replicate from scratch, which was good news.
So right now, I'm testing how long it's taking to send 287 MB to the cloud, and it's turning out to be a pretty respectable time. Then again, I haven't had an opportunity to dig into any of the documentation, which might answer just why the software is configured to use a system proxy. Why that should be the case is not clear to me.
Everything went very well following the narrative on a page at instructables.com, up until I got to Step 4, in which I was to download and install the ownCloud software.
The trick had to do with the fact that the ownCloud web address in the instructions was no longer valid, so in the end, I crossed my fingers and added the ownCloud repository for Debian 7.0 to the repositories in place on my copy of Raspbian "wheezy" and invoked apt-get.
It worked.
Everything went very smoothly until I forgot to specify the USB drive as the place to store my cloud files. My attempt to fix that pretty much hosed my configuration, which was bad news, but the configuration was pretty easy to replicate from scratch, which was good news.
So right now, I'm testing how long it's taking to send 287 MB to the cloud, and it's turning out to be a pretty respectable time. Then again, I haven't had an opportunity to dig into any of the documentation, which might answer just why the software is configured to use a system proxy. Why that should be the case is not clear to me.
