Alpine production deployment - Revision history

Greenman: /* DataBases */ copyedit

2025-03-11T23:48:16Z

DataBases: copyedit

← Older revision		Revision as of 23:48, 11 March 2025
Line 31:		Line 31:
	WIP		WIP

	== ~~DataBases~~ ==		== Databases ==

	* SQlite, most easy to use database system without engine: [[Debelovers : sqlite]]		* SQlite, most easy to use database system without engine: [[Debelovers : sqlite]]

Greenman: /* DataBases */ link

2025-03-11T23:48:07Z

DataBases: link

← Older revision		Revision as of 23:48, 11 March 2025
Line 35:		Line 35:
	* SQlite, most easy to use database system without engine: [[Debelovers : sqlite]]		* SQlite, most easy to use database system without engine: [[Debelovers : sqlite]]
	* UnixODBC, how to connect with multiple databases: [[Production DataBases : unixodbc]]		* UnixODBC, how to connect with multiple databases: [[Production DataBases : unixodbc]]
	* MySQL/MariaDB deployment: [[MySQL]]		* MySQL/MariaDB deployment: [[MariaDB]]/[[MySQL]]

	== Networking ==		== Networking ==

Greenman: /* Web deploy: LAMP */links

2025-03-11T23:47:41Z

Web deploy: LAMP: links

← Older revision		Revision as of 23:47, 11 March 2025
Line 21:		Line 21:
	=== Web deploy: LAMP ===		=== Web deploy: LAMP ===

	In production web, LAMP means '''L'''inux + '''A'''pache + '''M'''ysql + '''P'''hp installed and integrated, but today the "A" of apache is more used as Nginx or Lighttpd, and the "M" of MySQL is more used as ~~Mariadb~~. The LAMP focused documents are:		In production web, LAMP means '''L'''inux + '''A'''pache + '''M'''ysql + '''P'''hp installed and integrated, but today the "A" of apache is more used as Nginx or Lighttpd, and the "M" of MySQL is 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: [[Production Web server: Lighttpd]]
	* LAMP deploy of the Web Server with PHP, user html_dir and MariaDB: [[MySQL]]		* LAMP deploy of the Web Server with PHP, user html_dir and [[MariaDB]]: [[MySQL]]
	* Deploy usage of Lets Encrypt without chain-tools – just add water: [[Production Lets Encrypt: dehydrated]]		* Deploy usage of Lets Encrypt without chain-tools – just add water: [[Production Lets Encrypt: dehydrated]]

Zcrayfish: Fixed double redirect.

2023-08-28T04:33:10Z

Fixed double redirect.

← Older revision		Revision as of 04:33, 28 August 2023
Line 35:		Line 35:
	* SQlite, most easy to use database system without engine: [[Debelovers : sqlite]]		* SQlite, most easy to use database system without engine: [[Debelovers : sqlite]]
	* UnixODBC, how to connect with multiple databases: [[Production DataBases : unixodbc]]		* UnixODBC, how to connect with multiple databases: [[Production DataBases : unixodbc]]
	* MySQL/MariaDB deployment: [[~~Production DataBases : mysql~~]]		* MySQL/MariaDB deployment: [[MySQL]]

	== Networking ==		== Networking ==

Zcrayfish: /* Web deploy: LAMP */ Fixed double redirect.

2023-08-28T04:32:29Z

Web deploy: LAMP: Fixed double redirect.

← Older revision		Revision as of 04:32, 28 August 2023
Line 24:		Line 24:

	* LAMP deploy of the Web Server: [[Production Web server: Lighttpd]]		* 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 deploy of the Web Server with PHP, user html_dir and MariaDB: [[MySQL]]
	* Deploy usage of Lets Encrypt without chain-tools – just add water: [[Production Lets Encrypt: dehydrated]]		* Deploy usage of Lets Encrypt without chain-tools – just add water: [[Production Lets Encrypt: dehydrated]]

Psykose: unlink deleted article

2023-03-01T14:15:48Z

unlink deleted article

← Older revision		Revision as of 14:15, 1 March 2023
Line 25:		Line 25:
	* LAMP deploy of the Web Server: [[Production Web server: Lighttpd]]		* 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 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]]		* Deploy usage of Lets Encrypt without chain-tools – just add water: [[Production Lets Encrypt: dehydrated]]

Arrogance: Tag for style improvement. Do some basic spelling / capitalization fixes, although basically the whole thing needs rewritten

2022-12-14T02:51:04Z

Tag for style improvement. Do some basic spelling / capitalization fixes, although basically the whole thing needs rewritten

← Older revision		Revision as of 02:51, 14 December 2022
Line 1:		Line 1:
			{{style\|This reads more like an essay than a useful tutorial or advice}}
	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 not the only place or system where it will be exclusively used (for example the script could be used on other computers in the network).		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 not the only place or system where it will be exclusively used (for example the script could be used on other computers in the network).

	The development environment is never the same as the production environment, commonly, production environment only has necessary software to run the installed and deployment products. In professional ~~linux~~ are no graphical ~~toos~~ and everything is minimalist.. just like Alpine ~~linux~~.		The development environment is never the same as the production environment, commonly, production environment only has necessary software to run the installed and deployment products. In professional Linux are no graphical tools and everything is minimalist.. just like Alpine Linux.

	= Servers and ~~Dockers~~ =		= Servers and Docker containers =

	The most famous cases in old days was use a ~~Centos~~ environment, but over time, ~~linux~~ became more heavy and more slow. 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://gitea.com/venenux/venenux/src/branch/master/docs/others-infodocs-details-centos-vs-fedora-en.md , Both projects are Red Hat related, one are ahead of and the other behind of, main difference from others distributions it’s their lack of packages and setups, due the shared market focused target of both.. obviously due the RedHAt relationship.		The most famous cases in old days was use a CentOS environment, but over time, Linux became more heavy and more slow. That changes with Alpine and Docker, if you think Red Hat and CentOS are the best here an article that describes in short the real life of those systems: https://gitea.com/venenux/venenux/src/branch/master/docs/others-infodocs-details-centos-vs-fedora-en.md , Both projects are Red Hat related, one are ahead of and the other behind of, main difference 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 changed, now there's Docker: a helpful tool for packaging, 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.		But today all of this changed, now there's Docker: a helpful tool for packaging, 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.

Arrogance: Arrogance moved page Alpine production deploy to Alpine production deployment

2022-12-14T02:35:20Z

Arrogance moved page Alpine production deploy to Alpine production deployment

← Older revision	Revision as of 02:35, 14 December 2022
(No difference)

Mckaygerhard: restore dead link from a mirror git

2022-01-06T17:51:25Z

restore dead link from a mirror git

← Older revision		Revision as of 17:51, 6 January 2022
Line 5:		Line 5:
	= Servers and Dockers =		= Servers and Dockers =

	The most famous cases in old days was use a Centos environment, but over time, linux became more heavy and more slow. 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{{dead link}}~~ , Both projects are Red Hat related, one are ahead of and the other behind of, main difference from others distributions it’s their lack of packages and setups, due the shared market focused target of both.. obviously due the RedHAt relationship.		The most famous cases in old days was use a Centos environment, but over time, linux became more heavy and more slow. 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://gitea.com/venenux/venenux/src/branch/master/docs/others-infodocs-details-centos-vs-fedora-en.md , Both projects are Red Hat related, one are ahead of and the other behind of, main difference 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 changed, now there's Docker: a helpful tool for packaging, 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.		But today all of this changed, now there's Docker: a helpful tool for packaging, 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.
Line 45:		Line 45:

	WIP		WIP

Mckaygerhard: /* See Also */ remove newbie references this content was started by me. but i let it as is cos it helps to the already poorly wiki

2022-01-06T17:48:27Z

See Also: remove newbie references this content was started by me. but i let it as is cos it helps to the already poorly wiki

← Older revision		Revision as of 17:48, 6 January 2022
Line 46:		Line 46:
	WIP		WIP

	~~= See Also =~~

	* [[Alpine newbie]]
	* [[Alpine newbie install manual]]
	* [[Alpine newbie desktops]]
	* [[Alpine newbie developer]]

	[[Category:Newbie]]		[[Category:Newbie]]