This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-10
Channels
- # beginners (151)
- # cider (41)
- # cljdoc (7)
- # cljs-dev (6)
- # clojure (92)
- # clojure-dev (5)
- # clojure-italy (26)
- # clojure-losangeles (1)
- # clojure-nl (10)
- # clojure-russia (3)
- # clojure-spec (23)
- # clojure-uk (82)
- # clojurescript (56)
- # clojutre (1)
- # core-async (3)
- # cursive (15)
- # datomic (26)
- # editors (3)
- # emacs (3)
- # events (2)
- # figwheel-main (192)
- # fulcro (66)
- # leiningen (12)
- # mount (1)
- # off-topic (131)
- # portkey (6)
- # re-frame (38)
- # reagent (10)
- # reitit (7)
- # ring-swagger (55)
- # shadow-cljs (21)
- # spacemacs (11)
- # tools-deps (48)
Re git merge vs git rebase round 2: I’m reading that book about applying forensic analysis like techniques to identify problematic areas
And I nod to myself and think, boy, are you ever gonna be surprised when someone applies a rebase
Depends. Do you mean doesn't rebase master onto something else (why would you do that?), or do you mean rebase your latest commits onto the head of master
Aah right. No, we just tend to work on master rather than with branches, so our default pull config is to do a noninteractive rebase (which does of course mean you have to have everything in-progress either committed or stashed to pull)
But we're also a close working team so we don't do pull requests and such for features, just pull (which rebases your new commits which aren't upstream onto the new head of master), followed by push assuming the pull didn't have any merge conflicts
Bore da
morrrrning
morning
måninng
also lovely on the sarf coast
blackcap looking towards brighton
huh, i guess file uploads are kinda broken in free slack @seancorfield ? (i just tried to upload a photo)
shame there’s no “delete old content to make room for new” setting
I can still see it 😄
huh, slack told me that while the image was uploaded, the space was out of storage, which i took to mean that it wouldn't be displayed without $$$
Nice view @mccraigmccraig
@mccraigmccraig yeah slack does that but then the image still shows ¯\(ツ)/¯
Its a lovely day for a Clojure coding dojo https://www.meetup.com/London-Clojurians/events/kfpxnpyxmbnb/
Admins can delete all public files (and we often delete files older than six months -- since no one can see those anyway) -- but we can't delete privately shared files, which is actually most of them here. From time to time, we all everyone to delete their own old files but a lot of people have over time become inactive so we can't reach them. It is frustrating.
Finding your files in Slack
Only with a script that uses the API...
Anyone out there got a few moments to spare to look at a Kubernetes Service definition that just does not seem to be working despite being exactly as per the tutorials and examples that I can find..?
I've got my Pod up and running from my Docker container, but now I can't expose it...
i don't know k8s @maleghast, but from my dc/os experience... first thing to check - is your app accessible on its private port on your pods ip address ? (assuming there is a public / load-balanced port which gets routed to the private port/ip of the pod(s))
if the private port is automatically allocated (it usually is on dc/os) then you'll have to use one of the k8s tools to look it up
presumably something in the k8s console or cli will tell you?
or maybe the pod has its own vip ?
Well, the K8s Dashboard is pretty good, and I can see that the Pod is "right", if you see what I mean? I can see that the Container has started up correctly, and everything.
So the K8s "way" would then be to define a "service" that exposes the pod via an AWS ELB
And my service config is basically line for line like the docs, but with my pod info swapped in, and yet it doesn't start up... 😞
(guessing here, but) the service probably creates a load-balanced port which then distributes to the pod-private ports ?
while the ELB just fronts the service port ?
possibly, the docs seem to insist that creating a Service of type "LoadBalancer" will set up an ELB that routes traffic directly to the app that is running in the Pod
is this EKS you are looking at ?
I could not get EKS in eu-west-1, so I used Kops to build a K8s cluster in that region.
This means that I have been able to give my cluster nodes access to my RDS database
and I have visible logs that it's started up and connected to the DB, so I am pleased with that part of the experience 🙂
is the LoadBalancer definitely talking about an ELB ? (that seems quite a high level of AWS integration)
https://aws.amazon.com/blogs/opensource/network-load-balancer-support-in-kubernetes-1-9/
hmm - i suspect that doesn't create an AWS ELB, but instead creates an nginx-based load-balancer service on k8s
(but i may be wrong)
Well, either way, as far as I can tell I am following the instructions and creating a service in the way as described I should get back an IP / DNS name that is public and that's what's not happening... 😞
(I mean I don't care if it's a real__ ELB I just care that I get a route in to the Container / App)
sure - so k8s console isn't showing a load-balancer service then ?
ah, my mistake - it looks like the spec/selector in that app-config will probably need to be adjusted to your app... did you do that ?
Yep, this is my service def:
apiVersion: v1
kind: Service
metadata:
name: foundation
namespace: default
annotations: {}
labels:
app: foundation-beta
env: pre-prod
spec:
ports:
- name: http
port: 80
protocol: TCP
targetPort: 3080
selector:
app: foundation-beta
type: LoadBalancer
I don't get any errors, and a Service does get created, but the ELB / Ingress side of it does not work.
I don't know if it's in any way significant, but the service that does get created doesn't have the targetPort set correctly either.
you've gone beyond my generic knowledge now @maleghast - specific k8s knowledge seems required to help