[About](#about) | [Installation](#installation) | [Docker](#docker) | [Documentation](https://digitalec.github.io/deemon) | [Support](#support)
### About
deemon is a command line tool written in Python that monitors artists for new releases, provides email notifications and can also integrate with the deemix library to automatically download new releases.
### Support
[Open an Issue](https://github.com/digitalec/deemon/issues/new) | [Discord](https://discord.gg/KzNCG2tkvn)
### Installation
#### Using pip
```bash
$ pip install deemon
```
#### From source
```bash
$ pip install -r requirements.txt
$ python3 -m deemon
```
#### Docker
Docker support has been added for `amd64`, `arm64` and `armv7` architectures. It is recommended to save your `docker run` command as a script to execute via cron/Task Scheduler.
**Note:** Inside deemon's `config.json`, download_location **must** be set to `/downloads` until I can integrate this myself.
**Example: Refreshing an existing database**
```
docker run --name deemon \
--rm \
-v /path/to/deemon/config:/config \
-v /path/to/music:/downloads \
-v /path/to/deemix/config:/deemix \
ghcr.io/digitalec/deemon:latest \
python3 -m deemon refresh
```
#### Unraid
Install Python/PIP using either Nerd-tools Plugin (Unraid 6), Python 3 for UNRAID Plugin (Unraid 6 or 7), or manually via command line.
See the installation instructions [here](https://digitalec.github.io/deemon/docs/installation.html) or install as root (**NOT** recommended!):
```bash
pip install deemon
```
Then:
```bash
deemon --init
```
If deemon is not found in your path, you can also call it as a python module:
```bash
python3 -m deemon --init
```
If installed using the **root** account, the config.json will be located at: **/root/.config/deemon/config.json**. Edit your configuration using the documentation located [here](https://digitalec.github.io/deemon/docs/configuration.html).
Use `deemon monitor -h` for help on adding artists, playlists, or albums to monitor for new releases.
#### Installation in a Python Virtual Environment (venv)
If you wish to install deemon and it's dependencies in a sandbox-style environment, I would recommend using venv.
Create a venv and install deemon (you may need to use `python3` and `pip3` depending on your system):
```commandline
$ python -m venv venv
$ source ./venv/bin/activate
$ pip install deemon
```
When you are finished, close the terminal or exit our venv:
```commandline
$ deactivate
```
Next time you want to run deemon, activate the venv first:
```commandline
$ source ./venv/bin/activate
$ deemon refresh
```
If you are moving to venv from the Docker container, be sure to update your cron/Task Scheduler scripts.
### Getting Started
You have to manually add artists, playlists, albums, etc.. deemon does not automatically pull artists unless they're being monitored. Refer to the documentation [here](https://digitalec.github.io/deemon/docs/commands/monitor.html).
================================================
FILE: deemon/__init__.py
================================================
#!/usr/bin/env python3
from deemon.utils import startup
__version__ = '2.22'
__dbversion__ = '3.7'
appdata = startup.get_appdata_dir()
startup.init_appdata_dir(appdata)
================================================
FILE: deemon/__main__.py
================================================
from deemon import cli
def main():
cli.run()
if __name__ == "__main__":
main()
================================================
FILE: deemon/assets/index.html
================================================
deemon
{UPDATE_MESSAGE}
{NEW_RELEASE_LIST}
""" all_new_releases = "" self.releases = sorted(self.releases, key=lambda x: x['release_date'], reverse=True) new_release_count = 0 for release in self.releases: if all_new_releases != "": all_new_releases += new_release_list_spacer release_date_ts = datetime.strptime(release["release_date"], "%Y-%m-%d") release_date_str = datetime.strftime(release_date_ts, "%A, %B %d").replace(" 0", " ") new_release_list_header = f"""
{release_date_str}
"""
new_release_list_item = ""
for album in release["releases"]:
new_release_count += 1
if album['record_type'].lower() == "ep":
record_type = "EP"
else:
record_type = album['record_type'].title()
if not album['track_num']:
album_info = record_type
else:
album_info = f"{record_type} | {album['track_num']} track(s)"
new_release_list_item += f"""
{album['artist']}
{album_info}
Judging by the results, it's possible that both artists are the same artist but for some reason have two separate artist profiles. It's also possible that they are unrelated and both artists happen to have the same name. You can then (hopefully) tell them apart based on their _Latest release_ and also by their _Total releases_. The _Artist ID_ is provided for reference so you can visit that specific artist in a browser if you need to. ## Navigation ```bash Discography for artist: John Doe Filter by: All | Sort by: Year (desc) 1. (2020) Broken 2. (2018) Greatest Hits Filters: (*) All (a) Albums (e) EP (s) Singles - (E) Explicit (r) Reset Sort: (y) Year Desc (Y) Year Asc (t) Title Desc (T) Title Asc Mode: (S) Toggle Select (b) Back (d) Download Queue (Q) Show Queue (f) Queue Filtered (m) Stop Monitoring :: Please choose an option or type 'exit': ```
At the top of the screen is information related to the menu you are currently on. In the example above you can see that you are looking at the _Discography_ for the artist _John Doe_. At the bottom of the screen you see four rows: Filters, Sort, Mode and Actions. ### Filters Here you can filter albums by type (albums, EP and singles), show only explicit releases and reset filters back to their default view. As of v2.22, you can now filter by date using `>=`, `<=` or `=` followed by the four digit year. For example, to find all releases between (and including) 2000 and 2003: Released in year 2000 or later: ```bash :: [SELECT] Please choose an option or type 'exit': >=2000 ``` Released in year 2003 or prior: ```bash :: [SELECT] Please choose an option or type 'exit': <=2003 ``` You'll notice the header has updated to reflect the filter: ```bash Filter: All | Sort: Release Date (desc) | Year: 2000 - 2003 ``` ### Sorting You can sort the results by release year and title, both ascending and descending. ### Modes There are two different _Modes_ available when it comes to selecting releases. _Regular_ mode is the default mode which displays a number to the left of each menu item. _Select_ mode allows you to select an album or track to add to the queue and is identified by two brackets: `[ ]` for unselected and `[*]` for selected. When selecting items, the prompt will change to let you know you are in _Select_ mode and how many items are in the queue: ```bash :: [SELECT] Please choose an option or type 'exit' (1 Queued): ``` ### Actions The _Actions_ bar is a group of actions you can perform while in the current view. Below is a list of all available actions throughout the dISC interface. You can only use an option if it is available in the _Actions_ bar. |Key|Name|Description| |-|--|---| |b|Back|Go back to the previous screen| |d|Download Queue|Download items currently in queue| |Q|Show Queue|Show all items presently in the queue| |c|Clear Queue|Clear all items from the queue| |f|Queue Filtered|Queue all items currently visible on the screen| |m|Start/Stop Monitoring|Toggle monitoring status of an artist| ================================================ FILE: docs/docs/commands/show.md ================================================ --- layout: default title: show parent: Commands --- # show {: .no_toc } ## Table of contents {: .no_toc .text-delta } 1. TOC {:toc} --- Using the `show` command, you can currently view information pertaining to artists, playlists and new releases. You can also view artist and playlist data in CSV format and export that data to a CSV file. ## Viewing artists or playlists To show a list of monitored artists: ```bash $ deemon show artists ArtistA ArtistB ``` To show a list of monitored playlists: ```bash $ deemon show playlists Summer Hits Playlist 2022 Indie Folk ``` ## CSV, filters and exporting data The `show` command allows you to view and export more data pertaining to each artist other than just their names. ### Viewing the data in CSV format First, we'll use the `-c` or `--csv` option to see all the data available: ```bash $ deemon show artists --csv name,id,bitrate,alerts,type,path John Doe,1234,,,, ``` You can also toggle the header of the CSV output by passing `--hide-header` or `-H`: ```bash $ deemon show artists -cH John Doe,1234,,,, ``` ### Using filters to customize the CSV output Next, we can apply filters to view only certain pieces of this data. If you would like to generate a CSV file containing only the ID and artists' name, you can do so by using the `-f` or `--filter` option: ```bash $ deemon show artists --csv --filter id,name id,name 1234,John Doe ``` Notice how the data is presented in the order in which you specify the filters. Filters can also be used more than once if you find the need to do so: ```bash $ deemon show artists -cf id,name,id id,name,id 1234,John Doe,1234 ``` ### Exporting monitored artists Another option for the `show artists` command is `-e` or `--export`. This allows you to export your artists to a CSV file. You can also combine this with `--hide-headers` and `--filter` to customize the data output to meet your needs. ```bash $ deemon show artists --export artists.csv CSV data has been saved to: artists.csv $ cat artists.csv name,id,bitrate,alerts,type,path John Doe,1234,,,, ``` A common use case is backing up a list of all monitored artist IDs to a CSV file which you can then import into deemon if you ever want to rebuild your database: ```bash $ deemon show artists -Hf id -e artists.csv CSV data has been saved to: artists.csv $ cat artists.csv 1234 ``` Introduced in version 2.9 is a new alias option `-b` or `--backup`. This option does the exact same thing as the previous example but does so in a much more user-friendly and simple way: ```bash $ deemon show artists --backup artists.csv CSV data has been saved to: artists.csv $ cat artists.csv 1234 ``` ## New releases You can view a list of releases that have been detected in chronological order (newest to oldest). By default, `show releases` will display the last 7 days worth of releases. You can override this by specify a number like so: ```bash $ deemon show releases 30 ``` ## Future releases You may have seen `Pending future releases` displayed in the output of the `refresh` command. When deemon detects a release with a release date in the future, it is flagged and is stored in the database until the release date approaches. If you'd like to view these future releases, you can use the `show` command: ```bash $ deemon show releases --future ``` ================================================ FILE: docs/docs/commands/test.md ================================================ --- layout: default title: test parent: Commands --- # test {: .no_toc } ## Table of contents {: .no_toc .text-delta } 1. TOC {:toc} --- ## SMTP settings test To verify that your SMTP settings are correctly configured, you may use `test --email` to send a test email to yourself. If you don't receive the email, confirm your SMTP settings with your mail provider and check the logs for additional information. --- ## Exclusions test If you have opted to use exclusion patterns or keywords to filter out releases, you may test those exclusions against any release URL to identify if that URL will be appropriately filtered out: ``` Artist: Various Artists Album: Broken Bow (Remix) Checking for the following patterns: 1. (?i)\bremix\b >> ** MATCH ** Checking for the following keywords: 1. remix >> ** MATCH ** 2. deluxe >> NO MATCH 3. bonus >> NO MATCH 4. special >> NO MATCH 5. live >> NO MATCH Result: This release would be excluded ``` ================================================ FILE: docs/docs/configuration.md ================================================ --- layout: default title: Configuration nav_order: 3 --- # Configuration {: .no_toc } deemon has some specific configuration parameters that can be defined in your config.json file. {: .fs-6 .fw-300 } ## Table of contents {: .no_toc .text-delta } 1. TOC {:toc} --- ## Configuration Location Depending on your operating system, your config.json file will be located in one of the locations below. When deemon is run with a command, it will automatically generate a default config if an existing configuration file is not present. For example: to generate this configuration file, run `deemon refresh`. - **Linux**: /home/user/.config/deemon - **macOS**: /User/user/Library/Application Support/deemon - **Windows**: %appdata%\deemon ### Default Configuration (Version 2.19.2) ```json { "check_update": 1, "debug_mode": false, "release_channel": "stable", "query_limit": 5, "smart_search": true, "rollback_view_limit": 10, "prompt_duplicates": false, "prompt_no_matches": true, "fast_api": true, "fast_api_threads": 25, "exclusions": { "enable_exclusions": true, "patterns": [], "keywords": [], }, "new_releases": { "release_max_age": 90, "include_unofficial": false, "include_compilations": false, "include_featured_in": false, }, "global": { "bitrate": "320", "alerts": false, "record_type": "all", "download_path": "", "email": "" }, "deemix": { "path": "", "arl": "", "check_account_status": true, "halt_download_on_error": false, }, "smtp_settings": { "server": "", "port": 465, "starttls": false, "username": "", "password": "", "from_addr": "" }, "plex": { "base_url": "", "ssl_verify": true, "token": "", "library": "" } } ``` ## Configuration Types There are technically three different "levels" of configuration in deemon. The first level (and default) is the "global" configuration, the second level is the "profile" configuration and the third level is the "per-artist" configuration. ### Global Configuration The global configuration is defined inside the `config.json` configuration file. This configuration is used by default when running deemon and the values defined in this configuration may be temporarily superseded by a [Profile](#profile-configuration-optional) or an [Artist](#per-artist-configuration-optional) configuration. ### Profile Configuration *(optional)* Within deemon, you can configure multiple profiles (using the `profile` command) which monitors their own sets of artists and can use settings that override the _Global Configuration_ while inheriting the settings that are not defined. You can also think of these profiles as separate users. For example, if you create a new profile and only specify a download path, that profile will inherit the other settings from the _Global Configuration_. ### Per-Artist Configuration *(optional)* Within deemon, you can configure different settings for each individual artist (using the `config` command). This gives you the flexibility to disable alerts for certain artists or specify a certain release type, bitrate or download path.
## Global Configuration This section outlines each setting available in the configuration file and their respective options. --- ### Global settings These settings affect the general operation of deemon. |Setting|Description| |-|---| |**check_update**
|This option allows you to specify how frequently (in days) to check for new updates to deemon. To disable checking for updates, change this to `0`.
| |**debug_mode**
options: _true, false_
|This option will allow you to print extra debug messages in the logs or on screen if used with `--verbose`.
| |**release_channel**
options: _stable, beta_
|When checking for updates (if enabled), this option allows you to choose what updates you are notified about. Most users will want to use _stable_. If you are interested in testing pre-release versions of deemon, you can set this to _beta_.
| |**query_limit**
options: _number_
|This option allows you to specify how many results are displayed when using the `search` command or when prompted using the `monitor` command (see _prompt_duplicates_ and _prompt_no_matches_ below).
| |**smart_search**
options: _true, false_
|This option allows you to skip the list of artist search results and proceed directly to the list of artist albums, provided there is only one exact match of the artists name (case insensitive).
| |**rollback_view_limit**
|This option allows you to specify the maximum number of transactions to display using the `rollback` command
| |**prompt_duplicates**
options: _true, false_
|When adding a new artist using the `monitor` command, deemon will choose the highest ranked artist in situations where two artists have identical names. Instead, you can set this option to `true` which will prompt you with choices including the latest release from each artist to help you better decide which is the artist you're looking for.
| |**prompt_no_matches**
options: _true, false_
|When adding a new artist using the `monitor` command, if deemon does not find an **exact** match for the artist you're searching for, it will prompt you with a list of results returned from the Deezer API.
| |**fast_api**
options: _true, false_
|In previous versions of deemon, this was referred to as the _experimental_api_ and has been the default API since version 2.1.
| |**fast_api_threads**
options: _number_
|This sets the number of threads to spawn when accessing the API. The higher the number, the faster artist data is retrieved. However, setting this number too high may result in a temporary ban of your IP address. **It is recommended to keep this number below 50.**
| --- ### Exclusion settings Exclusions can be setup to ignore releases matching a specific regular expression ("pattern") or by matching against specific keywords. You can test your exclusion settings by using the `test` command. |Setting|Description| |-|---| |**enable_exclusions**
options: _true, false_
|This setting enables exclusion patterns and keywords (below) to filter out releases.
| |**patterns**
options: _regex_
|Provide a list of regular expressions to filter out releases.
| |**keywords**
options: _true, false_
|Provide a list of keywords to filter out releases (_remix, deluxe, bonus_).
| --- ### New Release settings These settings affect what releases are filtered out by deemon. As of version 2.9, these settings are global only and cannot be configured in a profile nor per-artist configuration. |Setting|Description| |-|---| |**release_max_age**
|This lets you control how far back to consider a new release 'new' from it's actual release date. This setting is helpful if you only run a `refresh` monthly or if there is a delay in Deezer adding a release to their catalogue. If you wish to get all releases regardless of when they were released, set this to _0_.
**Note:** Version 2.8.x and earlier relied on a separate toggle _by_release_date_ which has been deprecated in favor of setting _release_max_age_ to _0_.
| |**include_unofficial**
options: _true, false_
|Each release result returned from the API includes a boolean value designating the release as either an official artist release or not. In many cases, this flag is incorrectly set resulting in some official releases not being detected.
**Warning:** If you are enabling this option on an existing database, you could potentially have hundreds or thousands of new releases detected.
| |**include_compilations**
options: _true, false_
|If you want to include all compilation albums that your artists are featured on, you can enable this.
**Warning:** If you are enabling this option on an existing database, you could potentially have hundreds or thousands of new releases detected.
| |**include_featured_in**
options: _true, false_
|Enabling this option will include every single release/track an artist is associated with. It is highly recommend to avoid using this but is included for testing purposes.
**Warning:** If you are enabling this option on an existing database, you could potentially have **_tens of thousands_** of new releases detected. Most users will NOT want this option enabled.
| --- ### Global settings These settings can be overriden within deemon using _profiles_ or by specifying a _per-artist configuration_. |Setting|Description| |-|---| |**bitrate**
options: _128, 320, FLAC_
|This option allows you to specify the bitrate used for downloads.
| |**alerts**
options: _true, false_
|Enable or disable email notification alerts when new releases are present. You must also have your email settings configured (see _[SMTP Settings](#smtp-settings)_).
| |**record_type**
options: all, album, ep, single
|This option allows you to specify what release types you wish to download upon release. Keep in mind, most EPs are labelled as albums in the Deezer API.
**Limitation:** Currently only one option at a time is allowed.
| |**download_path**
|This option allows you to specify where downloads are saved. If no path is provided, downloads will be saved in the default directory specified by deemix.
**Windows users:** When providing a path, you **must** use double backslashes: `C:\\Music` or forward slashes: `C:/Music`.
| |**email**
|This option allows you to specify the default email address to use when alerts are enabled and SMTP settings are defined.
| --- ### deemix settings These settings are needed for deemon to interface with deemix which is a third party library that does the actual downloading. |Setting|Description| |-|---| |**path**
|Specify the path to where your deemix configuration is stored. For most users, leave this blank. If you have moved the deemix configuration, you must specify that here.
| |**arl**
|This is your authorization token required by `deemix` to authenticate your Deezer account. This is stored in a cookie named `arl` in your browser after logging in to Deezer.
| |**check_account_status**
options: _true, false_
|This option allows you to force account verification before doing a refresh. If you have _bitrate_ set to FLAC and your account type is not HiFi, deemon will exit until you correct the issue (expired ARL or subscription). This option is useful for preventing low quality downloads due to an expired subscription.
| |**halt_download_on_error**
options: _true, false_
|If enabled, deemon will exit if deemix reports any errors when downloading. This prevents releases from being logged in the database so that you can try again later.
| --- ### SMTP settings These settings are needed for deemon to interface with deemix which is a third party library that does the actual downloading. |Setting|Description| |-|---| |**server**
|Server address for your mail server
| |**port**
|Port used to connect to your mail server (typically 587 or 465)
| |**starttls**
options: _true, false_
|If your mail server requires STARTTLS, you can enable that here.
| |**username**
|Username required to login to your mail server
| |**password**
|Password used to authenticate your account with your mail server
| |**from_addr**
|This is the email address your email is to be sent _from_ and typically must be a real address associated with your account on your mail server.
| --- ### Plex integration settings deemon features support for refreshing your Plex library after a download operation is complete. Plex has the ability to automatically detect changes and rescan but if you're having issues with that, this should help. |Setting|Description| |-|---| |**base_url**
|This is the URL to reach your Plex server including the port and protocol.
_Example_: http://192.168.0.2:32400
**Note:** You may need to use _https_ if your Plex setup is configured for secure connections.
| |**ssl_verify**
options: _true, false_
|If you have Plex configured to require secure connections, but have not provided a custom certificate, keep this set to _false_ to avoid SSL certificate errors.
| |**token**
|Authentication token required to connect to your Plex server
For instructions on how to find your token, [click here](https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/).
| |**library**
|The name of your Plex library to be refreshed.
| ================================================ FILE: docs/docs/installation.md ================================================ --- layout: default title: Installation nav_order: 2 --- # Installation {: .no_toc } ## Table of contents {: .no_toc .text-delta } 1. TOC {:toc} --- ## Step 1 - Required Dependencies In order to install and run deemon, you'll need to have at least Python 3.6 or higher installed along with the `pip` package manager. Please refer to [python.org](https://www.python.org/downloads/) for more information. ### Step 2 - Installing deemon Once you have at least Python 3.6 installed, go ahead and install deemon using `pip`. On some distributions, the `pip` command is for Python2. In this case, substitute `pip` for `pip3` in the commands below. **Windows users**: These commands should be typed in a Command Prompt, Windows Terminal or Powershell window. ```bash # Latest stable release $ pip install deemon # Latest release (including pre-release/beta) $ pip install --pre deemon ``` At this point, pip will download deemon and any other modules required to allow deemon to function. Once it's complete, use the following command to make sure deemon is installed: ```bash $ deemon -V deemon 2.19.2 ``` ## Configuration & First Use Congrats! If you've made it this far, you have successfully installed deemon. There are a few things you should configure before using deemon. Head on over to the [configuration](configuration.md) page to learn more. ================================================ FILE: docs/docs/troubleshooting/logs.md ================================================ --- layout: default title: Logs parent: Troubleshooting --- # Logs {: .no_toc } ## Table of contents {: .no_toc .text-delta } 1. TOC {:toc} --- If you're having issues or would like to see how things are running, you can view the log files which are located inside the [deemon config directory](/docs/configuration#configuration-file). As of version 1.0, the logs from deemix are now included (as well as other third-party modules used) in the deemon log file. ================================================ FILE: docs/docs/troubleshooting/queue.md ================================================ --- layout: default title: Queue parent: Troubleshooting --- # Queue {: .no_toc } ## Table of contents {: .no_toc .text-delta } 1. TOC {:toc} --- Each time deemon finds new releases, they are dumped to `queue.csv` inside the deemon application directory. This provides a way to recover a failed job. To redownload a queue, you can manually extract the `album_id` or `track_id` column and save it into a new file to pass to deemon: Album IDs: `deemon download --album-file file.csv` Track IDs: `deemon download --track-file file.csv` ================================================ FILE: docs/docs/troubleshooting/troubleshooting.md ================================================ --- layout: default title: Troubleshooting nav_order: 6 has_children: true permalink: /docs/troubleshooting --- ================================================ FILE: docs/index.md ================================================ --- layout: default title: Home nav_order: 1 description: "deemon is a monitoring utility for new artist releases that can provide email alerts and automate downloading via the deemix library" permalink: / --- # deemon 2.22 Documentation {: .fs-9 } deemon is a monitoring utility for new artist releases that can provide email alerts and automate downloading via the deemix library {: .fs-6 .fw-300 } [Get started now](#getting-started){: .btn .btn-primary .fs-5 .mb-4 .mb-md-0 .mr-2 } [View it on GitHub](https://github.com/digitalec/deemon){: .btn .fs-5 .mb-4 .mb-md-0 } Version 2.22 --- ## Disclaimer deemon does not download anything by itself. It requires a third party library called *deemix* in order to do this and will be installed automatically when installed via pip. --- ## Getting started ### Dependencies deemon depends on various python modules and libraries to perform all of its functions. Please refer to the `requirements.txt` file to see what those dependencies are. ### Installation & Configuration When you're ready to install deemon, head on over to the [installation]({{ site.baseurl }}{% link docs/installation.md %}) page. Once you've installed deemon, it is important to [configure]({{ site.baseurl }}{% link docs/configuration.md %}) it properly to get the best experience. --- ## About the project deemon (**dee**zer **mon**itor) is an open source project that came from the need to stay on top of new releases by some of my favorite artists. ### License deemon is distributed by a [GPL-3.0 license](https://github.com/digitalec/deemon/blob/main/LICENSE). ================================================ FILE: requirements.txt ================================================ deemix~=3.6 packaging~=23.0 requests~=2.28.0 click~=8.1.0 setuptools~=66.1.0 wheel~=0.43.0 PlexAPI~=4.5.2 tqdm~=4.61.0 mutagen~=1.46 Unidecode~=1.3.6 ================================================ FILE: setup.py ================================================ from pathlib import Path from setuptools import setup, find_packages from deemon import __version__ with open('requirements.txt') as f: required = f.read().splitlines() HERE = Path(__file__).parent README = (HERE / "README.md").read_text() DESCRIPTION = "Monitor new releases by a specified list of artists and auto download using the deemix library" setup( name="deemon", version=__version__, author="digitalec", description=DESCRIPTION, long_description=README, long_description_content_type="text/markdown", license="GPL3", classifiers=[ "License :: OSI Approved :: GNU General Public License v3 (GPLv3)", "Programming Language :: Python :: 3.8", "Operating System :: OS Independent", ], packages=find_packages(), include_package_data=True, python_requires=">=3.8", install_requires=required, url="https://github.com/digitalec/deemon", entry_points = { "console_scripts": ["deemon=deemon.__main__:main"], } )