Re: [go-nuts] Go offline development recommendations

2018-12-13 Thread snmed
Indeed vendoring is a possible way we will consider that option but with go mod instead with dep. I strongly believe that the module way go is heading is the right way, but i'd like to have more documentation about using go modules in an air gapped network environment. Anyway thank you for

Re: [go-nuts] Go offline development recommendations

2018-12-13 Thread Nathan Fisher
We use dep at work and commit the vendor folder. The main benefit we see is that it ensures consistent builds across machines, tends to be faster, and allows offline development. assuming you don’t have to use a third party security or infrastructure team to download the dependencies. If you do

Re: [go-nuts] Go offline development recommendations

2018-12-13 Thread Jeff Kowalczyk
On Thursday, December 13, 2018 at 11:27:40 AM UTC-8, Daniel Theophanes wrote: > > Vendoring will be around a long time. Support for vendoinrg + modules is > getting better with the 1.12 release even. > > If you need to develop offline, that is the way to go. Also, vendoring is > not a footgun.

Re: [go-nuts] Go offline development recommendations

2018-12-13 Thread Ian Lance Taylor
On Thu, Dec 13, 2018 at 4:00 AM akshita babel wrote: > > Hey, can anyone guide me on how to take octet stream as input in API and/or > how to convert octet stream to byte array using golang If you want to ask an unrelated question, please send a new message, rather than replying to an existing

Re: [go-nuts] Go offline development recommendations

2018-12-13 Thread Daniel Theophanes
Hi, Vendoring will be around a long time. Support for vendoinrg + modules is getting better with the 1.12 release even. If you need to develop offline, that is the way to go. Also, vendoring is not a footgun. You check in your vendor directory and that ensures all developers and CI tools are

Re: [go-nuts] Go offline development recommendations

2018-12-13 Thread akshita babel
Hey, can anyone guide me on how to take octet stream as input in API and/or how to convert octet stream to byte array using golang On Thu, Dec 13, 2018 at 5:14 PM snmed wrote: > I'm not sure if i fully understand your point on "vetted binaries", but if > every source code is vetted and then

Re: [go-nuts] Go offline development recommendations

2018-12-13 Thread snmed
I'm not sure if i fully understand your point on "vetted binaries", but if every source code is vetted and then transferred to the isolated environment, there should not be a problem with security issues. All the developer machine living already in the same isolated environment and also i

Re: [go-nuts] Go offline development recommendations

2018-12-13 Thread Wojciech S. Czarnecki
On Wed, 12 Dec 2018 22:15:23 -0800 (PST) snmed wrote: > Thank you very much for your reply. It seems to be a possible way to do it, > what do you think about the athens way? >From the secop pov it'll be a hells gate. Also it does not allow for vetted binary arifacts as current unix/Go ways do.

Re: [go-nuts] Go offline development recommendations

2018-12-12 Thread Tom Mitchell
On Wed, Dec 12, 2018 at 10:15 PM snmed wrote: > Thank you very much for your reply. It seems to be a possible way to do > it, what do you think about the athens way? In my point of view it would be > the easiest way as far i can preload the athens cache with all the required > packages, > And

Re: [go-nuts] Go offline development recommendations

2018-12-12 Thread snmed
Thank you very much for your reply. It seems to be a possible way to do it, what do you think about the athens way? In my point of view it would be the easiest way as far i can preload the athens cache with all the required packages, And then the only thing a developer has to do, is to set the

Re: [go-nuts] Go offline development recommendations

2018-12-12 Thread Justin Israel
On Thu, Dec 13, 2018 at 11:19 AM snmed wrote: > Hi thepudds > > Thanks for you Reply. Indeed vendoring is an Option, but I'm not sure how > long that will be supported. I think i've read about a blog post which says > vendoring will be remove from the go tools, but i'm not sure if this still >

Re: [go-nuts] Go offline development recommendations

2018-12-12 Thread Wojciech S. Czarnecki
On Wed, 12 Dec 2018 13:35:36 -0800 (PST) thepudds1...@gmail.com wrote: > Hi Sandro, > > Vendoring is another approach that can work here. IMO a big No! Vendoring is a footgun (talking secure corporate environment settings). There are too many ways to get Bob and Anna developers and builder box

Re: [go-nuts] Go offline development recommendations

2018-12-12 Thread Wojciech S. Czarnecki
On Wed, 12 Dec 2018 11:59:59 -0800 (PST) snmed wrote: > Hi all > > Our customer demands an offline development environment with no internet > connection, is there any best practices to handle package download and > project setup for such an use case? Such setups are supported by the Go from

Re: [go-nuts] Go offline development recommendations

2018-12-12 Thread snmed
Hi Tom Thanks for your input. Generally speaking, the overall process how to handle development in an air gapped environment is clear and also how i can identify the required files. My question was more about best practices to handle such situation for go project. At the moment i favour athens

Re: [go-nuts] Go offline development recommendations

2018-12-12 Thread snmed
Hi thepudds Thanks for you Reply. Indeed vendoring is an Option, but I'm not sure how long that will be supported. I think i've read about a blog post which says vendoring will be remove from the go tools, but i'm not sure if this still on the Roadmap of the go Team. I will have a look into

Re: [go-nuts] Go offline development recommendations

2018-12-12 Thread thepudds1460
Hi Sandro, Vendoring is another approach that can work here. In a pre-modules world, vendoring is fairly well known. In a modules world, vendoring is still an option. For example, you can see this FAQ here that touches on using 'go mod vendor' with modules:

Re: [go-nuts] Go offline development recommendations

2018-12-12 Thread Tom Mitchell
On Wed, Dec 12, 2018 at 12:00 PM snmed wrote: > Hi all > > Our customer demands an offline development environment with no internet > connection, is there any best practices to handle package download and > project setup for such an use case? And how would the new go modules fit in > in such an

Re: [go-nuts] Go offline development recommendations

2018-12-12 Thread snmed
Thank you for you reply, yes i have already read about that project, but as far as I see, there is no offline loading implemented. But I'm sure it would be doable with some customisation. I wondering if there is another approach for an offline scenario. Some other ideas or suggestions? Thanks

Re: [go-nuts] Go offline development recommendations

2018-12-12 Thread Burak Serdar
On Wed, Dec 12, 2018 at 1:00 PM snmed wrote: > > Hi all > > Our customer demands an offline development environment with no internet > connection, is there any best practices to handle package download and > project setup for such an use case? And how would the new go modules fit in > in such

[go-nuts] Go offline development recommendations

2018-12-12 Thread snmed
Hi all Our customer demands an offline development environment with no internet connection, is there any best practices to handle package download and project setup for such an use case? And how would the new go modules fit in in such an environment? Any advise will be most appreciated.