Let's get started with deploying Cerigo in your compute module. Cerigo itself is a simplified server program built using various tools and components. That way, Cerigo can continuously improve itself in a scalable manner while making the user experience easier.
Before we do something, let’s understand Cerigo in a nut shell.
Cerigo is a full-fletch library package module. Hence, there are no
go get for.
Supported Version Patterns
Currently, Cerigo releases its packages under a different definition of Semantic Versioning. It is defined as follows:
vX.Y.Z v = requirement to attach "v" X = flag to indicate package mode ("production" = 1 | "development = "0" ) Y = non-backward compatible version release Z = backward compatible version release. Reset to 0 if Y is increased.
v1.3.0, the time sequences and
priority list (latest updates first) would be:
v1.3.0 v0.3.0 v0.2.1 v0.2.0
Using Branching Over Tagging
We decided to use branching over tagging mainly because the current
go get enforces version folder implementation or magical
We tried both ways. They are a roller-coaster experience for Cerigo team so to
keep things simple, we stick to branching and keep the major number between
1 as a flag instead.
Hence, when you update Cerigo in your
go.mod, you can use any of the following
$ go get gitlab.com/zoralab/cerigo@main // latest stable release $ go get gitlab.com/zoralab/cerigo@staging // next stable (testing) $ go get gitlab.com/zoralab/cerigo@next // bleeding edge $ go get firstname.lastname@example.org // v0.0.1 release
Now that we understand how Cerigo works, we can proceed to use it in your project.
import any of Cerigo’s library package, you can call in the
statement like the usual Go style. For example, to import
you can do the following:
If you’re using
import group, the best practice would be:
import ( "bytes" "io" ... // leave a space here "gitlab.com/zoralab/cerigo/XYZ" // include library )
To update your
go.mod automatically, you can
go get it at the
$ go get gitlab.com/zoralab/cerigo@BRANCH-NAME
Example, to track
next branch, it is:
$ go get gitlab.com/zoralab/cerigo@next
That’s it. Cerigo is that easy to use in Go project. The rest of the steps would be checking out the Go Documentations section and apply the necessary modules to it. If you have any questions, please feel free to raise a ticket at our Issues section available here: