gocenter - The Github README for JFrog Go-center. Use this for reporting issues

  •        36

If you are reading this, then hopefully you have an interest in immutable re-usable Go modules, so welcome to JFrog GoCenter. If you haven't already, you can check out the actual web page at gocenter.io, but you may as well stick around and read this page first. The Go client fails if at least one dependency can’t be found at GOPROXY. We recommend using goc instead of go to build your projects with GoCenter. For example: goc build. This is more fully explained in the Using goc wiki page.

https://gocenter.io
https://github.com/jfrog/gocenter

Tags
Implementation
License
Platform

   




Related Projects

athens - A Go module datastore and proxy

  •    Go

Welcome to the Athens project! We are a proxy server for the Go Modules download API. See our documentation site https://docs.gomods.io for more details on the project.

GOPROXY - A global proxy for Go modules.

  •    Go

GOPROXY is a global proxy for Go modules. When you build your applications, Go will fetch dependencies via goproxy.io. You can also permanently export the GOPROXY environment in ~/.bashrc or ~/.profile file.

goop - A simple dependency manager for Go (golang), inspired by Bundler.

  •    Go

A dependency manager for Go (golang), inspired by Bundler. It is different from other dependency managers in that it does not force you to mess with your GOPATH. Run goop install. This will install packages inside a subdirectory called .vendor and create Goopfile.lock, recording exact versions used for each package and its dependencies. Subsequent goop install runs will ignore Goopfile and install the versions specified in Goopfile.lock. You should check this file in to your source version control. It's a good idea to add .vendor to your version control system's ignore settings (e.g. .gitignore).

gpm - Barebones dependency manager for Go.

  •    Shell

Go Package Manager (or gpm, for short) is a tool that helps achieve reproducible builds for Go applications by specifying the revision of each external Go package that the application depends on.Being simple and unobstrusive are some of the most important design choices for gpm: go get already provides a way to fetch dependencies, and relies on versions control systems like Git to do it, gpm adds the additional step of setting each dependency repo to the desired revision, neither Go or your application even know about any of this happening, it just works.

asciigraph - Go package to make lightweight ASCII line graph ╭┈╯ in command line apps with no other dependencies

  •    Go

Go package to make lightweight ASCII line graphs ╭┈╯. This package also brings a small utility for command line usage. Assuming $GOPATH/bin is in your $PATH, simply go get it then install CLI.


golang-builder - Containerized build environment for compiling an executable Golang package and packaging it in a light-weight Docker container

  •    Shell

Containerized build environment for compiling an executable Golang package and packaging it in a light-weight Docker container.One of the (many) benefits of developing with Go is that you have the option of compiling your application into a self-contained, statically-linked binary. A statically-linked binary can be run in a container with NO other dependencies which means you can create incredibly small images.

JFrog - Artifact Repository Manager

  •    Java

JFrog is an universal Artifact Repository Manager on the market, JFrog Artifactory fully supports software packages created by any language or technology. As a local proxy to the outside world, Artifactory guarantees consistent access to the components needed by your build tools. Remote artifacts are cached locally for reuse, so that you don’t have to download them over and over again. Automate all aspects of artifact management using a powerful REST API.

patch-package - Fix broken node modules with no fuss 📦👌

  •    TypeScript

patch-package lets app authors instantly make and keep fixes to npm dependencies. It's a vital band-aid for those of us living on the bleeding edge. Patches created by patch-package are automatically and gracefully applied when you use npm(>=5) or yarn.

Glide - Package Management for Golang

  •    Go

Are you used to tools such as Cargo, npm, Composer, Nuget, Pip, Maven, Bundler, or other modern package managers? If so, Glide is the comparable Go tool. Manage your vendor and vendored packages with ease. Glide is a tool for managing the vendor directory within a Go package. This feature, first introduced in Go 1.5, allows each package to have a vendor directory containing dependent packages for the project. These vendor packages can be installed by a tool (e.g. glide), similar to go get or they can be vendored and distributed with the package.

structs - Utilities for Go structs

  •    Go

Structs contains various utilities to work with Go (Golang) structs. It was initially used by me to convert a struct into a map[string]interface{}. With time I've added other utilities for structs. It's basically a high level package based on primitives from the reflect package. Feel free to add new functions or improve the existing code.The structs functions can be also used as independent methods by creating a new *structs.Struct. This is handy if you want to have more control over the structs (such as retrieving a single Field).

color - Color package for Go (golang)

  •    Go

Color lets you use colorized outputs in terms of ANSI Escape Codes in Go (Golang). It has support for Windows too! The API can be used in several ways, pick one that suits you.Note that the vendor folder is here for stability. Remove the folder if you already have the dependencies in your GOPATH.

depscheck - Dependency checker for Golang (Go) packages

  •    Go

Dependency checker for Golang (Go) packages. Prints stats and suggests to remove small LeftPad-like imports if any. DepsCheck analyzes source code of your package and all its imports and attempts to find good candidates to be removed as a dependency. It only suggests to pay attention to those dependencies, nothing more. It also can shows detailed statistics for imported packages usage, including external functions, methods, variables and types used in your project. For functions and methods it calculates LOC (Lines Of Code), Cumulative LOC (sum of nested functions), number of calls, nesting depth and so on.

gobenchui - UI for overview of your Golang package benchmarks progress.

  •    Go

UI for overview of your package benchmarks progress. GoBenchUI does one simple thing - it copies your package into temporary directory, checks out every commit in source control history and run benchmarks for this version. It presents results on highcharts.js based web UI in realtime.

goapp - An opinionated guideline to structure & develop a Go web application/service

  •    Go

This is an opinionated guideline to structure a Go web application/service (or could be extended for any application). My opinions were formed over a span of 5+ years building web applications/services with Go, trying to implement DDD (Domain Driven Development) & Clean Architecture. Even though I've mentioned go.mod and go.sum, this guideline works for 1.4+ (i.e. since introduction of the special 'internal' directory). P.S: This guideline is not directly applicable for an independent package, as their primary use is to be consumed in other applications. In such cases, having most or all of the package code in the root is probably the best way of doing it. And that is where Go's recommendation of "no unnecessary sub packages" shines.

gps - your dependencies have arrived

  •    Go

gps is the Go Packaging Solver. It is an engine for tackling dependency management problems in Go. It is trivial - about 35 lines of code - to replicate the fetching bits of go get using gps. gps is not Yet Another Go Package Management Tool. Rather, it's a library that package management (and adjacent) tools can use to solve the hard parts of the problem in a consistent, holistic way. It is a distillation of the ideas behind language package managers like bundler, npm, elm-package, cargo (and others) into a library, artisanally handcrafted with ❤️ for Go's specific requirements.

nut - Vendor Go dependencies

  •    Go

Gophers love nuts.nut is a tool that allows Go projects to declare dependencies, download dependencies, rewrite import paths and ensure that dependencies are properly vendored.

tenus - Linux networking in Golang

  •    Go

tenus is a Golang package which allows you to configure and manage Linux network devices programmatically. It communicates with Linux Kernel via netlink to facilitate creation and configuration of network devices on the Linux host. The package also allows for more advanced network setups with Linux containers including Docker. tenus uses runc's implementation of netlink protocol. The package only works with newer Linux Kernels (3.10+) which are shipping reasonably new netlink protocol implementation, so if you are running older kernel this package won't be of much use to you I'm afraid. I have developed this package on Ubuntu Trusty Tahr which ships with 3.13+ and verified its functionality on Precise Pangolin with upgraded kernel to version 3.10. I could worked around the netlink issues by using ioctl syscalls, but I decided to prefer "pure netlink" implementation, so suck it old Kernels.

gocron - Easy and fluent Go cron scheduling

  •    Go

gocron is a Golang job scheduling package which lets you run Go functions periodically at pre-determined interval using a simple, human-friendly syntax. gocron is a Golang implementation of the Ruby module clockwork and the Python job scheduling package schedule.

gocron - A Golang Job Scheduling Package.

  •    Go

This package is currently looking for new maintainers. Please message @jasonlvhit if you are interested. goCron is a Golang job scheduling package which lets you run Go functions periodically at pre-determined interval using a simple, human-friendly syntax.

tenus - Linux networking in Go

  •    Go

tenus is a Golang package which allows you to configure and manage Linux network devices programmatically. It communicates with Linux Kernel via netlink to facilitate creation and configuration of network devices on the Linux host. The package also allows for more advanced network setups with Linux containers including Docker. tenus uses runc's implementation of netlink protocol. The package only works with newer Linux Kernels (3.10+) which are shipping reasonably new netlink protocol implementation, so if you are running older kernel this package won't be of much use to you I'm afraid. I have developed this package on Ubuntu Trusty Tahr which ships with 3.13+ and verified its functionality on Precise Pangolin with upgraded kernel to version 3.10. I could worked around the netlink issues by using ioctl syscalls, but I decided to prefer "pure netlink" implementation, so suck it old Kernels.






We have large collection of open source products. Follow the tags from Tag Cloud >>


Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.