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: support for grabbing latest from master #90

Closed
jef opened this issue Jul 7, 2020 · 4 comments
Closed

feat: support for grabbing latest from master #90

jef opened this issue Jul 7, 2020 · 4 comments

Comments

@jef
Copy link

jef commented Jul 7, 2020

linuxserver.io

It'd be nice to have multiple versions to grab from calibre-web.


Expected Behavior

Adding a Docker tag of nightly like beets would be beneficial as releases don't happen as often as other services (Sonarr, Radarr, etc).

Current Behavior

Only includes latest release.

@jef
Copy link
Author

jef commented Jul 7, 2020

I believe this can be solved by using CALIBREWEB_RELEASE to master. Maybe should just update the doc to include this unless it's somewhere else that specifies this configuration?

@aptalca
Copy link
Member

aptalca commented Jul 7, 2020

if you're just troubleshooting, you can build it locally and pass the docker arg. Instructions are in the readme: https://github.com/linuxserver/docker-calibre-web#building-locally

Before we decide to publish a new tag, we'd have to take into consideration various things like how much interest there is for building master commits, how stable they are, how frequent they are, etc.

@jef
Copy link
Author

jef commented Jul 10, 2020

Releases seem to vary. Most things pushed to master are fixes rather than features it seems. I'll build locally for now and go from there.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@jef jef closed this as completed Aug 10, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants