config

The entry is not removed if you remove manually using the `about:config` way.

Many changes were done before the next F-35 to roll out, resulting in the current overall config.

Deploying new microservices is as simple as managing the HAProxy config file via Chef or Puppet.

Most other vendors don't even give this oppertunity when installing, but can only be done later via some deep-down config change.

Knowledge about Xorg config files is admittedly not very useful, but it's been years since I've touched one.

It just means that instead of deploying Baker Street as part of your microservice push, you're deploying a) your microservice b) your dual HAProxy setup and/or new HAProxy config and c) DNS.

I loved the idea of Airbnb's Synapse, but it's tricky to configure (you basically have to write an haproxy config from scratch plus learn how synapse config sections map to the haproxy config).

You can try out my config if you like: [1].

Perhaps if I A) needed enormous configurability or B) knew Haskell well I would have stuck around, but i3's config is much simpler to manage.

I got tired of complex ZMQ routing and endless config files.

Gnome basically decided that text-basd configuration was too sane and opted for a mix of config files and the Windows Registry (gconf, dconf) which is a hilariously poor design choice.

Plain old apache but tuned very well on a massive server (32 cores, 96G of RAM), the server is actually the production server for a high traffic website and this is just piggy-backed onto the site as a 'servername' entry in the apache config.