Ever tinkered with configuration files - made a mistake - and then needed the default version again?
# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default.conf
Listen 80
<IfModule ssl_module>
Listen 443
</IfModule>
<IfModule mod_gnutls.c>
Listen 443
</IfModule>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
For example using the keywords:
ports.conf Apache Ubuntu 14.04
Take look at the unaltered configuration file. Exactly the way it was shipped by the application vendor.
If needed you can download the raw config directly
wget -O ports.conf.example http://exampleconfig.com/static/raw/apache/ubuntu14.04/etc/apache2/ports.conf
# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default.conf
Listen 80
<IfModule ssl_module>
Listen 443
</IfModule>
<IfModule mod_gnutls.c>
Listen 443
</IfModule>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
Download the default configuration files of apps like NGINX, Apache, MySQL and many others.
ExampleConfig is free to use for personal and commercial purposes. We’re fully committed to building an archive you can rely on.
All configuration files are pulled from a fresh installation of the application. They remain unaltered in the state they where shipped.
Speed up your process developing Dockerfiles by fetching the right configuration file.
No point in trying to fix things, when clearly a fresh start makes more sense.
Tell me more