Capstan is a Golang web framework that shares some similarities with others in its segment.
Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
Benjamin Shelton 48677fa4db Still uncertain about launcher attributes. 2 semanas atrás
auth Replaced KeyStar references with cryptohelper, which has been split out 6 meses atrás
cmd Placeholder for future capstan CLI tool. 3 semanas atrás
config Use libkeystar. 3 semanas atrás
docs Added extra skeleton files for other topics. 4 meses atrás
errors Added application-specific errors. 6 meses atrás
extension Removed: Methods provided via embedded struct. 3 semanas atrás
fixtures/templates Added zipped fixture. 1 ano atrás
installer Fixed package name. 3 semanas atrás
internal Updated/added comments. 5 meses atrás
launcher Still uncertain about launcher attributes. 2 semanas atrás
mappers Re-homed project and most declared dependencies. 1 ano atrás
middleware Application is now an interface. 8 meses atrás
render Added TODO notes for theme support and correct VFS for theming. See 10 meses atrás
session Replaced KeyStar references with cryptohelper, which has been split out 6 meses atrás
status Re-homed project and most declared dependencies. 1 ano atrás
tests Added unit test for mounting applications at root. 3 semanas atrás
utils More contemplation. 10 meses atrás
vfs Re-homed project and most declared dependencies. 1 ano atrás
.gitignore Ignore any .pid files generated by test binaries. 1 ano atrás
LICENSE Bump copyright date. 1 mês atrás
Makefile Added benchmark options for convenience. 6 meses atrás My brain's autocorrect doesn't work. 4 meses atrás
api.go Added Each to apply a function for every registered subapplication. 3 semanas atrás
application.go Default logger was never set for production mode. 3 semanas atrás
capstan_test.go Split integration tests into their own files and outside of root. 1 ano atrás
context.go Okay, the actual underlying mistake was pretty stupid, which made it 9 meses atrás
extension.go Added deinitialization interface. 2 meses atrás
funcs.go Cast function to the appropriate signal otherwise it won't match the 1 mês atrás
go.mod Upstream dependency chain(s) updated. 2 semanas atrás
go.sum Upstream dependency chain(s) updated. 2 semanas atrás
http.go Moved routing files into base package. 1 ano atrás
netlisten_unix.go Wrap direct access in function calls to gate internal API behavior for 5 meses atrás
netlisten_windows.go Moved routing files into base package. 1 ano atrás
network.go Socket management types include given address -> real address mappers 5 meses atrás
network_unix.go Moved routing files into base package. 1 ano atrás
network_windows.go Moved routing files into base package. 1 ano atrás
package_test.go Added setup code for package-level tests. 6 meses atrás
proxy.go Added comments to resolve outstanding issue caused by temporal proximity 3 semanas atrás
route.go Changed signal method signatures to include context passing. 3 semanas atrás
router.go Removed AfterResponse and replaced with signal code. 1 mês atrás
router_bind.go Added more signal emit points. And comments. 1 mês atrás
router_listen.go Actually return errors. 5 meses atrás
router_private.go Removed AfterResponse and replaced with signal code. 1 mês atrás
router_trie.go Moved routing files into base package. 1 ano atrás
router_utils.go Moved routing files into base package. 1 ano atrás
routergroup.go Removed AfterResponse and replaced with signal code. 1 mês atrás
service.go Serialize given -> real addr mapping. 5 meses atrás
signals.go Removed multi bool flag. Not applicable. 3 semanas atrás
trie.go Added Overwrite method. 4 meses atrás
trie_test.go Renamed node types away from temporary assignments. 5 meses atrás
types.go Import top-level types. 6 meses atrás
urls.go Logging API for inheritance is now parent -> child rather than child -> 2 semanas atrás
urls_test.go Re-homed project and most declared dependencies. 1 ano atrás
vfs.go Moved routing files into base package. 1 ano atrás

Capstan: A Convenience Framework for Golang

Capstan is a framework that aims to simplify complex use cases that reach beyond basic HTTP handlers, such as dependency management, and reduces the amount of code required as handlers grow and evolve beyond what is possible with the standard library. It provides helpers for common (and not so common) tasks, including graceful shutdowns, rebinding mount points, and more. Capstan uses go-chi for its route muxer. Philosophically, Capstan is inspired in part by Flask and Flask-Classy.

Capstan is not for you if you require handlers that retain compatibility with net/http. Though this could (and arguably should) be rememdied by using the context package, there are no plans currently to reimplement Capstan in this fashion. Be ware! The Capstan API may appear simple at first blush, but it has a depth and complexity that may not be viable for all projects. If you need a simple API server, consider using go-chi directly.

Bear in mind that the project is still very much in its infancy, and APIs are subject to change. There are numerous rough patches and sharp objects in the code.


Capstan's implementation comprises these features (and some anti-features):

  • Controller-centric MVC. At present, it's largely "VC" as there is no defined model implementation. Capstan is very much "bring your own model."
  • Requests are designed to call method-named functions per controller per path. This means that individual functions are named after and define an HTTP verb, such as Get or Post. Controllers therefore should be highly focused to a single endpoint. (This isn't strictly necessary; see below.)
  • Custom methods can be defined by implementing either the Binder interface, MapperHandler interface (work-in-progress), or by naming functions according to the pattern <Method><Name><SlashState>. This will become clearer later in the documentation once it's written.
  • Multiple renderers are supported through the Templater interface. We primarily encourage the use of pongo2 but provide wrappers for Go's built in template rendering library. (Note: Using anything but pongo2 may limit features available to templates, and using multiple template types in a single project will present unique challenges and difficulties that, while not insurmountable, are unnecessary and will be frought with sleepless nights.)
  • Renderers may be defined globally or per-controller. If a renderer is defined globally, all controller bindings that don't define a renderer will use the global one by default.
  • Capstan's pongo2 wrappers can make use of our VFS layer that integrates with Embedder for embedding assets into the compiled binary. The template engine is therefore capable of reading templates and other assets directly from disk or the binary itself. ZIP files are also supported. When combined with VFS, it's possible to layer reads from multiple sources (e.g. the binary, a ZIP file, or the file system).
  • Built-in TLS configuration helpers are provided. ACME support is a work in progress which will allow use of services like Let's Encrypt.
  • Capstan can listen on Unix sockets for use with local front end proxies like nginx or HAProxy. Doing so does not provide noticeable performance improvements over using TCP sockets.
  • Supports remapping endpoints (called "rebinding" in Capstan parlance) without restarting the service. Endpoints may be deleted (Router.Unmount) or renamed (Router.ReplacePath).
  • Optional websocket endpoint handlers as part of the controller semantics.
  • Graceful shutdown and in-place replacement/restart for seamless upgrades. Not presently supported on Windows and likely never will be.
  • URL mapper that exposes URL resolution for templates. In pongo2, this is provided via the functions url() and external(). URLs are typically mapped as [<prefix>.]<name>.<suffix>; for example, if you have a controller IndexController and were accessing its Get method, you would retrieve the mapped URL by calling url("IndexController:get"). Custom url() binding is provided by Router.ManualBind. The <prefix> is dictated by router groups or through manual declaration at controller bind time. Naming conflicts can be resolved during controller initialization manually, by providing a symbolic name for the controller, or automatically through a numeric suffix (e.g. IndexController2).
  • Trailing slashes can be controlled via the ?, ! or + syntax. ? indicates a trailing slash is optional. ! indicates a trailing slash must not be provided (and a 404 is generated). + indicates a trailing slash is mandatory for subroute declarations (but is typically unnecessary). Otherwise, if a route is declared with a trailing slash it is considered mandatory and requests made without the trailing slash will result in a 404. Optional slashes (indicated by a trailing ?) can either have a slash-provided or slash-absent default state; if a ? is immediately preceded by a slash, e.g. /?, a redirection route will be created that directs requests minus the trailing slash to a route that has the trailing slash appended. Likewise, if there is no slash preceding the ?, the redirection route will direct requests with a trailing / to the route without it. You should use optional slash routes sparingly since this does necessitate the generation of (potentially) superfluous routes.
  • Typed route variables. This requires a syntax differing slightly from go-chi. Type enforcement is not presently implemented (but likely will be). We use < and > to delineate route variables and deliberately introduce incompatibilities with go-chi to prevent confusion. Variable types are declared with a :<type> suffix, e.g. /path/<name:string>, which would create a parameterized variable of the name name and type string. Regex is passed through to go-chi.
  • Route groups wrap go-chi's groups and provide methods namespacing them from other routes both for url() template function(s) and for isolation.
  • Supports any middleware supported by go-chi and provides slight modifications for middleware supplied by go-chi (such as supporting the NO_COLOR envvar for go-chi's logger).
  • Supports before and after response bindings for cases where middleware may be too low level and where the route context needs to be fully configured prior to or after handling the endpoint.
  • Custom error page support, with context helpers.
  • Extension support that includes a few out-of-the-box extensions, such as CSRF protection and session management. Authentication support is forthcoming.
  • Fully-featured dependency injection.
  • Limited support for privilege reduction; e.g., setting Capstan's RunAs configuration option and running initially as the root user will provoke Capstan into first binding to its configured ports then dropping privileges. This is useful for listening on lower ports, such as port 80 and 443, and although Capstan is fully capable of doing so, it is advisable to use reverse proxies in front of a Capstan application.
  • Open port scanner for automatically picking open ports. Useful for writing installers that need to find a free port in order to start a visual browser-based installer.
  • Multiple application support for running multiple instances of Capstan applications under the same Capstan instance. It's Capstans all the way down!
  • Additional utilities. See the utils subpackage.

Sample Application

package main

import (

type IndexController struct {
    Server capstan.Server `inject:"app"`

func (c *IndexController) Index(ctx capstan.Context) error {
    return ctx.Write([]byte("Hello! Listening on address: "+c.Server.Config().ListenAddress))

func main() {
    app := capstan.New(&capstan.ServerConfig{
        ListenAddress: ":8080",

        BaseController: capstan.BaseController{
            Path: "/",



The Capstan source distribution contains documentation under the docs/ subdirectory. Presently, this documentation is somewhat sparse but the file contains a beginner's guide adequate enough to get started. There is also a small but mostly complete discussion on Capstan's dependency injection framework.


Capstan is licensed under the fairly liberal and highly permissive NCSA license. We prefer this license as it combines the best of BSD and MIT licenses while also providing coverage for associated documentation and other works that are not strictly considered original source code. Consequently, all Capstan documentation is likewise covered under the same license as the codebase itself.

As with BSD-like licenses, attribution is, of course, required.