Docker image

[krezovic]

This is more of an info. Feel free to either include Dockerfile here, ignore and close the issue, or link to the docker repository.

I've created an image for this module and published it at docker hub. This prevents me from installing tons of packages on a server where they shouldn't be needed, so I can automate deployment of nexus3.

FROM python:3-alpine

USER root

RUN apk add --no-cache --update --virtual .build-deps build-base libffi-dev openssl-dev && \
    pip install nexus3-cli && \
    apk del .build-deps && \
    rm -rf ~/.cache/pip

https://hub.docker.com/r/krezovic/nexus3-cli

[thiagofigueiro]

That's great, @krezovic - I think I'll create a separate project to build this weekly so we always have a docker image with the latest security updates.

I also want to add an ENTRYPOINT so one can pass direct arguments to the utility.

What do you do when you have to transfer files? Do you manually mount a volume to $(pwd)?

[krezovic]

Hi, your suggestion about entrypoint sounds good.

As for the file transfer, I'm not sure how it works as I haven't tried it. I've only mounted user's home dir (USER root), to be able to store nexus login credentials inside my own home dir.

[thiagofigueiro]

With regards to authentication, another option would be to make the login options global so that they can be set as environment variables for any subcommand.

If the docker container then has access to these variables, the utility could use the credentials without having to rely on a config file.

[krezovic]

Nice, I did not know all commands support the login options. It can be automated easily enough with a bash script.

[thiagofigueiro]

Any options can be passed as an environment variable - this comes for free with click.

But the login options are currently only accepted with the login command. It should be easy enough to make them global.

[thiagofigueiro]

Added the suggested dockerfile and a follow-up issue #119