Hi, thanks, ok good to go then !
> And, it doesn't really work for local dev Yeah, I figured this out after some reading. Some resources explains it might be possible to work with letsencrypr for local domains, but the setup is complex (my taste) and adds additional maintenance. What i want to do is to ease the dev setup, which is annoying because to get ssl working you need - to install openssl on the computer - run the appropriate commands In an environment with various skills this is annoying, either you got to write an Nth whole readme (like this one https://gist.github.com/denji/12b3a568f092ab951456) and hope people will catch up, you also hope they won t run into additional troubles because some uses windows, others macos, other linux, different openssl verions. Or you store those data into the VCS, but this has nothing to do here, and if your project is public and hosted on github/bitbucket/whatever, its not fair to store trash data there. On the other hand, if i can have just one program to generate those files, and put a one liner in the doc, that s done, that don t pollute the vcs, that works well for everyone, that s reusable for non go projects. Yet for go projects, i believe, this can be replaced with an in-memory certificate provider, it only requires to create a certificate provider like acme does and figure out the details. anyway, my sauce! thanks again. On Thursday, November 3, 2016 at 2:46:40 PM UTC+1, Diego Medina wrote: > > >> Back on my original question, its ok if i copy paste the code into a >> specific module with its appropriate credits ? >> Given the quick red i gave it, there s really not much to change to this >> code, it if works already. >> >> > at the top of that file it says : > > // Use of this source code is governed by a BSD-style > > So, as long as your binary doesn't break the BSD license, it should be ok. > > Regarding using autocert with let's encrypt for local dev, let's encrypt > limits the number of certs you can get in (X days, I can't remember the > limit), so if you load them just in memory, you would run into issues > sooner or later. And, it doesn't really work for local dev, let's encrypt > needs to reach your server to validate you own the domain (you could setup > your router to allow external incoming request, setup dns to point to your > house/office/ etc, but this isn't the normal dev env.) > > Hope that helps. > > Regards, > > Diego > > > >> On Thursday, November 3, 2016 at 1:54:44 PM UTC+1, Jan Mercl wrote: >>> >>> On Thu, Nov 3, 2016 at 1:40 PM <mhh...@gmail.com> wrote: >>> >>> > to provide support for got get, windows/debian/rpm installers ? >>> >>> I probably do not understand the goal correctly, but: If the user can do >>> `go get` then he has the go tool installed. That means he has Go installed. >>> That means he does not have to go get the crypto/tls package as it is >>> already sitting in his $GOROOT/src/crypto/tls. >>> >>> -- >>> >>> -j >>> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
