Project Manager TUI Added

• Built an interactive terminal user interface (TUI) to manage local projects seamlessly.
• Status indicators display whether a project is currently active.
• Selecting a project opens it directly in your preferred editor.

Project Manager TUI Added

• Built an interactive terminal user interface (TUI) to manage local projects seamlessly.
• Status indicators display whether a project is currently active.
• Selecting a project opens it directly in your preferred editor.

Release Setup & CI Integration

• Automated CI pipeline validates every single commit.
• Releases and builds are automatically published to GitHub on update.
• Auto-completion support for fast terminal navigation and project tracking.

What’s Next

• Built-in auto-updater.
• TUI for project management

You can try it now at https://github.com/InvalidJoker/scratchpad/releases

Release Setup & CI Integration

• Automated CI pipeline validates every single commit.
• Releases and builds are automatically published to GitHub on update.
• Auto-completion support for fast terminal navigation and project tracking.

What’s Next

• Built-in auto-updater.
• TUI for project management

You can try it now at https://github.com/InvalidJoker/scratchpad/releases

Base is ready now

Added

• First-Run Onboarding: Prompts users to run setup on initial execution to initialize CLI configuration.
• Project Creation & Lifecycle:
  • new <name>: Create a scratch project.
  • open <name>: Open a project and mark it active.
  • keep <name>: Promote a project out of scratch, permanently.
• Project Discovery & Inspection:
  • list: List your scratch projects.
  • info <name>: Show everything known about a project.
• Trash Management:
  • trash <name>...: Move a project to the trash.
  • restore <name>: Bring a project back from the trash.

Base is ready now

Added

• First-Run Onboarding: Prompts users to run setup on initial execution to initialize CLI configuration.
• Project Creation & Lifecycle:
  • new <name>: Create a scratch project.
  • open <name>: Open a project and mark it active.
  • keep <name>: Promote a project out of scratch, permanently.
• Project Discovery & Inspection:
  • list: List your scratch projects.
  • info <name>: Show everything known about a project.
• Trash Management:
  • trash <name>...: Move a project to the trash.
  • restore <name>: Bring a project back from the trash.

Scratchpad

I’ve started working on Scratchpad, a small tool for managing temporary projects and experiments.

The idea behind Scratchpad is simple: I often create projects in my Downloads folder when I’m testing an idea or starting something small. After a while, those projects pile up and I have to manually figure out what I still need and what I can delete.

Scratchpad is meant to make that process easier by giving these temporary projects their own workspace and eventually helping manage their lifecycle.

For the first step, I set up the project in Go and implemented the first command. This gives me the basic foundation to start building the rest of the tool around.

It’s still very early, but the initial structure is now in place.

Scratchpad

I’ve started working on Scratchpad, a small tool for managing temporary projects and experiments.

The idea behind Scratchpad is simple: I often create projects in my Downloads folder when I’m testing an idea or starting something small. After a while, those projects pile up and I have to manually figure out what I still need and what I can delete.

Scratchpad is meant to make that process easier by giving these temporary projects their own workspace and eventually helping manage their lifecycle.

For the first step, I set up the project in Go and implemented the first command. This gives me the basic foundation to start building the rest of the tool around.

It’s still very early, but the initial structure is now in place.

Artifact Mirroring

You can now mirror artifacts from other registries.

Why?

• Better reliability — builds are less affected by external registry outages or network issues.
• More control — keep the artifacts you depend on available within your own infrastructure.

Next steps

• QoL fixes
• More artifact types, such as Cargo crates

Artifact Mirroring

You can now mirror artifacts from other registries.

Why?

• Better reliability — builds are less affected by external registry outages or network issues.
• More control — keep the artifacts you depend on available within your own infrastructure.

Next steps

• QoL fixes
• More artifact types, such as Cargo crates

maven-repo is now Artifact Forge

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.

What’s new

• NPM package support — same reliability as before
• Docker build support — push and pull images through the same system
• One registry for more artifact types — less infrastructure to manage

What’s next

• More artifact types
• Mirroring public repos

maven-repo is now Artifact Forge

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.

What’s new

• NPM package support — same reliability as before
• Docker build support — push and pull images through the same system
• One registry for more artifact types — less infrastructure to manage

What’s next

• More artifact types
• Mirroring public repos

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