FAQs

How do I change the listen address?

If you’re using the Run method to start the web server, you may change the listen address using either the environment variable FLAMEGO_ADDR:

export FLAMEGO_ADDR=localhost:8888

Or the variable arguments of the Run method:

f.Run("localhost")       // => localhost:2830
f.Run(8888)              // => 0.0.0.0:8888
f.Run("localhost", 8888) // => localhost:8888

Alternatively, http.ListenAndServeopen in new window or http.ListenAndServeTLSopen in new window can also be used to change the listen address:

http.ListenAndServe("localhost:8888", f)
http.ListenAndServeTLS("localhost:8888", "certFile", "keyFile", f)

How do I do graceful shutdown?

The github.com/ory/gracefulopen in new window package can be used to do graceful shutdown with the Flame instance:

package main
import (
    "net/http"
    "github.com/flamego/flamego"
    "github.com/ory/graceful"
)
func main() {
    f := flamego.New()
    ...
    server := graceful.WithDefaults(
        &http.Server{
            Addr:    "0.0.0.0:2830",
            Handler: f,
        },
    )
    if err := graceful.Graceful(server.ListenAndServe, server.Shutdown); err != nil {
        // Handler error
    }
}

How do I integrate into existing applications?

Because Flame instances implement the http.Handleropen in new window interface, a Flame instance can be plugged into anywhere that accepts a http.Handler.

Example: Integrating with net/http

Below is an example of integrating with the net/http router for a single route "/user/info":

• Code
• Test

package main
import (
    "log"
    "net/http"
    "github.com/flamego/flamego"
)
func main() {
    f := flamego.New()
    f.Get("/user/info", func() string {
        return "The user is Joe"
    })
    // Pass on all routes under "/user/" to the Flame isntance
    http.Handle("/user/", f)
    if err := http.ListenAndServe("0.0.0.0:2830", nil); err != nil {
        log.Fatalf("Failed to start server: %v", err)
    }
}

$ curl -i http://localhost:2830/user/info
The user is Joe

Example: Integrating with Macaron

Below is an example of integrating with the Macaron router for a single route "/user/info":

• Code
• Test

package main
import (
    "log"
    "net/http"
    "github.com/flamego/flamego"
    "gopkg.in/macaron.v1"
)
func main() {
    f := flamego.New()
    f.Get("/user/info", func() string {
        return "The user is Joe"
    })
    // Pass on all routes under "/user/" to the Flame isntance
    m := macaron.New()
    m.Any("/user/*", f.ServeHTTP)
    if err := http.ListenAndServe("0.0.0.0:2830", m); err != nil {
        log.Fatalf("Failed to start server: %v", err)
    }
}

$ curl -i http://localhost:2830/user/info
The user is Joe

What is the difference between inject.Invoker and inject.FastInvoker?

The inject.Invokeropen in new window is the default way that the Flame instance uses to invoke a function through reflection.

In 2016, @tupuncoopen in new window contributed a patchopen in new window with the concept and the implementation of the inject.FastInvokeropen in new window, which invokes a function through interface. The inject.FastInvoker is about 30% faster to invoke a function and uses less memory.

What is the idea behind this other than Macaron/Martini?

Martini brought the brilliant idea of build a web framework with dependency injection in a magical experience. However, it has terrible performance and high memory usage. Some people are blaming the use of reflection for its slowness and memory footprint, but that is not fair by the way, most of people are using reflections every single day with marshalling and unmarshalling JSON in Go.

Macaron achieved the reasonable performance and much lower memory usage. Unfortunately, it was not a properly designed product, or let’s be honest, there was no design. The origin of Macaron was to support the rapid development of the Gogsopen in new window project, thus almost all things were inherited from some other web frameworks at the time.

Absence of holistic architecture view and design principles have caused many bad decisions, including but not limited to:

• The *macaron.Contextopen in new window is very heavy, thus separation of concernsopen in new window wasn’t a thing.
• The choice of using the opening-only style (e.g. :name) for named parametersopen in new window has limited capability and extensibility of the routing syntax.
• Being too opinionated in many aspects, a simple example is the existence of SetConfigopen in new window/Configopen in new window that kinda kidnaps all users to import the package "gopkg.in/ini.v1" but not using it at 99% of the time.
• The way to set a cookieopen in new window is a disaster.

All in all, Macaron is still an excellent web framework, and Flamego is just better as the successor. 🙂

Why the default port is 2830?