max-mapper / max-mapper/gifify-docker
gifify version is out of date in public registry image
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 138
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
If you run:
$ docker run -it --rm -v $(pwd):/data maxogden/gifify --version
...
2.1.1
Whereas gifify in npm is currently at 2.1.5 (and has a fix I'd like). The public registry image is of course prebuilt. I could clone this repo and build it myself, but I wonder if there's a better way to keep gifify up to date without too much effort from you? I honestly don't know, and have been running into a similar issue when using docker for builds / tools.
One way I found is to do a COPY /package.json / within the Dockerfile, and then as long as the version is pinned it will rebuild with proper caching. But that doesn't help this case too much, because this is a public tool.
Anyway, thanks for this great image! It's been extremely useful!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the docker command shown in the issue and inspect the Dockerfile and package.json relationship; compare the bundled gifify version with npm 2.1.5. Trace how the public registry image is built and published, then define an update path that preserves useful caching and verify that the published image reports the current version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100