https://github.com/philpennock/poetry
Some sample data
https://github.com/philpennock/poetry
docker-image kipling poetry sample-data
Last synced: about 1 year ago
JSON representation
Some sample data
- Host: GitHub
- URL: https://github.com/philpennock/poetry
- Owner: philpennock
- Created: 2018-02-19T00:45:24.000Z (over 8 years ago)
- Default Branch: main
- Last Pushed: 2020-06-14T07:08:04.000Z (about 6 years ago)
- Last Synced: 2025-01-24T17:18:08.503Z (over 1 year ago)
- Topics: docker-image, kipling, poetry, sample-data
- Size: 3.91 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
poetry
======
This repo holds some dummy data, which exists purely for workflow tests with
build systems.
The contents of the `poems` directory might have various things done with
them.
That's it.
---
Pushes to this repo are automatically built at Docker Hub into the image
`philpennock/poetry`:
---
We generate a Docker image. This is silly for data this small.
Normally you use a Docker image to hold "something executable", to treat a
"userland contents" bundle like a program. In this case, there's nothing to
execute. Thus usually you'd use some kind of tarball/zipfile to hold this
data.
But for much larger data-sets, being able to use Docker image caching
caching pays off, as you just pull when there's a difference. You can build
repeatedly and get proper caching across builds which otherwise don't share
content.
There are security model trade-offs involved, around private/sensitive data.
Think carefully before going this route. But if you're going to, then here's
some trivial sample data, consisting of a very few poems, which can help you
test the workflows.
Ideally, you want to use a `VOLUME` directive in your Dockerfile, and be able
to satisfy the source of that Volume directly from a Docker image. Instead,
you'll probably need some kind of workaround.
---