KansaiGaijin/mbid-poller
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch 'main' of https://gitea.kansaigaijin.com/KansaiGaijin/mbid-poller

Browse Source 
Updated README.md
This commit is contained in:
Jamie Miller
2025-09-26 11:29:14 +00:00
parent f75b21ad1e 4e0696a0b4
commit 35afe1c492
1 changed files with 89 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@@ -34,8 +34,8 @@ Before starting, ensure you have:
The `mbid-poller` container needs to communicate with your Lidarr instance.
1. **Rename the Example:** Rename the provided `docker-compose.yaml.example` to `docker-compose.yaml`.
2. [cite_start]**Network Setup:** Ensure the `lidarr` and `mbid-poller` services are on the **same Docker network** (e.g., `example_network`)[cite: 4, 5]. If you use a different setup (like host network), update `LIDARR_BASE` accordingly.
3. [cite_start]**Lidarr Base URL:** Verify the `LIDARR_BASE` environment variable in the `mbid-poller` service points to your Lidarr instance[cite: 5].
2. **Network Setup:** Ensure the `lidarr` and `mbid-poller` services are on the **same Docker network** (e.g., `example_network`). If you use a different setup (like host network), update `LIDARR_BASE` accordingly.
3. **Lidarr Base URL:** Verify the `LIDARR_BASE` environment variable in the `mbid-poller` service points to your Lidarr instance.
```yaml
# Example for the default setup:
@@ -44,7 +44,7 @@ The `mbid-poller` container needs to communicate with your Lidarr instance.
### 3. Choose the MBID Input Source
[cite_start]The `poller.pl` script supports three different ways to provide MBIDs, in order of priority[cite: 5, 6]:
The `poller.pl` script supports three different ways to provide MBIDs, in order of priority:
| Environment Variable | Priority | Description |
| :--- | :--- | :--- |
@@ -52,11 +52,11 @@ The `mbid-poller` container needs to communicate with your Lidarr instance.
| `MBID_JSON_FILE` | **2nd** | A path to a local JSON file (like `ids.json`) containing the MBID array. |
| `MBID_URL` | **3rd** (Lowest) | A single MusicBrainz URL or ID to process. |
[cite_start]In your `docker-compose.yaml`, **only one** of these should be uncommented and set[cite: 5, 6, 7].
In your `docker-compose.yaml`, **only one** of these should be uncommented and set.
#### A. Using a JSON File (Recommended for simple setups)
1. [cite_start]Place your list of IDs in an `ids.json` file in the project directory (or adjust the volume mount)[cite: 7].
1. Place your list of IDs in an `ids.json` file in the project directory (or adjust the volume mount).
2. In `docker-compose.yaml`, **comment out** `MBID_API_URL` and **uncomment** `MBID_JSON_FILE`:
```yaml
@@ -75,13 +75,13 @@ The `mbid-poller` container needs to communicate with your Lidarr instance.
With your files and `docker-compose.yaml` configured, you can build and run the poller.
1. [cite_start]**Build the Container:** This compiles the Perl dependencies using the `Dockerfile`[cite: 1, 2, 3].
1. **Build the Container:** This compiles the Perl dependencies using the `Dockerfile`.
```bash
docker compose build mbid-poller
```
2. [cite_start]**Run the Poller:** Since the `restart` policy is set to `"no"`[cite: 7], this command will run the script once and exit.
2. **Run the Poller:** Since the `restart` policy is set to `"no"`, this command will run the script once and exit.
```bash
docker compose up mbid-poller