posts
cross-posted from: https://lemmy.world/post/36668264
cross-posted from: https://lemmy.world/post/36668172
Please enjoy this very technical discussion on Nextcloud Atomic, the immutable system-level wrapper for Nextcloud AIO, which is being designed as the successor to NextcloudPi. Atomic delivers Nextcloud as a simple deployment for single machines, allowing easy selfhosting for home enthusiasts and anyone else wanting to run Nextcloud.
Interview includes Tobias (Atomic, NextcloudPi, Nextcloud Secrets) and Marcel (Floccus, Bookmarks, Recognize). Begins with quick overview and review of running Nextcloud, along with popular outlying Nextcloud implementations and apps then discussed at-length. For comprehensive show notes and timestamps click here.
If you enjoy the interview, please do share it with others! Thanks so much.
Would it be reasonable to expect a Raspberry Pi 4 to run Nextcloud and manage a photo backup of +100 Gb?
The Raspberry Pi is from 2020, running Raspbian, and it was used as an intervalometer with the help of gphoto2 (meaning no great efforts were demanded from it).
The pictures are on two external hard drives
*1Tb WesternDigital SATA (bought second hand, but "like new" according to the sales guy.
*320Gb WesternDigital SATA (inherited from an AcerOne laptop once I realized it could not even handle lubuntu)
My very limited knowledge on the subject tells me I need to:
*Get rid of Raspbian and install Raspberry Pi OS
*Install Nextcloud (and upgrade an existing account)
*Upload +100 Gb
Would the aforementioned steps allow me to access the files on Fedora/Kubuntu (two separate hard drives on a desktop) and openSUSUE (on a laptop)?
I’m also testing a filen.io account and a sync.com account. All three services (NextCloud, Filen, and Sync) work as I expect on an Ipad.
Filen and Nextcloud have Linux applications, and both have been working without problems on test backups of 100 pictures.
Sync is CANADIAN but not Linux friendly (I tried Wine, didn’t work, gave up)… I’m accessing a free account via Firefox only, so I’m not counting on them for this journey.
So, long story short, I want to back up my files (mostly pictures/scans and some pfd documents) on someone else's computer and locally.
Now the question. Can anyone recommend a guide to achieve what I want?
I’m a cook by trade without any technical (software/hardware) training who has been using Linux (openSUSE, Ubuntu, Arch, Mint) since 2012. Please forgive any mistakes on terminology.
I included a picture of my intervalo-Frankenstein-meter from 2020.
Thank You.
Moin,
Überlege auf dem Server wo Nextcloud läuft, ollama zu installieren und eventuell damit dem DeepSeek Modell zu betreiben. Hat das jemand gemacht? LocalAI geht, aber da sind mir die Modelle zu ungenau.
I'm just curious as I don't have a need for it outside my personally use as of now.
I know that gsuite and office365 has been jacking up their prices and it might be a time to make nextcloud shine.
services:
db:
image: mariadb
restart: always
command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
volumes:
- ./mysql:/var/lib/mysql
environment:
- MYSQL_PASSWORD=supersecretpassword
- MYSQL_DATABASE=nextclouddb
- MYSQL_USER=nextclouduser
- MYSQL_RANDOM_ROOT_PASSWORD='yes'
redis:
image: redis
restart: always
command: redis-server --requirepass supersecretpassword2
app:
image: nextcloud:27
restart: always
ports:
- 8080:80
links:
- db
- redis
volumes:
- ./html:/var/www/html
environment:
- MYSQL_PASSWORD=supersecretpassword
- MYSQL_DATABASE=nextclouddb
- MYSQL_USER=nextclouduser
- MYSQL_HOST=db
- REDIS_HOST_PASSWORD=supersecretpassword2
depends_on:
- db
- redis
cron:
image: nextcloud:27
restart: always
volumes:
- ./html:/var/www/html
entrypoint: /cron.sh
depends_on:
- db
To use this you need docker-compose installed. Once thats installed create a nextcloud folder and copy in this file as docker-compose.yaml. Once you are in the working directory run docker-compose up -d
I was looking for a way to use a reverse Proxy with my nextcloud snap install, this guid was what I needed. https://github.com/nextcloud-snap/nextcloud-snap/wiki/Putting-the-snap-behind-a-reverse-proxy
First change, what ports nextcloud listens to:
sudo snap set nextcloud ports.http=81 ports.https=444
Install haproxy and append this to the config file in /etc/haproxy/haproxy.cfg
backend nextcloud-http
mode http
balance roundrobin
option forwardfor
option httpchk HEAD /
http-check send ver HTTP/1.1 hdr Host localhost
server nextcloud 127.0.0.1:81 check
timeout connect 4s
timeout server 4s
backend nextcloud-https
mode tcp
balance roundrobin
option httpchk HEAD /
http-check send ver HTTP/1.1 hdr Host localhost
option ssl-hello-chk
server nextcloud 127.0.0.1:444 check
timeout connect 4s
timeout server 4s
And this for the front end, don't forget to change to your domain. nextcloud.example.org
frontend http
bind *:80
mode http
acl host_nextcloud hdr(host) -i <domain name>
use_backend nextcloud-http if host_nextcloud
timeout client 4s
frontend https
bind *:443
mode tcp
tcp-request inspect-delay 5s
tcp-request content accept if { req_ssl_hello_type 1 }
acl host_nextcloud req_ssl_sni -i <domain name>
use_backend nextcloud-https if host_nextcloud
timeout client 4s
Check if everything is correct with
sudo haproxy -c -f /etc/haproxy/haproxy.cfg
and start it.
sudo systemctl enable haproxy
sudo systemctl start haproxy
just do the lets-encrypt stuff again:
nextcloud.enable-https
And it worked for me(Apache)
Do you use the default location for the database? I found a cool middle ground that allowed me to run my operating system and snap off a ssd and the database on a slower hdd.
I installed nextcloud with snap and did the setup.
When everything was how I wanted it to be, I search for the datas location
(for me:/var/snap/nextcloud/common/nextcloud/data). Then I created a /data on my hdd and binded it to nextclouds /data folder.
My fstab now looks like this:
/data /var/snap/nextcloud/common/nextcloud/data none bind 0 0
You only have to rebuild the database:
nextcloud.occ files:cleanup
nextcloud.occ files:scan
!!! Important, move your data first to the new location.(I think you won't lose it, but you cannot access it)