-
-
Notifications
You must be signed in to change notification settings - Fork 50
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] Running the docker container without starting up a web instance #119
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Regarding your need to run this sporattically, regardless of the web server running, it's not going to stop this functionality. |
That suggestion does work. However, to script this import, that means that I would have to do a: start To be able to script the import. That assumes that the exec doesn't have any issues. |
Regardless of the web server running or not, you would need script something like that anyways? |
Even in a script with it's current state you'd still have to handle the management of the webserver. In the context of a single exectution run, thats a bit excessive. |
Mount a dummy
Contents of the
beets web service no longer starts with the container:
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is locked due to inactivity |
Is this a new feature request?
Wanted change
I would like to be able to query beets without standing up a web server here. This would run it as a CLI command
Reason for change
Need for this is that the importing and collection management isn't needed as a true server sense. The need is so that I can run this sporattically when needed.
Proposed code change
Adding environment varraible
Adding conditional logic in the service d to not start up the beets server.
Accept the arguements as what to run from the command line.
The text was updated successfully, but these errors were encountered: