Artifact Forge
- 7 Devlogs
- 15 Total hours
A lightweight artifact repository build for simplicity
A lightweight artifact repository build for simplicity
You can now mirror artifacts from other registries.
maven-repo did one thing well: simple, self-hosted Maven hosting.
But self-hosted registries aren’t just a Java problem. Docker images need a home too, and running a separate service just for that never made sense. So I merged both into one tool.
The old name didn’t fit anymore. maven-repo is now Artifact Forge.
Today I’m shipping v0 of the Maven repository! I think it’s stable enough for an initial release.
For future releases, I plan to add support for Docker images and other artifact types, but that’ll come later.
You can check out the public instance here: https://repo.koder.wtf/
If you’d rather host it yourself, it’s easy to do with Docker, just follow the instructions in the readme.
In my last Dev Log, I mentioned that I had finished the first prototype with all the core features in place.
Over the past week, I’ve focused on completely refreshing the frontend. The interface has been redesigned to be cleaner, more modern, and much more enjoyable to use.
I also introduced Instance Settings, allowing you to fully customize your Maven repository. Since the project is self-host-first, it should feel like your repository. You can now personalize the instance name, logo, and color scheme to match your style.
As you can see, the application now features a brand-new green and black color palette.
The basic prototype is now complete, and the core features are already in place.
The core functionality is now in place, so the focus can shift towards improving the user experience and expanding support for more package ecosystems.