A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you’d prefer to keep out of more focused work-related channels.
Hey there! I’m looking for an opensource project I found some months before but i can’t remember how its called now. It is a simple web shortcuts dashboard with links bound to icons where you can add all your ops tools to be accessible with one click (prom, grafana, k8s dashboard, jaeger etc..)
wow, that’s bring memory, I built something like that using https://getbootstrap.com/docs/5.0/examples/starter-template/ only static content can be added, I added ip/url: port and create my ownlist - dockerize it with nginx
Yeah, we have 5/6 envs with specifics urls, I remember of a already-built project that takes data from config map. it would fit more our need. will continue to dig and report here if i found it
nice tool, thanks for sharing, I’m thinking of get all service from nginx/apache config and add them there automatically since I’m working with lot of reverse proxy services and projects
Thanks, that’s exactly it!!
Say I had a graphql api that some customers wished was a REST API. Is there any proxy / tooling I could use to just slap rest methods over my Graphql mutations/queries, or would I need to manage that manually?
And now we welcome the new year. Full of things that have never been. — Rainer Maria Rilke January 4th 2021 was the first working day of the year for many around the globe, and for most of us at Slack too (except of course for our on-callers and our customer experience team, who never …
Good summary here https://www.theregister.com/2021/02/02/slack_outage_aws_autoscaling/
‘We attempted to add 1,200 servers to our web tier’ – but with a saturated network it did no good
Curious if anyone’s used keycloak before? Any pros/cons/gotchas to look out for? I’ll of course spin up the docker container and play around with it, but I’d love any input from this group.
I tested it only for fun, but see good amount of hype configure it using Terraform,
needs a lot of effort to maintain and keep HA. If used in prod it becomes the crucial part of your entire org. If it sneezes sh*t hits the fan!
I am not saying its bad but it need more effort then your usual self-hosted soft
Have used it previously - single node within a Java stack for a small number of users (~50). It works well, but it’s a complicated beast.
My team has been using it for just over a year, supporting about 1000 employees (it is the auth broker for GitLab so we can centralize the SAML connection to corporate SSO).
It is powerful, configurable, sometimes very complicated, but overall a positive experience.
Since the user/group management is done elsewhere, we run our Keycloak stateless. Full Configuration as Code (CaC), no database (it has an internal H2 in-memory database). Since it is running in kubernetes, it auto-heals easily with minimal downtime. We haven’t spent the time to figure out how to do HA yet, but we haven’t seen the need to either (GitLab isn’t mission critical. If it goes down nobody is going to die, unlike some other stuff we do…).
You might want to take this warning into consideration
Red Hat surprised the open source world with its announcment that it is pulling the plug on CENTOS. But should anyone be surprised? At the end of the day, why does it make sense to offer a product that undermines your business model? On the one hand, you have a huge investment in Red Hat Enterprise Linux that generates a ton of revenue. On the other hand, you have an underfunded effort working on an
I’ll cross that bridge when I come to it. If it happens I think it is likely that the community will fork keycloak and provide a mostly-drop-in replacement.
That article is a shill for Gluu, since Janssen is maintained by Gluu people, just like Keycloak is (mostly) maintained by Red Hat people.
Yeah, fair enough
Thanks all! I appreciate it and I’m sure I’ll have more questions once I get into using it.
If you haven’t yet, check out the Sudo Show podcast! It is your place for all things Enterprise Open Source. We cover topics from Linux to Cloud to DevOps! Check out our latest episode hot off the press! https://sudo.show/18
Read a targeted set of docs consistently over a sustained period – say, a couple of years – and you will be able to perform magic.
Hey, where can I ask question about Gitlab CI
I currently have a Gitlab CI pipeline which consists of following stages:
- test <- checks if app works correctly, unit tests, linting etc (from node base image)
build <- creates a docker image and tags it I want to publish my docker image after it is built. Should I create another stage:
- publish <- sends a docker image to Amazon ECR
I think I should create a next stage to clearly separate functions. But that poses question, how to I transfer docker image from stage 2 to stage 3? Do i use “docker save” to create artifact and pass it, and “docker load” to load it, or should I push the image in the stage 2 to the Gitlab registry and pull it in the stage 3, so that i can push it again to ECR in the same stage?
Or just avoid creating another stage and publish it in the stage 2 directly to ECR, That seems simplest, but that is not just “build stage” right? It’s build and publish and that kind of seems like an anti-pattern.
I build and push in same stage usually but for the times I don’t I save and load image
Yeah, I also build and push at the same time.
Another thing you could do is push the image to the Gitlab container registry in the build stage and let the publish stage be:
• pull from gitlab
• Push to ECR That way you could push the same image to different repositories/environments without rebuilding. And decouple the build from publish.
IMO there’s no reason to have a discrete build stage. If you make each stage independent, then “test” will first build the image if it needs to. “Publish” will also build if it needs to (it might not, depending on how caching/execution is set up).
But in my example, test stage uses ‘node’ base image and performs linting and unit testing without involving docker. Is this something wrong or? As I understand docker image should have instructions on how to run the app, not how to run, test, etc.
But if I understand what you are saying is to have ‘test’ stage and then ‘publish’ stage that builds tags and publishes docker image.
The filter is not from Zoom itself but came pre-installed on Dell laptops.
oh lolcat. the attack of old software!
we showed the vid to a lawyer in our D&D group the other night and he straight rofled himself out of his chair (over zoom)
was he a cat?
#gadgets #hightech #agilesoftwaredevelopment ,… 263 comments on LinkedIn
I know there are 3,450 AWS experts in this channel so it may not be a wealth of previously-unknown information to anyone, but this YouTube channel on AWS tutorials is seriously well done and underrated… https://www.youtube.com/channel/UClCB_NDN1-cmbhIEPQcf83A
Really useful for learning about AWS Services when the docs just don’t cut it
I love visualizations and if you want to learn things the fun way, Join me cause all my videos are Visually Explained. Apart from the ones where I code or give a hands-on demo of course :) Learn Once. Never Forget Keep rocking !!
Hofstadter’s law is a self-referential adage, coined by Douglas Hofstadter in his book Gödel, Escher, Bach: An Eternal Golden Braid (1979) to describe the widely experienced difficulty of accurately estimating the time it will take to complete tasks of substantial complexity: Hofstadter’s Law: It always takes longer than you expect, even when you take into account Hofstadter’s Law. The law is often cited by programmers in discussions of techniques to improve productivity, such as The Mythical Man-Month or extreme programming.