go-martini/martini

★ 11,609GoAudience · developerComplexity · 3/5Setup · moderate

Mindmap

mindmap
  root((martini))
    What it does
      HTTP routing
      Middleware chaining
      Dependency injection
    Tech Stack
      Go
      net/http
    Use Cases
      Legacy Go APIs
      HTTP middleware
    Status
      Archived
      No security patches

mindmap root((martini)) What it does HTTP routing Middleware chaining Dependency injection Tech Stack Go net/http Use Cases Legacy Go APIs HTTP middleware Status Archived No security patches

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Maintain or debug an existing Go web application built on Martini before migrating to a modern framework.

USE CASE 2

Study how early Go frameworks implemented dependency injection by inspecting handler argument types at runtime.

USE CASE 3

Add REST API routes to a legacy Go project using Martini's named URL parameters and middleware chaining.

Tech stack

Getting it running

Difficulty · moderate Time to first run · 30min

Project is unmaintained, no security patches or Go version updates since it was archived.

In plain English

Martini is a web framework for Go that makes it quick to build web servers and HTTP APIs. It is no longer maintained, as the README prominently states at the top, so it is mostly of historical interest or still in use by projects that have not yet migrated away. The framework centers on a routing and middleware system. You define routes by pairing an HTTP method (GET, POST, PUT, DELETE, and so on) with a URL pattern, and attach one or more handler functions to each route. URL patterns can include named parameters, glob wildcards, and regular expressions. Handlers can be stacked so that authentication or authorization checks run before the main logic. A notable feature is dependency injection into handler functions. Martini inspects the argument types of each handler at runtime and automatically provides matching services, such as the HTTP request object, a logger, or any custom object you have registered. This means you declare what your handler needs as function arguments and Martini supplies them, rather than having to pass everything explicitly through a context object. The Classic() setup is a quick-start configuration that includes request and response logging, panic recovery (so an unhandled error does not crash the whole server), static file serving, and the router. Additional middleware is available through the separate martini-contrib organization on GitHub. Because the project is no longer maintained, it does not receive security patches or compatibility updates. Newer Go web frameworks and the Go standard library's own HTTP tooling have largely replaced it.

Copy-paste prompts

Prompt 1

Using go-martini/martini, create a Go web server with GET /users/:id and POST /users routes that use Martini's dependency injection to receive a logger and the http.Request in each handler.

Prompt 2

I have a Martini-based Go app I need to migrate to the standard net/http library or Gin. Map each m.Get, m.Post, and middleware call to its modern equivalent.

Prompt 3

Show me how Martini's Classic() setup works: what middleware does it include by default and how do I add custom middleware before the router?

Prompt 4

Rewrite this Martini handler that relies on dependency injection as a plain http.HandlerFunc so I can remove the Martini dependency entirely.

Open on GitHub → Explain another repo

← go-martini on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.