DevOps/SRE Fulltime Dortmund, Germany
About Us Hey! We’re a nice little team devoted to consult and support our mostly e-commerce-focused developer teams with DevOps-related hot stuff like automation, containerization, orchestration and cloud technologies. About The Opportunity We’re searching for a new team member, that has either an ops background and dev interest or vice versa. It’s a permanent, full
tflookup – Developer diary Epilogue
Dear diary, it’s been some days since I wrote to you about my experience with creating a Terraform documentation lookup app and while I’m using tflookup on a daily, I noticed something. When I start my work in the morning and have the first interest in looking up some provider resource of Terraform, I naturally
tflookup – Developer Diary Part 5
Dear Diary! MY LOOKUP APP WORKS! Yayy! Locally at least. But what good is a web app, if you can only enjoy it yourself? So I needed a way to deploy my app automatically (and for free). Luckily, Heroku is around. Heroku is a simple app hosting provider, which hosts very simple apps for free.
tflookup – Developer Diary Part 4
Dear Diary! So I finished my REST service which will deliver my search results. But what good is that without an appealing frontend. After I was nearly blown away by the overwhelming good critics about Vue.js at last year’s enterjs I took the Vue-way immediately. I think, Vue is very easy compared to other frameworks
tflookup – Developer Diary Part 3
Dear Diary! Now that I have a documentation index, I could write a server, that serves that index and searches it. That server will ultimately also deliver my frontend application, because I’m too lazy to do it the microservices way right now. The most easy and stable web server for Node I know today is
tflookup – Developer Diary Part 2
Dear Diary! Hmmm… A lookup app. How could that work? I need a frontend obviously. And a backend, that does the heavy work. Frontend and backend should communicate through REST. What else? The backend should index the Terraform documentation Everything should be well tested of course First things first. The absolute basis for the whole
tflookup – Developer Diary Part 1
Dear Diary! As a DevOps engineer (or SRE as the cool people call it) I’m working closely together with Terraform which is one more great open source based application from Hashicorp and allows to define an infrastructure in text files (read: „Infrastructure as code“) Terraform has a great and extensive documentation, especially for the things
What are your non-tech hobbies
Following the great post „Yes, You should have hobbies outside of code by Ashlee Boyer, I’d like to know what your hobbies outside the tech bubble really are. I go first: I’m a hobby musician and actor in an amateur open air theatre (german speaking folks can check out our website) and that’s a great
Data Sources DOWN!
Do you know that situation where you roam through the Terraform providers documentation, use your trusted browser’s search function to search for a resource documentation, clicked the first search match and bummer! you landed on the documentation for the data source with the same name? Well, I was. Multiple times. And I always search for
Better Ansible Playbook Output in Teamcity
We’re using some good amount of Ansible playbooks in my company and we use TeamCity as our main CI service. On TeamCity, our playbook output looks like this: 🤨🙁😞 I don’t know about you, but I quite dislike the Ansible playbook default output. It’s quite packed and big and it’s hard to check where Ansible