fix: resolve merge conflicts with master

- config.yaml: adopt master's env_vars block and version (1.76.12), drop data_folder option
- run: adopt master's /config/data symlink approach (real dir chowned by entrypoint, then symlinked)
- README: keep badge indent fix, update config table to remove data_folder row, fix install steps
- docker-entrypoint.sh: keep passthrough (master doesn't have this file)

aurral/README.md

@@ -8,7 +8,6 @@ This addon is based on the docker image https://github.com/lklynet/aurral
 | Option | Default | Description |
 |---|---|---|
 | `download_folder` | `/share/aurral/downloads` | Path where Aurral writes flow downloads. Must be under `/share`. |
-| `data_folder` | `/share/aurral/data` | Path for Aurral's database and persistent config. Must be under `/share`. |
 
 ## Installation
 
@@ -22,7 +21,7 @@ The installation of this add-on is pretty straightforward and not different in c
 
 2. Install this add-on.
 3. Click the `Save` button to store your configuration.
-4. Set the `download_folder` and `data_folder` options to your preferred paths.
+4. Set the `download_folder` option to your preferred path.
 5. Start the add-on.
 6. Check the logs of the add-on to see if everything went well.
 7. Open the webUI and complete onboarding.

aurral/config.yaml

@@ -1,5 +1,5 @@
 name: Aurral
-version: "1.76.12-1"
+version: "1.76.12"
 slug: aurral
 description: >-
   Self-hosted music discovery, request management, flows, and playlist
@@ -29,6 +29,11 @@ map:
   - share:rw
   - media:rw
 
+env_vars:
+  - name: DOWNLOAD_FOLDER
+    description: "Path for music downloads"
+    required: false
+
 options:
   download_folder: /share/aurral/downloads
 

aurral/rootfs/etc/services.d/aurral/run

@@ -8,15 +8,22 @@ DOWNLOAD_FOLDER=$(bashio::config 'download_folder')
 # Ensure host-side download directory exists
 mkdir -p "${DOWNLOAD_FOLDER}"
 
+# Aurral writes its database/config to /app/backend/data inside the container.
+# We bind that to HA's addon_config directory (/config) which is always writable.
+# The upstream entrypoint chowns /app/backend/data — this must be a real directory,
+# not a symlink to a protected HA path, so we do NOT symlink it.
+mkdir -p /config/data
+
+# If /app/backend/data exists as a real dir (from image), replace with our persistent dir
+if [ ! -L /app/backend/data ]; then
+  rm -rf /app/backend/data
+  ln -sf /config/data /app/backend/data
+fi
+
 bashio::log.info "Starting Aurral"
-bashio::log.info "  Data      : /data (HA persistent storage)"
 bashio::log.info "  Downloads : ${DOWNLOAD_FOLDER}"
+bashio::log.info "  Data      : /config/data"
 
-# /data is HA's private persistent storage, automatically mounted per-addon.
-# AURRAL_DATA_DIR redirects Aurral's database/config there.
-# DOWNLOAD_FOLDER is user-configured and points to /share.
-export AURRAL_DATA_DIR="/data"
 export DOWNLOAD_FOLDER="${DOWNLOAD_FOLDER}"
-export WEEKLY_FLOW_FOLDER="${DOWNLOAD_FOLDER}/weekly-flow"
 
-exec node /app/backend/server.js
+exec /usr/local/bin/docker-entrypoint.sh node /app/server.js