Comments (7)
package main
import (
"fmt"
"os"
"github.com/gin-gonic/gin"
)
func main() {
os.Setenv("GIN_MODE", "release")
g := gin.New()
gin.SetMode(gin.ReleaseMode)
g.Run(":9000")
fmt.Println("running")
}
if you insert os.Setenv("GIN_MODE", "release")
one line or
Enter environment variables export GIN_MODE=release
in command line before go run main.go
you get Expected result
from gin.
I think a new Gin instance has been New and should be set up around it
like this:
package main
import (
"fmt"
"github.com/gin-gonic/gin"
)
func main() {
g1 := gin.New()
g1.SetMode(gin.ReleaseMode)
g1.Run(":9001")
g2 := gin.New()
g2.SetMode(gin.DebugMode)
g2.Run(":9002")
fmt.Println("running")
}
from gin.
I think a new Gin instance has been New and should be set up around it like this:
package main import ( "fmt" "github.com/gin-gonic/gin" ) func main() { g1 := gin.New() g1.SetMode(gin.ReleaseMode) g1.Run(":9001") g2 := gin.New() g2.SetMode(gin.DebugMode) g2.Run(":9002") fmt.Println("running") }
- Gin Mode is a global variable in the package, it isn’t a per instance setting. The gin.Engine doesn’t have a method SetMode
- Let’s say mode was per instance, the way your code is, both instances would print the debug warning even though the first one you’re running in release mode
@FarmerChillax
Unless you're saying, what you put with g2.SetMode is how you THINK it should be. If so, I could get behind that.
from gin.
I think a new Gin instance has been New and should be set up around it like this:
package main import ( "fmt" "github.com/gin-gonic/gin" ) func main() { g1 := gin.New() g1.SetMode(gin.ReleaseMode) g1.Run(":9001") g2 := gin.New() g2.SetMode(gin.DebugMode) g2.Run(":9002") fmt.Println("running") }
- Gin Mode is a global variable in the package, it isn’t a per instance setting. The gin.Engine doesn’t have a method SetMode
- Let’s say mode was per instance, the way your code is, both instances would print the debug warning even though the first one you’re running in release mode
@FarmerChillaxUnless you're saying, what you put with g2.SetMode is how you THINK it should be. If so, I could get behind that.
The point I'm making is just that it's confusing to use the current API and it feels more natural to set up each instance.(for discussion purposes)
Regardless of current usage.(Maybe I should open a new issue)
from gin.
I think a new Gin instance has been New and should be set up around it like this:
package main import ( "fmt" "github.com/gin-gonic/gin" ) func main() { g1 := gin.New() g1.SetMode(gin.ReleaseMode) g1.Run(":9001") g2 := gin.New() g2.SetMode(gin.DebugMode) g2.Run(":9002") fmt.Println("running") }
- Gin Mode is a global variable in the package, it isn’t a per instance setting. The gin.Engine doesn’t have a method SetMode
- Let’s say mode was per instance, the way your code is, both instances would print the debug warning even though the first one you’re running in release mode
@FarmerChillaxUnless you're saying, what you put with g2.SetMode is how you THINK it should be. If so, I could get behind that.
The point I'm making is just that it's confusing to use the current API and it feels more natural to set up each instance.(for discussion purposes)
Regardless of current usage.(Maybe I should open a new issue)
Alright, yeah then you're further proving my point that it isnt so straight forward. Cause even in your suggested design, you would still get the Debug mention when you do g1 := gin.New() because the Gin MOde is declared after, which isnt what one would expect (At least isnt waht I would expect)
I think that debug warning shouldnt be called until the gin server is actually called upon to ListenAndServe. I can also see a value in it being on a per instance basis like you're suggesting as well.
from gin.
I think a new Gin instance has been New and should be set up around it like this:
package main import ( "fmt" "github.com/gin-gonic/gin" ) func main() { g1 := gin.New() g1.SetMode(gin.ReleaseMode) g1.Run(":9001") g2 := gin.New() g2.SetMode(gin.DebugMode) g2.Run(":9002") fmt.Println("running") }
- Gin Mode is a global variable in the package, it isn’t a per instance setting. The gin.Engine doesn’t have a method SetMode
- Let’s say mode was per instance, the way your code is, both instances would print the debug warning even though the first one you’re running in release mode
@FarmerChillaxUnless you're saying, what you put with g2.SetMode is how you THINK it should be. If so, I could get behind that.
The point I'm making is just that it's confusing to use the current API and it feels more natural to set up each instance.(for discussion purposes)
Regardless of current usage.(Maybe I should open a new issue)Alright, yeah then you're further proving my point that it isnt so straight forward. Cause even in your suggested design, you would still get the Debug mention when you do g1 := gin.New() because the Gin MOde is declared after, which isnt what one would expect (At least isnt waht I would expect)
I think that debug warning shouldnt be called until the gin server is actually called upon to ListenAndServe. I can also see a value in it being on a per instance basis like you're suggesting as well.
Yes, I agree with your point too. I hope that while improving the API, I will also correct the debug information you mentioned.
from gin.
Related Issues (20)
- Does gin.Recovery() run before or after Group middleware? HOT 1
- How can i prevent a http connection to close HOT 3
- BasicAuth is not suitable for proxy auth
- Can't get status as expected from context.Status() HOT 1
- Gin Context implementation breaks context.Context contract HOT 4
- [Suggestions] Introducing an AI-powered robot to assist with daily issue and pull request (PR) tasks.
- Need c.JSON() response like behaviour for c.SSEvent() response for supporting first party clients like OpenAI SDK HOT 2
- custom time.Time type can not use bindQuery get a value. HOT 3
- configure server parameters HOT 1
- The binding:"required" tag does not seem to work for struct types HOT 3
- Is there a way to preserve order in JSON on response? HOT 1
- redirect is not success HOT 1
- I want to use shouldmindbodywith first and then use formafile, but it doesn't work right now HOT 3
- Extend the routing tree entry
- Transparent decompression for gzip, deflate, etc? HOT 1
- Custom time.Time type can not use bindQuery get a value 2 HOT 2
- http: response.Write on hijacked connection from github.com/gin-gonic/gin.(*responseWriter).Write (response_writer.go:83) HOT 1
- AbortWithStatusJSON doesn't abort context HOT 2
- I translated `tree.go` into java
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gin.