Closed BWibo closed 9 months ago
@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 impexp
image did:
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:
bwibo/citydb-tool:edge
ghcr.io/bwibo/citydb-tool:edge
There are some points to discuss:
README.md
of this repo. Then everybody can test it, until the new docs are ready.Hi @BWibo, thanks for this PR. I try to answer all your questions below.
CITYDB_TYPE
. We currently only support PostgreSQL, so we have skipped this ENV variable for the moment.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. 0.5.0-beta
, 0.5.0
It works like this:
latest
too.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 main
. Two remotes are the core of all evil! ;-)
I force pushed main back to where I believe it was. Can you please check it's the correct commit? And sry.
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