Super simple deployment tool

Christopher McKenzie

Last update: Oct 4, 2022

Comments: 15

Dropship

Dropship is a simple tool for installing and updating artifacts from a CDN.

Features

Automatically performs md5sum checks of artifact that is on server and remote and will download automatically
Distributed sequential updates
Multiple Artifact Repository Support

Installation

To install on ubuntu do the following:

echo "deb http://dl.bintray.com/chrismckenzie/deb trusty main" >> /etc/apt/sources.list
sudo apt-get update
sudo apt-get install dropship

Configuration

To setup dropship you will need to add/update the following files.

First you will need to tell dropship how to connect to your artifact repository so you will need to uncomment out the desired repo and fill in its options.

/etc/dropship.d/dropship.hcl

# vim: set ft=hcl :
# Location that service config will be read from
service_path = "/etc/dropship.d/services"

# Rackspace Repo Config
# =====================
repo "rackspace" {
  user = "<your-rackspace-user>"
  key = "<your-rackspace-key>"
  region = "<rackspace-region>"
}

repo "s3" {
  accessKey = "<your-s3-key>"
  secret = "<your-s3-secret>"
  name = "us-west-1"
  endpoint = "https://s3-us-west-1.amazonaws.com"
}

You will then have to create a file in the services directory of dropship. this will tell dropship how to check and install you artifact. You can have multiple service definitions in one file or multiple files.

/etc/dropship.d/services/my-service.hcl

# vim: set ft=hcl :
service "my-service" {
  # Use a semaphore to update one machine at a time
  sequentialUpdates = true

  # Check for updates every 10s
  checkInterval = "10s"

  # Run this command before update starts
  before "script" {
    command = "initctl my-service stop"
  }

  # Artifact defines what repository to use (rackspace) and where 
  # your artifact live on that repository
  artifact "rackspace" {
    bucket = "my-container"
    path = "my-service.tar.gz"
    destination = "./test/dest"
  }

  # After successful update send an event to graphite
  # this allows you to show deploy annotations in tools like grafana
  # 
  # The graphite hook will automatically add this services name into the 
  # graphite tags. You also have access to all of the services meta data
  # like Name, "current hash", hostname.
  after "graphite-event" {
    host = "http://<my-graphite-server>"
    tags = "deployment"
    what = "deployed to {{.Name}} on {{.Hostname}}"
    data = "{{.Hash}}"
  }

  # Run this command after the update finishes
  after "script" {
    command = "initctl my-service start"
  }
}

Building

install go 1.5.1
clone repo
run go get ./...
run go build -o dropship main.go

Roadmap

Hooks
Support for Amazon S3
Support for different file types docker (currently only tar.gz, and simple files)
Reporting system
Redis, etcd for semaphore

Owner

Christopher McKenzie

Father, Edge Operations Manager Passionate about simpler deployment practices keybase.io/chrismckenzie

https://github.com/chrismckenzie/dropship http://chrismckenzie.io/post/deploy-anything/

Comments

Support for piping commands

I have the following command in my dropship config file:

  before "script" {
    command = "ls | xargs echo"
  }

However, when I run it I get the following error:

2016/05/09 20:16:50 [INF]: Executing "script" hook with map[command:ls | xargs echo]
2016/05/09 20:16:50 [INFO]:
2016/05/09 20:16:50 [ERR]: Unable to execute "script" hook exit status 2

I'd like to be able to pipe commands in these scripts - is there a way to do that?

Need rolling deployment

This might be related to #18, but I'm not certain so I'm creating a new issue. An application accessing the API that is being updated receives 502s for a short period of time during deployments. Ideally, there would be rolling updates, and each instance could be removed from the load balancer during the update, and added back in as soon as it was completed.
Issues with script Hook

It would seem that one of my commands fails in my before "script" hook which is there to stop the process before installing an updated binary this causes the update to fail. Unfortunately none of the commands output is logged to the dropship logs, it would be nice to see this.

Thanks @sdedelbrock for the report!
Timeout for distributed deploys

@dewey4iv brought up a good point today sometimes we may want to have a sleep timeout on our lock so that we for example can say 1 deploy can happen every 10 minutes or some thing like that currently it unlock the second it is finished, which makes it feel like all of the deploys are happening at once.
Add a Gitter chat badge to README.md

ChrisMcKenzie/dropship now has a Chat Room on Gitter

@ChrisMcKenzie has just created a chat room. You can visit it here: https://gitter.im/ChrisMcKenzie/dropship.

This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.

Happy chatting.

PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.
Implement Plain file downloading

Currently dropship only supports Tarball installation and it would be nice to be install for example just a single binary file. this should be super simple to implement.

Race condition onClose

after a long download is finished exiting the agent will panic do to a send on closed channel.

panic: send on closed channel

goroutine 8 [running]:
github.com/ChrisMcKenzie/dropship/work.(*Dispatcher).start(0xc8200f8750)
        /Users/chrism/gocode/src/github.com/ChrisMcKenzie/dropship/work/dispatcher.go:59 +0x293
created by github.com/ChrisMcKenzie/dropship/work.NewDispatcher
        /Users/chrism/gocode/src/github.com/ChrisMcKenzie/dropship/work/dispatcher.go:45 +0x178

goroutine 1 [semacquire]:
sync.runtime_Semacquire(0xc820104534)
        /usr/local/Cellar/go/1.5.1/libexec/src/runtime/sema.go:43 +0x26
sync.(*WaitGroup).Wait(0xc820104528)
        /usr/local/Cellar/go/1.5.1/libexec/src/sync/waitgroup.go:126 +0xb4
github.com/ChrisMcKenzie/dropship/work.(*Runner).Shutdown(0xc820104520)
        /Users/chrism/gocode/src/github.com/ChrisMcKenzie/dropship/work/runner.go:41 +0x3e
github.com/ChrisMcKenzie/dropship/commands.agent(0x7dab00, 0xc820019040, 0x0, 0x2)
        /Users/chrism/gocode/src/github.com/ChrisMcKenzie/dropship/commands/agent.go:46 +0x4c4
github.com/spf13/cobra.(*Command).execute(0x7dab00, 0xc820018f20, 0x2, 0x2, 0x0, 0x0)
        /Users/chrism/gocode/src/github.com/spf13/cobra/command.go:503 +0x869
github.com/spf13/cobra.(*Command).Execute(0x7dacc0, 0x0, 0x0)
        /Users/chrism/gocode/src/github.com/spf13/cobra/command.go:586 +0x46a
github.com/ChrisMcKenzie/dropship/commands.Execute()
        /Users/chrism/gocode/src/github.com/ChrisMcKenzie/dropship/commands/dropship.go:38 +0x28
main.main()
        /Users/chrism/Projects/dropship/main.go:6 +0x14

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
        /usr/local/Cellar/go/1.5.1/libexec/src/runtime/asm_amd64.s:1696 +0x1

goroutine 5 [syscall]:
os/signal.loop()
        /usr/local/Cellar/go/1.5.1/libexec/src/os/signal/signal_unix.go:22 +0x18
created by os/signal.init.1
        /usr/local/Cellar/go/1.5.1/libexec/src/os/signal/signal_unix.go:28 +0x37

goroutine 6 [select]:
github.com/ncw/swift.(*Connection).doTimeoutRequest(0xc820138120, 0xc8201e0100, 0xc82035a620, 0xc8203da120, 0x0, 0x0)
        /Users/chrism/gocode/src/github.com/ncw/swift/swift.go:226 +0x21d
github.com/ncw/swift.(*Connection).Call(0xc820138120, 0xc8201e0000, 0x3d, 0xc8200fc861, 0x6, 0xc8200197c1, 0x19, 0x55b8c0, 0x4, 0x0, ...)
        /Users/chrism/gocode/src/github.com/ncw/swift/swift.go:468 +0x6ec
github.com/ncw/swift.(*Connection).storage(0xc820138120, 0xc8200fc861, 0x6, 0xc8200197c1, 0x19, 0x55b8c0, 0x4, 0x0, 0x0, 0xc820014e10, ...)
        /Users/chrism/gocode/src/github.com/ncw/swift/swift.go:527 +0x128
github.com/ncw/swift.(*Connection).Object(0xc820138120, 0xc8200fc861, 0x6, 0xc8200197c1, 0x19, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
        /Users/chrism/gocode/src/github.com/ncw/swift/swift.go:1679 +0xe2
github.com/ChrisMcKenzie/dropship/updater.(*RackspaceUpdater).IsOutdated(0xc820847cf0, 0xc8204ae340, 0x20, 0xc820847ee0, 0x1, 0x0, 0x0)
        /Users/chrism/gocode/src/github.com/ChrisMcKenzie/dropship/updater/rackspace.go:42 +0xb2
github.com/ChrisMcKenzie/dropship/work.(*Dispatcher).Work(0xc8200f8750)
        /Users/chrism/gocode/src/github.com/ChrisMcKenzie/dropship/work/dispatcher.go:74 +0x418
github.com/ChrisMcKenzie/dropship/work.NewRunner.func1(0xc820104520)
        /Users/chrism/gocode/src/github.com/ChrisMcKenzie/dropship/work/runner.go:26 +0x7e
created by github.com/ChrisMcKenzie/dropship/work.NewRunner
        /Users/chrism/gocode/src/github.com/ChrisMcKenzie/dropship/work/runner.go:29 +0xe4

goroutine 9 [select, locked to thread]:
runtime.gopark(0x63e798, 0xc82002ff28, 0x561f88, 0x6, 0x2cc18, 0x2)
        /usr/local/Cellar/go/1.5.1/libexec/src/runtime/proc.go:185 +0x163
runtime.selectgoImpl(0xc82002ff28, 0x0, 0x18)
        /usr/local/Cellar/go/1.5.1/libexec/src/runtime/select.go:392 +0xa64
runtime.selectgo(0xc82002ff28)
        /usr/local/Cellar/go/1.5.1/libexec/src/runtime/select.go:212 +0x12
runtime.ensureSigM.func1()
        /usr/local/Cellar/go/1.5.1/libexec/src/runtime/signal1_unix.go:227 +0x323
runtime.goexit()
        /usr/local/Cellar/go/1.5.1/libexec/src/runtime/asm_amd64.s:1696 +0x1

goroutine 25 [select]:
net/http.(*persistConn).writeLoop(0xc8204b40b0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:1009 +0x40c
created by net/http.(*Transport).dialConn
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:686 +0xc9d

goroutine 24 [IO wait]:
net.runtime_pollWait(0x2101098, 0x72, 0xc8200122e0)
        /usr/local/Cellar/go/1.5.1/libexec/src/runtime/netpoll.go:157 +0x60
net.(*pollDesc).Wait(0xc8204c2140, 0x72, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/fd_poll_runtime.go:73 +0x3a
net.(*pollDesc).WaitRead(0xc8204c2140, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/fd_poll_runtime.go:78 +0x36
net.(*netFD).Read(0xc8204c20e0, 0xc820536000, 0x8000, 0x8000, 0x0, 0xfa0050, 0xc8200122e0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/fd_unix.go:232 +0x23a
net.(*conn).Read(0xc82013c040, 0xc820536000, 0x8000, 0x8000, 0x0, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/net.go:172 +0xe4
crypto/tls.(*block).readFromUntil(0xc820487260, 0x21011a8, 0xc82013c040, 0x5, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/crypto/tls/conn.go:455 +0xcc
crypto/tls.(*Conn).readRecord(0xc8204d6000, 0x63e817, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/crypto/tls/conn.go:540 +0x2d1
crypto/tls.(*Conn).Read(0xc8204d6000, 0xc8204f8000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/crypto/tls/conn.go:901 +0x167
net/http.noteEOFReader.Read(0x210df88, 0xc8204d6000, 0xc8204b4108, 0xc8204f8000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:1370 +0x67
net/http.(*noteEOFReader).Read(0xc8204f01a0, 0xc8204f8000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
        <autogenerated>:126 +0xd0
bufio.(*Reader).fill(0xc82049cba0)
        /usr/local/Cellar/go/1.5.1/libexec/src/bufio/bufio.go:97 +0x1e9
bufio.(*Reader).Peek(0xc82049cba0, 0x1, 0x0, 0x0, 0x0, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/bufio/bufio.go:132 +0xcc
net/http.(*persistConn).readLoop(0xc8204b40b0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:876 +0xf7
created by net/http.(*Transport).dialConn
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:685 +0xc78

goroutine 4046 [select]:
net/http.(*persistConn).writeLoop(0xc8204b4370)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:1009 +0x40c
created by net/http.(*Transport).dialConn
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:686 +0xc9d

goroutine 4045 [select]:
net/http.(*persistConn).readLoop(0xc8204b4370)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:976 +0xac7
created by net/http.(*Transport).dialConn
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:685 +0xc78

goroutine 4027 [select]:
net/http.(*persistConn).writeLoop(0xc820413970)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:1009 +0x40c
created by net/http.(*Transport).dialConn
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:686 +0xc9d

goroutine 4026 [IO wait]:
net.runtime_pollWait(0x2100f18, 0x72, 0xc8200122e0)
        /usr/local/Cellar/go/1.5.1/libexec/src/runtime/netpoll.go:157 +0x60
net.(*pollDesc).Wait(0xc82001a3e0, 0x72, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/fd_poll_runtime.go:73 +0x3a
net.(*pollDesc).WaitRead(0xc82001a3e0, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/fd_poll_runtime.go:78 +0x36
net.(*netFD).Read(0xc82001a380, 0xc8202be800, 0x400, 0x400, 0x0, 0xfa0050, 0xc8200122e0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/fd_unix.go:232 +0x23a
net.(*conn).Read(0xc820030038, 0xc8202be800, 0x400, 0x400, 0x0, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/net.go:172 +0xe4
crypto/tls.(*block).readFromUntil(0xc8203e22d0, 0x21011a8, 0xc820030038, 0x5, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/crypto/tls/conn.go:455 +0xcc
crypto/tls.(*Conn).readRecord(0xc8204d6580, 0x63e817, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/crypto/tls/conn.go:540 +0x2d1
crypto/tls.(*Conn).Read(0xc8204d6580, 0xc820261000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/crypto/tls/conn.go:901 +0x167
net/http.noteEOFReader.Read(0x210df88, 0xc8204d6580, 0xc8204139c8, 0xc820261000, 0x1000, 0x1000, 0xc820222840, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:1370 +0x67
net/http.(*noteEOFReader).Read(0xc8203beee0, 0xc820261000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
        <autogenerated>:126 +0xd0
bufio.(*Reader).fill(0xc82047d7a0)
        /usr/local/Cellar/go/1.5.1/libexec/src/bufio/bufio.go:97 +0x1e9
bufio.(*Reader).Peek(0xc82047d7a0, 0x1, 0x0, 0x0, 0x0, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/bufio/bufio.go:132 +0xcc
net/http.(*persistConn).readLoop(0xc820413970)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:876 +0xf7
created by net/http.(*Transport).dialConn
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:685 +0xc78

goroutine 4023 [select]:
net/http.(*persistConn).roundTrip(0xc820413970, 0xc82046a0a0, 0x0, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:1164 +0xb0d
net/http.(*Transport).RoundTrip(0xc8201bad80, 0xc82035a620, 0xb8, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/transport.go:235 +0x530
net/http.send(0xc82035a620, 0xfa44b0, 0xc8201bad80, 0xc82047c660, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/client.go:220 +0x52c
net/http.(*Client).send(0xc82043ad20, 0xc82035a620, 0x5e, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/client.go:143 +0x15a
net/http.(*Client).doFollowingRedirects(0xc82043ad20, 0xc82035a620, 0x63e390, 0x0, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/client.go:380 +0xbc0
net/http.(*Client).Do(0xc82043ad20, 0xc82035a620, 0x2246b1, 0x0, 0x0)
        /usr/local/Cellar/go/1.5.1/libexec/src/net/http/client.go:175 +0x9c
github.com/ncw/swift.(*Connection).doTimeoutRequest.func1(0xc820138120, 0xc82035a620, 0xc82047c480)
        /Users/chrism/gocode/src/github.com/ncw/swift/swift.go:222 +0x36
created by github.com/ncw/swift.(*Connection).doTimeoutRequest
        /Users/chrism/gocode/src/github.com/ncw/swift/swift.go:224 +0x8b

Add tool to verify dropship.yml

It would be awesome to have a tool that can validate/run your dropship.yml from a cli on a developer machine. This would greatly reduce the commit->deploy->check workflow that most hook systems have.
Build UI for deployment logs

We need a way to view the response from the remote servers so that it is easier to debug and monitor. I imagine something akin to _Wercker, or CI's alike.
Mult-task definitions
I would like to be able to define custom tasks in my dropship.yml for example a task that migrates database schemas as well as a task that just deploys the app

Example:

tasks: "deploy:migrate": steps: - ... deploy: steps: - ...
Add Environment support
Github API can optionally send a deployment environment it would be nice to be able to define a different set of servers for each environment.

maybe something like this:

servers: development: provider: list options: list: - address: 127.0.0.1

@ericgreene || @krisbarrett || @mattwarren1234 do you have any input?
Release, Build, and Testing

Currently I am the only active developer on this project and so I have tended not to get crazy with automation initially so I build, test and release somewhat manually through my own machine which is not the best. I would like to use Werckers new workflows feature and setup the system to do all these things for me!
Management and Monitoring Interface

This meant as a planning issue for the new v2 UI additions.

The management and monitoring interface is pretty self explanatory and provides a central ui for all dropship instances to be monitored and configured. This will allow users to easily catch errors on deployment for there service on an overall or per-machine basis. This interface will also supply some much needed coordination for services and will allows us to fire hooks for when an entire service (all machines) have completed their deployment.

I have started development on this first as it will change quite a few things in the architecture of the application. This will be accomplished by using an grpc service for streaming and registering service data back and forth between agent and manager.

Manager

The manager is the responsible for serving both the UI and a portion of the RPC service. The UI will be a simple web service that will display all services that are registered with it and allow users to see past deployments as well as the state of any current deployments. The Manager RPC service will be a gRPC service that will contain a few functions for managing (adding, removing) Service Members, as well as a set of streaming interfaces for receiving results from current deployments.

Wrong mime detection

The following dropship config errors out:

service "cadabra-api" {
  sequentialUpdates = true
  checkInterval = "10s"

  before "script" {
    command = "initctl stop cadabra-api"
  }

  artifact "rackspace" {
    bucket = "private-binaries"
    path = "cadabra/api/api.tar.gz"
    destination = "/sites"
  }

  after "script" {
    command = "initctl start cadabra-api"
  }
}

Dropship logs:

2016/02/28 02:11:42 [INF]: Acquiring lock for cadabra-api
2016/02/28 02:11:42 [INF]: Downloading update for cadabra-api...
2016/02/28 02:11:42 [INF]: Executing "script" hook with map[command:initctl stop cadabra-api]
2016/02/28 02:11:42 [INF]: Update for cadabra-api installed successfully. [hash: b39e9351ecd98df60752ef7cf99ca878] [files written: 1]
2016/02/28 02:11:42 [INF]: Executing "script" hook with map[command:initctl start cadabra-api]
2016/02/28 02:11:42 [ERR]: Unable to execute "script" hook fork/exec /sbin/initctl: not a directory

this ends up creating a binary file (not the one in the tarball weirdly enough) at /sites (supposed to be the install directory)

Post-deployment testing + rollback

It would be awesome if we had the ability to rollback the deployment based on the pass or fail of a post-deployment script that can be anything, though in the case I'm thinking of, automated integration tests. Also provide hooks for notifications in case of failure, though to start the script could do this.

Go version manager. Super simple tool to install and manage Go versions. Install go without root. Gobrew doesn't require shell rehash.

gobrew Go version manager Install or update With curl $ curl -sLk https://git.io/gobrew | sh - or with go $ go get -u github.com/kevincobain2000/gobre

Jan 5, 2023

a build tool for Go, with a focus on cross-compiling, packaging and deployment

goxc NOTE: goxc has long been in maintenance mode. Ever since Go1.5 supported simple cross-compilation, this tool lost much of its value. There are st

Dec 9, 2022

A Go based deployment tool that allows the users to deploy the web application on the server using SSH information and pem file.

A Go based deployment tool that allows the users to deploy the web application on the server using SSH information and pem file. This application is intend for non tecnhincal users they can just open the GUI and given the server details just deploy.

Oct 16, 2021

Zdeploy - Deployment file tool with golang

zdeploy 中文 Deployment file tool Transfer deployment files Provide shell/bat exec

Sep 22, 2022

crud is a cobra based CLI utility which helps in scaffolding a simple go based micro-service along with build scripts, api documentation, micro-service documentation and k8s deployment manifests

crud crud is a CLI utility which helps in scaffolding a simple go based micro-service along with build scripts, api documentation, micro-service docum

Nov 29, 2021

A super simple demo to document my journey to reasonably sized docker containers.

hello-docker A super simple demo to document my journey to reasonably sized docker containers. Task at Hand Build a docker container as small as possi

Nov 30, 2021

Kubernetes Operator for a Cloud-Native OpenVPN Deployment.

Meerkat is a Kubernetes Operator that facilitates the deployment of OpenVPN in a Kubernetes cluster. By leveraging Hashicorp Vault, Meerkat securely manages the underlying PKI.

Jan 4, 2023

El Carro is a new project that offers a way to run Oracle databases in Kubernetes as a portable, open source, community driven, no vendor lock-in container orchestration system. El Carro provides a powerful declarative API for comprehensive and consistent configuration and deployment as well as for real-time operations and monitoring.

El Carro: The Oracle Operator for Kubernetes Run Oracle on Kubernetes with El Carro El Carro is a new project that offers a way to run Oracle database

Jan 7, 2023

Access your Kubernetes Deployment over the Internet

Kubexpose: Access your Kubernetes Deployment over the Internet Kubexpose makes it easy to access a Kubernetes Deployment over a public URL. It's a Kub

Dec 5, 2022

Kubernetes workload controller for container image deployment

kube-image-deployer kube-image-deployer는 Docker Registry의 Image:Tag를 감시하는 Kubernetes Controller입니다. Keel과 유사하지만 단일 태그만 감시하며 더 간결하게 동작합니다. Container, I

Mar 8, 2022

Secure Distributed Thanos Deployment using an Observability Cluster

Atlas Status: BETA - I don't expect breaking changes, but still possible. Atlas, forced by Zeus to support the heavens and the skies on his shoulders.

Jun 11, 2022

provider-kubernetes is a Crossplane Provider that enables deployment and management of arbitrary Kubernetes objects on clusters

provider-kubernetes provider-kubernetes is a Crossplane Provider that enables deployment and management of arbitrary Kubernetes objects on clusters ty

Dec 14, 2022

expose controller, when deployment created service and ingress will be created

expose-controller expose controller, when deployment created service and ingress will be created How to test git clone repository cd expose-controller

Dec 23, 2021

Cdk-ecr-deployment - CDK Contruct for publishing ECR Images

cdk-ecr-deployment CDK construct to deploy docker image to Amazon ECR ⚠️ Please

Dec 30, 2021

Pega-deploy - Pega deployment on Kubernetes

Pega deployment on Kubernetes This project provides Helm charts and basic exampl

Jan 30, 2022

Linux provisioning scripts + application deployment tools. Suitable for self-hosting and hobby-scale application deployments.

Apollo Linux provisioning scripts + application deployment tools. Suitable for self-hosting and hobby-scale application deployments. Philosophy Linux-

Feb 7, 2022

Super simple deployment tool

Dropship

Features

Installation

Configuration

Building

Roadmap

Owner

Christopher McKenzie

Comments

Support for piping commands

Need rolling deployment

Issues with script Hook

Timeout for distributed deploys

Add a Gitter chat badge to README.md

ChrisMcKenzie/dropship now has a Chat Room on Gitter

Implement Plain file downloading

Race condition onClose

Add tool to verify dropship.yml

Build UI for deployment logs

Mult-task definitions

Add Environment support

Release, Build, and Testing

Management and Monitoring Interface

Manager

Wrong mime detection

Post-deployment testing + rollback

Related tags

Go version manager. Super simple tool to install and manage Go versions. Install go without root. Gobrew doesn't require shell rehash.

a build tool for Go, with a focus on cross-compiling, packaging and deployment

A Go based deployment tool that allows the users to deploy the web application on the server using SSH information and pem file.

Zdeploy - Deployment file tool with golang

crud is a cobra based CLI utility which helps in scaffolding a simple go based micro-service along with build scripts, api documentation, micro-service documentation and k8s deployment manifests

A super simple demo to document my journey to reasonably sized docker containers.

Kubernetes Operator for a Cloud-Native OpenVPN Deployment.

Access your Kubernetes Deployment over the Internet

Kubernetes workload controller for container image deployment

Secure Distributed Thanos Deployment using an Observability Cluster

provider-kubernetes is a Crossplane Provider that enables deployment and management of arbitrary Kubernetes objects on clusters

expose controller, when deployment created service and ingress will be created

Cdk-ecr-deployment - CDK Contruct for publishing ECR Images

Pega-deploy - Pega deployment on Kubernetes

Linux provisioning scripts + application deployment tools. Suitable for self-hosting and hobby-scale application deployments.

Kubernetes Operator to automate Helm, DaemonSet, StatefulSet & Deployment updates

Go-reconcile - Super tiny go package which does reconcile planning

Nycmesh-tool - nycmesh-tool CLI