I think you can use Immich external libraries for this, also to be extra safe you can just mount your external images folder as read only by adding :ro to the docker volume mount so that the container won’t be able to modify anything as a precaution.
I use a .dev and it just works with letsencrypt. I don’t do anything special with wildcards, I just let traefik request a cert for every subdomain I use and it works. I use the tls challenge which works on port 443, so I don’t think HSTS or port 80 matters, but I still forwarded port 80 it so I can serve an http->https redirect since stuff like curl and probably other tools might not know about HSTS.
Gotcha thanks for the info! It looks like I would be fine with ocis or opencloud, but since my main use case and pain points are with document editing which is collabora, it probably wouldn’t change much besides simplifying the docker setup (I had to make a gross pile of nginx config stuff pieced together from many forum help posts to get the nextcloud fpm container to work smoothly). But it already works so unless it breaks there’s little incentive for me to change.
What are the apps that you would miss? I basically only use my NC as a Google drive and docs replacement, so all it has to do is store docx files and let me edit them on desktop or mobile without being glitchy and I’ve really wanted to consider OCIS or similar.
That second requirement for me seems hard because of how complex office suites are, but NC is driving me to my wit’s end with how slow and error prone it is, and how glitchy the NC office UI is (like glitches when selecting text or randomly scrolling you to the beginning).
Hmm, well it doesn’t seem to be any problem with the docker compose then as best as I can tell. I picked a random ext4 flash drive and replicated your setup with the UID and GID set and it seems to work fine:
# /etc/fstab
/dev/sda1 /home/<me>/mount/ext_hdd_01 ext4 defaults 0 2
~/mount % ls -an
total 12
drwxr-xr-x 3 1000 1000 4096 Mar 27 16:22 .
drwx------ 86 1000 1000 4096 Mar 27 16:31 ..
drwxrwxrwx 3 0 0 4096 Mar 27 16:26 ext_hdd_01
~/mount/ext_hdd_01 % ls -an
total 6521728
drwxrwxrwx 3 0 0 4096 Mar 27 16:26 .
drwxr-xr-x 3 1000 1000 4096 Mar 27 16:22 ..
-rw-r--r-- 1 1000 1000 6678214224 May 5 2024 PXL_20240504_233345242.mp4
drwxrwxrwx 2 0 0 16384 May 5 2024 lost+found
-rwxr--r-- 1 1000 1000 5 Mar 27 16:27 test.txt
# ~/samba/docker-compose.yml
services:
samba:
image: dockurr/samba
container_name: samba
environment:
NAME: "Data"
USER: "user"
PASS: "pass"
UID: "1000"
GID: "1000"
ports:
- 445:445
volumes:
- /home/<me>/mount:/storage
restart: always
I was able to play the PXL.mp4 video from my desktop and write back the test.txt file
Have you checked the logs with docker logs -f samba to see if there’s anything there?
Also you could try to access the HD from within the container, using docker exec -it samba bash and then cd into /storage and see what happens.
I would suggest adding “UID” and “GID” environment variables to the container, and set them to the numeric values for user and group numbers that show in place of your name when you use “ls -an” inside of the “mount” folder (they will probably be the same number).
For example, if inside your mount folder you see:
ls -an
total 12
drwx------ 2 1001 1001 4096 Mar 27 13:54 .
drwxr-xr-x 3 1000 1000 4096 Mar 27 13:51 ..
-rwx------ 1 1001 1001 0 Mar 27 13:54 hello.txt
-rwx------ 1 1001 1001 4 Mar 27 13:54 test.txt
Then set UID: 1001 and GID: 1001
I get the same error as you when I copy your docker-compose and try to access a folder owned by my user. When I add the UID and GID of my user id to the docker-compose (1001 for me), the error goes away.
Since you want to avoid supports and cleanup, what I would do is modify the model to flatten out the inside of the dome. You can do it easily in most slicers by adding a cylinder part and squishing it until it’s more like a disc.
A flat roof to the inside of the dome will cause it to switch to bridging for that section which won’t be perfect but will be a lot better than stringing, especially if you play around with thick bridges.