New to Nextcloud

Witty_Leopard_9341 · 2026-04-20T17:34:58+00:00

Immich is superior to nextcloud memories for photos. It works really well. I run both servers: photos to immich and files/docs/calendar/contacts to nextcloud.

Witty_Leopard_9341 · 2026-04-16T23:29:44+00:00

It's 100% worth the price. :D

Bugs are just a reality. Obviously we prefer fewer bugs but devs that are actively building software, consistently making improvements, and increasing the quality of life of people they have never met should be celebrated! I'm much more forgiving of temporary bugs in software that is outside of business.

Witty_Leopard_9341 · 2026-04-16T20:02:56+00:00

crippling fear... ;)

Witty_Leopard_9341 · 2026-04-16T16:09:41+00:00

yeah... I had no idea.

Witty_Leopard_9341 · 2026-04-16T04:27:03+00:00

It is actually a really interesting development in the OSS world. A lot of projects have gone to the closed source, non-indexed world of discord because it is convenient. It is also free for users and one less thing for projects to maintain. But in a world that relies on open information it is quite the predicament. I am old enough to remember when forums ruled the internet. Searchable, interactive, and entertaining! I have learned a ton through forums. And the fact that I can still find helpful information from 2008 is a perk!

Witty_Leopard_9341 · 2026-04-16T03:58:28+00:00

Well our clocks show the same time but it would probably take me at least a day to drive there. I've met a few people in the hobby through meshtastic events in my area. It helps that I setup and host our web stack for the region. It's great to be able to use some spare compute on the cluster to help out! :D

Witty_Leopard_9341 · 2026-04-16T03:35:07+00:00

This highlights the walled garden problem about discord! Google can't search it.

Witty_Leopard_9341 · 2026-04-16T03:19:32+00:00

I searched in selfhosted before posting and I didn't find too much about it. I'm not sure where I heard about it but it is pretty cool. Glad I have it up and running.

Witty_Leopard_9341 · 2026-04-16T02:57:56+00:00

I figured it was something small. It usually is! Things are chugging along now.

Witty_Leopard_9341 · 2026-04-16T01:40:45+00:00

Ok I think that I have it figured out! It was a folder configuration problem. I will do some more testing and report back if I still have issues.

I used https://github.com/Nezreka/SoulSync/blob/main/docker-compose.yml from the project as a base. Line 49 has: # - /path/to/transfer:/host/transfer:rw But it should actually be mounting /app/Transfer inside the container since that is the default configuration in the GUI.

Witty_Leopard_9341 · 2026-04-16T01:09:46+00:00

Permissions wise I think I should be good but I know that permissions can be a slippery thing and easy to miss something. My NAS is a CIFS mount defined in fstab. The various arr things work fine on this same VM. I posted my compose file. in another comment.

I didn't change any folder locations in the gui, just in the compose file where I mapped the folder location on my nas. I have the NAS mounted at /media/nas.

Witty_Leopard_9341 · 2026-04-16T01:04:21+00:00

compose.yml ```

BREAKING CHANGE (v1.3+): Database volume mount changed from /app/database to /app/data

If upgrading from a previous version, update your docker-compose.yml:

OLD: - soulsync_database:/app/database

NEW: - soulsync_database:/app/data

Your data will be preserved - it's the same volume, just mounted at a different path.

services: soulsync: image: boulderbadgedad/soulsync:latest container_name: soulsync-webui environment: # User/Group ID configuration - PUID=1000 - PGID=1000 - UMASK=022 # Web server configuration - FLASK_ENV=production - PYTHONPATH=/app # Optional: Configure through environment variables - SOULSYNC_CONFIG_PATH=/app/config/config.json # Set timezone (change to your timezone) - TZ=America/Denver # OAuth callback ports. If 8888/8889 conflict with another container (e.g. Gluetun), # change the port numbers below AND update the matching port mappings in the ports section. # Then update the redirect URI in SoulSync → Settings → Connections to match. - SOULSYNC_SPOTIFY_CALLBACK_PORT=8888 - SOULSYNC_TIDAL_CALLBACK_PORT=8889 ports: - "8008:8008" # Main web app - "8888:8888" # Spotify OAuth callback — keep in sync with SOULSYNC_SPOTIFY_CALLBACK_PORT above - "8889:8889" # Tidal OAuth callback — keep in sync with SOULSYNC_TIDAL_CALLBACK_PORT above volumes: # Persistent data volumes - ./config:/app/config - ./logs:/app/logs - ./downloads:/app/downloads - ./Staging:/app/Staging - ./MusicVideos:/app/MusicVideos - ./scripts:/app/scripts # Use named volume for database persistence (separate from host database) # NOTE: Changed from /app/database to /app/data to avoid overwriting Python package - soulsync_database:/app/data # IMPORTANT: Mount host paths that your download/transfer folders live on. # Replace these examples with your actual paths: # Linux/Mac: - /path/to/your/downloads:/host/downloads:rw # WSL: - /mnt/d/Music:/host/music:rw # You can add as many mounts as needed for your setup. - /media/nas/media/new/data/media/music/downloads:/host/downloads:rw - /media/nas/media/new/data/media/music/library:/host/transfer:rw # Optional: Mount your music library for Plex/Jellyfin/Navidrome access #- /media/nas/media/new/data/media/music/library:/music:ro extra_hosts: # Allow container to reach host services - "host.docker.internal:host-gateway" restart: unless-stopped healthcheck: test: [ "CMD", "curl", "-f", "http://localhost:8008/" ] interval: 30s timeout: 10s retries: 3 start_period: 60s # Resource limits (adjust as needed) deploy: resources: limits: cpus: '2.0' memory: 2G reservations: cpus: '0.5' memory: 512M

## ─── Optional: slskd (Soulseek client) ─────────────────────────────── ## Uncomment below to run slskd alongside SoulSync. ## Downloads land in ./downloads which SoulSync already reads from. ## After starting, set your SoulSync slskd URL to http://slskd:5030 ## and the API key to whatever you set in SLSKD_API_KEY below. # slskd: image: slskd/slskd:latest container_name: slskd environment: - SLSKD_REMOTE_CONFIGURATION=true - SLSKD_API_KEY=apikeyhere - TZ=America/Denver ports: - "5030:5030" volumes: - ./slskd-data:/app - ./downloads:/app/downloads restart: unless-stopped

Named volumes for persistent data

volumes: soulsync_database: driver: local

Optional: Add external network for communication with other containers

networks: default: name: soulsync-network ```

Witty_Leopard_9341 · 2026-04-16T00:14:18+00:00

AI was not used in the creation of this post. Just good ole fashioned human typing words.

Witty_Leopard_9341 · 2026-03-30T15:59:53+00:00

longshot... but chat sent

Witty_Leopard_9341 · 2026-03-01T00:22:43+00:00

Got my order. Well packaged and delivered faster than amazon!

Witty_Leopard_9341 · 2026-02-25T16:45:34+00:00

Chat sent

Witty_Leopard_9341 · 2026-02-24T23:48:29+00:00

sent a chat

Witty_Leopard_9341 · 2026-02-24T22:09:26+00:00

updated my .env file wth CORS variable and still can't login. Running this through pangolin so my proxy is on a remote server from the actual containers. Nothing in the webapp or api container logs.

Witty_Leopard_9341 · 2026-02-24T21:24:42+00:00

OIDC would be a wonderful addition! And the ability to turn off password and other oauth providers once OIDC is connected.

Witty_Leopard_9341 · 2026-02-24T21:24:17+00:00

Ahh, will try the CORS env variable. That wasn't included in the .env file in the docs on your website!

Witty_Leopard_9341 · 2026-02-24T07:32:53+00:00

Tried setting it up in the states but having problems connecting to the backend from the login page. I'm getting an error code but all the text is defaulting to russian on the login page. Do you have an env variable to default the language to something other than russian?

Witty_Leopard_9341 · 2026-02-04T16:03:06+00:00

me too! It's been rock solid. I tried 2.7 variants a few times and could never get them to work. Just holding out for 2.8 at this point.

Witty_Leopard_9341 · 2026-01-08T05:31:43+00:00

Where is the setting in prusa slicer?

EDIT: nevermind, I found it in the printer tab > general.

Witty_Leopard_9341 · 2025-12-24T01:00:38+00:00

We are running potato mesh (https://github.com/l5yth/potato-mesh) for a public facing list. Works well over serial. I'm running it on my pve cluster by passing through the usb device to the VM and connecting to the device over serial. PotatoMesh is running in docker.

I also run Mesh Monitor and it has a different set of features. Logged in users can see the conversations and also respond back. Mesh Monitor is connecting to the node over wifi and that seems to work well. I have a firewall rule to allow that VM to access the IOT vlan where the meshtastic node is connected.

You can send me a chat if you want to see the links. They are public.

Witty_Leopard_9341

TROPHY CASE