Documentation
¶
Overview ¶
Package version says what build a binary is. A release build sets Release with -ldflags "-X github.com/flokkit/apptown/internal/version.Release=v1.0.0"; every other build names its commit from Go's build information.
Which binaries work together is not decided by this string but by the protocol numbers each side states (worker.Protocol*, CLIProtocol here).
Index ¶
Constants ¶
const ( CLIProtocolHeader = "X-AppTown-CLI-Protocol" // CLIProtocol is what this build's CLI speaks. CLIProtocol = 1 // CLIProtocolMin and CLIProtocolMax are what this build's AppTown accepts. CLIProtocolMin = 1 CLIProtocolMax = 1 // Header names AppTown's version on every API response. Header = "X-AppTown-Version" )
The CLI protocol says which CLIs an AppTown accepts (design/operations, stock/docs/guides/upgrading.md, "Versions"). The CLI states the number it speaks on every request; an AppTown accepts a range and refuses another by name. A CLI an AppTown hands its agents is built from AppTown's own tree, so it always matches; a person's own CLI can lag or lead.
Variables ¶
var Release string
Release is the release name stamped at build, empty for other builds.
var Revision string
Revision is the commit stamped by make and the deploy scripts, for a build whose Go build information names none: Go does not stamp a build made in a git worktree, which is where deploys are built.
Functions ¶
Types ¶
This section is empty.
Source Files