infrastructure

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
infrastructure [2023-03-20 05:04] – [NextCloud instance] asdfinfrastructure [2023-05-08 06:04] (current) – asdf
Line 15: Line 15:
  
 ===== Future ideas ===== ===== Future ideas =====
 +<WRAP center round todo 60%>
 +Migrate this section to [[:rnd:sketchpad]]?
 +</WRAP>
 +
 ==== NextCloud instance ==== ==== NextCloud instance ====
 Initial tests have been //very// satisfying. It will likely meet my stated need for a unified storage solution. In keeping with the above plan to Dockerize my services, I would like to build it around [[https://hub.docker.com/_/nextcloud|this image]]. Enable files, calendar, contacts, Talk (video conferencing), and Deck (kanban). Offer access to the sibs. Initial tests have been //very// satisfying. It will likely meet my stated need for a unified storage solution. In keeping with the above plan to Dockerize my services, I would like to build it around [[https://hub.docker.com/_/nextcloud|this image]]. Enable files, calendar, contacts, Talk (video conferencing), and Deck (kanban). Offer access to the sibs.
Line 20: Line 24:
 The current plan is to install the instance on a Raspberry Pi, which will allow me to have full hands-on access to the storage media. This may complicate global access, as I have little control over port forwarding at my current residence. See "5G Hotspots and Tinc" in 38:1 of 2600 for a possible solution to this exact problem. The current plan is to install the instance on a Raspberry Pi, which will allow me to have full hands-on access to the storage media. This may complicate global access, as I have little control over port forwarding at my current residence. See "5G Hotspots and Tinc" in 38:1 of 2600 for a possible solution to this exact problem.
  
-Currently installed on the Raspberry Pi, though the reverse proxy has not been set up. Note that some finagling will be necessary to get CalDAV to work; see [[https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/reverse_proxy_configuration.html#nginx|here]] for NGINX instructions.+Currently installed on the Raspberry Pi and the reverse proxy is functional. <del>Note that some finagling will be necessary to get CalDAV to work; see [[https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/reverse_proxy_configuration.html#nginx|here]] for NGINX instructions.</del> This expected finagling seems to have been unnecessary, as bidirectional calendar sync is working just fine without it. The next step is to prepare the hard drive that will back the data store, mount it at ''/srv/nextcloud'', and point the containers at it.  
 + 
 +I'm not thrilled by the speeds I've seen thus far, but it's hard to tell where the bottleneck is. Ping times through the VPN from my laptop to the Pi average ~350 ms, and with NextCloud configured for reverse proxy, it's impossible to test its local performance (even navigating to its internal IP redirects to sinensis). The problem could simply be CPU usage at the node itself. It's not that big a deal, but it does warrant notice.
  
 ==== Airflow ==== ==== Airflow ====
  • infrastructure.1679288693.txt.gz
  • Last modified: 2023-03-20 05:04
  • by asdf