Add Dockerfile for registry

[BlowaXD]

This should partially solve #45

Additions

• added registry/Dockerfile
• added registry/.dockerignore ignoring **/target/** to avoid having to sending too much files to context
• added README.md in registry project with docker build command

I decided to manually install protobuff deps to have an easy way to manage the protobuf compiler version

[tomkarw]

Shouldn't the Dockerfile live in /registry folder?

[mara-schulke]

Hei @BlowaXD, tysm for your contribution! 😊

[mara-schulke]

I agree with @tomkarw's comment, otherwise this looks good to me 😊

[BlowaXD]

I agree with @tomkarw's comment, otherwise this looks good to me 😊

Sure, I did first assume that someone would have wanted to build from the same directory

Moving it to registry folder requires either:

Having this COPY statement instead of the current one (https://github.com/helsing-ai/buffrs/pull/206/files#diff-94b4fdf407a88fb5e59fcd22bd231c04f89deb5aa0bc67c37baedb600e2e6226R20)

COPY .. .

or using this command to build

docker build -t registry . --file registry/Dockerfile

I don't know which UX you want to provide, I do not see an alternative because of the registry requiring buffrs as a dependency

[tomkarw]

I don't know which UX you want to provide, I do not see an alternative because of the registry requiring buffrs as a dependency

I'd go with COPY .. ..

I think the issue is more general, we have a CLI, a registry, and they share some common parts. This clearly indicates 3 crates (cli, registry and buffrs-lib), but currently cli.contains(buffrs-lib). I'd move the Dockerfile and hack it to work, and we can open a ticket about at some point extracting the common parts out.

[BlowaXD]

Edited the PR, I gave a command in the registry/README to guide user to build the docker so it will be ready when registry works
As registry is a WIP, I didn't know what to write in the README so I decided to add a short disclaimer that can be removed whenever

[mara-schulke]

Awesome, thank you @BlowaXD!