Alpine production deploy
The production environment is the final destination of all development results, almost always when someone does some kind of development no matter how small it is (for example a simple script) the development environment is the place or final system where it will always be used (for example the script will be used in the other computers of the family, but it was made in the personal computer).
The development environment is never the same as the production environment, commonly, production environment only has just necesary software to run the installed and deployment products. In professional linux, there's no graphical toos and everything are made minimalist.. just like Alpine linux does all.
Servers and Dockers
The most famous cases in old days was use a Centos environment, but with time, linux becomes more heavy and more slowly, that changes with Alpine and Dockers, if you think Redhat and Centos are the best here an article that describes in short the real life of those systems: https://venenux.github.io/venenux/others-infodocs-details-centos-vs-fedora-en.html , Both projects are Red Hat related, one are ahead of and the other behind of, main diferencie from others distributions it’s their lack of packages and setups, due the shared market focused target of both.. obviously due the RedHAt relationship.
But today all of this are changed, now there's Docker: a helpful tool for packing, shipping, and running applications within "containers" (like virtual machines) that remove the need for physical hardware, allowing for more efficient use of computing resources, in terms of energy consumption and cost effectiveness. Today even the big dogs like Google, VMware and Amazon are building services to support it.
The server are mostly a very powerful machine in production environments, but think about it! a 500GB disk to only run a DNS for a local network? that's the reason of the Dockers and their relationship with the servers.
The one big difference between containers and a hole Server is that containers *share* the host server system’s kernel with other containers, and of course same server resources in a isolated environment.
Server focused documents
Web deploy: LAMP
In production web, LAMP means Linux + Apache + Mysql + Php installed and integrated, but today the "A" of apache are more used as Nginx or Lighttpd, and the "M" of MySQL are more used as Mariadb, the LAMP focused documents are:
- LAMP deploy of the Web Server: Production Web server: Lighttpd
- LAMP deploy of the Web Server with PHP, user html_dir and MariaDB: Production LAMP system: Lighttpd + PHP + MySQL
- LAMP special cases for PHP5 only softwares, user html_dir and MariaDB: Production LAMP system: Lighttpd + PHP5 + MySQL
- Deploy usage of Lets Encrypt without chain-tools – just add water: Production Lets Encrypt: dehydrated
Web deploy: LUA
- SQlite, most easy to use database system without engine: Debelovers : sqlite
- UnixODBC, how to connect with multiple databases: Production DataBases : unixodbc
- MySQL/MariaDB deployment: Production DataBases : mysql
- Dual stack (ipv4 to ipv6) DNS with chain slave, just only for brave linux sysadmin: : Production DNS: dual stack Bind server
- Cacti: traffic analysis and monitoring network