But a nice idea :)
120 karma · joined September 16, 2015
But a nice idea :)
But this might be a good start: https://www.conventionalcommits.org/en/v1.0.0/#summary
We've used this as a starting point and adapted it to our needs (E.g. some simplification, defining the possible values for scope, etc.)
> We encountered an error when trying to load your application and your page could not be served. Check the logs for your application in the App Platform dashboard.
Multiple DCs in FFM, heterogeneous environment with custom developed applications mostly on Ubuntu. Also a Kubernetes environment for newer applications. SaltStack for configuration management, close collaboration with round about five main development teams.
Apply here: https://ctseventim.softgarden.io/job/2500811/Systemadministr...
Like staticassertion already mentioned, it depends on the real project and problem to solve.
I've pitched a startup which started directly with an microservice like architecture. It was the best possible approach for the given problem.
So if I need to check the production nameserver it's ns-pdap-01.internal.tld and so on.
[0] https://www.racktables.org/ [1] https://github.com/digitalocean/netbox
From 3: It has been reported that 90,000 - 230,000 people were killed as a result of the dam breaking.
I don't see your point
In most discussions the time is ignored. Nuclear power plants already produced waste for many generations which is irresponsible.
Yes sometimes it's pain to solve some TLS based errors and I also miss the opportunity to debug each transmitted packet with tcpdump but I also appreciate it that the continuous focus on TLS improves the tooling and libraries and each day it get's a little bit easier to setup a secure encrypted connection.
Only very few pages are on my whitelist. E.g. Stack Overflow because they have good ads which are well-chosen.