Seafile on raspberry pi8/17/2023 The next step is to configure eduroam with adequate keys and credentials in between those options - and that could be sufficient for most of my usage scenarios, I think. I've already tried with my home network as first priority, falling back to the iPhone's hot spot (the idea would be to connect everything to the hot spot when working in the street). I've found that it would be trivial to simply configure wpa_nf with multiple networks. But the setup is perfectly usable - otherwise, I might learn how to implement a persistent sqlite cache in emacs Lisp.Īs for network connections, Tailscale is magic (it will assign each device a fixed private IP address and deal with all the routing complexities for you). This is mostly because of the Pi's limited I/O throughput with the microSD card. To be sure, it takes some time to index a few thousand notes when I call helm-phi-find - as shown above - for the first time (later calls will be cached). After that, I only have to connect from the iPad.īlink.sh makes use of mosh, which is interesting because it will not drop the connection if the iPad goes idle or if you switch applications. It takes about 100 seconds to have everything ready. It runs emacs -nw with all the bells & whistles! To have everything promptly available, I'm also running emacs in a tmux session started as a systemd service. ![]() ![]() The Pi Zero has all the notes in it, synchronized with seafile-cli. Proxy_request_buffering off # enables large file uploadsĪccess_log /var/log/nginx/ seafileformat Įrror_log /var/log/nginx/ Īccess_log /var/log/nginx/ Įrror_log /var/log/nginx/ you explain your setup a bit more, i.e. # used for view/edit office file via Office Online ServerĪccess_log /var/log/nginx/ seafileformat Įrror_log /var/log/nginx/ ![]() Proxy_set_header X-Forwarded-Host $server_name Proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for Ssl_certificate_key /etc/letsencrypt/live/YOURDOMAIN.XYZ/privkey.pem # Path to your privkey.pem Ssl_certificate /etc/letsencrypt/live/YOURDOMAIN.XYZ/fullchain.pem # Path to your fullchain.pem Server_tokens off # Prevents the Nginx version from being displayed in the HTTP response header Rewrite ^ $http_host$request_uri? permanent # Forced redirect from HTTP to HTTPS Log_format seafileformat ' $http_x_forwarded_for $remote_addr " $request" $status $body_bytes_sent " $http_referer" " $http_user_agent" $upstream_response_time' It can take a few minutes to an hour for your dns server to refresh which is why If you add a domain like seafile then your seafile will be on If you leave the domain (sometimes called hostname) blank then this will point How this isĭone is a little different for each site but there should be an option to manageĭns where you can add an a record pointing to your public ipv4 address and aĪaaa record pointing to your ipv6 address. Once you have this you need to point dns records to your public ip. You can even use the same address’s subdomainsįor other applications such as. I use Namesilo but there are many options. Setting up your own domainįor security we’re only going to access seafile though https. Setup your pi with 64-bit Raspberry Pi OS. It hasn’t been well tested so use at own risk. There is a script I wrote to automate the whole process, available on my Github. On Seafile’s website but the script and docker image don’t seem to work on with So we can connect to it remotely though our own domain. We’ll be installing Seafile on a Raspberry Pi 4 and setting up a reverse proxy WebDAV, etc., but it will probably be a lot more trouble. You could hack together your own server with Syncthing, rclone mount, nginx Which can’t be accessed through a normal file browser. There is one well-known disadvantage: Files are stored in a proprietary format
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |