This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-09-21
Channels
- # admin-announcements (17)
- # aws (19)
- # beginners (28)
- # boot (103)
- # cider (5)
- # clojure (183)
- # clojure-art (46)
- # clojure-russia (25)
- # clojure-sg (2)
- # clojure-uk (1)
- # clojurescript (342)
- # clojurex (3)
- # core-matrix (1)
- # cursive (1)
- # datascript (2)
- # devcards (77)
- # devops (15)
- # emacs (4)
- # funcool (8)
- # hoplon (15)
- # immutant (47)
- # jobs (1)
- # ldnclj (10)
- # lein-figwheel (4)
- # off-topic (2)
- # om (23)
- # onyx (10)
- # re-frame (1)
- # reagent (23)
- # yada (7)
How do you guys overcome the normal delay of update, when deploying new versions using Beanstalk?
i'm not aware of a workaround
Not even using docker containers on top? Coming from Heroku, this is what I’m really hoping to find a solution for.
afaict using docker on beanstalk makes for no faster deploys
there is Dokku, which would give you the ease and speed, but not really the scalability
we have dokku on an EC2 and use it for little low-use apps behind our VPN
well, for the stuff we use dokku for, the weird URLs are ok
i'm not sure what's involved in hooking up dokku to dns on ec2. but when i was looking for stuff, i did find lots of blog posts etc. so maybe there's a way
we are seeing elevated dynamo errors in east, awspocalypse might not be over
alandipert: I don't see errors btw
I recovered service yesterday and it works as expected
Datadog?
yeah, it's sweet, although parts of it also went down with cloudwatch 😞
yeah, cloudwatch and cloudtrail didn't work for me esterday as well