Documenting the Maven Repo

Just a quick devlog on the changes I made since attempting the first ship:

• I added the ability to set a custom admin password when requesting a reset
• Added docs for usage and good setup docs

Initial Release

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.

UI Refresh

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.

Basic Prototype Complete

The basic prototype is now complete, and the core features are already in place.

Current features include:

• Customizable repository name/icon
• Full Gradle and Maven authentication support
• Personal access tokens with configurable read and write permissions
• Read-only tokens for development environments, allowing dependencies to be installed without the risk of accidentally publishing artifacts
• Support for both public and private repositories, making it easy to host open-source packages while keeping private artifacts secure

Next up:

• Improve and polish the frontend
• Add support for additional artifact types

The core functionality is now in place, so the focus can shift towards improving the user experience and expanding support for more package ecosystems.

I started working on an initial protype of our maven repo

It currently has:

• basic maven repo
• authentication
• basic admin area (creating/deleting repos)

Later it will support:

• custom docker registry
• oauth
• full featured admin repo

Focus is on selfhosted first and dx

Relay is now public

I think Relay has reached a point where I’m comfortable letting other people try it out. It’s now available at https://relay.koder.wtf/dashboard.

The CLI supports Windows, macOS, and Linux, and can be installed with a simple script (https://relay.koder.wtf/#how-it-works).

Currently, each user gets 2 reserved ports, 3 subdomains, and 1 completely custom domain.

There’s still plenty of work ahead. Over the coming weeks, I’ll continue improving Relay and completely rework the dashboard, as it doesn’t look quite as polished as I’d like yet. I also plan to add a way for users to request additional subdomains directly through the platform.

For now, I’d love for people to try it out and share their feedback.

First Working Version

I’ve got a first real version of Relay up and running :D

The dashboard works, and both the HTTP and TCP proxy are stable.
Next up is mostly cleanup: polishing the frontend, improving the CLI tools, and finally implementing run configurations so you can have a relay.toml file in your project and don’t have to type the entire command every time.

After that, I’ll put together a demo deployment so people can actually try it out and break it a bit.

First Working Version

I’ve got a first real version of Relay up and running :D

The dashboard works, and both the HTTP and TCP proxy are stable.
Next up is mostly cleanup: polishing the frontend, improving the CLI tools, and finally implementing run configurations so you can have a relay.toml file in your project and don’t have to type the entire command every time.

After that, I’ll put together a demo deployment so people can actually try it out and break it a bit.

I’ve started working on the frontend for Relay and made some structural changes.

One major change is the removal of the dedicated Rust backend. All functionality is now handled directly within the Svelte application, simplifying development and deployment complexity.

For the UI, I chose a minimal design built with shadcn-svelte. This gives Relay a clean, modern look.

Upcoming Features:

The dashboard will soon allow you to:

• Create and manage custom domains and subdomains
• Reserve specific ports for your projects, so you don’t have to send new ports to your friends everytime

More updates soon :D

What is Relay?

Relay is a TCP tunneling service. Unlike many other services on the market, it will be open-source and free to use (with some limitations, of course).

We also plan to offer unique features, such as persistent domains, so your friends won’t have to update the URL every time they want to visit your site.

Relay is currently a work in progress, so don’t expect anything too crazy just yet.

I’ll keep you updated :)

I wanted the CLI to be as intuitive as possible, so I came up with the following design.

I’ve also made progress on building the Relay server itself. It now includes a communication layer for interacting with the CLI and supports client authentication.

I wanted the CLI to be as intuitive as possible, so I came up with the following design.

I’ve also made progress on building the Relay server itself. It now includes a communication layer for interacting with the CLI and supports client authentication.

What is Relay?

Relay is a TCP tunneling service. Unlike many other services on the market, it will be open-source and free to use (with some limitations, of course).

We also plan to offer unique features, such as persistent domains, so your friends won’t have to update the URL every time they want to visit your site.

Relay is currently a work in progress, so don’t expect anything too crazy just yet.

I’ll keep you updated :)