This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-06
Channels
- # 100-days-of-code (15)
- # beginners (32)
- # calva (2)
- # cider (37)
- # clara (1)
- # cljs-dev (47)
- # clojure (177)
- # clojure-boston (1)
- # clojure-dev (2)
- # clojure-germany (1)
- # clojure-greece (5)
- # clojure-italy (13)
- # clojure-nl (2)
- # clojure-sanfrancisco (1)
- # clojure-uk (72)
- # clojurescript (46)
- # cursive (20)
- # datascript (7)
- # datomic (14)
- # devcards (6)
- # docker (1)
- # duct (1)
- # emacs (1)
- # figwheel (3)
- # figwheel-main (151)
- # graphql (2)
- # hyperfiddle (1)
- # interop (3)
- # jobs (3)
- # lumo (2)
- # off-topic (21)
- # pedestal (1)
- # re-frame (9)
- # reagent (25)
- # shadow-cljs (57)
- # slack-help (4)
- # specter (21)
- # tools-deps (53)
- # vim (2)
Morning 😄
One more week until ClojuTRE. I know this has been asked before, but who else is going this year?
not going either sadly 😞
morning!
morning
måninng
Bore da
110 days to the winter holidays.
On Saturday 15th September I'm starting a 100 days of clojure code challenge, which ends just before the winter holidays. The basic plan and log of my efforts is on https://github.com/jr0cket/100-days-of-clojure-code and in the #100-days-of-code channel. Any advice and support is most welcome.
Sounds like an interesting thing to do @U05254DQM 👍
any other cljs+cordova users in here ?
Anyone got experience with connecting an app deployed in AWS US regions to an RDS instance deployed in EU regions?
@maleghast i've had heroku apps (i think they were AWS US) connected to (AWS eire) RDS instances, so i think you should be ok
@mccraigmccraig - That is comforting / good to know...
I am hoping that I can give the security group of my EKS worker nodes to the RDS instance and it will all just be seamless, but I am not going to know until I try...
some of the AWs networking stuff can be pretty awkward to get working... not because of lack of features, just because it's not always obvious how to configure it
Yeah, that's really my concern, that I won't be able to decode the magical incantation, not that it's impossible.
@mccraigmccraig it's that old joke about every time you find out how to do something in AWS, it feels like an easter egg b/c the docs/ui are so sprawling
you may get poor latency though if your app is far from your db - apologies if that’s stating the obvious!
dunno if people have already seen it... but Clojure 1.10.0-alpha7 has been released. Also a new version of spec as well.
@thomas the chicken knows what it did :knife:
@peterwestmacott - I've decided to put up a manually built K8s cluster in the same location as my RDS instance, basically inside the same vpc.
That way I don't have to worry about connectivity, but the trade-down on that is that it's going to take me more time.
@maleghast have you deployed many services already to K8s?
My production experience of Docker is ECS and I have vowed never to use that again.
dyu see unreliable container networking in k8s @firthh?
I’ve seen random network failures, some of it I think was down to how we were doing service to service communication and kube-dns
But also where I am now, I’ve been less involved but there have been some random issues with network connectivity
I think a lot of it comes down to dns, which might be a little slower to replicate than pods shutting down (so kube-dns returns the ip of a pod that’s now dead)
otoh I've found ECS to be pretty stable... but then we're using it for a non-critical internal service so...
in a similar vein, dc/os networking is rock solid - never had any issues with container-dns or inter-container load-balancing and networking
do you find the overhead worth it?
or is there not as much overhead as I would imagine?
the overhead of dc/os ?
I mean everything's a sliding scale of pain upfront vs over time but still...
sledgehammer and nuts etc
there's definitely a learning curve...
deploying a cluster is pretty straightforward with https://github.com/dcos/terraform-dcos though
no harder than deploying any other cluster with terraform or puppet or salt or whatever really
once EKS makes it over here i'll definitely be looking at switching to that though - since i could deploy to both AWS and google-cloud with k8s and i'm all in favour of paying someone else to look after complicated stuff
"over here"?
Am I the only person that finds git rebase ...
doing unexpected things on occasion (like getting a little confused on subsequent rebases between the same branches down the line)?
We have a code base that is share across a couple of domains (the URI kind and the business kind) with fairly frequent/iterative releases so rebase seems to be the appropriate solution for staying in line with the latest on master
I completely agree with the concept of rebase, but I'm finding it borking every now and again. Most likely a PEBKAC, but not obvious in the nature of the actual cause of the bork
My team were just discussing this article https://medium.com/@fredrikmorken/why-you-should-stop-using-git-rebase-5552bee4fed1