-
Notifications
You must be signed in to change notification settings - Fork 2
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 #3
Docker #3
Conversation
@clausnagel I don't have any rights on this repo jet. That's why the PR is coming from a fork. @clausnagel @yaozhihang @thomashkolbe The image works the same way the old docker run --rm --name impexp [-i -t] \
[-e CITYDB_HOST=the.host.de] \
[-e CITYDB_PORT=5432] \
[-e CITYDB_NAME=theDBName] \
[-e CITYDB_SCHEMA=theCityDBSchemaName] \
[-e CITYDB_USERNAME=theUsername] \
[-e CITYDB_PASSWORD=theSecretPass] \
[-v /my/data/:/data] \
3dcitydb/citydb-tool[:TAG] COMMAND You can use these images for testing already:
There are some points to discuss:
|
Hi @BWibo, thanks for this PR. I try to answer all your questions below.
|
The docker image build and running the citydb-tool work very nice in my tests on a WIN10 PC. |
From my side this is ready. I added a workflow to build release images too. To make it work, we need to use versioning conforming to semver. E.g. It works like this:
Note: The workflow does not apply to existing tags. So we need to create a new release to build a first release image. |
Ah wait, there is one small thing to fix. |
@clausnagel @yaozhihang Oh damn, I just accidentally pushed to |
I could not manage to re-open this. It is now: #4 |
This PR adds a build workflow and
Dockerfile
for a Docker image for thecitydb-tool
.Features
3dcitydb/citydb-tool:edge
ghcr.io/3dcitydb/citydb-tool:edge
edge
image build from the latest commit tomain
amd64
,arm64
,arm/v7