i will split and expand this task a little bit and try to draw an small roadmap of features. There are things over that list that should be tasks in the backlog of this project while others should be discussed
Thu, Dec 6
i've redeployed zotero on codfw, i'm watching the graphs and don't see anything strange over metrics so i'll claim this as fixed.
Tue, Dec 4
Thu, Nov 22
i've got some metrics at least.
Wed, Nov 21
Mon, Nov 19
i took a quick look with strace and it seems is hanging launching this
Thu, Nov 15
please @Addshore report if happens again with container image and date/timestamp of the pulling.
that layer looks ok also on storage, either is a caching issue or an nginx issue breaking connections from client, I'll continue to debug it
According to the registry view everything went fine.
Wed, Nov 14
latest should be avoided for production, in my experience is also problematic for development (since you don't know which version are you running considering caches) is only handy for local environments or for CI.
Tue, Nov 13
Regarding @Joe 's comment. The last picture should be something similar to this, this is quite complex and is build up from the idea that Portus is HA ( that means that the DB that Portus uses for state is resilient enough), in this scenario if Portus goes down we will have no registry.
After looking into it a little bit, packaging harbor would be challenging. Harbor is a set of microservices published as containers. The installation and dev guide refers to docker-compose as a strong requirement for running harbor components, in order to run this docker-compose we need to build the container images and hosted them in our own docker registry which seems a sort of catch-22 problem (other people could rely on downloading it from DockerHub).