Alpine Linux - User contributions [en]

Alpine production deployment

2021-02-16T12:12:39Z

Baldlizard: I think the "not" was missing because if not it would go against what the article is about. changed sentence for better readability

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.

= 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 , 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.

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 Server is that containers *share* the host server system’s kernel and server resources with other containers in a isolated environment.

== Server focused documents ==

TODO: webpack, npm (advanced.. cos is includen below in lamp), bigdata, Dockers focused well made tutorial

=== 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:

* 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 ===

WIP

== DataBases ==

* 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]]

== Networking ==

* 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]]

== Docker focused documents ==

WIP

= See Also =

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

[[Category:Newbie]]
[[Category:Server]]
[[Category:PHP]]
[[Category:Monitoring]]
[[Category:Development]]
[[Category:Security]]
[[Category:Production]]

Alpine production deployment

2021-02-16T12:06:52Z

Baldlizard:

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 on other computers in the family, but it was made on one personal computer).

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.

= 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 , 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.

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 Server is that containers *share* the host server system’s kernel and server resources with other containers in a isolated environment.

== Server focused documents ==

TODO: webpack, npm (advanced.. cos is includen below in lamp), bigdata, Dockers focused well made tutorial

=== 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:

* 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 ===

WIP

== DataBases ==

* 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]]

== Networking ==

* 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]]

== Docker focused documents ==

WIP

= See Also =

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

[[Category:Newbie]]
[[Category:Server]]
[[Category:PHP]]
[[Category:Monitoring]]
[[Category:Development]]
[[Category:Security]]
[[Category:Production]]

Alpine production deployment

2021-02-16T11:29:04Z

Baldlizard: /* Servers and Dockers */

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 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 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 ==

TODO: webpack, npm (advanced.. cos is includen below in lamp), bigdata, Dockers focused well made tutorial

=== 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 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 ===

WIP

== DataBases ==

* 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]]

== Networking ==

* 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]]

== Docker focused documents ==

WIP

= See Also =

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

[[Category:Newbie]]
[[Category:Server]]
[[Category:PHP]]
[[Category:Monitoring]]
[[Category:Development]]
[[Category:Security]]
[[Category:Production]]

Production LAMP system: Lighttpd + PHP + MySQL

2021-02-16T11:26:19Z

Baldlizard: /* 1. The web server part: Lighttpd */

In production web, '''LAMP''' means '''L'''inux + '''A'''pache + '''M'''ysql + '''P'''hp 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:

== 1. The web server part: Lighttpd ==

[http://www.lighttpd.net/ lighttpd] is a simple, standards-compliant, secure, and flexible web server, Nginx is the most used due to beeing manageable by ISP panel's software, but '''lighttpd performs always better. Nginx could not process fast-cgi programs'''. for more complete lighttpd information consult the [[Production Web server: Lighttpd]] wiki page.

=== Lighttpd Installation ===

Production environment only will handle need packages.. so no doc or manages allowed:

# run apk for need packages

<pre>
<nowiki>
apk add lighttpd gamin
</nowiki>
</pre>

=== Lighttpd pre php configuration ===

# make the htdos public web root directories
# change default port to production one, http are used with 80
# use FAM style (gamin) file alteration monitor, increases performance '''ONLY ON 3.4 to 3.8 releases!!!'''
# use linux event handler, increases performance due Alpine are linux only
# added the service to the default runlevel, not to boot, because need networking activated
# started the web server service
# Enable the mod_status at the config files
# change path in the config file, we are using security by obfuscation
# restart the service to see changes at the browser

<pre>
<nowiki>
mkdir -p /var/www/localhost/htdocs/stats /var/log/lighttpd /var/lib/lighttpd

sed -i -r 's#\#.*server.port.*=.*#server.port = 80#g' /etc/lighttpd/lighttpd.conf

sed -i -r 's#\#.*server.event-handler = "linux-sysepoll".*#server.event-handler = "linux-sysepoll"#g' /etc/lighttpd/lighttpd.conf

chown -R lighttpd:lighttpd /var/www/localhost/

chown -R lighttpd:lighttpd /var/lib/lighttpd

chown -R lighttpd:lighttpd /var/log/lighttpd

rc-update add lighttpd default

rc-service lighttpd restart

echo "it works" > /var/www/localhost/htdocs/index.html

sed -i -r 's#\#.*mod_status.*,.*# "mod_status",#g' /etc/lighttpd/lighttpd.conf

sed -i -r 's#.*status.status-url.*=.*#status.status-url = "/stats/server-status"#g' /etc/lighttpd/lighttpd.conf

sed -i -r 's#.*status.config-url.*=.*#status.config-url = "/stats/server-config"#g' /etc/lighttpd/lighttpd.conf

rc-service lighttpd restart
</nowiki>
</pre>

'''For testing open a browser and go to <code><nowiki>http://<webserveripaddres></nowiki></code> and you will see "it works"'''. The "webserveripaddres" are the ip address of your setup/server machine.

'''There's a problem in Alpine linux, FAM (gamin) are activated as a lighttpd only service''', that's make sense in dockers but in servers could be a problem if FAM (gamin) are also need for others services at the same time.

'''OPTIONAL:''' alpine packagers are a mess, removed fam on recents, soolder releases of alpine can use compiled fam packages with <code>sed -i -r 's#.*server.stat-cache-engine.*=.*# server.stat-cache-engine = "fam"#g' /etc/lighttpd/lighttpd.conf</code>

== 2. The php scripting part: PHP fpm ==

In Alpine there's two main language for programming dynamic web pages: PHP and LUA. Alpine are minimalist so not all PHP packages are need in most cases, both repositories must be enabled (main and community), here are explained the most common used in production, for PHP at development please watch the [[Alpine_newbie_developer]] wiki page.

=== PHP Installation ===

Since version v3.5, PHP 7 is available along with PHP 5.6 coexisting together, until version v3.9 where the latter was removed. So for Alpine 3.5+m we will assume PHP7, if you need PHP5.6 still could use it, that wil be cover in the special [[Production LAMP system: Lighttpd + PHP5 + MySQL]] wiki page for older Alpine systems and some specific php softwares.

<pre><nowiki>
apk add php7 php7-bcmath php7-bz2 php7-ctype php7-curl php7-dom php7-enchant php7-exif php7-fpm php7-gd php7-gettext php7-gmp php7-iconv php7-imap php7-intl php7-json php7-mbstring php7-opcache php7-openssl php7-phar php7-posix php7-pspell php7-recode php7-session php7-simplexml php7-sockets php7-sysvmsg php7-sysvsem php7-sysvshm php7-tidy php7-xml php7-xmlreader php7-xmlrpc php7-xmlwriter php7-xsl php7-zip php7-sqlite3
</nowiki></pre>

{{Note|'''The below packages are only for specific situations.. only install when need (specially php-pear one)''', by example, <code>cacti</code> and <code>cacti-php7</code> are in edge that depends on <code>php7</code>, but you must only install from edge only the cacti package, all the depends must be previously installed from stable.}}

<pre><nowiki>
apk add php7-pgsql php7-mysqli php7-mysqlnd php7-snmp php7-soap php7-ldap php7-pcntl php7-pear php7-shmop php7-wddx php7-cgi php7-pdo php7-snmp php7-tokenizer
</nowiki></pre>

{{Note|'''The below packages are only for databases access using php in specific ways.. only install when need (specially php--pdo ones)''', by example, <code>cacti</code> and <code>cacti-php7</code> are in edge that depends on <code>php7-mysqli</code>, but you must only install from edge only the cacti package, all the depends like <code>php7</code> and <code>php7-mysqli</code> must be previously installed from stable.}}

<pre><nowiki>
apk add php7-dba php7-sqlite3 php7-mysqli php7-mysqlnd php7-pgsql php7-pdo_dblib php7-pdo_odbc php7-pdo_pgsql php7-pdo_sqlite
</nowiki></pre>

A special case it's the <code>php7-odbc</code>, unless the others, that are able php to connect to only specific database, '''[[Production DataBases : unixodbc|unixodbc]]''' are a universal way to do so, the most important difference are that by example, <code>php7-mysqli</code> package has better functions to manage data into the php software usage.

=== PHP Global Configuration ===

# Use fix.pathinfo
# Set safe mode off
# Dont expose php code if something fails
# Set amount of memory limit for execution to 536Mb (most servers are minimal of 1Gb of RAM)
# So then set upload size to 128Mb as maximun.
# Set then POST max size to 256Mb based on the upload max size limit.
# Turn on the url open method
# Set default charset to UTF-8 more compatible
# Increase the execution time and the input time for.

<pre><nowiki>
sed -i -r 's|.*cgi.fix_pathinfo=.*|cgi.fix_pathinfo=1|g' /etc/php*/php.ini
sed -i -r 's#.*safe_mode =.*#safe_mode = Off#g' /etc/php*/php.ini
sed -i -r 's#.*expose_php =.*#expose_php = Off#g' /etc/php*/php.ini
sed -i -r 's#memory_limit =.*#memory_limit = 536M#g' /etc/php*/php.ini
sed -i -r 's#upload_max_filesize =.*#upload_max_filesize = 128M#g' /etc/php*/php.ini
sed -i -r 's#post_max_size =.*#post_max_size = 256M#g' /etc/php*/php.ini
sed -i -r 's#^file_uploads =.*#file_uploads = On#g' /etc/php*/php.ini
sed -i -r 's#^max_file_uploads =.*#max_file_uploads = 12#g' /etc/php*/php.ini
sed -i -r 's#^allow_url_fopen = .*#allow_url_fopen = On#g' /etc/php*/php.ini
sed -i -r 's#^.default_charset =.*#default_charset = "UTF-8"#g' /etc/php*/php.ini
sed -i -r 's#^.max_execution_time =.*#max_execution_time = 150#g' /etc/php*/php.ini
sed -i -r 's#^max_input_time =.*#max_input_time = 90#g' /etc/php*/php.ini
</nowiki></pre>

=== PHP-FPM Configuration ===

# Create directory for php socket and pid files, MUST BE EQUAL to openrc defined!
# Set into configuration file the socket path, MUST BE EQUAL to openrc defined!
# Set into configuration file the pid file path, MUST BE EQUAL to openrc defined!

<pre>
<nowiki>
mkdir -p /var/run/php-fpm7/

chown lighttpd:root /var/run/php-fpm7

sed -i -r 's|^.*listen =.*|listen = /run/php-fpm7/php7-fpm.sock|g' /etc/php*/php-fpm.d/www.conf

sed -i -r 's|^pid =.*|pid = /run/php-fpm7/php7-fpm.pid|g' /etc/php*/php-fpm.conf

sed -i -r 's|^.*listen.mode =.*|listen.mode = 0640|g' /etc/php*/php-fpm.d/www.conf

rc-update add php-fpm7 default

service php-fpm7 restart
</nowiki>
</pre>

The PHP-FPM defined a master process with some pool of process for each service resuests, by default there's only one pool of processes, the www pool process.

Default values are good for starting, but later will need tuning, the best it's static one but need test and set until get right configuration.

=== Lighttpd + PHP-FPM ===

The web server comes to and very unmantained config file so we must handle all the required settings:

# enable the mod_alias at the config file, due need of a specific path for cgi files into security
# be sure and disable the fastcgi-php module by cgi only
# and then enable the fastcgi-php-fpm specific module then
# write a much much better approach of the php handler in the local server using the socket
# configure the php to use also the socket too for direct connection locally
# restart the service to see changes at the browser

<pre>
<nowiki>
mkdir -p /var/www/localhost/cgi-bin

sed -i -r 's#\#.*mod_alias.*,.*# "mod_alias",#g' /etc/lighttpd/lighttpd.conf

sed -i -r 's#.*include "mod_cgi.conf".*# include "mod_cgi.conf"#g' /etc/lighttpd/lighttpd.conf

sed -i -r 's#.*include "mod_fastcgi.conf".*#\# include "mod_fastcgi.conf"#g' /etc/lighttpd/lighttpd.conf

sed -i -r 's#.*include "mod_fastcgi_fpm.conf".*# include "mod_fastcgi_fpm.conf"#g' /etc/lighttpd/lighttpd.conf

cat > /etc/lighttpd/mod_fastcgi_fpm.conf << EOF
server.modules += ( "mod_fastcgi" )
index-file.names += ( "index.php" )
fastcgi.server = (
".php" => (
"localhost" => (
"socket" => "/var/run/php-fpm7/php7-fpm.sock",
"broken-scriptfilename" => "enable"
))
)
EOF

sed -i -r 's|^.*listen =.*|listen = /var/run/php-fpm7/php7-fpm.sock|g' /etc/php*/php-fpm.d/www.conf

sed -i -r 's|^.*listen.owner = .*|listen.owner = lighttpd|g' /etc/php*/php-fpm.d/www.conf

sed -i -r 's|^.*listen.group = .*|listen.group = lighttpd|g' /etc/php*/php-fpm.d/www.conf

sed -i -r 's|^.*listen.mode = .*|listen.mode = 0660|g' /etc/php*/php-fpm.d/www.conf

rc-service php-fpm7 restart

rc-service lighttpd restart

echo "<?php echo phpinfo(); ?>" > /var/www/localhost/htdocs/info.php
</nowiki>
</pre>

'''For testing open a browser and go to <code><nowiki>http://<webserveripaddres>/info.php</nowiki></code> and you will see only the minimal info due in production there's no need for too much information to crackers. The "webserveripaddres" are the ip address of your setup/server machine.

After that, all the files with php will be proceses faster than used a host based, also under the <code>/var/www/localhost/cgi-bin</code> directory will be showed as <nowiki>http://localhost/cgi-bin/</nowiki> path.

=== Multiple PHP-FPM cluster ===

As we said, in FPM it is managed by process pools, but the connection can be over the network or over a direct n socket, the configuration for a powerful server of average requests is with socket and localhost, but for high availability it is required CAT6 wired network connections of 1000Mbps and php-fpm by network connections in roundrobin mode.

For php fpm pool will be on a specific machine and the web server(s) will simply connect to these machines with php to serve the php pages, the result is that we have a cluster of lighttpd web servers against other php-fpm process clusters, the php project can be the same code on all web servers and connected to a single database.

At the Linux console the change are, by example two machines 10.10.1.10 and 10.10.2.10 both have php and lighttpd, so then in each one will setup the php of the other:

<pre>
<nowiki>
mkdir -p /var/www/localhost/cgi-bin

sed -i -r 's#\#.*mod_alias.*,.*# "mod_alias",#g' /etc/lighttpd/lighttpd.conf

sed -i -r 's#.*include "mod_cgi.conf".*# include "mod_cgi.conf"#g' /etc/lighttpd/lighttpd.conf

sed -i -r 's#.*include "mod_fastcgi.conf".*#\# include "mod_fastcgi.conf"#g' /etc/lighttpd/lighttpd.conf

sed -i -r 's#.*include "mod_fastcgi_fpm.conf".*# include "mod_fastcgi_fpm.conf"#g' /etc/lighttpd/lighttpd.conf

cat > /etc/lighttpd/mod_fastcgi_fpm.conf << EOF
server.modules += ( "mod_fastcgi" )
index-file.names += ( "index.php" )
fastcgi.server = ( ".php" =>
(
( "host" => "10.10.1.10",
"port" => 9000
),
( "host" => "10.10.2.10",
"port" => 9000 )
)
)
EOF

sed -i -r 's|^.*listen =.*|listen = 9000|g' /etc/php*/php-fpm.d/www.conf

sed -i -r 's|^.*listen.owner = .*|listen.owner = lighttpd|g' /etc/php*/php-fpm.d/www.conf

sed -i -r 's|^.*listen.group = .*|listen.group = lighttpd|g' /etc/php*/php-fpm.d/www.conf

sed -i -r 's|^.*listen.mode = .*|listen.mode = 0660|g' /etc/php*/php-fpm.d/www.conf

rc-service php-fpm7 restart

rc-service lighttpd restart

echo "<?php echo phpinfo(); ?>" > /var/www/localhost/htdocs/info.php
</nowiki>
</pre>

== 3. The DBMS part: mysql/mariadb ==

Alpine Linux has dummy counterparts packages for those that are not close to that change from ''mysql'' to ''mariadb'' naming packages.

=== Installation ===

Take in consideration that the user <code>mysql</code> was created during instalation of packages, in the initialization section two users will be created in database init: <code>root</code> and <code>mysql</code>, and in that point only if are in their respective system accounts, will be able to connect to the database service.

<pre><nowiki>
apk add mysql mysql-client
</nowiki></pre>

=== Initialization ===

The ''datadir'' are located to <code>/var/lib/mysql</code> must be owned by the mysql user and group. You can modify this behavior but must edit the service file at <code>/etc/init.d</code> directory. Also, you need to set <code><nowiki>datadir=<YOUR_DATADIR></nowiki></code> under section <code>[mysqld]</code> at the config file.

# Initialize the main mysql database, and the data dir as standardized to <code>/var/lib/mysql</code> by the rc script
# Then initialize the service, root account and socket connection are enabled without password at this point
# Setup the root account by asignes a proper password, this are purely paranoid. due next step already do that!
# Setup and init the installation by running the <code>mysql_secure_installation</code>
# Setup permissions for manage others users and databases
# Run the <code>mysql_secure_installation</code> script and answer the questions (see section below)

<pre>
<nowiki>
mysql_install_db --user=mysql --datadir=/var/lib/mysql

rc-service mariadb start

mysqladmin -u root password toor

mysql_secure_installation
</nowiki>
</pre>

# '''Enter current password for root (enter for none):''' must be provided due we already set previously. correct respond are <code>OK, successfully used password, moving on...</code>
# '''Switch to unix_socket authentication [Y/n]''' this are not the case and must be disabled, '''so answer NO''', and response will be <code>... skipping.</code>
# '''Change the root password? [Y/n]''' Just press "n" only if you provided a good password, otherwise just change it!
# '''Remove anonymous users? [Y/n]''' In any case, '''production system must remove it, so answer Y''' and proper respond mus be <code>... Success!</code>.
# '''Disallow root login remotely? [Y/n]''' For sure answer Y''' and proper respond mus be <code>... Success!</code>.
# '''Remove test database and access to it? [Y/n]''' Should be removed, so answer Y''' and proper respond mus be <code>... Success!</code>.
# '''Reload privilege tables now? [Y/n]''' Aanswer Y''' and proper respond mus be <code>... Success!</code>.

After reponse all the questions.. restart the service with <code>rc-service mariadb restart</code>

=== Configuration ===

Newer system Alpine packages can set in independent files in any case those commands always works and where are not apply just will ignore the output, for more info about that watch the [[MariaDB#Configuration_files_and_customization|MariaDB Configuration files]] section of the MariaDB wiki page.

* On older Alpine system must set config files for MAX ALLOWED PACKETS to minimun proper amount:
* Only allow local connections on cases where there's only one server or no expected to connect from others:
* Set default charset to UTF8MB4
* Added the service to start process but not at boot process due needs networking started.
* Restart the service to apply changes.

<pre>
<nowiki>
sed -i "s|.*max_allowed_packet\s*=.*|max_allowed_packet = 100M|g" /etc/mysql/my.cnf
sed -i "s|.*max_allowed_packet\s*=.*|max_allowed_packet = 100M|g" /etc/my.cnf.d/mariadb-server.cnf

sed -i "s|.*bind-address\s*=.*|bind-address=127.0.0.1|g" /etc/mysql/my.cnf
sed -i "s|.*bind-address\s*=.*|bind-address=127.0.0.1|g" /etc/my.cnf.d/mariadb-server.cnf

cat > /etc/my.cnf.d/mariadb-server-default-charset.cnf << EOF
[client]
default-character-set = utf8mb4

[mysqld]
collation_server = utf8mb4_unicode_ci
character_set_server = utf8mb4

[mysql]
default-character-set = utf8mb4
EOF

rc-service mariadb restart

rc-update add mariadb default
</nowiki>
</pre>

'''On upgrade cases:''' If are unable to run any mysql command after an upgrade, it's because MySQL cannot start try run MySQL in safemode with <code>mysqld_safe --datadir=/var/lib/mysql/</code> command and then run the <code>mysql_upgrade -u root -p</code> script. For more information watch the [[MariaDB#Updating_or_comming_from_upgrading|MariaDB upgrading section]] of the MariaDB wiki page.

=== adminer: Web Frontend administration ===

[https://www.adminer.org/ Adminer] are a simple and single tool, tons of times faster thant PhpMysqladmin that are great but have too much security issues and lot of complext settings, we must use a more single and simpel solution easy to manage and upgrade.

Take in consideration that this needs as requisite the previous sections of web server, php scripting and mysql/mariadb engine configured and running:

<pre>
<nowiki>

mkdir -p /var/www/webapps/adminer

wget https://github.com/vrana/adminer/releases/download/v4.7.6/adminer-4.7.6.php -O /var/www/webapps/adminer/adminer-4.7.6.php

ln -s adminer-4.7.6.php /var/www/webapps/adminer/index.php

cat > /etc/lighttpd/mod_adminer.conf << EOF
# NOTE: this requires mod_alias
alias.url += (
"/adminer/" => "/var/www/webapps/adminer/"
)
$HTTP["url"] =~ "^/adminer/" {
# disable directory listings
dir-listing.activate = "disable"
}
EOF

sed -i -r 's#\#.*mod_alias.*,.*# "mod_alias",#g' /etc/lighttpd/lighttpd.conf

sed -i -r 's#.*include "mod_cgi.conf".*# include "mod_cgi.conf"#g' /etc/lighttpd/lighttpd.conf

checkssl="";checkssl=$(grep 'include "mod_adminer.conf' /etc/lighttpd/lighttpd.conf);[[ "$checkssl" != "" ]] && echo listo || sed -i -r 's#.*include "mod_cgi.conf".*#include "mod_cgi.conf"\ninclude "mod_adminer.conf"#g' /etc/lighttpd/lighttpd.conf

rc-service lighttpd restart
</nowiki>
</pre>

The administrator must visit with exact url <code><nowiki>http://<ipaddress>/adminer/index.php</nowiki></code> because two main reasons: there's no directory listing and there's no direct php index reference in web server, all of this due paranoiac settings.

= See Also =

* [[Production LAMP system: Lighttpd + PHP5 + MySQL]]
* [[Production Lets Encrypt: dehydrated]]
* [[Alpine newbie developer]]
* [[Alpine newbie lammers]]

[[Category:Newbie]]
[[Category:Server]]
[[Category:Web_Server]]
[[Category:Monitoring]]
[[Category:Development]]
[[Category:Security]]
[[Category:Production]]