Took me a week to realize that "!rant" just means "not rant".

I thought it was some sort of post front-matter that was no longer supported by the app (like a Duck Duck Go "bang").

😅

Fuck. YAML.
Who the fuck thought this was a good idea?

For real! Forgive me if this was already posted.

SICK AND TIRED OF READABILITY VS. EFFICIENCY!!!!!!!

I HAD TO SEPARATE A 4 LOC JSON STRING, WHICH HAD AN ARRAY OF A SINGLE KEY-VALUE PAIRS (TOTAL OF 10 OBJECTS IN THE ARRAY).

ITS READABLE IF YOU KNOW JSON. HOW HARD IS TO READ JSON FORMAT IF YOU GET YOUR STYLE AND INDENTATION PROPERLY?!?

SO I HAD TO
BREAK THE POOR FREAKING JSON APART TO A FUCKING DIFFERENT YAML FILE FORMAT ONLY SO I CAN CALL IT FROM THERE TO THE MAIN CONTROLLER, ITERATE AND MANIPULATE ALL THE ID AND VALUES FROM YAML BACK TO MATCH THE EXPECTED JSON RESPONSE IN THE FRONT END.

THE WHOLE PROCESS TOOK ME ABOUT 15 MINUTES BUT STILL, THE FUCKING PRINCIPLE DRIVES ME INSANE.

WHY THE FUCK SHOULD I WASTE TIME AT AN ALREADY WORKING PIECE OF CODE, TO MAKE IT LESS EFFICIENT AND A SLIGHTLY BIT MORE READABLE?!? FML.

I fucking hate YAML!!! Whoever thought a fucking whitespace delimited file was a good idea should......

</rant>
Ahh that's better; back to learning Ansible.

I dunno why, but my brain is just not weird to like syntactic whitespace.

Things like yaml, python and coffeescript...as much as I like Python...i just can't stand being forced to deal with whitespace.

Can we please stop using a file structure (YAML, JSON, XML etc) and just changing the file extension and calling it a new file type?

Stop trying to make your software/framework sound more complicated by saying this shit, if you use something, own it and don't try to mask it...

And mini rant over...

XML is meant for computers to read, not humans.

It's 2016. Please use yaml instead!

Server configuration file formats...

some use custom text file
some use ini files,
some use xml..
some use json..
some use yaml..
some use toml..

How many file formats I need to learn!!!

Took a devops position for a friend who needed help managing a small datacenter.

Five months of writing nothing but yaml for ansible. I'm about to go mad...

Today I woke up with 2 things in my personal todo list

1. As coder, I need to figure out why my yaml parser doesn't work

2. As Lv 60 wizard, I need to clear morroc 245. Wtf with that once punch kill charge attack....

when CodeClimate reports it 2.0 GPA but your colleagues says it's good code-wise and styling wise...

turns out I didn't have the YAML override

Trying to automate gitlab deployment with Ansible. It runs but freaking keeps failing on task. Reconfigure the gitlab server. Without helpful output!

After 2 days bashing and commenting line after line the answer reveals.

True != true Fuuucc...

YAML files are one of the worst type I have ever seen until now. Fuck that shit. And fuck that indentation.

Hi Everybody,
Here by I introduce you the new Java Script framework and package manager that is going to change your life forever. We have considered all the problems developers are facing during their everyday career. We use latest techniques used in configuration files (xml, yaml, json, etc.), package managers (npm, gulp, yawn, etc) and other frameworks (require-js, vuejs, reactjs, etc) into consideration to bring you a framework that has them all together in ONE BIG PACKAGE! HAHAHAHAAHAAA!
Nope. I'm just kidding :-D

FUCK YOU AMAZON! Stop telling me my configuration yaml file contains a tab... THE FUCKING FILE DOES NOT EVEN EXIST!

Psst. Hey. Eclipse. You too, Gradlew. Cmere. I have a secret to whisper in your ear:

FUCK. YOU.

- today, sick as fuck, working on my project, la de da
- hey, I need some fake data for my project. Hmm I really like faker for Python
- oh nice, on GitHub there's a port of faker for Java
- cloned.. alright where's the JAR file ..
- oh, maybe I need to add the folder to my project.. hmm
- ok, added the git repo to my project..
- in editor, typing: import other package.class
- dafuq? Package doesn't exist?
- can't figure how to fucking make a Jar file out of eclipse
- ok. COMMAND LINE TIME. Fuck you eclipse! Going commando!!!!
- oh, there's an executable here called gradlew...
- dafuq is Gradlew... (Google, read docs)
- (10 min later)feeling very proud of myself now
- gradlew jar
- good, fucking finally, a JAR file
- import statement works, coding some more, run tests, fuck yeah.
- test failure: Java.lang.NoClassDefFoundError:org/yaml/snakeyaml/Yaml

FUUUUUUUUuuuuu 🤒🤒😡😡😭😭🔥🔥🔥

Python and Django have made it so fucking easy to get shit done, I have been spoiled rotten..

Fuck you *insert package name here* I am just going to have my tests shit random character sequences. That's all a name is anyway. Fuck...

*PS: eclipse is damn handy for -writing- java, that I admit*

I'm such a fucking idiot

I'm setting up an api and to prevent unwanted fields or circular dependencies from showing up I define what fields should appear in a few serialization yaml files.

These files define what fields should appear in a given context. The default context for every field is to always show the id, and only a call to /posts will give you all the fields of the posts for example. This means that if you retrieve a comment with a linked post, the post will only show up as an id, but the comment will have all its fields.

I've been struggling with a stupid problem for 2 hours, I could verify that the yaml files were loaded in, all entities had such a file and the configuration was exactly according to the docs.

Guess why my api calls still caused circular errors?

Because I forgot to do the $view->setContext$this->defaultContext); call that determines what context should be used for the response.

FUCK ME WHY DID IT TAKE SO FUCKING LONG TO FIGURE THAT OUT OMG

Google you say? Ofcourse I hunted google results! But I was unknowingly part of an XY problem and was looking for what the problem wasn't >:(

At least it works now, ugh

YAML: "The error appears to have been in [file] : line 47, column 7, but may be elsewhere in the file depending on the exact syntax problem." Shoot me.

When starting projects, following semver.org quickly gets out of hand. Nothing is "backwards-compatible"

0.0.0 gitignore
0.1.0 prints arguments
1.0.0 prints text of web requests
2.0.0 prints parsed web requests
3.0.0 prints filtered requests
4.0.0 prints using yaml
5.0.0 logs to file
5.0.1 catch error
5.1.0 interactive

Ok, guys, which configuration format is your favorite? (something like toml, ini, json, yaml, etc)

Who knew YAML forbids the use of TABS? Good for them.

Spent a little more than an a hour trying to figure out why an octopus deployment tool isn't picking up my project definitions.
Called a colleague to help me, as I explain the situation to him I find out that I created *.yaml files instead of *.yml
Wtf brain! Y u do this brain?

Grails 2.x all groovy syntax for code and configuration. Simple and elegant.

Grails 3.x all groovy syntax except for the main configuration file. Let's make that a YAML file. F#%king genius!

who doesn't love a bit of this?

I suspect the creator of YAML to also run a private psychiatric hospital. I mean; meaningful spaces... Who comes up with that!?

Today i chartered new realms for me.

I created a new hyper-v vm on the company windows servers and added a 5th instance to it, but instead of running another windows server i installed an ubuntu 18.04 (cause i am a bit familiar with debian from my raspberry pi)

we have two servers, one which runs the 4 vms and a replica. I first had the new vm on the main server but it occured me to move it instead to the unusued replica machine. That kinda worked..i did a planned failover but the main server isnt configured to be the replica..and even when activating that it didnt work. This is weird.

For the moment i ignored that and proceeded to install nginx, mariadb and php 7.2..basically the lemp stack. I managed to setup nginx and a static ip adress for the machine (which was different from how i remembered it to do (in 18.04 its not done with the network conf but a yaml file).

in the end i added two different virtual servers, one for actual use and one for dev stuff (with phpmyadmin running for instance), listening on port 80 and some random other port.

as a test i brought a mediawiki onto the Port 80 server and it worked.

on monday i have to figure out how to implement the wildcard certificate i have for our company domain (internal dns simply routes intranet.company.com to the local server vm)

i am mighty proud cause all my experience with linux was with a raspberry pi so far and i am fairly certain i did it right and without shortcuts this time. (unlike my raspberry experience)

just wanted to share

(i also sweated a lot of blood when editing the hyper v settings as i did not set up the server in the first place)

((i also installed xrdp and a mate desktop, but i am less proud of that, but sometimes seeing folders graphically helps me))

Fuck yaml.

I'm creating a little "cloud" app, for training and learning about how network communications work. I try to do it with SOLID principles in mind, but it's faster said than done, as I don't have a lot of experience.
Anyway, I want to write the server config in a file which would be read at launch, but I'm wondering how you'd do it while respecting SOLID as much as possible.
Do you see any interesting design pattern I could dive into to implement this part while still being able to change or add things efficiently ?
Or any open source project where I could read the code and inspire myself for my project ?

For example, things I might want to implement later (and reasons to make the code flexible) :
- At first the config file is read only (edited manually) but later you'd be able to update it from within the app
- Later in development, you could maybe use overwriting flags when launching the server from command line
- Currently, if a field in the config file is invalid or absent, an error is displayed and the program closes. I intend to use default values instead, or to ask the user to manually enter the parameters before continuing execution
- I'd like to be able to switch the file format without changing much code (currently in JSON, because parsing libraries are easy to use, but it could switch to YAML or XML or whatever)
- Maybe even switch to a config stored in database instead of a simple file ?
- To be portable, the config path depends on the OS (AppData for Windows, $HOME/.config/ for Linux, $HOME/Library/Preferences for OSX...) but could be also given from the command line

It's a training personal project and a challenge, not something which is intended to be released publicly (in its current state), so I don't really care about YAGNI or "using a database is a dumb idea", I'm just trying to force myself to apply SOLID principles in front or real potential problems (not tuto code).

Also note that I'm asking for advice, not that you do all the work for me, of course. If you have a design pattern or two that come in mind, or an open-source project which already reads config from a file from which I could inspire myself, just cite a name, I'll do the research myself (I'm already, actually, but some guidance would be helpful).

A very long rant.. but I'm looking to share some experiences, maybe a different perspective.. huge changes at the company.

So my company is starting our microservices journey (we have a 359 retail websites at this moment)

First question was: What to build first?

The first thing we had to do was to decide what we wanted to build as our first microservice. We went looking for a microservice that can be used read only, consumers could easily implement without overhauling production software and is isolated from other processes.

We’ve ended up with building a catalog service as our first microservice. That catalog service provides consumers of the microservice information of our catalog and its most essential information about items in the catalog.

By starting with building the catalog service the team could focus on building the microservice without any time pressure. The initial functionalities of the catalog service were being created to replace existing functionality which were working fine.

Because we choose such an isolated functionality we were able to introduce the new catalog service into production step by step. Instead of replacing the search functionality of the webshops using a big-bang approach, we choose A/B split testing to measure our changes and gradually increase the load of the microservice.

Next step: Choosing a datastore

The search engine that was in production when we started this project was making user of Solr. Due to the use of Lucene it was performing very well as a search engine, but from engineering perspective it lacked some functionalities. It came short if you wanted to run it in a cluster environment, configuring it was hard and not user friendly and last but not least, development of Solr seemed to be grinded to a halt.

Elasticsearch started entering the scene as a competitor for Solr and brought interesting features. Still using Lucene, which we were happy with, it was build with clustering in mind and being provided out of the box. Managing Elasticsearch was easy since there are REST APIs for configuration and as a fallback there are YAML configurations available.

We decided to use Elasticsearch since it provides us the strengths and capabilities of Lucene with the added joy of easy configuration, clustering and a lively community driving the project.

Even bigger challenge? Which programming language will we use

The team responsible for developing this first microservice consists out of a group web developers. So when looking for a programming language for the microservice, we went searching for a language close to their hearts and expertise. At that time a typical web developer at least had knowledge of PHP and Javascript.

What we’ve noticed during researching various languages is that almost all actions done by the catalog service will boil down to the following paradigm:

- Execute a HTTP call to fetch some JSON

- Transform JSON to a desired output

- Respond with the transformed JSON

Actions that easily can be done in a parallel and asynchronous manner and mainly consists out of transforming JSON from the source to a desired output. The programming language used for the catalog service should hold strong qualifications for those kind of actions.

Another thing to notice is that some functionalities that will be built using the catalog service will result into a high level of concurrent requests. For example the type-ahead functionality will trigger several requests to the catalog service per usage of a user.

To us, PHP and .NET at that time weren’t sufficient enough to us for building the catalog service based on the requirements we’ve set. Eventually we’ve decided to use Node.js which is better suited for the things we are looking for as described earlier. Node.js provides a non-blocking I/O model and being event driven helps us developing a high performance microservice.

The leap to start programming Node.js is relatively small since it basically is Javascript. A language that is familiar for the developers around that time. While Node.js is displaying some new concepts it is relatively easy for a developer to start using it.

The beauty of microservices and the isolation it provides, is that you can choose the best tool for that particular microservice. Not all microservices will be developed using Node.js and Elasticsearch. All kinds of combinations might arise and this is what makes the microservices architecture so flexible.

Even when Node.js or Elasticsearch turns out to be a bad choice for the catalog service it is relatively easy to switch that choice for magic ‘X’ or component ‘Z’. By focussing on creating a solid API the components that are driving that API don’t matter that much. It should do what you ask of it and when it is lacking you just replace it.

Many more headaches to come later this year ;)

3 year old issue that can be solved with less than 10 lines of yaml that are 90% copy & paste... The official statement why it's not done yet: We are out of time and we have problems with higher priority.

Thank you for nothing. Providing RPM and deb builds without repository and without being signed.

If you don't want to do it, just close the issue with "won't fix" and don't keep people waiting. I mean your entire team is out of time for 3 years?!? Nice but you can review and close all community attempts to solve it with references to the issue after 3 days of discussion.

This is totally broken!

together, we can make YAML great again!

Hey Java Devs, Snakeyaml is trolling us all. For their parser you must use spaces for indentation.

We say TAB, they say TOO BAD. #ForcedConvention

This is an actual transcript...
Since it's way too long for the normal 5000 characters, hence splitting it up...

Infra Guy: mr Dev, could you please give some rational for update of jjb?
Dev: sparse checkout support is missing
Infra Guy: is this support mandatory to achive whatever you trying to do?
Dev: yes
Infra Guy: u trying to get set of specific folder for set of specific components?
Dev: yes
Infra Guy: bash script with cp or mv will not work for you?
Dev: no
Infra Guy: ?
Dev: when you have already present functionality why reinvent the wheel
Dev: jenkins has support for it
Dev: the jjb is the bottle neck
Infra Guy: getting this functionality onto our infra would have some implications
Dev: why should I write bash script if jenkins allows me to do that
Dev: what implications ??
Infra Guy: will you commit to solve all the issues caused by new jjb?
Dev: you show me the implications first
Infra Guy: like a year ago i have tried to get new jjb <commit_url>
Infra Guy: no, the implications is a grey area
Infra Guy: i cant show all of them and they may hit like in week or eve month
Dev: then why was it not tackled
Dev: and why was it kept like that
Infra Guy: few jobs got broken on something
Dev: it will crop up some time later
Dev: if jobs get broken because of syntax
Dev: then jobs can be fixed
Dev: is it not ???
Infra Guy: ofc
Infra Guy: its just a question who will fix them
Dev: follow the syntax and follow the guidelines
Dev: put up a test server and try and lets see
Dev: you have a dev server
Dev: why not try on that one and see what all jobs fails
Dev: and why they fail
Dev: rather than saying it will fail and who will fix
Dev: let them fail and then lets find why
Dev: I manually define a job
Dev: I get it done
Infra Guy: i dont think we have test server which have the same workload and same attention as our prod
Dev: unless you test how would you know ??
Dev: and just saying that it broke one with a version hence I wont do it
Infra Guy: and im not sure if thats fair for us to deal with implication of upgrading of the major components just cause bash script is not good enough for u
Dev: its pretty bad
Infra Guy: i do agree
Infra TL Guy: Dev, what Infra Guy is saying is that its not possible to upgrade without downtime
Infra Guy: no
Dev: how long a downtime are we looking at ??
Infra Guy: im saying that after this upgrade we will have deal with consequences for long time
Infra Guy-2: No this is not testing the upgrade is the huge effort as we dont have dev resources to handle each job to run
Dev: if your jjb compiles all the yaml without error
Dev: I am not sure what consequences are we talking of
Infra Guy: so you think there will be no consequences, right?
Dev: unless you take the plunge will you know ??
Dev: you have a dev server running at port 9000
Infra Guy: this servers runs nothing
Dev: that is good
Dev: there you can take the risk
Infra Guy: and the fack we have managed to put something onto api doesnt mean it works
Dev: what API ?
Infra Guy: jenkins api
Infra Guy: hmmm
Dev: what have you put on Jenkins API ??
Infra Guy: (
Dev: jjb is a CLI
Infra Guy: ((
Dev: is what I understand
Dev: not a Jenkins API
Infra Guy: (((
Dev: (((((
Infra Guy: jjb build xmls and push them onto api
Infra Guy: and its doent matter
Dev: so you mean to say upgrading a CLI is goig to upgrade your core jenkisn API
Dev: give me a break
Infra Guy: the matter is that even if have managed to build something and put it onto api
Infra Guy: doesnt mean it will work
Dev: the API consumes the xml file and creates a job
Infra Guy: right
Dev: if it confirms to the options which it understands
Dev: then everything will work
Dev: I am actually not getting your point Infra Guy
Infra Guy: i do agree mr Dev
Dev: we are beating around the bush
Infra Guy: just want to be sure that if this upgrade will break something
Infra Guy: we will have a person who will fix it
Dev: that is what CICD is supposed to let me know with valid reasons
Dev: why can't that upgrade be done
Infra Guy: it can be done
Infra Guy: i even have commit in place

Using CodeWriter (the one from windows store) since a few days for small tasks (like editing an xml or yaml etc) and i like it.
Yep vim guys, u hate me now, but idc ^^

So this is more like an accident rather than a dissapointment but the thing goes like this.
I make multivariant stacks with vagrant, shell script loaded as stated in yaml config and every bit and piece done from there the only times it disapointed me was the first time i lost it and when i got asked to make it tomcat compatible, not that the person really needed tomcat but just because i called it a stack initialiser it must have tomcat support.

I come from a simple html, css background with a bit knowledge in php and some simple cms.
Decided to use a modern cms to learn something new...

Salt is awesome, no questions about that. YAML is giving me headaches, but it's my fault and eventually I'll get used to it. But this being my first encounter with jinja, WHO THE HELL THOUGHT THIS PIECE OF CRAP DESERVES TO LIVE! Instead of writing python inside {% %} you have to write kinda pseudo python and I just spend over hour trying to build list inside for. Yes, great idea, scoping fors, and lets make it hard to escape scoping, beacause it would be a shame if somebody COULD ACTUALLY DO SOMETHING USEFULL. I though several times of using different renderer, but I want to keep my code readable and mainrainable and in the end I found a workaround, but still, Jinja, YOU SUCK!

Ok... I am defeated I don't know what else to try...

Do you guys have any experience with ansible vault? I have my SSH password stored on a vault. It's referenced in my host file like this:
-----START SNIPPET-----
[LCL:vars]
ansible_ssh_pass='{default_pass}'

[LCL]
myhost ansible_user=my username
-----END SNIPPET-----

default_pass is stored as a yaml variable in passed.yml that I supply using --extra-vars '@passwd.yml'

When I enter my vault password I get an exception 'non hexadecimal digit found'.

The password is right for the vault, the vault file is in PWD .... I cannot find anything helpful.

Any ideas?

I've been thinking about ways to improve my workflow for my personal projects.

I'm getting to grips with continuous integration and deployment etc, but I want to also automate, or at least semi automate my changeling generation.

I don't like using any sort of gitlog shenanigans, and I quite like the girls way of doing it.

I.e you run a script which generates a yaml file with your changeling info in, and then all the files are written into the changelog.md file.

How do you guys handle the generation of your changelings?

PowerShell - Why do you need separate modules for reading and writing YAML? Spent half a day trying to merge to GitHub projects to support ConvertFrom-YAML and ConvertTo-YAML

My colleague is trying out docker for the first time. He is installing stuff so that he can add the same steps to gitlab yaml. I will like to see his reaction when he will start the container next time.

Waiting now and hoping that he will save the container.

YAML - The skill is in the indentation don't you know?

Anyone herr tried API Platform?

I know I know. Generic ass name but that is what the framework is called.

Its in php, it contains a lot of goodies from(try and guess...no?? Ok I'll tell ya) the Symfony platform(go figure right) so if you are familiar with Laravel or well....Symfony then I guess that you will be good to go. I ain't...so fuck me because I only know Laravel.

Either way the concepts are very simple. Configs is donde almost entirely with YAML, i dunno how to feel about that, not used at writing routes on yaml, but the framework is thus far quite powerful. About to test jwt auth so wish me luck!

WHAT IS EVERYONE'S FAVOURITE DATA INTERCHANGE FORMAT?

(CLUE: RHYMES WITH CAMEL)

I tell you what YAML is good for....
RAML, suck on that bitch!

Was generating a JSON based config manually to be used by a script another dev wrote - only to be criticized for using the text editors built in formatter. Evidently lining up the colon separating key value pairs is a thing.

If readability was so important to you why the fuck did you decide on using JSON as a configuration format? Especially when you could have gone with YAML or better yet INI (flat key/value pairs) style config.