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

Docker deployment of tidal-dl-ng #341

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

Easel4932
Copy link

I created a simple Dockerfile starting from a Python Image to build a container with tidal-dl-ng installed and settings.json configured with ffmpeg path. Also modified the README.md in consequence to add instructions on how to build the container and how to run it, trying to make it as simple as possible. I hope this addition can be useful to some people and that this PR is done properly. Feel free to educate me on what to modify to do this better if needed :)

…DME.md to build and run a container that has tidal-dl-ng installed with ffmpeg and path setup in settings.json.
@exislow
Copy link
Owner

exislow commented Jan 17, 2025

Great idea, thank you very much for this PR. To be honest: In my opinion it is not really efficient to keep a separate settings.json in this repository, since it get usually generated by this app on the very first start and you can modify it with tdn cfg -h. Do you mind to propose a proper solution in this case? Instead of copying the settings.json you could add commands to modify the settings within the Dockerfile for example.

…ned folder creation a bit as well as removed now-useless settings.json from the repo.
@Easel4932
Copy link
Author

I modified the Dockerfile to use tidal-dl-ng cli to configure ffpmeg and download path and removed the settings.json. You were right, this is much cleaner now.

Dockerfile Outdated
RUN apt update

# Installing nano just in case one need to edit something in the container, installing ffmpeg for tidal-dl-ng
RUN apt install -y nano ffmpeg
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you need to install nano? This container is hopefully stable and nobody needs to edit anything in it. I would not recommend to install nano to keep the container as small as possible.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed it is useless, it is a leftover code, from when I was tinkering, that I forgot to remove. I changed the Dockerfile accordingly, thanks for pointing that out! I also wonder if the modifications I made in the README.md are fitting with the rest of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants