core

Documentation

Index

• func SpawnHyperSpaceViper(paths ...string) *viper.Viper
• type HyperViper
  • func CreateHyperViper(path string) *HyperViper
• type RootViper
  • func CreateRootViper() *RootViper

Functions

func SpawnHyperSpaceViper

func SpawnHyperSpaceViper(paths ...string) *viper.Viper

* Spawn a HyperSpaceViper given a path to a hyperspace.yaml

Types

type HyperViper

type HyperViper struct {
	// Path to the directory that contains the hyperspace.yaml
	Path string
	// Viper instance for hyperspace config
	// named act so you can access and call like
	// hyperViper.cmd.GetString()
	Viper *viper.Viper
}

* Living config files with relevant network information and paths. HyperVipers don't care about information they hold (the actual data in the hyperspace.yaml. They just act as living data stores for import network information relative to their station.

func CreateHyperViper

func CreateHyperViper(path string) *HyperViper

* Creates a HyperViper for a particular squadron/fleet

type RootViper

type RootViper struct {
	Viper        *viper.Viper
	Network      string
	NetworkPath  string
	NetworkViper *viper.Viper
}

func CreateRootViper

func CreateRootViper() *RootViper

* Creates two Vipers, one at Hyperspace Root (the control center) and another at the Network Root