Learning Golang: Dependencies, Modules and How to manage Packages

[@rahulsriram6295]

I found this gem of a channel today and I can't stop binging

[@MarioCarrion]

Welcome to the team Rahul! Take care.

[@SolelyMat]

Grande Mario! Tuve que dejar el curso de Microsoft y venir a ver este video para entender muchas de las cosas que no estaban tan bien explicadas, saludos de Argentina.

[@TheAlissonX1]

thanks for the video! Very good explanation

[@MarcelloLins]

Incredibly useful video ! Thanks for helping demystify something that turned out to be quite simple

[@MarioCarrion]

Thanks Marcello. Take care!

[@josevitormorais4367]

Olá Mario tudo bem? Espero que sim.. falo aqui do Brasil, queria agradecer pelo conteúdo que está disponibilizando no seu canal, sou novo no mundo GOLANG, e seus vídeos são excelentes, ensinando muita coisa que é realmente usado no mercado..atualmente trabalho com nodejs, e tudo q vc ensina aqui eu utilizo com node no dia a dia... parabéns pela didática, suas explicações são ótimas e concisas, espero que continue com o trabalho, sucesso e tudo de bom pra você..

[@MarioCarrion]

Olá Jose. Obrigado pelo seu apoio, fico feliz que os vídeos sejam úteis. Espero que você esteja bem. Take care.

[@ultiumlabs4899]

thanks, it clarifies something I don't understand before.

[@phenvrc]

Thank you so much!!! Your videos are helping me a lot!!

[@MarioCarrion]

Thanks for watching Pedro. Stay safe.

[@dmitrydmitriev2554]

Thank you. A lot of useful information and amazing way to explain things.

[@MarioCarrion]

Thanks Dmitry. Take care.

[@MegaSovietRussian]

Excellent delivery! thank you so much for the tutorial:)

[@MarioCarrion]

Thanks for watching! Take care

[@jasonjiang1326]

This is extremely useful! Thank you so much for the tutorial!

[@MarioCarrion]

Thanks for watching Jason, take care.

[@proudindian3697]

Nice tutorial..!! Thanks

[@MarioCarrion]

Thanks! I'm glad you liked it

[@thorfinnthegoatmc]

This is a very detailed explaination for go modules! thank you very much! although I have a question, If youre using branches as versions of the module how would you manage it if you are merging it with the main branch?

[@MarioCarrion]

Thanks for watching! I think I need a bit more of details regarding your question because I'm not sure if you meant using Go modules (ie importing third party modules) or creating your own (ie versioning/branching/tagging)

[@thorfinnthegoatmc]

@@MarioCarrion creating my own module i mean. Sorry for the vague question 😅

[@MarioCarrion]

No worries! What you're asking is really interesting; assuming each branch is also tagged with their own respective version then you should be able to refer to those individually; however I think it will be a bit difficult to bring changes (as-is) back to main because the go.mod would be different (among other things); a real-life example of this approach that I know of is: github.com/olivere/elastic

[@luq2337]

awesome and excellent explanation!!!! THX!!!!!🥰🥰🥰🥰🥰🥰

[@MarioCarrion]

Thanks! I'm glad you found it useful

[@MarioCarrion]

*Blog* mariocarrion.com/
*Learning Golang* ruclips.net/p/PL7yAAGMOat_F7bOImcjx4ZnCtfyNEqzCy
*Building Microservices in Go* ruclips.net/p/PL7yAAGMOat_Fn8sAXIk0WyBfK_sT1pohu
*Go Tools and Packages* ruclips.net/p/PL7yAAGMOat_HEEOvH99agDs_5g51A0Ls3
*Testing in Go* ruclips.net/p/PL7yAAGMOat_HSeW4zF0uRL9EaHadE4ZZq
*Keep it up!*

[@abdulrafaykhan5996]

Excellent explanation Mario Carrion!! Can you tell what v0.0.0 means?

[@MarioCarrion]

Thanks Abdul
"v0.0.0" means: "Version 0 (Major), 0 (Minor), 0 (Patch)" which in practice means the module being used still has no tagged versions therefore it defaults to something like "v0.0.0-commit-hash".
Best

[@abdulrafaykhan5996]

@@MarioCarrion Great, thanks

[@zikomo8913]

You're the boss!

[@jimzhu7654]

very clear, thank you sir.

[@liminal27]

Excellent. Thank you.

[@rsrini7]

Thanks for the explanation. What is vendor and go mod vendor and vendor folder.

[@MarioCarrion]

Hello Srini
The "vendor" folder is used to keep a local copy of the packages you use in your module (with their corresponding versions); it's a way to avoid downloading remote packages when using the go module, in that case the local copies relative to the module are used instead.

[@jackedelic9188]

What if my dependencies are private repo? How can we configure go mod such that it knows our ssh private key in order to access the private repos?

[@MarioCarrion]

Using private modules is a bit more complicated, the two ways I found working were either using Access Tokens or netrc credentials, I wrote a post about it mariocarrion.com/2020/09/19/configuring-gitlab-ci-and-private-go-modules.html it's for Gitlab but if you use a different VCS there's a similar way to do it.

[@JoeKme]

@@MarioCarrion That is awesome Mario!

[@JayMikB]

First 🚀🚀

[@buacomgiadinh1]

thank you