I haven't done that, but with what little I do know about that type of deployment, I cannot see how choosing Caddy would make any difference.
If you do go that route, I would appreciate hearing about any success or problems that you have. -- Kevin Powick On Friday, 10 March 2017 22:33:29 UTC-5, Sankar wrote: > > Just curios to know if I am going to use kubernetes for deployment, would > choosing Caddie make any difference (either good or bad) ? I will > investigate myself later, but wanted to know your opinion, incase you have > already done that. Thanks. > > 2017-03-10 20:46 GMT+05:30 Kevin Powick <kpo...@gmail.com <javascript:>>: > >> I know you're just looking for a checklist, but we found it better to use >> Caddy (built in Go) as our web, and then have our Go API service proxied >> via that. It's pretty awesome because it's so easy to use Caddy in that >> way. >> >> For example : >> >> http://mydomain/mypage will serve up your page, but you can tell Caddy >> to route requests for http://mydomain/api/dosomething to the port behind >> your firewall that your Go service is running on. >> >> Caddy also allows gives you http2 and automatic security via https >> >> https://caddyserver.com/ >> >> For us, the big advantage is that we could focus on our Go API service >> being only that, and not a web page server as well. >> >> -- >> Kevin Powick >> >> >> On Wednesday, 8 March 2017 14:02:50 UTC-5, Sankar wrote: >>> >>> Hi >>> >>> I have written a golang REST API server and a react webapp that talks to >>> this REST server. There is a mysql server that the golang server talks to. >>> There is an init script with a bunch of SQL statements to create a few >>> tables and indexes. Everything works fine in my local machine. I have >>> bought a domain name too. I have a VM on cloud with ssh access. >>> >>> I wanted to find out if there are any good blog posts or talks or >>> tutorials or "checklists" documenting the process to deploy such a golang >>> server + a web front end behind a domain name (example.com for the >>> react webapp and api.example.com for the golang) and both accessible >>> only via HTTPS, with the API Server probably behind a load balancer, and >>> all certificates being valid, etc. >>> >>> I understand that I can use kubernetes for such orchestration. But I >>> wanted to find out a deploy solution which could work reliably and easily >>> (without depending on too many third party projects) on AWS. GKE does not >>> exist in my region (India) and so cannot use Kube. Any pointers ? >>> >>> Thanks. >>> >>> Sankar >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "golang-nuts" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/golang-nuts/sTsDhJLKTqU/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> golang-nuts...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Sankar P > http://psankar.blogspot.com > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
