help needed?
I've just come across openrepo and it looks potentially perfect for something we need at work. Would be happy to help out contributing (or would like some of the PRs merged) but notice no new release for a while. Is this project a going concern?
@bownie What are your requirements - repository type, scale, etc.? I have recently adopted OpenRepo for my own workplace as Debian repository, but I had to manually patch a couple of crucial things before making it usable.
The Web Interface is notoriously slow for large repos (my repo contains 1.4k-ish packages and takes around 10 seconds to load up the packages list; and the page hangs up in a while) and has no search interface for packages, most of the repository metadata is hardcoded. And the hosted repos somehow get corrupted with no actual cause (none that I could find) and I would need to manually copy the package to an intermittent repo, re-create my repo, and copy the packages back.
So yeah, it is ok for small scale projects, you should re-consider if you have large repos like me.
In fact, I have been planning on writing my own repository host for a while but never found the time. If you are willing to contribute, I can whip up a minimal functional variant and push it to Github.
@Sai-Raveendra-Kandregula redhat RPMs mainly for build push and pull, querying repo data is also what I'm after especially as we have a hand tooled deployment system which is integrated with Artifactory and we're looking to migrate away. The solution doesn't have to be production ready - the system it's supporting is going into maintenance so I would consider it a very slow moving but it is a big project. This for me looks like it could initially do 90% but we have several TBs of RPMs - probably wouldn't need all of that but it's going to be conservatively 1TB at least. I'm allergic to starting from scratch but I'm happy to contribute small features here
@bownie This project does not seem to be actively maintained, and I don't think it can handle a TB of packages well. Try it out, but for PRs I suggest forking out. You can use your own fork in deployment. And I could help whatever way I can, if needed.