Modified dev instructions for new docker location and removed accidental

config commit.

Author: semohr

docker/dev_config/beets-flask/beets-flask-sqlite.db

@@ -21,12 +21,12 @@ services:
             # if you want to use the same beets-library inside and out:
             # YOU NEED TO MAP YOUR MUSIC FOLDER IN THE CONTAINER TO THE SAME PATH AS OUTSIDE
             # and make sure the config used in the container has the right path!
-            # - /music/:/music/
+            - ../local/music/:/music/
 
             # we put the beets and our beets-flask config into the /config directory
             # create these folders before starting the container! otherwise you might
             # get permission issues.
-            - ./dev_config/:/config
+            - ../local/config/:/config
 
             # for development. (disable if target is `prod`)
             - ../:/repo/

docker/dev_config/beets-flask/config.yaml

@@ -14,10 +14,12 @@ cd beets-flask
 We use a development container for a consistent development environment across devices You can use the provided `docker-compose-dev.yaml` to start a development container.
 
 ```bash
-docker-compose -f docker-compose-dev.yaml up --build
+docker-compose -f docker/docker-compose.dev.yaml up --build
 ```
 
-This mounts `./` to `/repo` in the container for live reloading and enhanced development experience and starts the development flask server and serves the frontend at `http://localhost:5173`.
+This mounts `./` to `/repo` in the container for live reloading and enhanced development experience and starts the development flask server and serves the frontend at `http://localhost:5173` and the backend at `http://localhost:5001`. 
+
+As always you may need to adjust the user, ports and volumes in the compose file for your specific setup. We recommend to create a copy of the `docker-compose.dev.yaml` and adjust it to your needs.
 
 ### Apple Issues