Publish `2.0.0-alpha.1` crate

[josecelano]

Testing the:

• Docker image release workflow
• Package release on crates.io

I'm following the version convention used on torrust-tracker.

[josecelano]

Hi @WarmBeer to publish docker images you have to set up the environment like the tracker. I can't do it:

[josecelano]

The package was published on crates.io.

[mickvandijke]

Hi @josecelano ,

I have added the following environment to torrust/torrust-index-backend:

[josecelano]

@WarmBeer it seems the credentials are wrong: https://github.com/torrust/torrust-index-backend/actions/runs/5002547167/jobs/8962758264#step:4:23

[mickvandijke]

@WarmBeer it seems the credentials are wrong: https://github.com/torrust/torrust-index-backend/actions/runs/5002547167/jobs/8962758264#step:4:23

Hmm sorry, I might have put in the wrong username. I have updated it now. Could you try again?

[josecelano]

@WarmBeer it seems the credentials are wrong: https://github.com/torrust/torrust-index-backend/actions/runs/5002547167/jobs/8962758264#step:4:23

Hmm sorry, I might have put in the wrong username. I have updated it now. Could you try again?

Hey @WarmBeer It does not work. I think it could be DOCKER_HUB_REPOSITORY_NAME because the login works.

secrets:
DOCKER_HUB_USERNAME=torrust
DOCKER_HUB_ACCESS_TOKEN=********
DOCKER_HUB_REPOSITORY_NAME=index-backend

I think we should change the username and repository name to normal env vars instead of secrets:

env vars:
DOCKER_HUB_USERNAME=torrust
DOCKER_HUB_REPOSITORY_NAME=index-backend

secrets:
DOCKER_HUB_ACCESS_TOKEN=********

So that we can see the docker image name on the log:

#29 ERROR: failed to push ***/***:2.0.0-alpha.1: failed to authorize: failed to fetch oauth token: unexpected status: 400 Bad Request

[mickvandijke]

Hi @josecelano ,

I thought I had to add the torrust/ prefix to the repository name as that is how it shows in the Docker Hub UI: torrust/index-backend. I have now however removed the prefix and just set index-backend. I Also changed the username and repository variables to be normal env vars instead of secrets like you suggested. Third time is the charm? :)

[josecelano]

Hi @josecelano ,

I thought I had to add the torrust/ prefix to the repository name as that is how it shows in the Docker Hub UI: torrust/index-backend. I have now however removed the prefix and just set index-backend. I also changed the username and repository variables to be normal env vars instead of secrets like you suggested. Third time is the charm? :)

Hey @WarmBeer sorry :-(, you cannot change the var from secret to normal var without changing the workflow, because they are used like this:

DOCKER_HUB_USERNAME: "${{ secrets.DOCKER_HUB_USERNAME }}"

Sorry, I did not mention it. We can open a new issue for that.

[mickvandijke]

@josecelano Oh no haha, should I make them all secrets again or did you update the workflow?

[josecelano]

@josecelano Oh no haha, should I make them all secrets again or did you update the workflow?

Change them don't he settings for the time being, and I will create a new issue to change the workflow.

[josecelano]

I've fixed the env secrets and published the docker image (3.0.0-alpha.2) manually.