Add registry-watcher image and separate docker-compose services

[Nemo157]

Creates a separate image for the registry-watcher, setup to run the correct command. Reconfigures the docker-compose setup to use the web-server image and this new registry-watcher image as intended to be used in the new production infrastructure, along with a new build-server image that is close to what will be used in the new production infrastructure, replicated twice.

[Nemo157]

Probably needs some infra input on the deploy changes (what exactly the tags they use will be). Also I want to investigate the crates.io-index initialization a little more and make sure that's working (and probably have it be local to each container instead of shared as it is now).

[syphar]

Thank you for working on this @Nemo157 !

Sorry for already adding a review in the draft-stage, but I thought some feedback would already help :)

[Nemo157]

I have removed the CI changes pushing the new image to production, since that will require some input from infra and can be done later.

[syphar]

I wasn't able to fully test yet, but I already have some comments / ideas.

Also I want to investigate the crates.io-index initialization a little more and make sure that's working (and probably have it be local to each container instead of shared as it is now).

Were you able to test if the index clone works without the entrypoint.sh?

[syphar]

short test result:

• trying to run the registry watcher gives me /usr/bin/tini: invalid option -- '-'

[Nemo157]

Fixed that, I was normalizing the COMMANDs and thought that the -- wasn't actually needed with tini. I've normalized them the other way and split the ENTRYPOINT and COMMAND so that it's possible to run other cratesfyi commands under any image.

[syphar]

Fixed that, I was normalizing the COMMANDs and thought that the -- wasn't actually needed with tini. I've normalized them the other way and split the ENTRYPOINT and COMMAND so that it's possible to run other cratesfyi commands under any image.

I'm still seeing the same error when trying to run the registry watcher container?

[Nemo157]

I'm still seeing the same error when trying to run the registry watcher container?

Coming back to this finally, are you using --build with the docker compose up call? It doesn't have any kind of change detection and requires you to tell it to rebuild. I've added that to the comment about how to run it.

[syphar]

tested

• web container
• cli container
• registry watcher
• builder-a

awesome, thank you for keeping to work on it!

Some small documentation comments, and a missing platform.

[syphar]

it's not clear that you have to run this command to make the service work.

[syphar]

this is missing the platform: "linux/amd64" definition, or am I missing something?

[syphar]

same here, the command has to be run initially, to be able to use the registry-watcher container at all

[Nemo157]

Rebased, and tried to improve the documentation about initial docker compose setup.

Turns out the start-registry-watcher command is currently broken though, it tries to use reqwest::blocking from within an async task which tokio doesn't like.