rnd:projects:homecloud

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
rnd:projects:homecloud [2023-11-12 04:24] – asdfrnd:projects:homecloud [2024-02-20 00:40] (current) – asdf
Line 15: Line 15:
 ==== Tinc ==== ==== Tinc ====
 We began the deployment with tinc since we, like the 2600 author, had no control over port forwarding at the installation location. Unfortunately, tinc's configuration parameters had changed in the year and change since the article's publication.  We began the deployment with tinc since we, like the 2600 author, had no control over port forwarding at the installation location. Unfortunately, tinc's configuration parameters had changed in the year and change since the article's publication. 
 +
 +By far the most painful part of setting tinc up is distributing the key files. Every node on the network needs to have the public key of every other node, even if they're connecting to a central hub as in our case((Tinc 1.1 promises an [[https://www.tinc-vpn.org/documentation-1.1/Invitations.html|invitation feature]] to ease this process.)). 
  
 ==== Nextcloud ==== ==== Nextcloud ====
Line 25: Line 27:
  
 <code nginx> <code nginx>
 +# replace www.example.com throughout with the actual domain
 server { server {
-  server_name PUBLICURL;+  server_name www.example.com;
   access_log /var/log/nginx/nextcloud.log;   access_log /var/log/nginx/nextcloud.log;
   error_log /var/log/nginx/nextcloud.error.log debug;   error_log /var/log/nginx/nextcloud.error.log debug;
Line 33: Line 36:
      
   # redirect http connections to https   # redirect http connections to https
-  error_page 497 =301 https://PUBLICURL:8080$request_uri;+  error_page 497 =301 https://www.example.com:8080$request_uri;
      
   location / {   location / {
Line 50: Line 53:
  
  
-===== Operation ===== +===== Results ===== 
-Once configured properly, operation has been very smooth. Audio/video streaming worked right out of the box, and calendar syncing to Android was easy enough to set up. Navigation does come with a noticeable lag; as far as we can tell, this is due to hardware limitations. +Once configured properly, operation has been very smooth. The user experience is exactly what one would expect from a cloud storage service. Media streaming worked right out of the box, and calendar syncing to Android((Though we will not cover it in detail here, we use DAVx for bidirectional syncing. It's a set-and-forget app that allows the phone to interact with the Nextcloud calendars as though they were native.)) was easy enough to set up. Navigation (including local access) does come with a noticeable lag, most likely due to hardware limitations. On the whole, however, we are very satisfied with the final product.  
 + 
 +===== Future work ===== 
 +As of this writing, our Docker data is all stored on a single external hard drive mounted at ''/mnt/nextcloud''. We believe we will be able to add additional storage space by union mounting however many disks we need over that same directory using something like [[https://github.com/trapexit/mergerfs|MergerFS]], but more research is required. 
  
 +{{tag>selfhosting}}
  • rnd/projects/homecloud.1699763086.txt.gz
  • Last modified: 2023-11-12 04:24
  • by asdf