digital ocean automated remote golang app deployment : git push, go build, remove source code and start docker container with binary as entrypoint

[twiggg]

Good afternoon,

I am very new to git, cloud and deployment. Is it possible to easily create a tunnel between local computer and a coreOs machine (hosted by digital ocean), and remotely push golang source code to the cloud, automatically build the binary at reception, start a docker container running this binary (webapp) and delete source code to secure the app?

[Paperback]

This isn't really an issue with gitreceive...

but sure, absolutely. The problem is that unless you're using an existing solution (Checkout these PaaS: Dokku, Flynn or Deis) you will obviously have to tie everything together yourself.
Needless to say, this takes a bit of time and effort, especially if you're learning.

Unless you require large scale deployment, maybe Dokku running on different OS is better for you. (I don't know much about Dokku and CoreOS working together).

If you are very new to all this I'd recommend starting super simple. If you can't setup a server and deploy releases on it while knowing exactly what you're doing, don't bother trying to automate that process.

Maybe this article from DigitalOcean will help you.

[twiggg]

You are correct, this is not an issue ... It was juste a way to contact you
efficiently sorry for doing it this way.

Thank you for your answer. You are right it should be simpler to start by
just doing everything manualy, or even scp the binary ... I just wanted to
know if this was approachable easily with gitreceive.

Lahssen

Le 6 oct. 2016 4:36 PM, "Sam Sweeney" notifications@github.com a écrit :

This isn't really an issue with gitreceive...

but sure, absolutely. The problem is that unless you're using an existing
solution (Checkout these PaaS: Dokku https://github.com/dokku/dokku, Flynn
https://flynn.io/docs/apps or Deis http://deis.io/) you will obviously
have to tie everything together yourself.
Needless to say, this takes a bit of time and effort, especially if you're
learning.

Unless you require large scale deployment, maybe Dokku running on
different OS is better for you. (I don't know much about Dokku and CoreOS
working together).

If you are very new to all this I'd recommend starting super simple. If
you can't setup a server and deploy releases on it while knowing exactly
what you're doing, don't bother trying to automate that process.

Maybe this article from DigitalOcean
https://www.digitalocean.com/community/tutorials/how-to-use-the-dokku-one-click-digitalocean-image-to-run-a-go-app
will help you.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#43 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKx8lO3KgtA8uueE5gPZrMegESc98ndlks5qxQdzgaJpZM4KP9WS
.