I certainly could, though I've avoided it so far. The existing single binary should be very easy to deploy. Being inside a container would add some complexities, the TCP port mapping and mapping a mounted volume to somewhere so that the downloaded files are available.
In what way would it make your setup easier ?
I certainly could, though I've avoided it so far. The existing single binary should be very easy to deploy. Being inside a container would add some complexities, the TCP port mapping and mapping a mounted volume to somewhere so that the downloaded files are available.
In what way would it make your setup easier ?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
could you provide an docker file or better a docker-compose to run it as service?
I certainly could, though I've avoided it so far. The existing single binary should be very easy to deploy. Being inside a container would add some complexities, the TCP port mapping and mapping a mounted volume to somewhere so that the downloaded files are available.
In what way would it make your setup easier ?
docker compose added in v1.0.0