Beego: A Full Stack Web Framework for Go
github.com
Beego: A Full Stack Web Framework for Go
1–10 of 16 posts
Re: Beego: A Full Stack Web Framework for Go
#2It was interesting to see this in the Readme.
> Kindly remind that sometimes the HTTPS certificate is expired, you may get some NOT SECURE warning
I thought let’s encrypt removed all the friction that such worries were a thing of the past. Any reason people still manually do this and worry about it?
Re: Beego: A Full Stack Web Framework for Go
#3It was interesting to see this in the Readme. > Kindly remind that sometimes the HTTPS certificate is expired, you may get some NOT SECURE warning I thought let’s encrypt removed all the friction that such worries were a thing of the past. Any reason people still manually do this and worry about it?
[deleted]
Re: Beego: A Full Stack Web Framework for Go
#4It was interesting to see this in the Readme. > Kindly remind that sometimes the HTTPS certificate is expired, you may get some NOT SECURE warning I thought let’s encrypt removed all the friction that such worries were a thing of the past. Any reason people still manually do this and worry about it?
Let's Encrypt issues DV (domain-validated) certs, some people need OV (organisation-validated) certs.
But you're right that Let's Encrypt can cover a vast majority of usecases these days.
Re: Beego: A Full Stack Web Framework for Go
#5Ha, the good old days of Go frameworks... Remember Martini drama? Iris drama?
I actually wished the web dev community would have stuck to these petty fights instead of fighting over partisan politics. But things are what they are.
And don't get me started on Go ORM drama...
Re: Beego: A Full Stack Web Framework for Go
#6Ha, the good old days of Go frameworks... Remember Martini drama? Iris drama? I actually wished the web dev community would have stuck to these petty fights instead of fighting over partisan politics. But things are what they are. And don't get me started on Go ORM drama...
> I actually wished the web dev community would have stuck to these petty fights instead of fighting over partisan politics.
I often kinda missed the days where computers weren't cool.
Re: Beego: A Full Stack Web Framework for Go
#7web stuff n even web services is where golang got a lot to catch up to with jvm ecosystem i.e java / kotlin etc in terms of productivity and industrial off-the-shelf stuff.
Re: Beego: A Full Stack Web Framework for Go
#8we all know frameworks are the worst right?
Eventually you end up fighting your framework....
Re: Beego: A Full Stack Web Framework for Go
#9we all know frameworks are the worst right? Eventually you end up fighting your framework....
Eventually you end up writing your own framework
Re: Beego: A Full Stack Web Framework for Go
#10It was interesting to see this in the Readme. > Kindly remind that sometimes the HTTPS certificate is expired, you may get some NOT SECURE warning I thought let’s encrypt removed all the friction that such worries were a thing of the past. Any reason people still manually do this and worry about it?
In practice, for production, it's best to leave it out to separate component, especially if you might end up having to run with customer-supplied certs