Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add Readarr custom service #671

Merged
merged 2 commits into from
Aug 8, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions docs/customservices.md
Original file line number Diff line number Diff line change
Expand Up @@ -96,18 +96,19 @@ Two lines are needed in the config.yml :
The url must be the root url of Medusa application.
The Medusa API key can be found in General configuration > Interface. It is needed to access Medusa API.

## Lidarr, Prowlarr, Sonarr and Radarr
## Lidarr, Prowlarr, Sonarr, Readarr and Radarr

This service displays Activity (blue), Warning (orange) or Error (red) notifications bubbles from the Lidarr, Radarr or Sonarr application.
This service displays Activity (blue), Warning (orange) or Error (red) notifications bubbles from the Lidarr, Readarr, Radarr or Sonarr application.
Readarr display also a Missing (purple) notification bubbles.
Two lines are needed in the config.yml :

```yaml
type: "Lidarr", "Prowlarr", "Radarr" or "Sonarr"
apikey: "<---insert-api-key-here--->"
```

The url must be the root url of Lidarr, Prowlarr, Radarr or Sonarr application.
The Lidarr, Prowlarr, Radarr or Sonarr API key can be found in Settings > General. It is needed to access the API.
The url must be the root url of Lidarr, Prowlarr, Readarr, Radarr or Sonarr application.
The Lidarr, Prowlarr, Readarr, Radarr or Sonarr API key can be found in Settings > General. It is needed to access the API.
If you are using an older version of Radarr or Sonarr which don't support the new V3 api endpoints, add the following line to your service config "legacyApi: true", example:

```yaml
Expand Down
112 changes: 112 additions & 0 deletions src/components/services/Readarr.vue
Original file line number Diff line number Diff line change
@@ -0,0 +1,112 @@
<template>
<Generic :item="item">
<template #indicator>
<div class="notifs">
<strong v-if="activity > 0" class="notif activity" title="Activity">
{{ activity }}
</strong>
<strong v-if="missing > 0" class="notif missing" title="Missing">
{{ missing }}
</strong>
<strong v-if="warnings > 0" class="notif warnings" title="Warning">
{{ warnings }}
</strong>
<strong v-if="errors > 0" class="notif errors" title="Error">
{{ errors }}
</strong>
<strong
v-if="serverError"
class="notif errors"
title="Connection error to Readarr API, check url and apikey in config.yml"
>?</strong
>
</div>
</template>
</Generic>
</template>

<script>
import service from "@/mixins/service.js";
import Generic from "./Generic.vue";

const API = "/api/v1";

export default {
name: "Readarr",
mixins: [service],
props: {
item: Object,
},
components: {
Generic,
},
data: () => {
return {
activity: null,
missing: null,
warnings: null,
errors: null,
serverError: false,
};
},
created: function () {
this.fetchConfig();
},
methods: {
fetchConfig: function () {
const handleError = (e) => {
console.error(e);
this.serverError = true;
};
this.fetch(`${API}/health?apikey=${this.item.apikey}`)
.then((health) => {
this.warnings = health.filter((h) => h.type === "warning").length;
this.errors = health.filter((h) => h.type === "errors").length;
})
.catch(handleError);
this.fetch(`${API}/queue?apikey=${this.item.apikey}`)
.then((queue) => {
this.activity = queue.totalRecords;
})
.catch(handleError);
this.fetch(`${API}/wanted/missing?apikey=${this.item.apikey}`)
.then((missing) => {
this.missing = missing.totalRecords;
})
.catch(handleError);
},
},
};
</script>

<style scoped lang="scss">
.notifs {
position: absolute;
color: white;
font-family: sans-serif;
top: 0.3em;
right: 0.5em;
display: flex;
gap: 0.2rem;
.notif {
padding: 0.2em 0.35em;
border-radius: 0.25em;
font-size: 0.8em;
&.activity {
background-color: #4fb5d6;
}

&.missing {
background-color: #9d00ff;
}

&.warnings {
background-color: #d08d2e;
}

&.errors {
background-color: #e51111;
}
}
}
</style>
Loading