Alpine Linux - User contributions [en]

Talk:Alpine Install: from a disc to a old computer single only boot

2022-01-06T17:58:44Z

Mckaygerhard: clarifications.. to zcrayfish that knows how to coordinate, thanks to him

== Proposal for deletion ==
I do not support the proposal for deletion. This article is 2 clicks away from the main page. If the content of this article exists elsewhere, it should be merged. [[User:Zcrayfish|zcrayfish]] ([[User talk:Zcrayfish|talk]]) 00:07, 15 December 2021 (UTC)
: hi [[User:Zcrayfish|zcrayfish]], this article is and special case setup, the main install article is too generic and focused in x64 iso setups with high ramifications.. this article is more focused in x86 32bit cases, that i have almost 200 machines, those almost 30 uses older versions of alpine linux in intranet with no networking.
: also, this article make focus on special steps to made for those computers.. by example some kernels does not have support for ISA devices so this must be pointed in!
: at last: i separate those kind of articles in a category names "newbie" that currently are mess up with the Guest09248 user now! due the unable to coordinate with him i emailed to staff to removal all my content.. with no so friendly responses.. [[User:Mckaygerhard|Mckaygerhard]] ([[User talk:Mckaygerhard|talk]]) 12:07, 6 Jan 2022 (UTC)

Alpine production deployment

2022-01-06T17:51:25Z

Mckaygerhard: restore dead link from a mirror git

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://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.

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

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

Alpine production deployment

2022-01-06T17:48:27Z

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

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{{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.

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

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

Post installation

2022-01-06T17:44:21Z

Mckaygerhard: Guest09248 i removed any NEWBIE install , i was talk with staff about that.. use your pages only

{{Draft|Still might be missing some things but (i think) it is mostly complete}}

== General Notes ==

* When '''#''' is displayed before a command that means the command needs to be run with root privileges,

* Anything in < > is likely just a placeholder that you need to replace (example: <editor> file.txt)

* Some information in here might be a repeat of information in other wiki pages, if you find a section where that is the case please add a link to the original wiki page.

 

== Network setup ==

==== Wi-Fi ====

* [[Wi-Fi]]
* [[NetworkManager]]

==== Ethernet (Wired) ====

{{Expand|Documentation on Ethernet (Wired) internet setup needs to be created/expanded, maybe information from other wiki's/docs might be helpful?}}

* [[Ethernet|Ethernet]]
* [[NetworkManager]]

 

== Creating a new user account ==

After installing Alpine by default you only get a root account. You will probably want to create an account that is not root,

{{cmd|# adduser <YourUsername>}}
{{Note|replace <YourUsername> with the username of your choice}}

 

You will probably want to install '''doas''' so you can allow <YourUsername> to use root privileges
{{cmd|# apk add doas}}

 

If you want your user to be able to use root privileges add them to the Wheel group
{{cmd|# adduser <YourUsername> wheel}}

 

Allow members of the '''Wheel''' group to use root privileges with doas:

{{cmd|# <editor> /etc/doas.d/doas.conf}}

add this to a new line:
{{cmd|permit persist :wheel}}

 

Switch to the new account type '''exit''' in the shell and login with the new user,

 

==== Groups ====

Groups are needed for certain operations on your system (e.g <code>audio</code> to manage your system audio), below is a list of groups,
{{Note|may be incomplete, if you see a group missing please add it along with a description}}

{{Cmd|disk:x:6:root,adm Only if need usage vith virtual machines and access to other partitions over new disks for
lp:x:7:lp If will need to use printing services and printers management
floppy:x:11:root Backguard compatible group, use only if need access to external special devices
audio:x:18: Need for audio listening and management of sound volumes as normal user
cdrom:x:19: For access to disck writers and mounting DVD, BR or CD rom disk as normal user
dialout:x:20:root Need for dial private connections and use of modems as normal users
tape:x:26:root Need have into this if plan to use special devices for backup.. rarelly in no servers
video:x:27:root For usage of cameras, mor thant one GPU special features, as normal user
netdev:x:28: For network connections management as normal user
kvm:x:34:kvm Only if as normal user will manage graphically virtual machines.. rarelly on no servers
games:x:35: Need if you want to play games also specially need if will share score between users
cdrw:x:80: To write RW-DVD, RW-BR or RW-CD disk on a disk writing device
apache:x:81: Need if you will perfom development as normal user and want to publish locally on web server
usb:x:85: Need to access to special usb devices, deprecated group
users:x:100:games If you plan to used common files for all users, mandatory as desktop usage}}

 

To add your user to a group use the following command:

{{Cmd|# adduser <YourUsername> <group>}}
{{Note|you need to log out for the group change(s) to take effect}}

 

== Shell ==

{{Note|[https://en.wikipedia.org/wiki/Almquist_shell ash] is the only shell included with Alpine by default, you will need to install another shell if you want a different one}}

 

By default AlpineLinux uses the [https://en.wikipedia.org/wiki/Almquist_shell ash] shell, but many users may prefer {{Pkg|bash}}, {{Pkg|zsh}}, {{Pkg|fish}} or another shell, to change this run the following command:

{{Cmd|$ chsh}}
enter your password and you should get the following output:

{{Cat|$ chsh|Changing the login shell for user
Enter the new value, or press ENTER for the default
Login Shell [/bin/ash]:}}

 

now enter the path for the shell you want to use (e.g <code>/bin/bash</code>) and press enter to confirm this change,
{{Note|You may need to log out or reboot for this change to take effect, '''ash''' is a part of busybox so you can revert back to '''ash''' at anytime with the same steps}}

 

== Repositories ==

The Alpine software repositories have three branches:

* '''Main''': Main packages are the Alpine software that has direct support and updates from the Alpine core and main team. They also have official special documentation, are always available for all releases and will have substitutions if some are not continued from upstream. Commonly, those packages are selected due to their responsibility and stability with respect to upstream availability. When those in ''testing'' perform well or are mature, they go to the ''main'' branch.
* '''Community''': Community packages are those made by users in concert with the official developers and integrated into the Alpine packages. They are user supported. Support could end if the user ends support with respect to Alpine work. For example, could not include substitution in next release due to lack of support by the upstream author. They are in ''edge'' and when accepted, go to the ''community'' branch.
* '''Edge''': New packages come into testing repositories of the edge Alpine version and are those made by any contributor or man power on Alpine. The edge contains unstable current development content. This branch has no release linked or related to Alpine. They are in ''testing'' and when accepted, go to the ''community'' branch.

 

By default only the '''main''' repository is enabled, most users will probably want to enable the '''community''' repository, to enable a repository remove the '''#''' in front of the url along with any blank space.

 

(Example) Disabled:
{{cat|/etc/apk/repositories|#http://dl-cdn.alpinelinux.org/alpine/v3.15/community}}

(Example) Enabled:
{{cat|/etc/apk/repositories|http://dl-cdn.alpinelinux.org/alpine/v3.15/community}}

 

To edit the repositories open the file in a text editor:
{{cmd|# <editor> /etc/apk/repositories}}

 

Example default configuration:

{{cat|/etc/apk/repositories|#/media/cdrom/apks
http://dl-cdn.alpinelinux.org/alpine/v3.15/main
# http://dl-cdn.alpinelinux.org/alpine/v3.15/community
#http://dl-cdn.alpinelinux.org/alpine/edge/main
#http://dl-cdn.alpinelinux.org/alpine/edge/community
#http://dl-cdn.alpinelinux.org/alpine/edge/testing}}

{{Note|The edge repositories contain unstable and/or possibly untested packages use at your own risk!}}

 

To avoid having to manually update the verison in '''/etc/apk/repositories''' for each Alpine Linux update, change '''v3.15''' to '''latest-stable'''

Example:
{{cat|/etc/apk/repositories|#/media/cdrom/apks
http://dl-cdn.alpinelinux.org/alpine/latest-stable/main
http://dl-cdn.alpinelinux.org/alpine/latest-stable/community
#http://dl-cdn.alpinelinux.org/alpine/edge/main
#http://dl-cdn.alpinelinux.org/alpine/edge/community
#http://dl-cdn.alpinelinux.org/alpine/edge/testing}}

{{Note|Changing the repositories to latest-stable may initiate unexpected release upgrades, do this at your own risk!}}

 

For [https://en.wikipedia.org/wiki/HTTPS#Technical security reasons] it may be a good idea to change the url's from '''http''' to '''https'''

Example:
{{cat|/etc/apk/repositories|#/media/cdrom/apks
https://dl-cdn.alpinelinux.org/alpine/v3.15/main
https://dl-cdn.alpinelinux.org/alpine/v3.15/community
#https://dl-cdn.alpinelinux.org/alpine/edge/main
#https://dl-cdn.alpinelinux.org/alpine/edge/community
#https://dl-cdn.alpinelinux.org/alpine/edge/testing}}

{{Note|some Alpine Linux package mirrors may not support https, if that is the case you will need to revert back or change mirrors}}

 

Once you have edited '''/etc/apk/repositories''' sync the repositories with:

{{cmd|# apk update}}

 

== Installing a Display Server (for graphical sessions) ==

==== Xorg ====
Most desktop enviroments (DE) or Windows Managers (WM) require Xorg (also called: X11, X), although in the future many will fully migrate to [[Wayland]] currently Xorg is still widely used,

 

There is two ways you can get Xorg installed,

 

By default Alpine Linux provides a script that will install Xorg, run the following command to install Xorg:
{{cmd|# setup-xorg-base}}

or

{{cmd|# apk add xorg-server xorg-server-common xorg-server-dev xorgproto xorgxrdp xorgxrdp-dev}}
{{Note| the apk add method is probably incomplete}}

 

==== Wayland ====
''See also: [[Wayland]]''

{{Expand|Wayland documentation needs to be expanded}}

 

== Fonts ==

If you plan to use a graphical environment you may need/want to install fonts
{{Note|depending on the desktop environment/window manager fonts may or may not be installed automatically or as dependencies}}

'''See: [[Fonts|Fonts]]'''

 

== Installing a desktop environment or window manager ==

'''See: [[Desktop environments and Window managers]]'''

 

== Sound ==

By default Alpine doesnt come with any Sound managment out of the box, these are your options:

* [[PipeWire]]
* [[PulseAudio]]
* [[ALSA]]

{{Note|If your unsure {{Pkg|pipewire}} is the recommended option}}

 

== Man pages ==

Most Linux distributions have '''man''' pages, man pages allow you type <code>man <package></code> in a terminal and get some useful information about packages installed on your system quicky without a internet connection, by default Alpine does not include '''man''', you can add that with the following:

* <code># apk add man-pages</code> Installs basic manual pages.
* <code># apk add mandoc</code> Installs the man command to be able to open man pages.
* <code># apk add mandoc-apropos</code> Installs the apropos command to search in man pages.
* <code># apk add docs</code> Installs all the *-doc sub-packages of installed packages.

{{Note|man pages may not be available for every package}}

 

== Language support ==

{{Expand}}

* Fix unicode defaults: <code>sed -i 's/#unicode="NO"/#unicode="NO"\nunicode="YES"/' /etc/rc.conf</code>
* <code>apk add musl-locales</code> Installs a limited set of locales (languages) for musl (C library) generated console messages.
* Listing defined locales is possible with <code>locale -a</code>
* <code>cp /etc/profile.d/locale.sh /etc/profile.d/locale.sh.sh</code> Copies the default locale settings. Then the custom override file can be edited <code>nano /etc/profile.d/locale.sh.sh</code>.
* <code>apk add lang</code> Pulls in the translation packages of all installed packages.
* <code>apk list hunspell*</code> To list available hunspell dictionary packages.
* <code>apk list *-xy *-xy-*</code> To list translation packages for your specific (xy) language (for example, pt for Portuguese).

 

== Miscellaneous ==

Some other miscellaneous things that might be useful:

==== basic tools ====

Alpine is a minimalist Linux distribution. If you expected a behavior like other Linux distributions, the similarity to them will be minimal at best. Run:

{{Cmd|# apk add sed attr dialog bash bash-completion grep util-linux pciutils usbutils binutils findutils readline lsof less nano curl}}

{{Cmd|<nowiki>$ export PAGER=less</nowiki>}}

 

== Troubleshooting ==

==== I dont have permission to do anything in my user's home directory ====

By default the permissions of your new user(s) home directory may be limited to the root account, run one of these commands to change that:

{{cmd|# chmod 700 /home/<YourUsername>}}

or

{{cmd|# chmod 777 /home/<YourUsername>}}

 

== See also ==
* [[Installation]]
* [[Comparison with other distros]]

[[Category:Installation]]

Install Alpine on Amazon EC2

2022-01-06T17:27:52Z

Mckaygerhard: remove AND STOP TO USE NEWBIE REFERENCE is a separate work in progress

{{Move| Alpine Install: from a image to a Amazon EC2 instance |This article need wikiformating consisten with setups procedure and naming formating.}}

EC2 instances are available in a variety of [https://aws.amazon.com/ec2/instance-types/ different sizes] with different specifications but all of them currently run on one of two types of virtualization technology: [https://en.wikipedia.org/wiki/Paravirtualization paravirtualization] (PV) or [https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine hardware virtual machine] (HVM).

PV instances boot with a special boot loader called PV-GRUB, which starts the boot cycle and then chain loads the kernel specified in the menu.lst file on your image. Paravirtual guests can run on host hardware that does not have explicit support for virtualization, but they cannot take advantage of special hardware extensions such as enhanced networking or GPU processing.

HVM instances are presented with a fully virtualized set of hardware and boot by executing the master boot record of the root block device of your image. This virtualization type provides the ability to run an operating system directly on top of a virtual machine without any modification, as if it were run on the bare-metal hardware. The Amazon EC2 host system emulates some or all of the underlying hardware that is presented to the guest. (from: [https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/virtualization_types.html Linux AMI Virtualization Types]).

Only older instance types support PV instances, all new instance types use an HVM hypervisor. For the purposes of setting up Alpine Linux on EC2 this mainly impacts the way the bootloader is configured.

EC2 instances are created from templates called Amazon Machine Images (AMI). AMIs are built using existing running instances and then are turned into AMIs using a snapshot process. Note that an AMI is region specific so you must either follow this guide in each region you plan to deploy Alpine Linux instances or you must copy the AMI using either the console or the AWS command line client to each region you plan to use.

All instance types are 64-bit. 32-bit images will not work.

This guide will create the smallest possible (1GB) EBS-backed image which acts as a virtual USB stick that will boot and run Alpine Linux.
= Initial Setup =
All AMI creation tasks follow the same set of setup steps which require a running Linux instance and an attached EBS volume. The Linux instance will only be used to set up the root filesystem for your Alpine Linux system so any distro works, Amazon Linux is the default so, where relevant, this guide will use that distro.

# Create an EC2 instance, t2.micro running Amazon Linux should suffice
# Create a 1GB EBS volume and attach it to the instance as {{Path|/dev/sdf}} (this will appear on an HVM instance as {{Path|/dev/xvdf}})
# Format the disk as ext4, there is no need to partition the drive: {{Cmd|mkfs.ext4 /dev/xvdf}}
# Mount the drive to the host: {{Cmd|mkdir /mnt/target && mount /dev/xvdf /mnt/target}}
# Fetch a copy of the latest virt release: {{Cmd|curl -o /tmp/alpine-release.iso http://dl-4.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-virt-3.7.0-x86_64.iso}}
# Mount the release iso: {{Cmd|mkdir /mnt/source && mount -o loop /tmp/alpine-release.iso /mnt/source}}
# Copy the files to the target {{Cmd|cp -av /mnt/source/boot /mnt/target}}

The sudo package is not included in the on-disk repository for the virt image which means that it will not be accessible for installation at system boot time; to enable this you will need a copy of the repository from the extended image. Download this image and copy the <tt>apks</tt> folder to the target.

# Fetch a copy of the latest extended release: {{Cmd|curl -o /tmp/alpine-extended-release.iso http://dl-4.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-extended-3.7.0-x86_64.iso}}
# Mount the release iso: {{Cmd|mkdir /mnt/source-extended && mount -o loop /tmp/alpine-extended-release.iso /mnt/source-extended}}
# Copy the files to the target {{Cmd|cp -av /mnt/source-extended/apks /mnt/target}}

Because the packages on Amazon Linux are a little older than the ones that ship with Alpine and because you will be creating an apkovl file for initial system configuration, you will either need an existing Alpine Linux system or a copy of the minirootfs image into which you can chroot. To set up a chroot:

# Fetch a copy of the latest minirootfs release: {{Cmd|curl -o /tmp/alpine-minirootfs.tar.gz http://dl-4.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-minirootfs-3.7.0-x86_64.tar.gz}}
# Unpack the root fs: {{Cmd|mkdir /tmp/alpine-chroot && tar -C /tmp/alpine-chroot -xvf /tmp/alpine-minirootfs.tar.gz}}
# Copy the system resolv.conf into the chroot so you will have internet access: {{Cmd|cp /etc/resolv.conf /tmp/alpine-chroot/etc}}

= Create an Apkovl File =
The top level of the EBS volume will be scanned during boot for files named <tt>*.apkovl.tar.gz</tt> and the first one that is found will be unpacked and overlayed onto the file system. The goal of this archive is to configure the system so that you will be able to login after the system boots. At a minimum this means:

* Configure networking to use dhcp and start when the system boots
* Install an SSH daemon
* Configure a user with your SSH keys
* Enable sudo so that you can gain root access

Set up the chroot and chroot into it, then add any desired packages. The <tt>busybox-initscripts</tt> package provides the required files for udhcpc which will allow DHCP to be enabled. The <tt>syslinux</tt> package is required to install the boot-loader but is not required on the final system.

<pre>
mkdir /tmp/alpine-chroot/mnt/target
mount -o bind /mnt/target /tmp/alpine-chroot/mnt/target
mount -t proc none /tmp/alpine-chroot/proc
mount -t devtmpfs none /tmp/alpine-chroot/dev
mount -t sysfs none /tmp/alpine-chroot/sys

chroot /tmp/alpine-chroot sh

apk update
apk add alpine-conf sudo openssh busybox-initscripts syslinux
</pre>

The Alpine init system will start up the core required services if the file {{Path|/etc/.default_boot_services}} exists, so create that.

<pre>
touch etc/.default_boot_services
</pre>

Set up networking:

<pre>
cat > /etc/network/interfaces <<EOF
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
EOF

ln -s /etc/init.d/networking /etc/runlevels/default/
ln -s /etc/init.d/sshd /etc/runlevels/default/
</pre>

Add a user, set an SSH key, and ensure that this user can sudo:

<pre>
adduser -D -s /bin/sh alpine
addgroup alpine wheel

mkdir /home/alpine/.ssh
chmod 700 /home/alpine/.ssh
chown alpine /home/alpine/.ssh
cat > /home/alpine/.ssh/authorized_keys <<EOF
... your ssh public key(s) ...
EOF
chmod 600 /home/alpine/.ssh/authorized_keys
chown alpine:alpine /home/alpine/.ssh/authorized_keys

passwd -u alpine

sed -i '/%wheel/s/^# //' /etc/sudoers
</pre>

Exclude backup files and any files that are going to exist in the unpacked image. Then create an apkovl bundle.

<pre>
lbu exclude \
etc/group- etc/passwd- etc/shadow- \
etc/apk/keys etc/apk/arch etc/apk/repositories \
etc/os-release \
etc/issue \
etc/alpine-release
lbu include /home/alpine/.ssh
lbu package amazon.apkovl.tar.gz
</pre>

Verify that everything you expect to be in the apovl file is there and if not you can [[Manually_editing_a_existing_apkovl|modify the apkovl]].

Finally, copy the apkovl to {{Path|/mnt/target}}.

<pre>
cp amazon.apkovl.tar.gz /mnt/target
</pre>

= EBS Backed HVM AMI =
For HVM instances you will need to install a boot-loader. Any bootloader should do the trick but this guide will use syslinux because it's fast and small and you don't have to support any odd hardware or system layout.

First you will need to ensure that the ext4 driver is loaded and may as well shorten the timeout to speed instance boot time.

{{Cmd|sed -i \
-e '/usb-storage/s//usb-storage,ext4/' \
-e '/^TIMEOUT/s/20/2/' \
/mnt/target/boot/syslinux/syslinux.cfg}}

Finally, install the bootloader: {{Cmd|extlinux -i /mnt/target/boot}}

= EBS Backed PV AMI =
For PV AMIs PV-GRUB will attempt to read {{Path|/boot/grub/menu.lst}} to load the kernel. First create a {{Path|/boot/grub/grub.conf}}:

<pre>
mkdir -p /mnt/target/boot/grub

cat > target/boot/grub/grub.conf <<EOF
default=0
timeout=2
hiddenmenu

title Alpine Linux
root (hd0)
kernel /boot/vmlinuz-virthardened alpine_dev=xvda1:ext4 modules=loop,squashfs,sd-mod,ext4 console=hvc0 pax_nouderef BOOT_IMAGE=/boot/vmlinuz-virthardened
initrd /boot/initramfs-virthardened
EOF

ln -s /mnt/target/boot/grub/grub.conf /mnt/target/boot/grub/menu.lst
</pre>

= Create the AMI =
The following will need to be done in the AWS console.

# Detach the new volume (make note of the volume ID)
# Launch a new instance, use the defaults; you are going to cannibalize it in a moment
# Once the instance starts, stop but do not terminate it
# Under EBS, detach the existing volume, and attach the Alpine Linux volume as {{Path|/dev/xvda}} (for HVM) or {{Path|/dev/sda1}} (for PV)
# Restart the instance
# Log in and make sure it works
# Do any final cleanups necessary. Only make changes appropriate for an AMI, you are going to snapshot this instance and use it as the base for the AMI.
# Stop but do not terminate the instance
# Right click the stopped instance and choose 'Create Image (EBS AMI)'
# Once the AMI creation finishes you can cleanup the instances and EBS volumes used

[[Category:Virtualization]]

Alpine Install: from a disc to a virtualbox machine single only

2022-01-06T17:25:04Z

Mckaygerhard:

'''Overall description:''' Installing Alpine from an official disc image to a VirtualBox machine.

This document guides you through installing Alpine on a VirtualBox VM - this is ideal if you only want to try out Alpine.

== Terminology ==

* '''Host machine''': the machine you're running VirtualBox on. It will "host" the target virtual machine.
* '''Guest machine''': your target machine where Alpine will be installed, executed by the VirtualBox software on the host machine.
* '''Reserved RAM''': the amount of host machine RAM that will be needed for exclusive use by the guest machine. The host machine cannot use this RAM while the guest machine is running.
* '''Virtual disc''': the emulated storage medium attached to the guest machine. Usually it is a file (or several files) which VirtualBox presents as a disk to the guest OS (Alpine).

== Requirements ==

On the host machine:

* Qemu or VirtualBox using package manager! Do not promote Oracle's policy of overversiones without security patches
* At least 1GB of RAM, 2GB or more if you don't want lockups while running something in addition to the virtual machine software
* The <code>curl</code> or <code>wget</code> programs to download the image to boot in the virtual software

On the guest machine:

* Minimum 512Mb RAM, but 1Gb or more is recommended if you're going to use a graphical interface. That obviouly must be in sync with the host machine.

== Preparing the medium to install ==

Download the source medium to install and put into your home; there's more hardware medium sources to download, like the '''[https://en.wikipedia.org/wiki/Linux_on_z_Systems s390x]''' and '''[https://en.wikipedia.org/wiki/Ppc64 ppc64le]''', but because VirtualBox handles only '''x86''' and '''x64'''
hardware, we will list those here

The name of the source medium to install will be in the following format: '''<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>''' where <code>ARCH</code> and <code>VERSION</code> can be one of the following, for VirtualBox virtual machines:

* <code><ARCH></code> can be
** '''x86''': The well known i386 to i686. (32-bit machines)
** '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines.
* <code><VERSION></code> can be
** '''latest-stable''' as the name says, the latest, stable version
** '''3.10''' UEFI support began with this version
** '''3.8''' recommended for machines manufactured between 2012 and 2016
** '''3.6''' recommended for older machines

Typically, the version most commonly used in a virtual box is the x86. The hardware is cheaper and operation does not consume a lot of memory.
The iso download URL format is:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' will be:
<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

'''Graphical download''': Just point the web browser to that URL and the download will start. A file with '''.iso''' extension type, with a name like <code>"alpine-standard-3.10.0-x86.iso"</code> (if i386/686); will be downloaded into the directory specified in your browser configuration.

'''Command line method''': just open a terminal and execute: <code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>, for example:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' the command will be:
<code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

You must be mindful of the directory you run the command from, as that is where the file will be saved.

== Preparing the virtual machine to install ==

Start the VirtualBox software program.

# In the main window '''create a new virtual machine''' by '''clicking the blue spark New button'''. That will open a new window with the following questions:
## It will ask for a '''name for the virtual like "alpine-desktop-try1"'''.
## The Type of the '''Operating system choose "linux"'''.
## The version '''choose "other linux"'''. It must match the chosen <code><ARCH></code> (e.g. x86).
## Click the "Next" button to continue creating the virtual machine.
# When selecting the amount of RAM for the virtual machine, choose a minimum of '''512MB''' then click the "Next" button.
# A new window with a '''Hard disk assistant will open'''.
## First choose '''"Create a virtual hard disk now"''' then click the "Create" button.
## Next choose the option for '''hard disk type: VDI''' and push "Next" button.
## Choose '''dynamically allocated''' then click the "Next" button.
## The next window will offer the '''size of virtual disk. 4GB''', however, you may choose a different amount of storage space.
## After clicking on "Create" the virtual machine will be ready to use.
# Now the main window shows you the "alpine-desktop-try1" virtual machine, select it.
## Click on the yellow "Configuration" button. Go to the storage menu and pull it down.
## Select the disc drive icon for CD/DVD ROM and click on the CD/DVD drive icon at the right.
## A Mini menu will open. Select an external file event the host CD/DVD drive.
## A file open dialog will open. Search for the downloaded Alpine iso and select it.
## Once you choose the iso file to boot, click the "Ok" button to finish creating the virtual machine.
# Click the green "Start" arrow to start the virtual machine and boot the iso.

[[File:Alpine Install from a disc to a virtualbox machine single only-01-0.png|center|Alpine configuration commonly used of a virtual machine on virtual box virtual machine]]

== Booting the Alpine ISO disc ==

When the machine starts, you must be sure to choose the Optical drive (commonly named CD/DVD ROM drive), so the disc/iso will boot. After a while, a command line shell will show you

[[File:Installation-alpine-alpine-setup-2-boot.png|350px|thumb|right|Installation : setup-alpine : booting process until login prompt]]

TODO restore the inclusion of template inclkude pages here, were edited and now does not have any sense respect this guide..

== Finishing the installation ==

After setup ends, a "reboot" will be offered. Type "reboot" and press enter and your newly installed virtual machine will be booted. Don't forget to remove the boot medium.

[[File:Installation-alpine-alpine-setup-9-setup-disk-3-7end.png]]

'''You cannot see a graphical window system? No problem.''' With Alpine, GUIs are made the right way. So '''if you need a desktop, you can install a desktop''' follow this link: Alpine newbie packages or go directly to [[Alpine newbie desktops]]

= Documents series =

{| class="wikitable"
|-
! Previous required !! What's next to read
|-
| Alpine newbie install manual || Alpine newbie packages
|}

= See Also =

# [[Alpine newbie developer]]
# [[Alpine newbie lammers]]

[[Category:Newbie]]

Install Alpine on Amazon EC2

2022-01-06T17:24:37Z

Mckaygerhard: use the page of the guest use that is too emotional to understand and use right wikitools

{{Move| Alpine Install: from a image to a Amazon EC2 instance |This article need wikiformating consisten with setups procedure and naming formating, see [[Alpine_newbie_installation]].}}

EC2 instances are available in a variety of [https://aws.amazon.com/ec2/instance-types/ different sizes] with different specifications but all of them currently run on one of two types of virtualization technology: [https://en.wikipedia.org/wiki/Paravirtualization paravirtualization] (PV) or [https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine hardware virtual machine] (HVM).

PV instances boot with a special boot loader called PV-GRUB, which starts the boot cycle and then chain loads the kernel specified in the menu.lst file on your image. Paravirtual guests can run on host hardware that does not have explicit support for virtualization, but they cannot take advantage of special hardware extensions such as enhanced networking or GPU processing.

HVM instances are presented with a fully virtualized set of hardware and boot by executing the master boot record of the root block device of your image. This virtualization type provides the ability to run an operating system directly on top of a virtual machine without any modification, as if it were run on the bare-metal hardware. The Amazon EC2 host system emulates some or all of the underlying hardware that is presented to the guest. (from: [https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/virtualization_types.html Linux AMI Virtualization Types]).

Only older instance types support PV instances, all new instance types use an HVM hypervisor. For the purposes of setting up Alpine Linux on EC2 this mainly impacts the way the bootloader is configured.

EC2 instances are created from templates called Amazon Machine Images (AMI). AMIs are built using existing running instances and then are turned into AMIs using a snapshot process. Note that an AMI is region specific so you must either follow this guide in each region you plan to deploy Alpine Linux instances or you must copy the AMI using either the console or the AWS command line client to each region you plan to use.

All instance types are 64-bit. 32-bit images will not work.

This guide will create the smallest possible (1GB) EBS-backed image which acts as a virtual USB stick that will boot and run Alpine Linux.
= Initial Setup =
All AMI creation tasks follow the same set of setup steps which require a running Linux instance and an attached EBS volume. The Linux instance will only be used to set up the root filesystem for your Alpine Linux system so any distro works, Amazon Linux is the default so, where relevant, this guide will use that distro.

# Create an EC2 instance, t2.micro running Amazon Linux should suffice
# Create a 1GB EBS volume and attach it to the instance as {{Path|/dev/sdf}} (this will appear on an HVM instance as {{Path|/dev/xvdf}})
# Format the disk as ext4, there is no need to partition the drive: {{Cmd|mkfs.ext4 /dev/xvdf}}
# Mount the drive to the host: {{Cmd|mkdir /mnt/target && mount /dev/xvdf /mnt/target}}
# Fetch a copy of the latest virt release: {{Cmd|curl -o /tmp/alpine-release.iso http://dl-4.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-virt-3.7.0-x86_64.iso}}
# Mount the release iso: {{Cmd|mkdir /mnt/source && mount -o loop /tmp/alpine-release.iso /mnt/source}}
# Copy the files to the target {{Cmd|cp -av /mnt/source/boot /mnt/target}}

The sudo package is not included in the on-disk repository for the virt image which means that it will not be accessible for installation at system boot time; to enable this you will need a copy of the repository from the extended image. Download this image and copy the <tt>apks</tt> folder to the target.

# Fetch a copy of the latest extended release: {{Cmd|curl -o /tmp/alpine-extended-release.iso http://dl-4.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-extended-3.7.0-x86_64.iso}}
# Mount the release iso: {{Cmd|mkdir /mnt/source-extended && mount -o loop /tmp/alpine-extended-release.iso /mnt/source-extended}}
# Copy the files to the target {{Cmd|cp -av /mnt/source-extended/apks /mnt/target}}

Because the packages on Amazon Linux are a little older than the ones that ship with Alpine and because you will be creating an apkovl file for initial system configuration, you will either need an existing Alpine Linux system or a copy of the minirootfs image into which you can chroot. To set up a chroot:

# Fetch a copy of the latest minirootfs release: {{Cmd|curl -o /tmp/alpine-minirootfs.tar.gz http://dl-4.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-minirootfs-3.7.0-x86_64.tar.gz}}
# Unpack the root fs: {{Cmd|mkdir /tmp/alpine-chroot && tar -C /tmp/alpine-chroot -xvf /tmp/alpine-minirootfs.tar.gz}}
# Copy the system resolv.conf into the chroot so you will have internet access: {{Cmd|cp /etc/resolv.conf /tmp/alpine-chroot/etc}}

= Create an Apkovl File =
The top level of the EBS volume will be scanned during boot for files named <tt>*.apkovl.tar.gz</tt> and the first one that is found will be unpacked and overlayed onto the file system. The goal of this archive is to configure the system so that you will be able to login after the system boots. At a minimum this means:

* Configure networking to use dhcp and start when the system boots
* Install an SSH daemon
* Configure a user with your SSH keys
* Enable sudo so that you can gain root access

Set up the chroot and chroot into it, then add any desired packages. The <tt>busybox-initscripts</tt> package provides the required files for udhcpc which will allow DHCP to be enabled. The <tt>syslinux</tt> package is required to install the boot-loader but is not required on the final system.

<pre>
mkdir /tmp/alpine-chroot/mnt/target
mount -o bind /mnt/target /tmp/alpine-chroot/mnt/target
mount -t proc none /tmp/alpine-chroot/proc
mount -t devtmpfs none /tmp/alpine-chroot/dev
mount -t sysfs none /tmp/alpine-chroot/sys

chroot /tmp/alpine-chroot sh

apk update
apk add alpine-conf sudo openssh busybox-initscripts syslinux
</pre>

The Alpine init system will start up the core required services if the file {{Path|/etc/.default_boot_services}} exists, so create that.

<pre>
touch etc/.default_boot_services
</pre>

Set up networking:

<pre>
cat > /etc/network/interfaces <<EOF
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
EOF

ln -s /etc/init.d/networking /etc/runlevels/default/
ln -s /etc/init.d/sshd /etc/runlevels/default/
</pre>

Add a user, set an SSH key, and ensure that this user can sudo:

<pre>
adduser -D -s /bin/sh alpine
addgroup alpine wheel

mkdir /home/alpine/.ssh
chmod 700 /home/alpine/.ssh
chown alpine /home/alpine/.ssh
cat > /home/alpine/.ssh/authorized_keys <<EOF
... your ssh public key(s) ...
EOF
chmod 600 /home/alpine/.ssh/authorized_keys
chown alpine:alpine /home/alpine/.ssh/authorized_keys

passwd -u alpine

sed -i '/%wheel/s/^# //' /etc/sudoers
</pre>

Exclude backup files and any files that are going to exist in the unpacked image. Then create an apkovl bundle.

<pre>
lbu exclude \
etc/group- etc/passwd- etc/shadow- \
etc/apk/keys etc/apk/arch etc/apk/repositories \
etc/os-release \
etc/issue \
etc/alpine-release
lbu include /home/alpine/.ssh
lbu package amazon.apkovl.tar.gz
</pre>

Verify that everything you expect to be in the apovl file is there and if not you can [[Manually_editing_a_existing_apkovl|modify the apkovl]].

Finally, copy the apkovl to {{Path|/mnt/target}}.

<pre>
cp amazon.apkovl.tar.gz /mnt/target
</pre>

= EBS Backed HVM AMI =
For HVM instances you will need to install a boot-loader. Any bootloader should do the trick but this guide will use syslinux because it's fast and small and you don't have to support any odd hardware or system layout.

First you will need to ensure that the ext4 driver is loaded and may as well shorten the timeout to speed instance boot time.

{{Cmd|sed -i \
-e '/usb-storage/s//usb-storage,ext4/' \
-e '/^TIMEOUT/s/20/2/' \
/mnt/target/boot/syslinux/syslinux.cfg}}

Finally, install the bootloader: {{Cmd|extlinux -i /mnt/target/boot}}

= EBS Backed PV AMI =
For PV AMIs PV-GRUB will attempt to read {{Path|/boot/grub/menu.lst}} to load the kernel. First create a {{Path|/boot/grub/grub.conf}}:

<pre>
mkdir -p /mnt/target/boot/grub

cat > target/boot/grub/grub.conf <<EOF
default=0
timeout=2
hiddenmenu

title Alpine Linux
root (hd0)
kernel /boot/vmlinuz-virthardened alpine_dev=xvda1:ext4 modules=loop,squashfs,sd-mod,ext4 console=hvc0 pax_nouderef BOOT_IMAGE=/boot/vmlinuz-virthardened
initrd /boot/initramfs-virthardened
EOF

ln -s /mnt/target/boot/grub/grub.conf /mnt/target/boot/grub/menu.lst
</pre>

= Create the AMI =
The following will need to be done in the AWS console.

# Detach the new volume (make note of the volume ID)
# Launch a new instance, use the defaults; you are going to cannibalize it in a moment
# Once the instance starts, stop but do not terminate it
# Under EBS, detach the existing volume, and attach the Alpine Linux volume as {{Path|/dev/xvda}} (for HVM) or {{Path|/dev/sda1}} (for PV)
# Restart the instance
# Log in and make sure it works
# Do any final cleanups necessary. Only make changes appropriate for an AMI, you are going to snapshot this instance and use it as the base for the AMI.
# Stop but do not terminate the instance
# Right click the stopped instance and choose 'Create Image (EBS AMI)'
# Once the AMI creation finishes you can cleanup the instances and EBS volumes used

[[Category:Virtualization]]

Alpine Install: from a iso to a virtualbox machine with external disc

2022-01-06T17:16:45Z

Mckaygerhard: remove newbie reference to stop the discussion

'''Overall description:''' Alpine Installation from a official disc/iso downloaded to a real hard disk by the usage of VirtualBox machine as the real machine, where will be single OS only.

This document will guide you to '''install Alpine into a real hard disk device but through the VirtualBox virtual machine acting as real machine''', use if want to install to a real hard disk device externally but no way to boot it so can use in VirtualBox virtual machine .

== Terminology ==

* '''Host machine''': will be your real machine with installed operating system that have installed the VirtualBox software and "will host" the target operating system, in that case Alpine.
* '''Guest machine''': will be your target machine where Alpine will be installed, emulated by the host operating system using the VirtualBox software installed in the real machine.
* '''Reserved RAM''': will be the amount of RAM that will be need to share exclusively to the virtual machine created by the VirtualBox software in the host machine, stolen from the real RAM.
* '''External disc''': will be the storage medium device attached as target for the emulated machine or "guest machine", where the Alpine will be installed.

== Requirements ==

* In the host machine we need installed the <code>virtualbox</code> program from VirtualBox software
* In the host machine we need at least 1Gb of RAM, recommended 2Gb of RAM installed
* The guest machine need 512Mb RAM, but recommended 1Gb reserved if desktop software will be installed
* In the host machine we need installed <code>wget</code> or a web browser to download install medium

== Preparing the medium origin to install ==

Download the source medium to install and put into your home, there's more hardware medium sources to download, like the '''[https://en.wikipedia.org/wiki/Linux_on_z_Systems s390x]''' and '''[https://en.wikipedia.org/wiki/Ppc64 ppc64le]''', but due VirtualBox only emulates '''x86''', '''x64''' and '''arm''' hardware only, will list those here.

The source medium to install will be as following format: '''<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-netboot-<VERSION>.0-<ARCH>.iso</code>''' where <code>ARCH</code> and <code>VERSION</code> could be the following for VirtualBox virtual machines:

* <code><ARCH></code> will be
** '''x86''': The popular i386/i686 compatible 32-bit x86 based machines, i386 recommended for olders.
** '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines, recommended for newer/lasted hardware.
* <code><VERSION></code> will be
** '''latest-stable''' for a more up to date without taking care of numbered
** '''3.10''' the most recommended for machines between 2016 to 2018

'''So using 3.10 version and i386 flavor the available links to download will be:''' <code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

'''Graphical download''': Just point the web browser to that url and the download of the iso file will start. A file with '''.iso''' extension type, with name like <code>"alpine-standard-3.10.0-x86_64.iso"</code> will be downloaded commonly into the Download directory of your home documents filesystem.

'''Command line method''': in unix-like terminal execute: <code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>, and where you run the command, in that place/dir will be downloaded the file.

== Preparing the medium target to install ==

Please take care of your attached devices.. for best care results only use those involved in the process, so only put the disc (that can be a USB flash, MMC card or external drive) attached, and remove all others that will no to be use. '''We will assume only one internal disc (that obviously cannot be removed) and one external disk attached'''.

The external disc will be detected and the operating system will create a new device representation, such like <code>/dev/sdb</code> commonly. In Linux systems you can detect the recently attached disk with following command:

<code>/bin/dmesg | tail -n 50| grep 'Attached SCSI' | cut -d' ' -f4</code>

This will output <code>[sde]</code> for our example installation. Caution due that previously command only will work if you recently attached the new external disk where the system will be installed.

Later with the detection of the disk, create the representation for the VirtualBox virtual machine, the detection will be put in <code>/dev/</code> parameter.. so if the disk was detect as <code>[sde]</code> you must use it without <nowiki>"["/"]"</nowiki> sings, the command for creating the virtual disk will be:

<code>VBoxManage internalcommands createrawvmdk -rawdisk /dev/sde -filename $HOME/rawdisk-sdb.vmdk</code>

{{Tip|in Linux if you don't have "disk" group access need to perform permission to device to 666, so take care of}}

{{Warning|We assume there are only two disk, the internal and the external, here detected as <nowiki>[sde]</nowiki> for practical reasons, commonly will be detected as <nowiki>[sdb]</nowiki>}}

== Preparing the virtual machine to install ==

Start the VirtualBox software program.

# In the main window '''create a new virtual machine''' by '''clicking the blue spark New button'''. Will open a new window with the following questions:
## Will ask for a '''name for the virtual like "alpine-desktop-try1"'''.
## The Type of the '''Operating system choose "linux"'''
## The version '''choose "other linux"''' and must match with the <code><ARCH></code> choosed (like x86)
## By push "Next" button to continue to create the machine
# Second are RAM of the virtual machine, choose '''memory as 512MB''' minimum amount of. and push "Next" button.
# A new windows with a '''Hard disk assistant will opened'''
## First choose the option '''"Choose a existing hard disk drive"''' and push the "Folder button" aside.
## An open file dialog window will be opened, '''search for the "VMDK" file <code>rawdisk-sdb.vmdk</code>and choose it'''
## Choose the '''dynamically allocated''' and push the "Next" button.
## By push on "Create" the virtual machine will be ready to use
# Now the main window show you the "alpine-desktop-try1" created virtual machine, select them
## By push on "Configuration" yellow button go to the storage part and push it over
## Select the disc drive icon for CD/DVD rom and push on the again CD/DVD drive icon at the right
## Mini menu will opened, choose to select and external file event the host CD/DVD drive
## A file open dialog will open.. search to the downloaded iso of Alpine and select it
## Once defined the iso file to boot, push on the "Ok" button and virtual machines are finished.
# Push on the green arrow that said "Start" to start the virtual machine and boot up the iso

[[File:Alpine Install from a disc to a virtualbox machine single only-01-0.png|center|Alpine configuration commonly used of a virtual machine on virtual box virtual machine]]

== Booting the Alpine ISO disc ==

When the machine start, you must be sure to choose the Optical drive (commonly named CD/DVD Rom drive), so the disc/iso will boot and after a while a command line shell will show you:

{{Tip|If your system are not configure to boot from a CD/DVD drive must be configure in the BIOS, ask to your vendor or technical support, VirtualBox need to hit the F12 key to choose boot medium}}

[[File:Installation-alpine-alpine-setup-2-boot.png|350px|thumb|right|Installation : setup-alpine : booting process until login prompt]]

TODO: restore original template of normal steps here! (inclusions)

== Finishing the installation ==

After al the scripts setup ends, a "reboot" will be offered, just type "reboot" and press enter, remobe the boot media and new installed system will be booted.

[[File:Installation-alpine-alpine-setup-9-setup-disk-3-7end.png]]

If you try to start that installation maybe '''you cannot see a graphical window system? take easy''' and get calm down.. in Alpine all are made by the right way.. so '''if user need a desktop.. user can install a desktop''' follow the next: Alpine newbie packages or bypass and go directly to Alpine newbie desktops

= Documents series =

{| class="wikitable"
|-
! Previous required !! What's next to read
|-
| [[Alpine newbie install manual]] || Alpine newbie packages
|}

= See Also =

# [[Alpine newbie developer]]
# [[Alpine newbie lammers]]

[[Category:Newbie]]

Alpine Install: from a disc to a virtualbox machine single only

2022-01-06T17:16:02Z

Mckaygerhard: remove newbie reference to stop the discussion

'''Overall description:''' Installing Alpine from an official disc image to a VirtualBox machine.

This document guides you through installing Alpine on a VirtualBox VM - this is ideal if you only want to try out Alpine.

== Terminology ==

* '''Host machine''': the machine you're running VirtualBox on. It will "host" the target virtual machine.
* '''Guest machine''': your target machine where Alpine will be installed, executed by the VirtualBox software on the host machine.
* '''Reserved RAM''': the amount of host machine RAM that will be needed for exclusive use by the guest machine. The host machine cannot use this RAM while the guest machine is running.
* '''Virtual disc''': the emulated storage medium attached to the guest machine. Usually it is a file (or several files) which VirtualBox presents as a disk to the guest OS (Alpine).

== Requirements ==

On the host machine:

* Qemu or VirtualBox using package manager! Do not promote Oracle's policy of overversiones without security patches
* At least 1GB of RAM, 2GB or more if you don't want lockups while running something in addition to the virtual machine software
* The <code>curl</code> or <code>wget</code> programs to download the image to boot in the virtual software

On the guest machine:

* Minimum 512Mb RAM, but 1Gb or more is recommended if you're going to use a graphical interface. That obviouly must be in sync with the host machine.

== Preparing the medium to install ==

Download the source medium to install and put into your home; there's more hardware medium sources to download, like the '''[https://en.wikipedia.org/wiki/Linux_on_z_Systems s390x]''' and '''[https://en.wikipedia.org/wiki/Ppc64 ppc64le]''', but because VirtualBox handles only '''x86''' and '''x64'''
hardware, we will list those here

The name of the source medium to install will be in the following format: '''<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>''' where <code>ARCH</code> and <code>VERSION</code> can be one of the following, for VirtualBox virtual machines:

* <code><ARCH></code> can be
** '''x86''': The well known i386 to i686. (32-bit machines)
** '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines.
* <code><VERSION></code> can be
** '''latest-stable''' as the name says, the latest, stable version
** '''3.10''' UEFI support began with this version
** '''3.8''' recommended for machines manufactured between 2012 and 2016
** '''3.6''' recommended for older machines

Typically, the version most commonly used in a virtual box is the x86. The hardware is cheaper and operation does not consume a lot of memory.
The iso download URL format is:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' will be:
<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

'''Graphical download''': Just point the web browser to that URL and the download will start. A file with '''.iso''' extension type, with a name like <code>"alpine-standard-3.10.0-x86.iso"</code> (if i386/686); will be downloaded into the directory specified in your browser configuration.

'''Command line method''': just open a terminal and execute: <code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>, for example:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' the command will be:
<code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

You must be mindful of the directory you run the command from, as that is where the file will be saved.

== Preparing the virtual machine to install ==

Start the VirtualBox software program.

# In the main window '''create a new virtual machine''' by '''clicking the blue spark New button'''. That will open a new window with the following questions:
## It will ask for a '''name for the virtual like "alpine-desktop-try1"'''.
## The Type of the '''Operating system choose "linux"'''.
## The version '''choose "other linux"'''. It must match the chosen <code><ARCH></code> (e.g. x86).
## Click the "Next" button to continue creating the virtual machine.
# When selecting the amount of RAM for the virtual machine, choose a minimum of '''512MB''' then click the "Next" button.
# A new window with a '''Hard disk assistant will open'''.
## First choose '''"Create a virtual hard disk now"''' then click the "Create" button.
## Next choose the option for '''hard disk type: VDI''' and push "Next" button.
## Choose '''dynamically allocated''' then click the "Next" button.
## The next window will offer the '''size of virtual disk. 4GB''', however, you may choose a different amount of storage space.
## After clicking on "Create" the virtual machine will be ready to use.
# Now the main window shows you the "alpine-desktop-try1" virtual machine, select it.
## Click on the yellow "Configuration" button. Go to the storage menu and pull it down.
## Select the disc drive icon for CD/DVD ROM and click on the CD/DVD drive icon at the right.
## A Mini menu will open. Select an external file event the host CD/DVD drive.
## A file open dialog will open. Search for the downloaded Alpine iso and select it.
## Once you choose the iso file to boot, click the "Ok" button to finish creating the virtual machine.
# Click the green "Start" arrow to start the virtual machine and boot the iso.

[[File:Alpine Install from a disc to a virtualbox machine single only-01-0.png|center|Alpine configuration commonly used of a virtual machine on virtual box virtual machine]]

== Booting the Alpine ISO disc ==

When the machine starts, you must be sure to choose the Optical drive (commonly named CD/DVD ROM drive), so the disc/iso will boot. After a while, a command line shell will show you

[[File:Installation-alpine-alpine-setup-2-boot.png|350px|thumb|right|Installation : setup-alpine : booting process until login prompt]]

TODO restore the inclusion of template inclkude pages here, were edited and now does not have any sense respect this guide..

== Finishing the installation ==

After setup ends, a "reboot" will be offered. Type "reboot" and press enter and your newly installed virtual machine will be booted. Don't forget to remove the boot medium.

[[File:Installation-alpine-alpine-setup-9-setup-disk-3-7end.png]]

'''You cannot see a graphical window system? No problem.''' With Alpine, GUIs are made the right way. So '''if you need a desktop, you can install a desktop''' follow this link: Alpine newbie packages or go directly to [[Alpine newbie desktops]]

= Documents series =

{| class="wikitable"
|-
! Previous required !! What's next to read
|-
| [[Alpine newbie install manual]] || Alpine newbie packages
|}

= See Also =

# [[Alpine newbie developer]]
# [[Alpine newbie lammers]]

[[Category:Newbie]]

Alpine Install: from a disc to a any computer single only boot

2022-01-06T17:15:13Z

Mckaygerhard: remove newbie reference to stop the discussion

{{Delete|there are other wiki pages with similar or same information, the proposal and idea of newbie pages was specific cases but now there are too mixed pages with same information DUE LACK OF COORDINATION, so the best is to delete this content}}

'''Overall description:''' Alpine Installation from a official disc/iso burned into DVD/CD to a new computer with or without [[Alpine and UEFI|UEFI]] and will be single only boot, it's means that any thing in the computer and their disc will be erased to put Alpine Linux as main system

This document will guide you to '''install Alpine into a new empty or just fresh PC or Laptop hardware computer, use if you have a [[Alpine and UEFI|BIOS or UEFI based hardware]] and only wants Alpine Linux into it.

== Terminology ==

* '''[[Alpine and UEFI|UEFI]]''': it's a new system included in every new hardware machine laptop or desktops, that will manage the early boot process as a little operating system, see more in the [[Alpine and UEFI]] page.
* '''New machine''': will be your real machine fresh and ready to install your new Alpine operating system, with a installed CD/DVD Rom optical drive where to put the burned downloaded disc media installation.
* '''Optical drive''': will be your hardware drive input to put the burned downloaded iso media with the operating system Alpine to install as source media; this drive are commonly named [https://en.wikipedia.org/wiki/CD-ROM DVD/CD Rom] unit.
* '''Source media''': will be the just burned/ disc from the downloaded iso file of Alpine operating system. Will be put into the optical drive or named [https://en.wikipedia.org/wiki/CD-ROM DVD/CD Rom] to property boot the source disc as media installation.
* '''Target media''': will be the storage medium device into the new computer target where the Alpine files for operating system will be installed, its one partition from the [https://en.wikipedia.org/wiki/Hard_disk_drive HardDisk] of the new computer.

== Requirements ==

* A blank disc (CD blank or DVD blank or BR blank) to just burn/record the source media file downloaded
* In the new machine we need optical drive as input source media
* In the new machine we need at least 512Mb of RAM, but required 2Gb of RAM for desktop/graphical applications
* In the new machine we need target media with at least 2G of hard disk, but required 10G for desktops
* Will need to previously downloaded and burned the Source media ISO file from https://alpinelinux.org/downloads/

== Preparing the source medium to install ==

Download the source medium to install and put into your home documents in a modern computer. There are more hardware medium sources to download, like the arm and i386, but ISO CD/DVD images are only to PC/Laptops that are i386 and amd64, so by downloading the x86 (32bit) flavor will be same for both cases, but UEFI need 64bit, so change to the x86_64 (amd64) if your computer is the most modern and lasted hardware.

The source medium to install for [[Alpine and UEFI|UEFI or '''modern hardware''']] '''are just 64-bit only''', the download URL will be as following format: <code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code> where <code>ARCH</code> and <code>VERSION</code> could be:

* <code><ARCH></code> will be
** '''x86''': the most used i386 32-bit x86 based machines, if your computer are too older use this only.
** '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines, i386 are not recommended for newer/lasted hardware.
** '''s390x''': For the Super powered IBM mainframes, especially IBM Z and IBM LinuxONE servers.
** '''ppc64le''': For the PowerPC devices with pure little-endian mode, mostly for POWER8 and POWER9
* <code><VERSION></code> will be
** '''latest-stable''' for a more up to date without taking care of numbered
** '''3.10''' the most recommended for machines between 2016 to 2018

'''So using 3.10 version the available links to download will be:'''
* '''x86_64''': <code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86_64/alpine-standard-3.10.0-x86_64.iso</nowiki></code>
* '''s390x''': <code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/ppc64le/alpine-standard-3.10.1-ppc64le.iso</nowiki></code>
* '''ppc64le''': <code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/ppc64le/alpine-standard-3.10.1-ppc64le.iso</nowiki></code>

'''Graphical download''': Just point the web browser to that url and the download of the iso file will start. A file with '''.iso''' extension type, with name like <code>"alpine-standard-3.10.0-x86_64.iso"</code> (if amd64) or like <code>alpine-standard-3.10.1-s390x.iso</code> (if s390x); will be downloaded commonly into the Download directory of your home documents filesystem.

'''Command line method''': in unix-like terminal execute: <code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86_64/alpine-standard-3.10.0-x86_64.iso</nowiki></code>, and where you run the command, in that place/dir will be downloaded the file.

== Burning the source medium to install ==

After downloading the source media file from [https://alpinelinux.org/downloads/ Alpine download page] ''' put the blank disc into the input optical drive''' named [https://en.wikipedia.org/wiki/CD-ROM DVD/CD Rom] and '''open your CD/DVD recording program, choose to "burn from iso file"''' and wait the process will end.

In detail if you downloaded with '''Graphical download''' (using a web browser), the source media file will be into the Download directory. If you downloaded with '''Command line method''' your source file probably will be in your root document home (or just <code>$HOME</code> of your Linux install or MAC install filesystem).

In Linux, assuming the blank disc is in the optical drive, the command to record/burn the downloaded source media file is :

<code>$ umount /dev/sr0;cdrecord -v -sao dev=/dev/sr0 alpine-standard-3.10.0-x86_64.iso</code>

If your blank media is a DVD or BD disc the command will be then :

<code>$ umount /dev/sr0;growisofs -dvd-compat -Z /dev/sr0=alpine-standard-3.10.0-x86_64.iso</code>

{{Note|growisofs has a small bug with blank BD-R media. It issues an error message after the burning is complete. Programs like k3b then believe the whole burn run failed.}}

== Booting the Alpine ISO disc ==

When the machine start, you must be sure to choose the optical drive (commonly named CD/DVD Rom drive), so the disc/iso will boot and after a while a command line shell will show you:

{{Tip|If your system is not configured to boot from a CD/DVD drive, it must be configured in the BIOS, '''ask/search to your vendor or technical support''', Toshiba computers need to hit F1 to choose boot medium, DELL must hit F11 to choose medium for example, and so and so}}

[[File:Installation-alpine-alpine-setup-2-boot.png|350px|thumb|right|Installation : setup-alpine : booting process until login prompt]]

TODO: restore the template about normal script steps for common pages (was inclusion here)

== Finishing the installation ==

After all of the scripts in the setup end, a "reboot" will be offered, just type "reboot" and press enter, remove the boot media and newly installed system will be booted.

[[File:Installation-alpine-alpine-setup-9-setup-disk-3-7end.png]]

'''You cannot see a graphical window system? take it easy''' and get calmed down.. in Alpine all are made by the right way.. so '''if user need a desktop.. user can install a desktop'''

= Documents series =

{| class="wikitable"
|-
! Previous required !! What's next to read
|-
| [[Alpine newbie install manual]] || Alpine newbie packages
|}

= See Also =

# [[Alpine newbie developer]]
# [[Alpine newbie lammers]]

[[Category:Newbie]]

Alpine Install: from a iso to a virtualbox machine with external disc

2022-01-06T17:14:02Z

Mckaygerhard: remove newbie reference to stop the discussion

'''Overall description:''' Alpine Installation from a official disc/iso downloaded to a real hard disk by the usage of VirtualBox machine as the real machine, where will be single OS only.

This document will guide you to '''install Alpine into a real hard disk device but through the VirtualBox virtual machine acting as real machine''', use if want to install to a real hard disk device externally but no way to boot it so can use in VirtualBox virtual machine .

== Terminology ==

* '''Host machine''': will be your real machine with installed operating system that have installed the VirtualBox software and "will host" the target operating system, in that case Alpine.
* '''Guest machine''': will be your target machine where Alpine will be installed, emulated by the host operating system using the VirtualBox software installed in the real machine.
* '''Reserved RAM''': will be the amount of RAM that will be need to share exclusively to the virtual machine created by the VirtualBox software in the host machine, stolen from the real RAM.
* '''External disc''': will be the storage medium device attached as target for the emulated machine or "guest machine", where the Alpine will be installed.

== Requirements ==

* In the host machine we need installed the <code>virtualbox</code> program from VirtualBox software
* In the host machine we need at least 1Gb of RAM, recommended 2Gb of RAM installed
* The guest machine need 512Mb RAM, but recommended 1Gb reserved if desktop software will be installed
* In the host machine we need installed <code>wget</code> or a web browser to download install medium

== Preparing the medium origin to install ==

Download the source medium to install and put into your home, there's more hardware medium sources to download, like the '''[https://en.wikipedia.org/wiki/Linux_on_z_Systems s390x]''' and '''[https://en.wikipedia.org/wiki/Ppc64 ppc64le]''', but due VirtualBox only emulates '''x86''', '''x64''' and '''arm''' hardware only, will list those here.

The source medium to install will be as following format: '''<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-netboot-<VERSION>.0-<ARCH>.iso</code>''' where <code>ARCH</code> and <code>VERSION</code> could be the following for VirtualBox virtual machines:

* <code><ARCH></code> will be
** '''x86''': The popular i386/i686 compatible 32-bit x86 based machines, i386 recommended for olders.
** '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines, recommended for newer/lasted hardware.
* <code><VERSION></code> will be
** '''latest-stable''' for a more up to date without taking care of numbered
** '''3.10''' the most recommended for machines between 2016 to 2018

'''So using 3.10 version and i386 flavor the available links to download will be:''' <code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

'''Graphical download''': Just point the web browser to that url and the download of the iso file will start. A file with '''.iso''' extension type, with name like <code>"alpine-standard-3.10.0-x86_64.iso"</code> will be downloaded commonly into the Download directory of your home documents filesystem.

'''Command line method''': in unix-like terminal execute: <code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>, and where you run the command, in that place/dir will be downloaded the file.

== Preparing the medium target to install ==

Please take care of your attached devices.. for best care results only use those involved in the process, so only put the disc (that can be a USB flash, MMC card or external drive) attached, and remove all others that will no to be use. '''We will assume only one internal disc (that obviously cannot be removed) and one external disk attached'''.

The external disc will be detected and the operating system will create a new device representation, such like <code>/dev/sdb</code> commonly. In Linux systems you can detect the recently attached disk with following command:

<code>/bin/dmesg | tail -n 50| grep 'Attached SCSI' | cut -d' ' -f4</code>

This will output <code>[sde]</code> for our example installation. Caution due that previously command only will work if you recently attached the new external disk where the system will be installed.

Later with the detection of the disk, create the representation for the VirtualBox virtual machine, the detection will be put in <code>/dev/</code> parameter.. so if the disk was detect as <code>[sde]</code> you must use it without <nowiki>"["/"]"</nowiki> sings, the command for creating the virtual disk will be:

<code>VBoxManage internalcommands createrawvmdk -rawdisk /dev/sde -filename $HOME/rawdisk-sdb.vmdk</code>

{{Tip|in Linux if you don't have "disk" group access need to perform permission to device to 666, so take care of}}

{{Warning|We assume there are only two disk, the internal and the external, here detected as <nowiki>[sde]</nowiki> for practical reasons, commonly will be detected as <nowiki>[sdb]</nowiki>}}

== Preparing the virtual machine to install ==

Start the VirtualBox software program.

# In the main window '''create a new virtual machine''' by '''clicking the blue spark New button'''. Will open a new window with the following questions:
## Will ask for a '''name for the virtual like "alpine-desktop-try1"'''.
## The Type of the '''Operating system choose "linux"'''
## The version '''choose "other linux"''' and must match with the <code><ARCH></code> choosed (like x86)
## By push "Next" button to continue to create the machine
# Second are RAM of the virtual machine, choose '''memory as 512MB''' minimum amount of. and push "Next" button.
# A new windows with a '''Hard disk assistant will opened'''
## First choose the option '''"Choose a existing hard disk drive"''' and push the "Folder button" aside.
## An open file dialog window will be opened, '''search for the "VMDK" file <code>rawdisk-sdb.vmdk</code>and choose it'''
## Choose the '''dynamically allocated''' and push the "Next" button.
## By push on "Create" the virtual machine will be ready to use
# Now the main window show you the "alpine-desktop-try1" created virtual machine, select them
## By push on "Configuration" yellow button go to the storage part and push it over
## Select the disc drive icon for CD/DVD rom and push on the again CD/DVD drive icon at the right
## Mini menu will opened, choose to select and external file event the host CD/DVD drive
## A file open dialog will open.. search to the downloaded iso of Alpine and select it
## Once defined the iso file to boot, push on the "Ok" button and virtual machines are finished.
# Push on the green arrow that said "Start" to start the virtual machine and boot up the iso

[[File:Alpine Install from a disc to a virtualbox machine single only-01-0.png|center|Alpine configuration commonly used of a virtual machine on virtual box virtual machine]]

== Booting the Alpine ISO disc ==

When the machine start, you must be sure to choose the Optical drive (commonly named CD/DVD Rom drive), so the disc/iso will boot and after a while a command line shell will show you:

{{Tip|If your system are not configure to boot from a CD/DVD drive must be configure in the BIOS, ask to your vendor or technical support, VirtualBox need to hit the F12 key to choose boot medium}}

[[File:Installation-alpine-alpine-setup-2-boot.png|350px|thumb|right|Installation : setup-alpine : booting process until login prompt]]

TODO: restore original template of normal steps here! (inclusions)

== Finishing the installation ==

After al the scripts setup ends, a "reboot" will be offered, just type "reboot" and press enter, remobe the boot media and new installed system will be booted.

[[File:Installation-alpine-alpine-setup-9-setup-disk-3-7end.png]]

If you try to start that installation maybe '''you cannot see a graphical window system? take easy''' and get calm down.. in Alpine all are made by the right way.. so '''if user need a desktop.. user can install a desktop''' follow the next: [[Alpine newbie packages]] or bypass and go directly to [[Alpine newbie desktops]]

= Documents series =

{| class="wikitable"
|-
! Previous required !! What's next to read
|-
| [[Alpine newbie install manual]] || [[Alpine newbie packages]]
|}

= See Also =

# [[Alpine newbie packages]]
# [[Alpine newbie desktops]]
# [[Alpine newbie developer]]
# [[Alpine newbie lammers]]

[[Category:Newbie]]

Alpine Install: from a disc to a virtualbox machine single only

2022-01-06T17:12:54Z

Mckaygerhard: remove newbie reference to stop the discussion

'''Overall description:''' Installing Alpine from an official disc image to a VirtualBox machine.

This document guides you through installing Alpine on a VirtualBox VM - this is ideal if you only want to try out Alpine.

== Terminology ==

* '''Host machine''': the machine you're running VirtualBox on. It will "host" the target virtual machine.
* '''Guest machine''': your target machine where Alpine will be installed, executed by the VirtualBox software on the host machine.
* '''Reserved RAM''': the amount of host machine RAM that will be needed for exclusive use by the guest machine. The host machine cannot use this RAM while the guest machine is running.
* '''Virtual disc''': the emulated storage medium attached to the guest machine. Usually it is a file (or several files) which VirtualBox presents as a disk to the guest OS (Alpine).

== Requirements ==

On the host machine:

* Qemu or VirtualBox using package manager! Do not promote Oracle's policy of overversiones without security patches
* At least 1GB of RAM, 2GB or more if you don't want lockups while running something in addition to the virtual machine software
* The <code>curl</code> or <code>wget</code> programs to download the image to boot in the virtual software

On the guest machine:

* Minimum 512Mb RAM, but 1Gb or more is recommended if you're going to use a graphical interface. That obviouly must be in sync with the host machine.

== Preparing the medium to install ==

Download the source medium to install and put into your home; there's more hardware medium sources to download, like the '''[https://en.wikipedia.org/wiki/Linux_on_z_Systems s390x]''' and '''[https://en.wikipedia.org/wiki/Ppc64 ppc64le]''', but because VirtualBox handles only '''x86''' and '''x64'''
hardware, we will list those here

The name of the source medium to install will be in the following format: '''<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>''' where <code>ARCH</code> and <code>VERSION</code> can be one of the following, for VirtualBox virtual machines:

* <code><ARCH></code> can be
** '''x86''': The well known i386 to i686. (32-bit machines)
** '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines.
* <code><VERSION></code> can be
** '''latest-stable''' as the name says, the latest, stable version
** '''3.10''' UEFI support began with this version
** '''3.8''' recommended for machines manufactured between 2012 and 2016
** '''3.6''' recommended for older machines

Typically, the version most commonly used in a virtual box is the x86. The hardware is cheaper and operation does not consume a lot of memory.
The iso download URL format is:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' will be:
<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

'''Graphical download''': Just point the web browser to that URL and the download will start. A file with '''.iso''' extension type, with a name like <code>"alpine-standard-3.10.0-x86.iso"</code> (if i386/686); will be downloaded into the directory specified in your browser configuration.

'''Command line method''': just open a terminal and execute: <code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>, for example:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' the command will be:
<code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

You must be mindful of the directory you run the command from, as that is where the file will be saved.

== Preparing the virtual machine to install ==

Start the VirtualBox software program.

# In the main window '''create a new virtual machine''' by '''clicking the blue spark New button'''. That will open a new window with the following questions:
## It will ask for a '''name for the virtual like "alpine-desktop-try1"'''.
## The Type of the '''Operating system choose "linux"'''.
## The version '''choose "other linux"'''. It must match the chosen <code><ARCH></code> (e.g. x86).
## Click the "Next" button to continue creating the virtual machine.
# When selecting the amount of RAM for the virtual machine, choose a minimum of '''512MB''' then click the "Next" button.
# A new window with a '''Hard disk assistant will open'''.
## First choose '''"Create a virtual hard disk now"''' then click the "Create" button.
## Next choose the option for '''hard disk type: VDI''' and push "Next" button.
## Choose '''dynamically allocated''' then click the "Next" button.
## The next window will offer the '''size of virtual disk. 4GB''', however, you may choose a different amount of storage space.
## After clicking on "Create" the virtual machine will be ready to use.
# Now the main window shows you the "alpine-desktop-try1" virtual machine, select it.
## Click on the yellow "Configuration" button. Go to the storage menu and pull it down.
## Select the disc drive icon for CD/DVD ROM and click on the CD/DVD drive icon at the right.
## A Mini menu will open. Select an external file event the host CD/DVD drive.
## A file open dialog will open. Search for the downloaded Alpine iso and select it.
## Once you choose the iso file to boot, click the "Ok" button to finish creating the virtual machine.
# Click the green "Start" arrow to start the virtual machine and boot the iso.

[[File:Alpine Install from a disc to a virtualbox machine single only-01-0.png|center|Alpine configuration commonly used of a virtual machine on virtual box virtual machine]]

== Booting the Alpine ISO disc ==

When the machine starts, you must be sure to choose the Optical drive (commonly named CD/DVD ROM drive), so the disc/iso will boot. After a while, a command line shell will show you

[[File:Installation-alpine-alpine-setup-2-boot.png|350px|thumb|right|Installation : setup-alpine : booting process until login prompt]]

TODO restore the inclusion of template inclkude pages here, were edited and now does not have any sense respect this guide..

== Finishing the installation ==

After setup ends, a "reboot" will be offered. Type "reboot" and press enter and your newly installed virtual machine will be booted. Don't forget to remove the boot medium.

[[File:Installation-alpine-alpine-setup-9-setup-disk-3-7end.png]]

'''You cannot see a graphical window system? No problem.''' With Alpine, GUIs are made the right way. So '''if you need a desktop, you can install a desktop''' follow this link: [[Alpine newbie packages]] or go directly to [[Alpine newbie desktops]]

= Documents series =

{| class="wikitable"
|-
! Previous required !! What's next to read
|-
| [[Alpine newbie install manual]] || [[Alpine newbie packages]]
|}

= See Also =

# [[Alpine newbie developer]]
# [[Alpine newbie lammers]]

[[Category:Newbie]]

Desktop environments and Window managers

2022-01-06T17:10:20Z

Mckaygerhard: remove newbie reference to stop the discussion

{{TOC right}}

'''Alpine Linux''' has no official desktop. Older versions used Xfce, but now, all GUI and graphical interfaces are optional. many are available and is attempted to be listed below:

== Desktop environments ==

# [[Xfce]]
# [[LXQt]]
# [[KDE|KDE Plasma]]
# [[Gnome]]
# [[MATE]]

== [https://en.wikipedia.org/wiki/Stacking_window_manager Stacking (floating) window managers] ==

* [[Openbox]]

== [https://en.wikipedia.org/wiki/Tiling_window_manager Tiling (dynamic) window managers] ==

* [[Dwm]]

* [[AwesomeWM|Awesome Window Manager]]

== See Also ==

* [[Fonts]]

[[Category:Desktop]]

Alpine Install: from a disc to a virtualbox machine single only

2022-01-06T16:16:49Z

Mckaygerhard: add a WIP note due now the pages i were used does not have logical info for use here

'''Overall description:''' Installing Alpine from an official disc image to a VirtualBox machine.

This document guides you through installing Alpine on a VirtualBox VM - this is ideal if you only want to try out Alpine.

== Terminology ==

* '''Host machine''': the machine you're running VirtualBox on. It will "host" the target virtual machine.
* '''Guest machine''': your target machine where Alpine will be installed, executed by the VirtualBox software on the host machine.
* '''Reserved RAM''': the amount of host machine RAM that will be needed for exclusive use by the guest machine. The host machine cannot use this RAM while the guest machine is running.
* '''Virtual disc''': the emulated storage medium attached to the guest machine. Usually it is a file (or several files) which VirtualBox presents as a disk to the guest OS (Alpine).

== Requirements ==

On the host machine:

* Qemu or VirtualBox using package manager! Do not promote Oracle's policy of overversiones without security patches
* At least 1GB of RAM, 2GB or more if you don't want lockups while running something in addition to the virtual machine software
* The <code>curl</code> or <code>wget</code> programs to download the image to boot in the virtual software

On the guest machine:

* Minimum 512Mb RAM, but 1Gb or more is recommended if you're going to use a graphical interface. That obviouly must be in sync with the host machine.

== Preparing the medium to install ==

Download the source medium to install and put into your home; there's more hardware medium sources to download, like the '''[https://en.wikipedia.org/wiki/Linux_on_z_Systems s390x]''' and '''[https://en.wikipedia.org/wiki/Ppc64 ppc64le]''', but because VirtualBox handles only '''x86''' and '''x64'''
hardware, we will list those here

The name of the source medium to install will be in the following format: '''<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>''' where <code>ARCH</code> and <code>VERSION</code> can be one of the following, for VirtualBox virtual machines:

* <code><ARCH></code> can be
** '''x86''': The well known i386 to i686. (32-bit machines)
** '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines.
* <code><VERSION></code> can be
** '''latest-stable''' as the name says, the latest, stable version
** '''3.10''' UEFI support began with this version
** '''3.8''' recommended for machines manufactured between 2012 and 2016
** '''3.6''' recommended for older machines

Typically, the version most commonly used in a virtual box is the x86. The hardware is cheaper and operation does not consume a lot of memory.
The iso download URL format is:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' will be:
<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

'''Graphical download''': Just point the web browser to that URL and the download will start. A file with '''.iso''' extension type, with a name like <code>"alpine-standard-3.10.0-x86.iso"</code> (if i386/686); will be downloaded into the directory specified in your browser configuration.

'''Command line method''': just open a terminal and execute: <code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>, for example:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' the command will be:
<code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

You must be mindful of the directory you run the command from, as that is where the file will be saved.

== Preparing the virtual machine to install ==

Start the VirtualBox software program.

# In the main window '''create a new virtual machine''' by '''clicking the blue spark New button'''. That will open a new window with the following questions:
## It will ask for a '''name for the virtual like "alpine-desktop-try1"'''.
## The Type of the '''Operating system choose "linux"'''.
## The version '''choose "other linux"'''. It must match the chosen <code><ARCH></code> (e.g. x86).
## Click the "Next" button to continue creating the virtual machine.
# When selecting the amount of RAM for the virtual machine, choose a minimum of '''512MB''' then click the "Next" button.
# A new window with a '''Hard disk assistant will open'''.
## First choose '''"Create a virtual hard disk now"''' then click the "Create" button.
## Next choose the option for '''hard disk type: VDI''' and push "Next" button.
## Choose '''dynamically allocated''' then click the "Next" button.
## The next window will offer the '''size of virtual disk. 4GB''', however, you may choose a different amount of storage space.
## After clicking on "Create" the virtual machine will be ready to use.
# Now the main window shows you the "alpine-desktop-try1" virtual machine, select it.
## Click on the yellow "Configuration" button. Go to the storage menu and pull it down.
## Select the disc drive icon for CD/DVD ROM and click on the CD/DVD drive icon at the right.
## A Mini menu will open. Select an external file event the host CD/DVD drive.
## A file open dialog will open. Search for the downloaded Alpine iso and select it.
## Once you choose the iso file to boot, click the "Ok" button to finish creating the virtual machine.
# Click the green "Start" arrow to start the virtual machine and boot the iso.

[[File:Alpine Install from a disc to a virtualbox machine single only-01-0.png|center|Alpine configuration commonly used of a virtual machine on virtual box virtual machine]]

== Booting the Alpine ISO disc ==

When the machine starts, you must be sure to choose the Optical drive (commonly named CD/DVD ROM drive), so the disc/iso will boot. After a while, a command line shell will show you

[[File:Installation-alpine-alpine-setup-2-boot.png|350px|thumb|right|Installation : setup-alpine : booting process until login prompt]]

TODO restore the inclusion of template inclkude pages here, were edited and now does not have any sense respect this guide..

== Finishing the installation ==

After setup ends, a "reboot" will be offered. Type "reboot" and press enter and your newly installed virtual machine will be booted. Don't forget to remove the boot medium.

[[File:Installation-alpine-alpine-setup-9-setup-disk-3-7end.png]]

'''You cannot see a graphical window system? No problem.''' With Alpine, GUIs are made the right way. So '''if you need a desktop, you can install a desktop''' follow this link: [[Alpine newbie apk packages]] or go directly to [[Alpine newbie desktops]]

= Documents series =

{| class="wikitable"
|-
! Previous required !! What's next to read
|-
| [[Alpine newbie install manual]] || [[Alpine newbie packages]]
|}

= See Also =

# [[Alpine newbie packages]]
# [[Alpine newbie desktops]]
# [[Alpine newbie developer]]
# [[Alpine newbie lammers]]

[[Category:Newbie]]

Alpine Install: from a disc to a virtualbox machine single only

2022-01-06T16:13:40Z

Mckaygerhard: /* Booting the Alpine ISO disc */ is a virtualbox case or generic case template, so dont added notes about vendor bvios due today is UEFI menu also is not about vendors bios!

'''Overall description:''' Installing Alpine from an official disc image to a VirtualBox machine.

This document guides you through installing Alpine on a VirtualBox VM - this is ideal if you only want to try out Alpine.

== Terminology ==

* '''Host machine''': the machine you're running VirtualBox on. It will "host" the target virtual machine.
* '''Guest machine''': your target machine where Alpine will be installed, executed by the VirtualBox software on the host machine.
* '''Reserved RAM''': the amount of host machine RAM that will be needed for exclusive use by the guest machine. The host machine cannot use this RAM while the guest machine is running.
* '''Virtual disc''': the emulated storage medium attached to the guest machine. Usually it is a file (or several files) which VirtualBox presents as a disk to the guest OS (Alpine).

== Requirements ==

On the host machine:

* Qemu or VirtualBox using package manager! Do not promote Oracle's policy of overversiones without security patches
* At least 1GB of RAM, 2GB or more if you don't want lockups while running something in addition to the virtual machine software
* The <code>curl</code> or <code>wget</code> programs to download the image to boot in the virtual software

On the guest machine:

* Minimum 512Mb RAM, but 1Gb or more is recommended if you're going to use a graphical interface. That obviouly must be in sync with the host machine.

== Preparing the medium to install ==

Download the source medium to install and put into your home; there's more hardware medium sources to download, like the '''[https://en.wikipedia.org/wiki/Linux_on_z_Systems s390x]''' and '''[https://en.wikipedia.org/wiki/Ppc64 ppc64le]''', but because VirtualBox handles only '''x86''' and '''x64'''
hardware, we will list those here

The name of the source medium to install will be in the following format: '''<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>''' where <code>ARCH</code> and <code>VERSION</code> can be one of the following, for VirtualBox virtual machines:

* <code><ARCH></code> can be
** '''x86''': The well known i386 to i686. (32-bit machines)
** '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines.
* <code><VERSION></code> can be
** '''latest-stable''' as the name says, the latest, stable version
** '''3.10''' UEFI support began with this version
** '''3.8''' recommended for machines manufactured between 2012 and 2016
** '''3.6''' recommended for older machines

Typically, the version most commonly used in a virtual box is the x86. The hardware is cheaper and operation does not consume a lot of memory.
The iso download URL format is:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' will be:
<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

'''Graphical download''': Just point the web browser to that URL and the download will start. A file with '''.iso''' extension type, with a name like <code>"alpine-standard-3.10.0-x86.iso"</code> (if i386/686); will be downloaded into the directory specified in your browser configuration.

'''Command line method''': just open a terminal and execute: <code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>, for example:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' the command will be:
<code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

You must be mindful of the directory you run the command from, as that is where the file will be saved.

== Preparing the virtual machine to install ==

Start the VirtualBox software program.

# In the main window '''create a new virtual machine''' by '''clicking the blue spark New button'''. That will open a new window with the following questions:
## It will ask for a '''name for the virtual like "alpine-desktop-try1"'''.
## The Type of the '''Operating system choose "linux"'''.
## The version '''choose "other linux"'''. It must match the chosen <code><ARCH></code> (e.g. x86).
## Click the "Next" button to continue creating the virtual machine.
# When selecting the amount of RAM for the virtual machine, choose a minimum of '''512MB''' then click the "Next" button.
# A new window with a '''Hard disk assistant will open'''.
## First choose '''"Create a virtual hard disk now"''' then click the "Create" button.
## Next choose the option for '''hard disk type: VDI''' and push "Next" button.
## Choose '''dynamically allocated''' then click the "Next" button.
## The next window will offer the '''size of virtual disk. 4GB''', however, you may choose a different amount of storage space.
## After clicking on "Create" the virtual machine will be ready to use.
# Now the main window shows you the "alpine-desktop-try1" virtual machine, select it.
## Click on the yellow "Configuration" button. Go to the storage menu and pull it down.
## Select the disc drive icon for CD/DVD ROM and click on the CD/DVD drive icon at the right.
## A Mini menu will open. Select an external file event the host CD/DVD drive.
## A file open dialog will open. Search for the downloaded Alpine iso and select it.
## Once you choose the iso file to boot, click the "Ok" button to finish creating the virtual machine.
# Click the green "Start" arrow to start the virtual machine and boot the iso.

[[File:Alpine Install from a disc to a virtualbox machine single only-01-0.png|center|Alpine configuration commonly used of a virtual machine on virtual box virtual machine]]

== Booting the Alpine ISO disc ==

When the machine starts, you must be sure to choose the Optical drive (commonly named CD/DVD ROM drive), so the disc/iso will boot. After a while, a command line shell will show you

[[File:Installation-alpine-alpine-setup-2-boot.png|350px|thumb|right|Installation : setup-alpine : booting process until login prompt]]

{{:Installation_pages_setup-alpine_script_normal}}
{{:Installation_pages_setup-disk_script_alpine_main_single}}

== Finishing the installation ==

After setup ends, a "reboot" will be offered. Type "reboot" and press enter and your newly installed virtual machine will be booted. Don't forget to remove the boot medium.

[[File:Installation-alpine-alpine-setup-9-setup-disk-3-7end.png]]

'''You cannot see a graphical window system? No problem.''' With Alpine, GUIs are made the right way. So '''if you need a desktop, you can install a desktop''' follow this link: [[Alpine newbie apk packages]] or go directly to [[Alpine newbie desktops]]

= Documents series =

{| class="wikitable"
|-
! Previous required !! What's next to read
|-
| [[Alpine newbie install manual]] || [[Alpine newbie packages]]
|}

= See Also =

# [[Alpine newbie packages]]
# [[Alpine newbie desktops]]
# [[Alpine newbie developer]]
# [[Alpine newbie lammers]]

[[Category:Newbie]]

Installation pages setup-alpine script normal

2022-01-06T16:07:05Z

Mckaygerhard: link to oficial wiki page of install

#REDIRECT [[Installation]]

Tutorials and Howtos

2022-01-06T16:04:47Z

Mckaygerhard: /* Installation:*/ Add case and let the main work of Guest09248 linked to general and all wiki work

{{Todo|This material needs to be re-organized .. as '''Howtos are smaller articles''' and '''tutorials are more detailed document''' both need to be reordered as independent sections }}

[[Image:package_edutainment.svg|right|link=]]
{{TOC left}}
'''Welcome to Tutorials and Howtos, a place of basic and advanced configuration tasks for your Alpine Linux.'''

'''The tutorials are hands-on''' and the reader is expected to try and achieve the goals described in each step, possibly with the help of a good example. The output in one step is the starting point for the following step.

'''Howtos are smaller articles''' explaining how to perform a particular task with Alpine Linux, that expects a minimal knowledge from reader to perform actions.

'''IMPORTANT:''' contributions on those pages must be complete articles as well as requesting topics to be covered, don't override already made contributions. If you want to request a topic, please add your request in this page's [[Talk:Tutorials_and_Howtos|Discussion]].

{{Clear}}

=== Postinstall ===

* [[Post_installation]]

==== Postinstall: desktops and applications ====

* [[Desktop environments and Window managers]] (overall information only)
** [[Xfce]]
** [[LXQt]]
** [[Openbox]]
** [[MATE]]
* [[Alpine and UEFI|Alpine and UEFI Support Status and related topics]]

==== Developers: compilers, IDEs and tools ====

* [[Alpine newbie developer]]
** [[Alpine newbie developer: gitea|Alpine newbie developer: Git management web frontend gitea]]
** [[Alpine newbie developer: full stack web]]

==== Servers: deploy in production ====

* [[Alpine production deploy]]
** [[Production Web server: Lighttpd‎‎]]
** [[Production DataBases : mysql]]
** [[Production LAMP system: Lighttpd + PHP + MySQL‎‎]]
* Alpine production monitoring
** [[Cacti: traffic analysis and monitoring network]]
** [[Zabbix|Zabbix - the professional complete manager]]

== Storage ==

* [[Alpine local backup|Alpine local backup (lbu)]] ''(Permanently store your modifications in case your box needs reboot)'' 
** [[Back Up a Flash Memory Installation]] 
** [[Manually editing a existing apkovl]]

* [[Setting up disks manually]] 
* [[Setting up a software RAID array]]

* [[Raid Administration]]
* [[Setting up encrypted volumes with LUKS]]
* [[Setting up LVM on LUKS]]
* [[Setting up Logical Volumes with LVM]]
** [[Setting up LVM on GPT-labeled disks]]
** [[Installing on GPT LVM]]
* [[Filesystems|Formatting HD/Floppy/Other]] 

* [[Setting up iSCSI]]
** [[iSCSI Raid and Clustered File Systems]]
* [[Setting up NBD]]
* [[Setting up ZFS on LUKS]]
* [[Setting up ZFS with native encryption]]
* [[High performance SCST iSCSI Target on Linux software Raid]] ''(deprecated)'' 
* [[Linux iSCSI Target (TCM)]]
* [[Disk Replication with DRBD]] 

* [[Burning ISOs]] 
* [[Partitioning and Bootmanagers]]
* [[Migrating data]]
* [[Create a bootable SDHC from a Mac]]
* [[Alpine on ARM]]

== Networking ==

* [[Configure Networking]]
* [[Connecting to a wireless access point]]
* [[Bonding]]
* [[Vlan]]
* [[Bridge]]
* [[Bridge wlan0 to eth0]]
* [[OpenVSwitch]]
* [[How to configure static routes]]
* [[Configure a Wireguard interface (wg)]]

* [[Alpine Wall]] - [[How-To Alpine Wall]] - [[Alpine Wall User's Guide]] ''(a new firewall management framework)''

* [[PXE boot]]

* [[Using serial modem]]
* [[Using HSDPA modem]]
* [[Setting up Satellite Internet Connection]]
* [[Using Alpine on Windows domain with IPSEC isolation]]

* [[Setting up a SSH server]] ''(Using SSH is the preferred way to administer your box remotely)'' 
** [[HOWTO OpenSSH 2FA with password and Google Authenticator]] ''(A simple two factor setup for OpenSSH)''
* [[How to setup a wireless access point]] ''(Setting up Secure Wireless AP w/ WPA encryption with bridge to wired network)''
* [[How to set up Alpine as a wireless router]] ''(Setting up a firewalled, Wireless AP with wired network on a Pi Zero W)''
* [[Setting up a OpenVPN server with Alpine]] ''(Allowing single users or devices to remotely connect to your network)''

* [[Experiences with OpenVPN-client on ALIX.2D3]] 

* [[Generating SSL certs with ACF]] 
* [[Setting up unbound DNS server]]
* [[Setting up nsd DNS server]]
* [[TinyDNS Format]]
* [[Fault Tolerant Routing with Alpine Linux]] 
* [[Freeradius Active Directory Integration]]
* [[Multi_ISP]] ''(Dual-ISP setup with load-balancing and automatic failover)''
* [[OwnCloud]] ''(Installing OwnCloud)''

* [[Seafile: setting up your own private cloud]]

* [[GNUnet]]

== Post-Install ==


* [[Setting up a new user]]
* [[Enable Community Repository]] ''(Providing additional packages)''
* [[Alpine Linux package management|Package Management (apk)]] ''(How to add/remove packages on your Alpine)''

** [[Comparison with other distros]]
* [[Alpine local backup|Alpine local backup (lbu)]] ''(Permanently store your modifications in case your box needs reboot)''
** [[Back Up a Flash Memory Installation]] 
** [[Manually editing a existing apkovl]]
* [[Alpine Linux Init System|Init System (OpenRC)]] ''(Configure a service to automatically boot at next reboot)''
** [[Multiple Instances of Services]]

* [[Alpine setup scripts#setup-xorg-base|Setting up Xorg]]
* [[Upgrading Alpine]]


* [[Setting up a ssh-server]] ''(Using ssh is a good way to administer your box remotely)''
** [[HOWTO OpenSSH 2FA with password and Google Authenticator]] ''(A simple two factor setup for OpenSSH)''
* [[setup-acf]] ''(Configures ACF (webconfiguration) so you can manage your box through https)''
* [[Changing passwords for ACF|Changing passwords]]
* [[Ansible]] ''(Configuration management)''

* [[Enable Serial Console on Boot]]

* [[How to get regular stuff working]] ''some notes on need-to-know topics''
* [[Installing Oracle Java]]
* [[Rsnapshot|Setting up periodic backups with <samp>rsnapshot</samp>]]

== Virtualization==

* [[Xen Dom0]] ''(Setting up Alpine as a dom0 for Xen hypervisor)''
* [[Xen Dom0 on USB or SD]]
* [[Create Alpine Linux PV DomU]]
* [[Xen PCI Passthrough]]
* [[Xen LiveCD]]
* [[QEMU]]
* [[KVM]] ''(Setting up Alpine as a KVM hypervisor)''
* [[LXC]] ''(Setting up a Linux container in Alpine Linux)''
* [[Docker]]
* [[Install_Alpine_on_VirtualBox]]
* [[Install Alpine on VMWare]]

== Desktop Environment ==

* [[AwesomeWM]]
* [[dwm]]
* [[EyeOS]] ''(Cloud Computing Desktop)''
* [[Gnome]]
* [[KDE]]
* [[MATE]]
* [[Oneye]] ''(Cloud Computing Desktop - Dropbox Alternative)''
* [[Nextcloud]] ''(Self hostable cloud suite - Dropbox Alternative)''
* [[Remote Desktop Server]]
* [[River]]
* [[Suspend on LID close]]
* [[Sway]]
* [[Xfce Desktop]]
* [[Sound Setup]]
* [[PipeWire]]
* [[Printer Setup]]
* [[Default applications]]

== Raspberry Pi ==

* [[Raspberry Pi|Raspberry Pi (Installation)]]
* [[Raspberry Pi - Headless Installation]]
* [[Classic install or sys mode on Raspberry Pi]]
* [[RPI Video Receiver]] ''(network video decoder using Rasperry Pi and omxplayer)''
* [[Linux Router with VPN on a Raspberry Pi]]
* [[Linux Router with VPN on a Raspberry Pi (IPv6)]]
* [[Raspberry Pi 4 - Persistent system acting as a NAS and Time Machine]]
* [[Raspberry Pi 3 - Configuring it as wireless access point -AP Mode]]
* [[Raspberry Pi 3 - Setting Up Bluetooth]]
* [[Raspberry Pi 3 - Browser Client]] - kiosk or digital sign
* [[Raspberry Pi Zero W - Installation]]
* [[Raspberry Pi Bluetooth Speaker]]

== PowerPC ==

* [[Ppc64le|Powerpc64le (Installation)]]

== IBM Z (IBM z Systems) ==

* [[s390x|s390x (Installation)]]

== Applications ==

=== Telephony ===
* [[Setting up Zaptel/Asterisk on Alpine]]
** [[Setting up Streaming an Asterisk Channel]]
* [[Freepbx on Alpine Linux]]
* [[FreePBX_V3]] ''(FreeSWITCH, Asterisk GUI web acces tool)''
* [[2600hz]] ''(FreeSWITCH, Asterisk GUI web access tool)''
* [[Kamailio]] ''(SIP Server, formerly OpenSER)''

=== Mail ===
* [[Hosting services on Alpine]] ''(Hosting mail, webservices and other services)''
** [[Hosting Web/Email services on Alpine]]
* [[ISP Mail Server HowTo]] 
** [[ISP Mail Server Upgrade 2.x]]
** [[ISP Mail Server 2.x HowTo]] ''(Beta, please test)''
** [[ISP Mail Server 3.x HowTo]]
* [[Roundcube]] ''(Webmail system)''
* [[Setting up postfix with virtual domains]]
* [[Protecting your email server with Alpine]]
* [[Setting up clamsmtp]]
* [[Setting up dovecot with imap and ssl]]
* [[relay email to gmail (msmtp, mailx, sendmail]]

=== HTTP ===
* [[Lighttpd]]
** [[Lighttpd Https access]]
** [[Setting Up Lighttpd with PHP]]
** [[Setting Up Lighttpd With FastCGI]]
* [[Cherokee]]
* [[Nginx]]
** [[Nginx_with_PHP#Nginx_with_PHP|Nginx with PHP]]
** [[Nginx as reverse proxy with acme (letsencrypt)]]
* [[Apache]]
** [[Apache with php-fpm]]
** [[Setting Up Apache with PHP]]
** [[Apache authentication: NTLM Single Signon]]

* [[High Availability High Performance Web Cache]] ''(uCarp + HAProxy for High Availability Services such as Squid web proxy)'' 

* [[Setting up Transparent Squid Proxy]] 
** [[SqStat]] ''(Script to look at active squid users connections)''
** [[Obtaining user information via SNMP]] ''(Using squark-auth-snmp as a Squid authentication helper)'' 
* [[Setting up Explicit Squid Proxy]]

* [[Drupal]] ''(Content Management System (CMS) written in PHP)''
* [[WordPress]] ''(Web software to create website or blog)''
* [[MediaWiki]] ''(Free web-based wiki software application)''
* [[DokuWiki]]
* [[Darkhttpd]]
* [[Tomcat]]
* [[Kopano]] ''(Microsoft Outlook compatible Groupware)''

=== Other Servers ===
* [[Setting up a ssh-server]] ''(Using ssh is a good way to administer your box remotely)''
** [[HOWTO OpenSSH 2FA with password and Google Authenticator]] ''(A simple two factor setup for OpenSSH)''

* [[Setting up a nfs-server]]
* [[Setting up a samba-server]] ''(standard file sharing)''
* [[Setting up a samba-ad-dc]] ''(Active Directory compatible domain controller)''
* [[Phpizabi]] ''(Social Networking Platform)''
* [[Statusnet]] ''(Microblogging Platform)''
* [[Pastebin]] ''(Pastebin software application)''
* [[Setting up Transmission (bittorrent) with Clutch WebUI]]

* [[Patchwork]] ''(Patch review management system)''
* [[Redmine]] ''(Project management system)''
* [[Request-Tracker]] ''(Ticket system)''
* [[OsTicket]] ''(Ticket system)''
* [[Setting up trac wiki|Trac]] ''(Enhanced wiki and issue tracking system for software development projects)''

* [[Alpine_newbie_developer: gitea|Setting up Git management web frontend gitea]]
* [[Cgit]]
** [[Setting up a git repository server with gitolite and cgit]] 
* [[Roundcube]] ''(Webmail system)''
* [[Glpi]] ''(Manage inventory of technical resources)''

* [[How to setup a Alpine Linux mirror]]
* [[Cups]]
* [[NgIRCd]] ''(Server for Internet Relay Chat/IRC)''
* [[How To Setup Your Own IRC Network]] ''(Using {{Pkg|charybdis}} and {{Pkg|atheme-iris}})''
* [[OpenVCP]] ''(VServer Control Panel)''
* [[Mahara]] ''(E-portfolio and social networking system)''
* [[Chrony and GPSD | Using chrony, gpsd, and a garmin LVC 18 as a Stratum 1 NTP source ]]
* [[Sending SMS using gnokii]]
* [[IPTV How To|Internet Protocol television (IPTV)]]
* [[UniFi_Controller]]
* [[DNSCrypt-Proxy]] ''Encrypt and authenticate DNS calls from your system''
* [[Odoo]]

=== Monitoring ===
* Setting up [[collectd]]
* [[Traffic monitoring]] 
* [[Setting up traffic monitoring using rrdtool (and snmp)]] 
* [[Setting up monitoring using rrdtool (and rrdcollect)]]
* [[Cacti: traffic analysis and monitoring network]] ''(Front-end for rrdtool networking monitor)''
* [[LTTng]] ''(Kernel and userspace tracing)''
* [[Zabbix|Zabbix - the professional complete manager]] ''(Monitor and track the status of network services and hardware)''
* [[Setting up A Network Monitoring and Inventory System]] ''(Nagios + OpenAudit and related components)'' 
** [[Setting up NRPE daemon]] ''(Performs remote Nagios checks)'' 
* [[Setting up Smokeping|Smokeping]] ''(Network latency monitoring)'' 
** [[Setting up MRTG and Smokeping to Monitor Bandwidth Usage and Network Latency]]
* [[Setting Up Fprobe And Ntop|Ntop]] ''(NetFlow collection and analysis using a remote fprobe instance)'' 
* [[Cvechecker]] ''(Compare installed packages for Common Vulnerabilities Exposure)'' 

* [[IP Accounting]] 
* [[Obtaining user information via SNMP]] ''(Using squark-auth-snmp as a Squid authentication helper)'' 
* [[SqStat]] ''(Script to look at active squid users connections)''

* [[Piwik]] ''(A real time web analytics software program)''
* [[Awstats]] ''(Free log file analyzer)''
* [[Intrusion Detection using Snort]]
** [[Intrusion Detection using Snort, Sguil, Barnyard and more]]
* [[Dglog]] ''(Log analyzer for the web content filter DansGuardian)''

* [[Webmin]] ''(A web-based interface for Linux system)''
* [[PhpPgAdmin]] ''(Web-based administration tool for PostgreSQL)''
* [[PhpMyAdmin]] ''(Web-based administration tool for MYSQL)''
* [[PhpSysInfo]] ''(A simple application that displays information about the host it's running on)''
* [[Linfo]]

* [[Setting up lm_sensors]]

* [[ZoneMinder video camera security and surveillance]]

== Misc ==

* [[:Category:Shell]]
* [[:Category:Programming]]
* [[Running glibc programs]]
* [[:Category:Drivers]]
* [[:Category:Multimedia]]
* [[Kernel Modesetting]]
* [[CPU frequency scaling]]

== Complete Solutions ==
* [[DIY Fully working Alpine Linux for Allwinner and Other ARM SOCs]]
* [https://codeberg.org/AVG7/alpine-sway-x86_64 DIY Live-USB-Stick with Sway]
* [[Alpine on the Aopen Chromebase or Chromebox Mini with Mainline Kernel]]
* [[Replacing non-Alpine Linux with Alpine remotely]]
* [[High performance SCST iSCSI Target on Linux software Raid]]
* [[Fault Tolerant Routing with Alpine Linux]]
* [[Experiences with OpenVPN-client on ALIX.2D3]]
* [[Building a cloud with Alpine Linux]]

* [[ISP Mail Server HowTo]] ''(Postfix+PostfixAdmin+DoveCot+Roundcube+ClamAV+Spamd - A full-serivce ISP mail server)''
** [[ISP Mail Server Upgrade 2.x]]
** [[ISP Mail Server 2.x HowTo]] ''(Beta, please test)''
* [[High Availability High Performance Web Cache]] ''(uCarp + HAProxy for High Availability Services such as Squid web proxy)''
* [[Setting up A Network Monitoring and Inventory System]] ''(Nagios + OpenAudit and related components)'' 
* [[Streaming Security Camera Video with VLC]]
* [[Dynamic Multipoint VPN (DMVPN)]] combined with [[Small_Office_Services]]



== Newbies ==

* [[Alpine_newbie]] (for overall information in funny sections)

* [[Alpine_newbie_apk_packages|Alpine newbie users post install and easy setups]]
** [[Alpine_newbie_apk_packages#New_users:_hostname_and_network_wired_connection|First steps at post install]]
** [[Alpine_newbie_apk_packages#New_users:_common_needed_package_to_install|Enable repositories]]
** [[Alpine_newbie_apk_packages#New_users:_management_of_users_and_logins|Added the first user to use the system]]
** [[Alpine_newbie_apk_packages#install_basic_tools|First packages to install]] (need the previous [[Alpine_newbie_apk_packages#New_users:_common_needed_package_to_install|Enable repositories]]) already done!

[[Category:System_Administration]]
[[Category:Installation]]

Tutorials and Howtos

2022-01-06T15:59:39Z

Mckaygerhard: /* Installation: Use cases */ remove newbie install references

{{Todo|This material needs to be re-organized .. as '''Howtos are smaller articles''' and '''tutorials are more detailed document''' both need to be reordered as independent sections }}

[[Image:package_edutainment.svg|right|link=]]
{{TOC left}}
'''Welcome to Tutorials and Howtos, a place of basic and advanced configuration tasks for your Alpine Linux.'''

'''The tutorials are hands-on''' and the reader is expected to try and achieve the goals described in each step, possibly with the help of a good example. The output in one step is the starting point for the following step.

'''Howtos are smaller articles''' explaining how to perform a particular task with Alpine Linux, that expects a minimal knowledge from reader to perform actions.

'''IMPORTANT:''' contributions on those pages must be complete articles as well as requesting topics to be covered, don't override already made contributions. If you want to request a topic, please add your request in this page's [[Talk:Tutorials_and_Howtos|Discussion]].

{{Clear}}

==== Postinstall: desktops and applications ====

* [[Desktop environments and Window managers]] (overall information only)
** [[Xfce]]
** [[LXQt]]
** [[Openbox]]
** [[MATE]]
* [[Alpine and UEFI|Alpine and UEFI Support Status and related topics]]

==== Developers: compilers, IDEs and tools ====

* [[Alpine newbie developer]]
** [[Alpine newbie developer: gitea|Alpine newbie developer: Git management web frontend gitea]]
** [[Alpine newbie developer: full stack web]]

==== Servers: deploy in production ====

* [[Alpine production deploy]]
** [[Production Web server: Lighttpd‎‎]]
** [[Production DataBases : mysql]]
** [[Production LAMP system: Lighttpd + PHP + MySQL‎‎]]
* Alpine production monitoring
** [[Cacti: traffic analysis and monitoring network]]
** [[Zabbix|Zabbix - the professional complete manager]]

== Storage ==

* [[Alpine local backup|Alpine local backup (lbu)]] ''(Permanently store your modifications in case your box needs reboot)'' 
** [[Back Up a Flash Memory Installation]] 
** [[Manually editing a existing apkovl]]

* [[Setting up disks manually]] 
* [[Setting up a software RAID array]]

* [[Raid Administration]]
* [[Setting up encrypted volumes with LUKS]]
* [[Setting up LVM on LUKS]]
* [[Setting up Logical Volumes with LVM]]
** [[Setting up LVM on GPT-labeled disks]]
** [[Installing on GPT LVM]]
* [[Filesystems|Formatting HD/Floppy/Other]] 

* [[Setting up iSCSI]]
** [[iSCSI Raid and Clustered File Systems]]
* [[Setting up NBD]]
* [[Setting up ZFS on LUKS]]
* [[Setting up ZFS with native encryption]]
* [[High performance SCST iSCSI Target on Linux software Raid]] ''(deprecated)'' 
* [[Linux iSCSI Target (TCM)]]
* [[Disk Replication with DRBD]] 

* [[Burning ISOs]] 
* [[Partitioning and Bootmanagers]]
* [[Migrating data]]
* [[Create a bootable SDHC from a Mac]]
* [[Alpine on ARM]]

== Networking ==

* [[Configure Networking]]
* [[Connecting to a wireless access point]]
* [[Bonding]]
* [[Vlan]]
* [[Bridge]]
* [[Bridge wlan0 to eth0]]
* [[OpenVSwitch]]
* [[How to configure static routes]]
* [[Configure a Wireguard interface (wg)]]

* [[Alpine Wall]] - [[How-To Alpine Wall]] - [[Alpine Wall User's Guide]] ''(a new firewall management framework)''

* [[PXE boot]]

* [[Using serial modem]]
* [[Using HSDPA modem]]
* [[Setting up Satellite Internet Connection]]
* [[Using Alpine on Windows domain with IPSEC isolation]]

* [[Setting up a SSH server]] ''(Using SSH is the preferred way to administer your box remotely)'' 
** [[HOWTO OpenSSH 2FA with password and Google Authenticator]] ''(A simple two factor setup for OpenSSH)''
* [[How to setup a wireless access point]] ''(Setting up Secure Wireless AP w/ WPA encryption with bridge to wired network)''
* [[How to set up Alpine as a wireless router]] ''(Setting up a firewalled, Wireless AP with wired network on a Pi Zero W)''
* [[Setting up a OpenVPN server with Alpine]] ''(Allowing single users or devices to remotely connect to your network)''

* [[Experiences with OpenVPN-client on ALIX.2D3]] 

* [[Generating SSL certs with ACF]] 
* [[Setting up unbound DNS server]]
* [[Setting up nsd DNS server]]
* [[TinyDNS Format]]
* [[Fault Tolerant Routing with Alpine Linux]] 
* [[Freeradius Active Directory Integration]]
* [[Multi_ISP]] ''(Dual-ISP setup with load-balancing and automatic failover)''
* [[OwnCloud]] ''(Installing OwnCloud)''

* [[Seafile: setting up your own private cloud]]

* [[GNUnet]]

== Post-Install ==


* [[Setting up a new user]]
* [[Enable Community Repository]] ''(Providing additional packages)''
* [[Alpine Linux package management|Package Management (apk)]] ''(How to add/remove packages on your Alpine)''

** [[Comparison with other distros]]
* [[Alpine local backup|Alpine local backup (lbu)]] ''(Permanently store your modifications in case your box needs reboot)''
** [[Back Up a Flash Memory Installation]] 
** [[Manually editing a existing apkovl]]
* [[Alpine Linux Init System|Init System (OpenRC)]] ''(Configure a service to automatically boot at next reboot)''
** [[Multiple Instances of Services]]

* [[Alpine setup scripts#setup-xorg-base|Setting up Xorg]]
* [[Upgrading Alpine]]


* [[Setting up a ssh-server]] ''(Using ssh is a good way to administer your box remotely)''
** [[HOWTO OpenSSH 2FA with password and Google Authenticator]] ''(A simple two factor setup for OpenSSH)''
* [[setup-acf]] ''(Configures ACF (webconfiguration) so you can manage your box through https)''
* [[Changing passwords for ACF|Changing passwords]]
* [[Ansible]] ''(Configuration management)''

* [[Enable Serial Console on Boot]]

* [[How to get regular stuff working]] ''some notes on need-to-know topics''
* [[Installing Oracle Java]]
* [[Rsnapshot|Setting up periodic backups with <samp>rsnapshot</samp>]]

== Virtualization==

* [[Xen Dom0]] ''(Setting up Alpine as a dom0 for Xen hypervisor)''
* [[Xen Dom0 on USB or SD]]
* [[Create Alpine Linux PV DomU]]
* [[Xen PCI Passthrough]]
* [[Xen LiveCD]]
* [[QEMU]]
* [[KVM]] ''(Setting up Alpine as a KVM hypervisor)''
* [[LXC]] ''(Setting up a Linux container in Alpine Linux)''
* [[Docker]]
* [[Install_Alpine_on_VirtualBox]]
* [[Install Alpine on VMWare]]

== Desktop Environment ==

* [[AwesomeWM]]
* [[dwm]]
* [[EyeOS]] ''(Cloud Computing Desktop)''
* [[Gnome]]
* [[KDE]]
* [[MATE]]
* [[Oneye]] ''(Cloud Computing Desktop - Dropbox Alternative)''
* [[Nextcloud]] ''(Self hostable cloud suite - Dropbox Alternative)''
* [[Remote Desktop Server]]
* [[River]]
* [[Suspend on LID close]]
* [[Sway]]
* [[Xfce Desktop]]
* [[Sound Setup]]
* [[PipeWire]]
* [[Printer Setup]]
* [[Default applications]]

== Raspberry Pi ==

* [[Raspberry Pi|Raspberry Pi (Installation)]]
* [[Raspberry Pi - Headless Installation]]
* [[Classic install or sys mode on Raspberry Pi]]
* [[RPI Video Receiver]] ''(network video decoder using Rasperry Pi and omxplayer)''
* [[Linux Router with VPN on a Raspberry Pi]]
* [[Linux Router with VPN on a Raspberry Pi (IPv6)]]
* [[Raspberry Pi 4 - Persistent system acting as a NAS and Time Machine]]
* [[Raspberry Pi 3 - Configuring it as wireless access point -AP Mode]]
* [[Raspberry Pi 3 - Setting Up Bluetooth]]
* [[Raspberry Pi 3 - Browser Client]] - kiosk or digital sign
* [[Raspberry Pi Zero W - Installation]]
* [[Raspberry Pi Bluetooth Speaker]]

== PowerPC ==

* [[Ppc64le|Powerpc64le (Installation)]]

== IBM Z (IBM z Systems) ==

* [[s390x|s390x (Installation)]]

== Applications ==

=== Telephony ===
* [[Setting up Zaptel/Asterisk on Alpine]]
** [[Setting up Streaming an Asterisk Channel]]
* [[Freepbx on Alpine Linux]]
* [[FreePBX_V3]] ''(FreeSWITCH, Asterisk GUI web acces tool)''
* [[2600hz]] ''(FreeSWITCH, Asterisk GUI web access tool)''
* [[Kamailio]] ''(SIP Server, formerly OpenSER)''

=== Mail ===
* [[Hosting services on Alpine]] ''(Hosting mail, webservices and other services)''
** [[Hosting Web/Email services on Alpine]]
* [[ISP Mail Server HowTo]] 
** [[ISP Mail Server Upgrade 2.x]]
** [[ISP Mail Server 2.x HowTo]] ''(Beta, please test)''
** [[ISP Mail Server 3.x HowTo]]
* [[Roundcube]] ''(Webmail system)''
* [[Setting up postfix with virtual domains]]
* [[Protecting your email server with Alpine]]
* [[Setting up clamsmtp]]
* [[Setting up dovecot with imap and ssl]]
* [[relay email to gmail (msmtp, mailx, sendmail]]

=== HTTP ===
* [[Lighttpd]]
** [[Lighttpd Https access]]
** [[Setting Up Lighttpd with PHP]]
** [[Setting Up Lighttpd With FastCGI]]
* [[Cherokee]]
* [[Nginx]]
** [[Nginx_with_PHP#Nginx_with_PHP|Nginx with PHP]]
** [[Nginx as reverse proxy with acme (letsencrypt)]]
* [[Apache]]
** [[Apache with php-fpm]]
** [[Setting Up Apache with PHP]]
** [[Apache authentication: NTLM Single Signon]]

* [[High Availability High Performance Web Cache]] ''(uCarp + HAProxy for High Availability Services such as Squid web proxy)'' 

* [[Setting up Transparent Squid Proxy]] 
** [[SqStat]] ''(Script to look at active squid users connections)''
** [[Obtaining user information via SNMP]] ''(Using squark-auth-snmp as a Squid authentication helper)'' 
* [[Setting up Explicit Squid Proxy]]

* [[Drupal]] ''(Content Management System (CMS) written in PHP)''
* [[WordPress]] ''(Web software to create website or blog)''
* [[MediaWiki]] ''(Free web-based wiki software application)''
* [[DokuWiki]]
* [[Darkhttpd]]
* [[Tomcat]]
* [[Kopano]] ''(Microsoft Outlook compatible Groupware)''

=== Other Servers ===
* [[Setting up a ssh-server]] ''(Using ssh is a good way to administer your box remotely)''
** [[HOWTO OpenSSH 2FA with password and Google Authenticator]] ''(A simple two factor setup for OpenSSH)''

* [[Setting up a nfs-server]]
* [[Setting up a samba-server]] ''(standard file sharing)''
* [[Setting up a samba-ad-dc]] ''(Active Directory compatible domain controller)''
* [[Phpizabi]] ''(Social Networking Platform)''
* [[Statusnet]] ''(Microblogging Platform)''
* [[Pastebin]] ''(Pastebin software application)''
* [[Setting up Transmission (bittorrent) with Clutch WebUI]]

* [[Patchwork]] ''(Patch review management system)''
* [[Redmine]] ''(Project management system)''
* [[Request-Tracker]] ''(Ticket system)''
* [[OsTicket]] ''(Ticket system)''
* [[Setting up trac wiki|Trac]] ''(Enhanced wiki and issue tracking system for software development projects)''

* [[Alpine_newbie_developer: gitea|Setting up Git management web frontend gitea]]
* [[Cgit]]
** [[Setting up a git repository server with gitolite and cgit]] 
* [[Roundcube]] ''(Webmail system)''
* [[Glpi]] ''(Manage inventory of technical resources)''

* [[How to setup a Alpine Linux mirror]]
* [[Cups]]
* [[NgIRCd]] ''(Server for Internet Relay Chat/IRC)''
* [[How To Setup Your Own IRC Network]] ''(Using {{Pkg|charybdis}} and {{Pkg|atheme-iris}})''
* [[OpenVCP]] ''(VServer Control Panel)''
* [[Mahara]] ''(E-portfolio and social networking system)''
* [[Chrony and GPSD | Using chrony, gpsd, and a garmin LVC 18 as a Stratum 1 NTP source ]]
* [[Sending SMS using gnokii]]
* [[IPTV How To|Internet Protocol television (IPTV)]]
* [[UniFi_Controller]]
* [[DNSCrypt-Proxy]] ''Encrypt and authenticate DNS calls from your system''
* [[Odoo]]

=== Monitoring ===
* Setting up [[collectd]]
* [[Traffic monitoring]] 
* [[Setting up traffic monitoring using rrdtool (and snmp)]] 
* [[Setting up monitoring using rrdtool (and rrdcollect)]]
* [[Cacti: traffic analysis and monitoring network]] ''(Front-end for rrdtool networking monitor)''
* [[LTTng]] ''(Kernel and userspace tracing)''
* [[Zabbix|Zabbix - the professional complete manager]] ''(Monitor and track the status of network services and hardware)''
* [[Setting up A Network Monitoring and Inventory System]] ''(Nagios + OpenAudit and related components)'' 
** [[Setting up NRPE daemon]] ''(Performs remote Nagios checks)'' 
* [[Setting up Smokeping|Smokeping]] ''(Network latency monitoring)'' 
** [[Setting up MRTG and Smokeping to Monitor Bandwidth Usage and Network Latency]]
* [[Setting Up Fprobe And Ntop|Ntop]] ''(NetFlow collection and analysis using a remote fprobe instance)'' 
* [[Cvechecker]] ''(Compare installed packages for Common Vulnerabilities Exposure)'' 

* [[IP Accounting]] 
* [[Obtaining user information via SNMP]] ''(Using squark-auth-snmp as a Squid authentication helper)'' 
* [[SqStat]] ''(Script to look at active squid users connections)''

* [[Piwik]] ''(A real time web analytics software program)''
* [[Awstats]] ''(Free log file analyzer)''
* [[Intrusion Detection using Snort]]
** [[Intrusion Detection using Snort, Sguil, Barnyard and more]]
* [[Dglog]] ''(Log analyzer for the web content filter DansGuardian)''

* [[Webmin]] ''(A web-based interface for Linux system)''
* [[PhpPgAdmin]] ''(Web-based administration tool for PostgreSQL)''
* [[PhpMyAdmin]] ''(Web-based administration tool for MYSQL)''
* [[PhpSysInfo]] ''(A simple application that displays information about the host it's running on)''
* [[Linfo]]

* [[Setting up lm_sensors]]

* [[ZoneMinder video camera security and surveillance]]

== Misc ==

* [[:Category:Shell]]
* [[:Category:Programming]]
* [[Running glibc programs]]
* [[:Category:Drivers]]
* [[:Category:Multimedia]]
* [[Kernel Modesetting]]
* [[CPU frequency scaling]]

== Complete Solutions ==
* [[DIY Fully working Alpine Linux for Allwinner and Other ARM SOCs]]
* [https://codeberg.org/AVG7/alpine-sway-x86_64 DIY Live-USB-Stick with Sway]
* [[Alpine on the Aopen Chromebase or Chromebox Mini with Mainline Kernel]]
* [[Replacing non-Alpine Linux with Alpine remotely]]
* [[High performance SCST iSCSI Target on Linux software Raid]]
* [[Fault Tolerant Routing with Alpine Linux]]
* [[Experiences with OpenVPN-client on ALIX.2D3]]
* [[Building a cloud with Alpine Linux]]

* [[ISP Mail Server HowTo]] ''(Postfix+PostfixAdmin+DoveCot+Roundcube+ClamAV+Spamd - A full-serivce ISP mail server)''
** [[ISP Mail Server Upgrade 2.x]]
** [[ISP Mail Server 2.x HowTo]] ''(Beta, please test)''
* [[High Availability High Performance Web Cache]] ''(uCarp + HAProxy for High Availability Services such as Squid web proxy)''
* [[Setting up A Network Monitoring and Inventory System]] ''(Nagios + OpenAudit and related components)'' 
* [[Streaming Security Camera Video with VLC]]
* [[Dynamic Multipoint VPN (DMVPN)]] combined with [[Small_Office_Services]]



== Newbies ==

* [[Alpine_newbie]] (for overall information in funny sections)

* [[Alpine_newbie_apk_packages|Alpine newbie users post install and easy setups]]
** [[Alpine_newbie_apk_packages#New_users:_hostname_and_network_wired_connection|First steps at post install]]
** [[Alpine_newbie_apk_packages#New_users:_common_needed_package_to_install|Enable repositories]]
** [[Alpine_newbie_apk_packages#New_users:_management_of_users_and_logins|Added the first user to use the system]]
** [[Alpine_newbie_apk_packages#install_basic_tools|First packages to install]] (need the previous [[Alpine_newbie_apk_packages#New_users:_common_needed_package_to_install|Enable repositories]]) already done!

[[Category:System_Administration]]
[[Category:Installation]]

Alpine Install: from a disc to a new computer single only boot

2022-01-06T15:58:23Z

Mckaygerhard: Mckaygerhard moved page Alpine Install: from a disc to a new computer single only boot to Delete-3: There's a installation page, the main purpose of the "newbie" categori is specific list of cases! please do not restore cos as disclamer cited a...

#REDIRECT [[Delete-3]]

Talk:Alpine Install: from a disc to a any computer single only boot

2022-01-06T15:52:52Z

Mckaygerhard: /* Proposal for Deletion */

==Proposal for Deletion==
Guest09248 asserts that "there are other wiki pages with similar (if not the same) information"
As such I do not support deleting this article, instead it should be merged or redirected.
[[User:Zcrayfish|zcrayfish]] ([[User talk:Zcrayfish|talk]]) 21:44, 14 December 2021 (UTC)
: the idea of newbie category are specific cases for almos any situation.. as must be for new users in .. but seems Guest09248 mixed several pages, this is a situation of lack of coordination and olders ways to made a team of work.. by example i send a email to devel-alpine and the response was "acts as you want"! in resume so we are not a anarchist here! so i let the citation of deletino but put a note about and removes any newbie reference from that user.
[[User:Mckaygerhard|Mckaygerhard]] ([[User talk:Mckaygerhard|talk]]) 01:44, 6 Jan 2022 (UTC)

== about grammar ==

yes .. there's a lot of grammar errors, but i was the only to take patiente to make screenshots (the only screenshot made are thanks to me) and put in some order to other can work!
of course now i have time to fix the context of my articles but we need coordination.
[[User:Mckaygerhard|Mckaygerhard]] ([[User talk:Mckaygerhard|talk]]) 01:44, 6 Jan 2022 (UTC)

Talk:Alpine Install: from a disc to a any computer single only boot

2022-01-06T15:52:18Z

Mckaygerhard: added talk to.. it seem the Guest09248 user dont take in consideration to Zcrayfish

==Proposal for Deletion==
Guest09248 asserts that "there are other wiki pages with similar (if not the same) information"
As such I do not support deleting this article, instead it should be merged or redirected.
[[User:Zcrayfish|zcrayfish]] ([[User talk:Zcrayfish|talk]]) 21:44, 14 December 2021 (UTC)
: the idea of newbie category are specific cases for almos any situation.. as must be for new users in ..
but seems Guest09248 mixed several pages, this is a situation of lack of coordination and olders ways to
made a team of work.. by example i send a email to devel-alpine and the response was "acts as you want"! in resume
so we are not a anarchist here! so i let the citation of deletino but put a note about and removes any newbie reference from that user.
[[User:Mckaygerhard|Mckaygerhard]] ([[User talk:Mckaygerhard|talk]]) 01:44, 6 Jan 2022 (UTC)

== about grammar ==

yes .. there's a lot of grammar errors, but i was the only to take patiente to make screenshots (the only screenshot made are thanks to me) and put in some order to other can work!
of course now i have time to fix the context of my articles but we need coordination.
[[User:Mckaygerhard|Mckaygerhard]] ([[User talk:Mckaygerhard|talk]]) 01:44, 6 Jan 2022 (UTC)

Alpine Install: from a disc to a any computer single only boot

2022-01-06T15:47:30Z

Mckaygerhard: unlink and remove newbie references and clarify the deletion if any

{{Delete|there are other wiki pages with similar or same information, the proposal and idea of newbie pages was specific cases but now there are too mixed pages with same information DUE LACK OF COORDINATION, so the best is to delete this content}}

'''Overall description:''' Alpine Installation from a official disc/iso burned into DVD/CD to a new computer with or without [[Alpine and UEFI|UEFI]] and will be single only boot, it's means that any thing in the computer and their disc will be erased to put Alpine Linux as main system

This document will guide you to '''install Alpine into a new empty or just fresh PC or Laptop hardware computer, use if you have a [[Alpine and UEFI|BIOS or UEFI based hardware]] and only wants Alpine Linux into it.

== Terminology ==

* '''[[Alpine and UEFI|UEFI]]''': it's a new system included in every new hardware machine laptop or desktops, that will manage the early boot process as a little operating system, see more in the [[Alpine and UEFI]] page.
* '''New machine''': will be your real machine fresh and ready to install your new Alpine operating system, with a installed CD/DVD Rom optical drive where to put the burned downloaded disc media installation.
* '''Optical drive''': will be your hardware drive input to put the burned downloaded iso media with the operating system Alpine to install as source media; this drive are commonly named [https://en.wikipedia.org/wiki/CD-ROM DVD/CD Rom] unit.
* '''Source media''': will be the just burned/ disc from the downloaded iso file of Alpine operating system. Will be put into the optical drive or named [https://en.wikipedia.org/wiki/CD-ROM DVD/CD Rom] to property boot the source disc as media installation.
* '''Target media''': will be the storage medium device into the new computer target where the Alpine files for operating system will be installed, its one partition from the [https://en.wikipedia.org/wiki/Hard_disk_drive HardDisk] of the new computer.

== Requirements ==

* A blank disc (CD blank or DVD blank or BR blank) to just burn/record the source media file downloaded
* In the new machine we need optical drive as input source media
* In the new machine we need at least 512Mb of RAM, but required 2Gb of RAM for desktop/graphical applications
* In the new machine we need target media with at least 2G of hard disk, but required 10G for desktops
* Will need to previously downloaded and burned the Source media ISO file from https://alpinelinux.org/downloads/

== Preparing the source medium to install ==

Download the source medium to install and put into your home documents in a modern computer. There are more hardware medium sources to download, like the arm and i386, but ISO CD/DVD images are only to PC/Laptops that are i386 and amd64, so by downloading the x86 (32bit) flavor will be same for both cases, but UEFI need 64bit, so change to the x86_64 (amd64) if your computer is the most modern and lasted hardware.

The source medium to install for [[Alpine and UEFI|UEFI or '''modern hardware''']] '''are just 64-bit only''', the download URL will be as following format: <code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code> where <code>ARCH</code> and <code>VERSION</code> could be:

* <code><ARCH></code> will be
** '''x86''': the most used i386 32-bit x86 based machines, if your computer are too older use this only.
** '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines, i386 are not recommended for newer/lasted hardware.
** '''s390x''': For the Super powered IBM mainframes, especially IBM Z and IBM LinuxONE servers.
** '''ppc64le''': For the PowerPC devices with pure little-endian mode, mostly for POWER8 and POWER9
* <code><VERSION></code> will be
** '''latest-stable''' for a more up to date without taking care of numbered
** '''3.10''' the most recommended for machines between 2016 to 2018

'''So using 3.10 version the available links to download will be:'''
* '''x86_64''': <code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86_64/alpine-standard-3.10.0-x86_64.iso</nowiki></code>
* '''s390x''': <code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/ppc64le/alpine-standard-3.10.1-ppc64le.iso</nowiki></code>
* '''ppc64le''': <code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/ppc64le/alpine-standard-3.10.1-ppc64le.iso</nowiki></code>

'''Graphical download''': Just point the web browser to that url and the download of the iso file will start. A file with '''.iso''' extension type, with name like <code>"alpine-standard-3.10.0-x86_64.iso"</code> (if amd64) or like <code>alpine-standard-3.10.1-s390x.iso</code> (if s390x); will be downloaded commonly into the Download directory of your home documents filesystem.

'''Command line method''': in unix-like terminal execute: <code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86_64/alpine-standard-3.10.0-x86_64.iso</nowiki></code>, and where you run the command, in that place/dir will be downloaded the file.

== Burning the source medium to install ==

After downloading the source media file from [https://alpinelinux.org/downloads/ Alpine download page] ''' put the blank disc into the input optical drive''' named [https://en.wikipedia.org/wiki/CD-ROM DVD/CD Rom] and '''open your CD/DVD recording program, choose to "burn from iso file"''' and wait the process will end.

In detail if you downloaded with '''Graphical download''' (using a web browser), the source media file will be into the Download directory. If you downloaded with '''Command line method''' your source file probably will be in your root document home (or just <code>$HOME</code> of your Linux install or MAC install filesystem).

In Linux, assuming the blank disc is in the optical drive, the command to record/burn the downloaded source media file is :

<code>$ umount /dev/sr0;cdrecord -v -sao dev=/dev/sr0 alpine-standard-3.10.0-x86_64.iso</code>

If your blank media is a DVD or BD disc the command will be then :

<code>$ umount /dev/sr0;growisofs -dvd-compat -Z /dev/sr0=alpine-standard-3.10.0-x86_64.iso</code>

{{Note|growisofs has a small bug with blank BD-R media. It issues an error message after the burning is complete. Programs like k3b then believe the whole burn run failed.}}

== Booting the Alpine ISO disc ==

When the machine start, you must be sure to choose the optical drive (commonly named CD/DVD Rom drive), so the disc/iso will boot and after a while a command line shell will show you:

{{Tip|If your system is not configured to boot from a CD/DVD drive, it must be configured in the BIOS, '''ask/search to your vendor or technical support''', Toshiba computers need to hit F1 to choose boot medium, DELL must hit F11 to choose medium for example, and so and so}}

[[File:Installation-alpine-alpine-setup-2-boot.png|350px|thumb|right|Installation : setup-alpine : booting process until login prompt]]

{{:Installation_pages_setup-alpine_script_normal}}
{{:Installation_pages_setup-disk_script_alpine_main_single}}

== Finishing the installation ==

After all of the scripts in the setup end, a "reboot" will be offered, just type "reboot" and press enter, remove the boot media and newly installed system will be booted.

[[File:Installation-alpine-alpine-setup-9-setup-disk-3-7end.png]]

'''You cannot see a graphical window system? take it easy''' and get calmed down.. in Alpine all are made by the right way.. so '''if user need a desktop.. user can install a desktop''' follow the next: [[Alpine newbie packages]] '''or bypass and go directly to [[Alpine newbie desktops]]'''

= Documents series =

{| class="wikitable"
|-
! Previous required !! What's next to read
|-
| [[Alpine newbie install manual]] || [[Alpine newbie packages]]
|}

= See Also =

# [[Alpine newbie packages]]
# [[Alpine newbie desktops]]
# [[Alpine newbie developer]]
# [[Alpine newbie lammers]]

[[Category:Newbie]]

Alpine Install: from a iso to a virtualbox machine with external disc

2022-01-06T15:45:10Z

Mckaygerhard: uinlink all newbie pages

'''Overall description:''' Alpine Installation from a official disc/iso downloaded to a real hard disk by the usage of VirtualBox machine as the real machine, where will be single OS only.

This document will guide you to '''install Alpine into a real hard disk device but through the VirtualBox virtual machine acting as real machine''', use if want to install to a real hard disk device externally but no way to boot it so can use in VirtualBox virtual machine .

== Terminology ==

* '''Host machine''': will be your real machine with installed operating system that have installed the VirtualBox software and "will host" the target operating system, in that case Alpine.
* '''Guest machine''': will be your target machine where Alpine will be installed, emulated by the host operating system using the VirtualBox software installed in the real machine.
* '''Reserved RAM''': will be the amount of RAM that will be need to share exclusively to the virtual machine created by the VirtualBox software in the host machine, stolen from the real RAM.
* '''External disc''': will be the storage medium device attached as target for the emulated machine or "guest machine", where the Alpine will be installed.

== Requirements ==

* In the host machine we need installed the <code>virtualbox</code> program from VirtualBox software
* In the host machine we need at least 1Gb of RAM, recommended 2Gb of RAM installed
* The guest machine need 512Mb RAM, but recommended 1Gb reserved if desktop software will be installed
* In the host machine we need installed <code>wget</code> or a web browser to download install medium

== Preparing the medium origin to install ==

Download the source medium to install and put into your home, there's more hardware medium sources to download, like the '''[https://en.wikipedia.org/wiki/Linux_on_z_Systems s390x]''' and '''[https://en.wikipedia.org/wiki/Ppc64 ppc64le]''', but due VirtualBox only emulates '''x86''', '''x64''' and '''arm''' hardware only, will list those here.

The source medium to install will be as following format: '''<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-netboot-<VERSION>.0-<ARCH>.iso</code>''' where <code>ARCH</code> and <code>VERSION</code> could be the following for VirtualBox virtual machines:

* <code><ARCH></code> will be
** '''x86''': The popular i386/i686 compatible 32-bit x86 based machines, i386 recommended for olders.
** '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines, recommended for newer/lasted hardware.
* <code><VERSION></code> will be
** '''latest-stable''' for a more up to date without taking care of numbered
** '''3.10''' the most recommended for machines between 2016 to 2018

'''So using 3.10 version and i386 flavor the available links to download will be:''' <code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

'''Graphical download''': Just point the web browser to that url and the download of the iso file will start. A file with '''.iso''' extension type, with name like <code>"alpine-standard-3.10.0-x86_64.iso"</code> will be downloaded commonly into the Download directory of your home documents filesystem.

'''Command line method''': in unix-like terminal execute: <code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>, and where you run the command, in that place/dir will be downloaded the file.

== Preparing the medium target to install ==

Please take care of your attached devices.. for best care results only use those involved in the process, so only put the disc (that can be a USB flash, MMC card or external drive) attached, and remove all others that will no to be use. '''We will assume only one internal disc (that obviously cannot be removed) and one external disk attached'''.

The external disc will be detected and the operating system will create a new device representation, such like <code>/dev/sdb</code> commonly. In Linux systems you can detect the recently attached disk with following command:

<code>/bin/dmesg | tail -n 50| grep 'Attached SCSI' | cut -d' ' -f4</code>

This will output <code>[sde]</code> for our example installation. Caution due that previously command only will work if you recently attached the new external disk where the system will be installed.

Later with the detection of the disk, create the representation for the VirtualBox virtual machine, the detection will be put in <code>/dev/</code> parameter.. so if the disk was detect as <code>[sde]</code> you must use it without <nowiki>"["/"]"</nowiki> sings, the command for creating the virtual disk will be:

<code>VBoxManage internalcommands createrawvmdk -rawdisk /dev/sde -filename $HOME/rawdisk-sdb.vmdk</code>

{{Tip|in Linux if you don't have "disk" group access need to perform permission to device to 666, so take care of}}

{{Warning|We assume there are only two disk, the internal and the external, here detected as <nowiki>[sde]</nowiki> for practical reasons, commonly will be detected as <nowiki>[sdb]</nowiki>}}

== Preparing the virtual machine to install ==

Start the VirtualBox software program.

# In the main window '''create a new virtual machine''' by '''clicking the blue spark New button'''. Will open a new window with the following questions:
## Will ask for a '''name for the virtual like "alpine-desktop-try1"'''.
## The Type of the '''Operating system choose "linux"'''
## The version '''choose "other linux"''' and must match with the <code><ARCH></code> choosed (like x86)
## By push "Next" button to continue to create the machine
# Second are RAM of the virtual machine, choose '''memory as 512MB''' minimum amount of. and push "Next" button.
# A new windows with a '''Hard disk assistant will opened'''
## First choose the option '''"Choose a existing hard disk drive"''' and push the "Folder button" aside.
## An open file dialog window will be opened, '''search for the "VMDK" file <code>rawdisk-sdb.vmdk</code>and choose it'''
## Choose the '''dynamically allocated''' and push the "Next" button.
## By push on "Create" the virtual machine will be ready to use
# Now the main window show you the "alpine-desktop-try1" created virtual machine, select them
## By push on "Configuration" yellow button go to the storage part and push it over
## Select the disc drive icon for CD/DVD rom and push on the again CD/DVD drive icon at the right
## Mini menu will opened, choose to select and external file event the host CD/DVD drive
## A file open dialog will open.. search to the downloaded iso of Alpine and select it
## Once defined the iso file to boot, push on the "Ok" button and virtual machines are finished.
# Push on the green arrow that said "Start" to start the virtual machine and boot up the iso

[[File:Alpine Install from a disc to a virtualbox machine single only-01-0.png|center|Alpine configuration commonly used of a virtual machine on virtual box virtual machine]]

== Booting the Alpine ISO disc ==

When the machine start, you must be sure to choose the Optical drive (commonly named CD/DVD Rom drive), so the disc/iso will boot and after a while a command line shell will show you:

{{Tip|If your system are not configure to boot from a CD/DVD drive must be configure in the BIOS, ask to your vendor or technical support, VirtualBox need to hit the F12 key to choose boot medium}}

[[File:Installation-alpine-alpine-setup-2-boot.png|350px|thumb|right|Installation : setup-alpine : booting process until login prompt]]

{{:Installation_pages_setup-alpine_script_normal}}
{{:Installation_pages_setup-disk_script_alpine_main_single}}

== Finishing the installation ==

After al the scripts setup ends, a "reboot" will be offered, just type "reboot" and press enter, remobe the boot media and new installed system will be booted.

[[File:Installation-alpine-alpine-setup-9-setup-disk-3-7end.png]]

If you try to start that installation maybe '''you cannot see a graphical window system? take easy''' and get calm down.. in Alpine all are made by the right way.. so '''if user need a desktop.. user can install a desktop''' follow the next: [[Alpine newbie packages]] or bypass and go directly to [[Alpine newbie desktops]]

= Documents series =

{| class="wikitable"
|-
! Previous required !! What's next to read
|-
| [[Alpine newbie install manual]] || [[Alpine newbie packages]]
|}

= See Also =

# [[Alpine newbie packages]]
# [[Alpine newbie desktops]]
# [[Alpine newbie developer]]
# [[Alpine newbie lammers]]

[[Category:Newbie]]

Alpine Install: from a disc to a virtualbox machine single only

2022-01-06T15:44:29Z

Mckaygerhard: uinlink all newbie pages

'''Overall description:''' Installing Alpine from an official disc image to a VirtualBox machine.

This document guides you through installing Alpine on a VirtualBox VM - this is ideal if you only want to try out Alpine.

== Terminology ==

* '''Host machine''': the machine you're running VirtualBox on. It will "host" the target virtual machine.
* '''Guest machine''': your target machine where Alpine will be installed, executed by the VirtualBox software on the host machine.
* '''Reserved RAM''': the amount of host machine RAM that will be needed for exclusive use by the guest machine. The host machine cannot use this RAM while the guest machine is running.
* '''Virtual disc''': the emulated storage medium attached to the guest machine. Usually it is a file (or several files) which VirtualBox presents as a disk to the guest OS (Alpine).

== Requirements ==

On the host machine:

* Qemu or VirtualBox using package manager! Do not promote Oracle's policy of overversiones without security patches
* At least 1GB of RAM, 2GB or more if you don't want lockups while running something in addition to the virtual machine software
* The <code>curl</code> or <code>wget</code> programs to download the image to boot in the virtual software

On the guest machine:

* Minimum 512Mb RAM, but 1Gb or more is recommended if you're going to use a graphical interface. That obviouly must be in sync with the host machine.

== Preparing the medium to install ==

Download the source medium to install and put into your home; there's more hardware medium sources to download, like the '''[https://en.wikipedia.org/wiki/Linux_on_z_Systems s390x]''' and '''[https://en.wikipedia.org/wiki/Ppc64 ppc64le]''', but because VirtualBox handles only '''x86''' and '''x64'''
hardware, we will list those here

The name of the source medium to install will be in the following format: '''<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>''' where <code>ARCH</code> and <code>VERSION</code> can be one of the following, for VirtualBox virtual machines:

* <code><ARCH></code> can be
** '''x86''': The well known i386 to i686. (32-bit machines)
** '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines.
* <code><VERSION></code> can be
** '''latest-stable''' as the name says, the latest, stable version
** '''3.10''' UEFI support began with this version
** '''3.8''' recommended for machines manufactured between 2012 and 2016
** '''3.6''' recommended for older machines

Typically, the version most commonly used in a virtual box is the x86. The hardware is cheaper and operation does not consume a lot of memory.
The iso download URL format is:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' will be:
<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

'''Graphical download''': Just point the web browser to that URL and the download will start. A file with '''.iso''' extension type, with a name like <code>"alpine-standard-3.10.0-x86.iso"</code> (if i386/686); will be downloaded into the directory specified in your browser configuration.

'''Command line method''': just open a terminal and execute: <code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>, for example:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' the command will be:
<code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

You must be mindful of the directory you run the command from, as that is where the file will be saved.

== Preparing the virtual machine to install ==

Start the VirtualBox software program.

# In the main window '''create a new virtual machine''' by '''clicking the blue spark New button'''. That will open a new window with the following questions:
## It will ask for a '''name for the virtual like "alpine-desktop-try1"'''.
## The Type of the '''Operating system choose "linux"'''.
## The version '''choose "other linux"'''. It must match the chosen <code><ARCH></code> (e.g. x86).
## Click the "Next" button to continue creating the virtual machine.
# When selecting the amount of RAM for the virtual machine, choose a minimum of '''512MB''' then click the "Next" button.
# A new window with a '''Hard disk assistant will open'''.
## First choose '''"Create a virtual hard disk now"''' then click the "Create" button.
## Next choose the option for '''hard disk type: VDI''' and push "Next" button.
## Choose '''dynamically allocated''' then click the "Next" button.
## The next window will offer the '''size of virtual disk. 4GB''', however, you may choose a different amount of storage space.
## After clicking on "Create" the virtual machine will be ready to use.
# Now the main window shows you the "alpine-desktop-try1" virtual machine, select it.
## Click on the yellow "Configuration" button. Go to the storage menu and pull it down.
## Select the disc drive icon for CD/DVD ROM and click on the CD/DVD drive icon at the right.
## A Mini menu will open. Select an external file event the host CD/DVD drive.
## A file open dialog will open. Search for the downloaded Alpine iso and select it.
## Once you choose the iso file to boot, click the "Ok" button to finish creating the virtual machine.
# Click the green "Start" arrow to start the virtual machine and boot the iso.

[[File:Alpine Install from a disc to a virtualbox machine single only-01-0.png|center|Alpine configuration commonly used of a virtual machine on virtual box virtual machine]]

== Booting the Alpine ISO disc ==

When the machine starts, you must be sure to choose the Optical drive (commonly named CD/DVD ROM drive), so the disc/iso will boot. After a while, a command line shell will show you:

{{Tip|If your system are not configure to boot from a CD/DVD drive, you must configure the BIOS. Ask to your vendor or technical support. Hitting the F12 key will enable you to choose the virtual machine's boot medium}}

[[File:Installation-alpine-alpine-setup-2-boot.png|350px|thumb|right|Installation : setup-alpine : booting process until login prompt]]

{{:Installation_pages_setup-alpine_script_normal}}
{{:Installation_pages_setup-disk_script_alpine_main_single}}

== Finishing the installation ==

After setup ends, a "reboot" will be offered. Type "reboot" and press enter and your newly installed virtual machine will be booted. Don't forget to remove the boot medium.

[[File:Installation-alpine-alpine-setup-9-setup-disk-3-7end.png]]

'''You cannot see a graphical window system? No problem.''' With Alpine, GUIs are made the right way. So '''if you need a desktop, you can install a desktop''' follow this link: [[Alpine newbie apk packages]] or go directly to [[Alpine newbie desktops]]

= Documents series =

{| class="wikitable"
|-
! Previous required !! What's next to read
|-
| [[Alpine newbie install manual]] || [[Alpine newbie packages]]
|}

= See Also =

# [[Alpine newbie packages]]
# [[Alpine newbie desktops]]
# [[Alpine newbie developer]]
# [[Alpine newbie lammers]]

[[Category:Newbie]]

LXQt

2022-01-06T14:42:12Z

Mckaygerhard: remove newbie reference to stop the discussion

'''LXQt''' is a lightweight QT based desktop environment, LXQt was originally a port of LXDE to QT (called LXDE-Qt), it was created due to LXDE maintainer Hong Jen Yee being dissatisfied with GTK 3, on 21 July 2013 the LXDE(-Qt) and [https://en.wikipedia.org/wiki/Razor-qt Razor-qt] projects merged creating LXQt.

 

= Prerequisites =

* [[Installation|Install]] AlpineLinux
* [[Post_installation#Creating_a_new_user_account|Create a user account]] (optional but recommended)
* [[Post_installation#Repositories|Enable the Community repository]]
* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]

{{Note|LXQt on Alpine currently requires having the edge repos enabled}}

 

= Installation =

{{Cmd|# apk add lxqt-desktop lxqt-core lxqt-panel lxqt-admin lxqt-config lxqt-notificationd lxqt-powermanagement lxqt-themes openbox}}

{{Note|By default LXQt usually uses [[Openbox]] as its window manager, but LXQt supports many different window managers, See: [https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers ConfigWindowManagers - LXQt Github wiki]}}

== Optional packages ==

===== Documentation =====

* {{Pkg|lxqt-config-doc}}
* {{Pkg|lxqt-openssh-askpass-doc}}
* {{Pkg|lxqt-panel-doc}}
* {{Pkg|lxqt-policykit-doc}}
* {{Pkg|lxqt-runner-doc}}
* {{Pkg|lxqt-session-doc}}
* {{Pkg|lxqt-sudo-doc}}

===== Development files =====

* {{Pkg|lxqt-globalkeys-dev}}
* {{Pkg|lxqt-panel-dev}}

===== Misc =====

* {{Pkg|lxqt-build-tools}}

= See Also =
* [[Installation]]
* [[Post installation]]
* [[Desktop environments and Window managers]]

[[Category:Desktop]]

Post installation

2022-01-06T14:41:43Z

Mckaygerhard: remove newbie original category from guest pages created, remove reference to stop the discussion

{{Draft|This page "should" contain accurate and up to date information but is a work in progess}}

== General Notes ==

* When '''#''' is displayed before a command that means the command needs to be run with root privileges,

* Anything in < > is likely just a placeholder that you need to replace (example: <editor> file.txt)

* Some information in here might be a repeat of information in other wiki pages, if you find a section where that is the case please add a link to the original wiki page.

 

== Network setup ==

==== Wi-Fi ====

* [[Wi-Fi]]
* [[NetworkManager]]

==== Ethernet (Wired) ====

{{Expand|Documentation on Ethernet (Wired) internet setup needs to be created/expanded, maybe information from other wiki's/docs might be helpful?}}

* [[Ethernet|Ethernet]]
* [[NetworkManager]]

 

== Creating a new user account ==

After installing Alpine by default you only get a root account. You will probably want to create an account that is not root,

{{cmd|# adduser <YourUsername>}}
{{Note|replace <YourUsername> with the username of your choice}}

 

You will probably want to install '''doas''' so you can allow <YourUsername> to use root privileges
{{cmd|# apk add doas}}

 

If you want your user to be able to use root privileges add them to the Wheel group
{{cmd|# adduser <YourUsername> wheel}}

 

Allow members of the '''Wheel''' group to use root privileges with doas:

{{cmd|# <editor> /etc/doas.d/doas.conf}}

add this to a new line:
{{cmd|permit persist :wheel}}

 

Switch to the new account type '''exit''' in the shell and login with the new user,

 

==== Groups ====

Groups are needed for certain operations on your system (e.g <code>audio</code> to manage your system audio), below is a list of groups,
{{Note|may be incomplete, if you see a group missing please add it along with a description}}

{{Cmd|disk:x:6:root,adm Only if need usage vith virtual machines and access to other partitions over new disks for
lp:x:7:lp If will need to use printing services and printers management
floppy:x:11:root Backguard compatible group, use only if need access to external special devices
audio:x:18: Need for audio listening and management of sound volumes as normal user
cdrom:x:19: For access to disck writers and mounting DVD, BR or CD rom disk as normal user
dialout:x:20:root Need for dial private connections and use of modems as normal users
tape:x:26:root Need have into this if plan to use special devices for backup.. rarelly in no servers
video:x:27:root For usage of cameras, mor thant one GPU special features, as normal user
netdev:x:28: For network connections management as normal user
kvm:x:34:kvm Only if as normal user will manage graphically virtual machines.. rarelly on no servers
games:x:35: Need if you want to play games also specially need if will share score between users
cdrw:x:80: To write RW-DVD, RW-BR or RW-CD disk on a disk writing device
apache:x:81: Need if you will perfom development as normal user and want to publish locally on web server
usb:x:85: Need to access to special usb devices, deprecated group
users:x:100:games If you plan to used common files for all users, mandatory as desktop usage}}

 

To add your user to a group use the following command:

{{Cmd|# adduser <YourUsername> <group>}}
{{Note|you need to log out for the group change(s) to take effect}}

 

== Shell ==

{{Note|[https://en.wikipedia.org/wiki/Almquist_shell ash] is the only shell included with Alpine by default, you will need to install another shell if you want a different one}}

 

By default AlpineLinux uses the [https://en.wikipedia.org/wiki/Almquist_shell ash] shell, but many users may prefer {{Pkg|bash}}, {{Pkg|zsh}}, {{Pkg|fish}} or another shell, to change this run the following command:

{{Cmd|$ chsh}}
enter your password and you should get the following output:

{{Cat|$ chsh|Changing the login shell for user
Enter the new value, or press ENTER for the default
Login Shell [/bin/ash]:}}

 

now enter the path for the shell you want to use (e.g <code>/bin/bash</code>) and press enter to confirm this change,
{{Note|You may need to log out or reboot for this change to take effect, '''ash''' is a part of busybox so you can revert back to '''ash''' at anytime with the same steps}}

 

== Repositories ==

The Alpine software repositories have three branches:

* '''Main''': Main packages are the Alpine software that has direct support and updates from the Alpine core and main team. They also have official special documentation, are always available for all releases and will have substitutions if some are not continued from upstream. Commonly, those packages are selected due to their responsibility and stability with respect to upstream availability. When those in ''testing'' perform well or are mature, they go to the ''main'' branch.
* '''Community''': Community packages are those made by users in concert with the official developers and integrated into the Alpine packages. They are user supported. Support could end if the user ends support with respect to Alpine work. For example, could not include substitution in next release due to lack of support by the upstream author. They are in ''edge'' and when accepted, go to the ''community'' branch.
* '''Edge''': New packages come into testing repositories of the edge Alpine version and are those made by any contributor or man power on Alpine. The edge contains unstable current development content. This branch has no release linked or related to Alpine. They are in ''testing'' and when accepted, go to the ''community'' branch.

 

By default only the '''main''' repository is enabled, most users will probably want to enable the '''community''' repository, to enable a repository remove the '''#''' in front of the url along with any blank space.

 

(Example) Disabled:
{{cat|/etc/apk/repositories|#http://dl-cdn.alpinelinux.org/alpine/v3.15/community}}

(Example) Enabled:
{{cat|/etc/apk/repositories|http://dl-cdn.alpinelinux.org/alpine/v3.15/community}}

 

To edit the repositories open the file in a text editor:
{{cmd|# <editor> /etc/apk/repositories}}

 

Example default configuration:

{{cat|/etc/apk/repositories|#/media/cdrom/apks
http://dl-cdn.alpinelinux.org/alpine/v3.15/main
# http://dl-cdn.alpinelinux.org/alpine/v3.15/community
#http://dl-cdn.alpinelinux.org/alpine/edge/main
#http://dl-cdn.alpinelinux.org/alpine/edge/community
#http://dl-cdn.alpinelinux.org/alpine/edge/testing}}

{{Note|The edge repositories contain unstable and/or possibly untested packages use at your own risk!}}

 

To avoid having to manually update the verison in '''/etc/apk/repositories''' for each Alpine Linux update, change '''v3.15''' to '''latest-stable'''

Example:
{{cat|/etc/apk/repositories|#/media/cdrom/apks
http://dl-cdn.alpinelinux.org/alpine/latest-stable/main
http://dl-cdn.alpinelinux.org/alpine/latest-stable/community
#http://dl-cdn.alpinelinux.org/alpine/edge/main
#http://dl-cdn.alpinelinux.org/alpine/edge/community
#http://dl-cdn.alpinelinux.org/alpine/edge/testing}}

{{Note|Changing the repositories to latest-stable may initiate unexpected release upgrades, do this at your own risk!}}

 

For [https://en.wikipedia.org/wiki/HTTPS#Technical security reasons] it may be a good idea to change the url's from '''http''' to '''https'''

Example:
{{cat|/etc/apk/repositories|#/media/cdrom/apks
https://dl-cdn.alpinelinux.org/alpine/v3.15/main
https://dl-cdn.alpinelinux.org/alpine/v3.15/community
#https://dl-cdn.alpinelinux.org/alpine/edge/main
#https://dl-cdn.alpinelinux.org/alpine/edge/community
#https://dl-cdn.alpinelinux.org/alpine/edge/testing}}

{{Note|some Alpine Linux package mirrors may not support https, if that is the case you will need to revert back or change mirrors}}

 

Once you have edited '''/etc/apk/repositories''' sync the repositories with:

{{cmd|# apk update}}

 

== Installing a Display Server (for graphical sessions) ==

==== Xorg ====
Most desktop enviroments (DE) or Windows Managers (WM) require Xorg (also called: X11, X), although in the future many will fully migrate to [[Wayland]] currently Xorg is still widely used,

 

There is two ways you can get Xorg installed,

 

By default Alpine Linux provides a script that will install Xorg, run the following command to install Xorg:
{{cmd|# setup-xorg-base}}

or

{{cmd|# apk add xorg-server xorg-server-common xorg-server-dev xorgproto xorgxrdp xorgxrdp-dev}}
{{Note| the apk add method is probably incomplete}}

 

==== Wayland ====
''See also: [[Wayland]]''

{{Expand|Wayland documentation needs to be expanded}}

 

== Fonts ==

If you plan to use a graphical environment you may need/want to install fonts
{{Note|depending on the desktop environment/window manager fonts may or may not be installed automatically or as dependencies}}

'''See: [[Fonts|Fonts]]'''

 

== Installing a desktop environment or window manager ==

'''See: [[Desktop environments and Window managers]]'''

 

== Sound ==

By default Alpine doesnt come with any Sound managment out of the box, these are your options:

* [[PipeWire]]
* [[PulseAudio]]
* [[ALSA]]

{{Note|If your unsure {{Pkg|pipewire}} is the recommended option}}

 

== Man pages ==

Most Linux distributions have '''man''' pages, man pages allow you type <code>man <package></code> in a terminal and get some useful information about packages installed on your system quicky without a internet connection, by default Alpine does not include '''man''', you can add that with the following:

* <code># apk add man-pages</code> Installs basic manual pages.
* <code># apk add mandoc</code> Installs the man command to be able to open man pages.
* <code># apk add mandoc-apropos</code> Installs the apropos command to search in man pages.
* <code># apk add docs</code> Installs all the *-doc sub-packages of installed packages.

{{Note|man pages may not be available for every package}}

 

== Language support ==

{{Expand}}

* Fix unicode defaults: <code>sed -i 's/#unicode="NO"/#unicode="NO"\nunicode="YES"/' /etc/rc.conf</code>
* <code>apk add musl-locales</code> Installs a limited set of locales (languages) for musl (C library) generated console messages.
* Listing defined locales is possible with <code>locale -a</code>
* <code>cp /etc/profile.d/locale.sh /etc/profile.d/locale.sh.sh</code> Copies the default locale settings. Then the custom override file can be edited <code>nano /etc/profile.d/locale.sh.sh</code>.
* <code>apk add lang</code> Pulls in the translation packages of all installed packages.
* <code>apk list hunspell*</code> To list available hunspell dictionary packages.
* <code>apk list *-xy *-xy-*</code> To list translation packages for your specific (xy) language (for example, pt for Portuguese).

 

== Miscellaneous ==

Some other miscellaneous things that might be useful:

==== basic tools ====

Alpine is a minimalist Linux distribution. If you expected a behavior like other Linux distributions, the similarity to them will be minimal at best. Run:

{{Cmd|# apk add sed attr dialog bash bash-completion grep util-linux pciutils usbutils binutils findutils readline lsof less nano curl}}

{{Cmd|<nowiki>$ export PAGER=less</nowiki>}}

 

== Troubleshooting ==

==== I dont have permission to do anything in my user's home directory ====

By default the permissions of your new user(s) home directory may be limited to the root account, run one of these commands to change that:

{{cmd|# chmod 700 /home/<YourUsername>}}

or

{{cmd|# chmod 777 /home/<YourUsername>}}

 

== See also ==
* [[Installation]]
* [[Comparison with other distros]]

[[Category:Installation]]

Alpine Install: from a disc to a virtualbox machine single only

2022-01-06T14:38:35Z

Mckaygerhard: remove newbie reference to stop the discussion

'''Overall description:''' Installing Alpine from an official disc image to a VirtualBox machine.

This document guides you through installing Alpine on a VirtualBox VM - this is ideal if you only want to try out Alpine. For other ways to install (including dual-boot) see [[Alpine_newbie_install_manual#Ways_to_install_Alpine_into_machines_or_virtuals|Alpine_newbie_install_manual]].

== Terminology ==

* '''Host machine''': the machine you're running VirtualBox on. It will "host" the target virtual machine.
* '''Guest machine''': your target machine where Alpine will be installed, executed by the VirtualBox software on the host machine.
* '''Reserved RAM''': the amount of host machine RAM that will be needed for exclusive use by the guest machine. The host machine cannot use this RAM while the guest machine is running.
* '''Virtual disc''': the emulated storage medium attached to the guest machine. Usually it is a file (or several files) which VirtualBox presents as a disk to the guest OS (Alpine).

== Requirements ==

On the host machine:

* Qemu or VirtualBox using package manager! Do not promote Oracle's policy of overversiones without security patches
* At least 1GB of RAM, 2GB or more if you don't want lockups while running something in addition to the virtual machine software
* The <code>curl</code> or <code>wget</code> programs to download the image to boot in the virtual software

On the guest machine:

* Minimum 512Mb RAM, but 1Gb or more is recommended if you're going to use a graphical interface. That obviouly must be in sync with the host machine.

== Preparing the medium to install ==

Download the source medium to install and put into your home; there's more hardware medium sources to download, like the '''[https://en.wikipedia.org/wiki/Linux_on_z_Systems s390x]''' and '''[https://en.wikipedia.org/wiki/Ppc64 ppc64le]''', but because VirtualBox handles only '''x86''' and '''x64'''
hardware, we will list those here

The name of the source medium to install will be in the following format: '''<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>''' where <code>ARCH</code> and <code>VERSION</code> can be one of the following, for VirtualBox virtual machines:

* <code><ARCH></code> can be
** '''x86''': The well known i386 to i686. (32-bit machines)
** '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines.
* <code><VERSION></code> can be
** '''latest-stable''' as the name says, the latest, stable version
** '''3.10''' UEFI support began with this version
** '''3.8''' recommended for machines manufactured between 2012 and 2016
** '''3.6''' recommended for older machines

Typically, the version most commonly used in a virtual box is the x86. The hardware is cheaper and operation does not consume a lot of memory.
The iso download URL format is:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' will be:
<code><nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

'''Graphical download''': Just point the web browser to that URL and the download will start. A file with '''.iso''' extension type, with a name like <code>"alpine-standard-3.10.0-x86.iso"</code> (if i386/686); will be downloaded into the directory specified in your browser configuration.

'''Command line method''': just open a terminal and execute: <code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v</nowiki><VERSION>/releases/<ARCH>/alpine-standard-<VERSION>.0-<ARCH>.iso</code>, for example:

* For '''"x86" <code><ARCH></code>''' and '''"3.10" <code><VERSION></code>''' the command will be:
<code>wget -c -t8 --no-check-certificate <nowiki>http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86/alpine-standard-3.10.0-x86.iso</nowiki></code>

You must be mindful of the directory you run the command from, as that is where the file will be saved.

== Preparing the virtual machine to install ==

Start the VirtualBox software program.

# In the main window '''create a new virtual machine''' by '''clicking the blue spark New button'''. That will open a new window with the following questions:
## It will ask for a '''name for the virtual like "alpine-desktop-try1"'''.
## The Type of the '''Operating system choose "linux"'''.
## The version '''choose "other linux"'''. It must match the chosen <code><ARCH></code> (e.g. x86).
## Click the "Next" button to continue creating the virtual machine.
# When selecting the amount of RAM for the virtual machine, choose a minimum of '''512MB''' then click the "Next" button.
# A new window with a '''Hard disk assistant will open'''.
## First choose '''"Create a virtual hard disk now"''' then click the "Create" button.
## Next choose the option for '''hard disk type: VDI''' and push "Next" button.
## Choose '''dynamically allocated''' then click the "Next" button.
## The next window will offer the '''size of virtual disk. 4GB''', however, you may choose a different amount of storage space.
## After clicking on "Create" the virtual machine will be ready to use.
# Now the main window shows you the "alpine-desktop-try1" virtual machine, select it.
## Click on the yellow "Configuration" button. Go to the storage menu and pull it down.
## Select the disc drive icon for CD/DVD ROM and click on the CD/DVD drive icon at the right.
## A Mini menu will open. Select an external file event the host CD/DVD drive.
## A file open dialog will open. Search for the downloaded Alpine iso and select it.
## Once you choose the iso file to boot, click the "Ok" button to finish creating the virtual machine.
# Click the green "Start" arrow to start the virtual machine and boot the iso.

[[File:Alpine Install from a disc to a virtualbox machine single only-01-0.png|center|Alpine configuration commonly used of a virtual machine on virtual box virtual machine]]

== Booting the Alpine ISO disc ==

When the machine starts, you must be sure to choose the Optical drive (commonly named CD/DVD ROM drive), so the disc/iso will boot. After a while, a command line shell will show you:

{{Tip|If your system are not configure to boot from a CD/DVD drive, you must configure the BIOS. Ask to your vendor or technical support. Hitting the F12 key will enable you to choose the virtual machine's boot medium}}

[[File:Installation-alpine-alpine-setup-2-boot.png|350px|thumb|right|Installation : setup-alpine : booting process until login prompt]]

{{:Installation_pages_setup-alpine_script_normal}}
{{:Installation_pages_setup-disk_script_alpine_main_single}}

== Finishing the installation ==

After setup ends, a "reboot" will be offered. Type "reboot" and press enter and your newly installed virtual machine will be booted. Don't forget to remove the boot medium.

[[File:Installation-alpine-alpine-setup-9-setup-disk-3-7end.png]]

'''You cannot see a graphical window system? No problem.''' With Alpine, GUIs are made the right way. So '''if you need a desktop, you can install a desktop''' follow this link: [[Alpine newbie apk packages]] or go directly to [[Alpine newbie desktops]]

For other ways to install, see the [[Alpine_newbie_install_manual#Ways_to_install_Alpine_into_machines_or_virtuals|Alpine_newbie_install_manual]]

= Documents series =

{| class="wikitable"
|-
! Previous required !! What's next to read
|-
| [[Alpine newbie install manual]] || [[Alpine newbie apk packages]]
|}

= See Also =

# [[Alpine newbie apk packages]]
# [[Alpine newbie desktops]]
# [[Alpine newbie developer]]
# [[Alpine newbie lammers]]

[[Category:Installation]]

Installing Alpine in a virtual machine

2022-01-06T14:37:08Z

Mckaygerhard: remove newbie reference to stop the discussion

This page will walk you through how to setup a virtual machine for AlpineLinux installation

= VirtualBox =

This guide describes a standard install of Alpine within a Virtual Box VM. (virtual machine)

Oracle VM [http://virtualbox.org VirtualBox] runs one or more virtual x86 or x64 guests on a host computer. 
This enables you to install and test Alpine on your main computer almost as you would any other program.

== Preparation ==

== Install Virtual Box on host ==

First you'll need to download and install Virtual Box on your host computer. Either from the official homepage (for Windows, OS X or Solaris) or from your distribution’s repository (for Linux).

Virtual Box consists of two components:

* VirtualBox platform package
* Oracle VM VirtualBox Extension Pack

Install both and start VirtualBox to check for proper operation. If you have problems, consult the VirtualBox user manual or one of the support sites for Virtual Box.

== Download Alpine ==

Download the [https://www.alpinelinux.org/downloads/ Virtual Alpine ISO], which is optimized for virtual systems, from the Alpine Download section. Save it in a location where you can find it easily.

== Setting up virtual PC ==

Start Virtual Box. You will see a mostly empty window with a couple symbols in the upper left corner. The leftmost icon is a multi pointed star. If you hover your mouse over it, the tooltip will say “New”.

Click on the multi pointed star to create a new machine. A window will pop up, asking you some questions about the virtual (guest) computer you want to create.

# Name: Choose anything you like. e.g. “Alpine”.
# Type: Linux
# Version: Other Linux, either 64 bit or 32 bit. Choose 64 bit if you downloaded the x86_64 Alpine-ISO, or 32 bit if you downloaded the x86 Alpine-ISO.
# Use the default values for the other questions, simply click “next” or “create” until the dialogue finishes.

You will see a new entry in Virtual Box, called Alpine (or the name you chose during step 1 in the dialogue above). Click on it for more information about your guest.

One of the entries should read Mass storage, and offer an IDE controller with a primary master (the virtual hard disc) and a secondary master (the virtual optical drive).

Click on the secondary master. A context menu will pop up. Select the entry “choose image” and open the Alpine ISO you downloaded earlier.

Once that is done, click on the green start arrow on the menu bar.

== Install Alpine on the virtual computer ==

Follow the steps described in the [[Installation#Installation_Handbook|Installation Handbook]], just as if you were installing Alpine on a real PC.

{{Tip|Do not reboot your virtual box after the installation. Instead, shut down the virtual machine, remove the Alpine ISO from the virtual optical drive, then restart the virtual machine.}}

== Install drivers for Virtual Box ==

Once you successfully reboot into the Alpine VM, there are two steps left:

# Enable the [[Enable_Community_Repository|Community Respository]]
# Enable [[VirtualBox_shared_folders|VirtualBox shared folders]]

These two steps install all drivers that other programs might request, and activate several comfort functions.

{{Note|The Virtualbox webcam driver is not present in the kernel provided with the Virtual Alpine ISO. To use the webcam whilst keeping the installation footprint small, install the <code>linux-firmware-none</code> package using apk, then install the <code>linux-lts</code> package to download a kernel with the appropriate drivers without pulling in hundreds of MB of uneeded firmware files. Uninstall the <code>linux-virt</code> package and reboot to use the new kernel.}}

 

= KVM / QEMU =

 

= VMware =

== See Also ==

* [[Installation]]
* [[Post installation]]

[[Category:Virtualization]]

UEFI

2022-01-06T14:36:41Z

Mckaygerhard: remove newbie reference to stop the discussion

{{TOC right}}

= UEFI and BIOS definitions and introduction =

In the old days, BIOS (for '''B'''asic '''I'''nput '''O'''utput '''S'''ystem) was how computers booted from the 1980s onwards. But now in newer hardware for devices, servers, laptops and desktops computers the UEFI (for '''U'''nified '''E'''xtensible '''F'''irmware '''I'''nterface) defines a software interface between an operating system and platform firmware into the vendor hardware.

UEFI replaces the BIOS firmware interface originally present in all IBM PC-compatible personal computers, early modern computer's UEFI firmware implementations provide legacy support for BIOS services.

== The history so far ==

Due newer incoming 64-bit incoming processors the older computers boot process are not more possible. It started life on Itanium (Intel's first 64-bit processor) systems. Itanium had no support for 32-bit, and certainly no embedded 80286, so they had to come up with a different system.

All this was driven by a problem in the most extensive and used architecture: x86 32-bit, inclusivelly a new 2019's Skylake i7-6700k still has an 80286 embedded in it because all x86 BIOS strictly only supports 16-bit 8088-derivative processors.

Intel developed the original Extensible Firmware Interface (EFI) specification. Some of the EFI's practices and data formats mirror those from M$ Redmon's OS. In 2005, UEFI deprecated EFI 1.10 (the final release of EFI). The Unified EFI Forum is the industry body that (seems) "manages" the UEFI specification.

= Alpine UEFI support =

Currently are only in basic form, not all the architectures are complete supported.

The '''support for
[https://en.wikipedia.org/wiki/EFI_system_partition EFI System Partition] was started in the [https://alpinelinux.org/posts/Alpine-3.7.0-released.html Alpine 3.7.0 new mayor release]''', preliminary support in that version does not create the
[https://en.wikipedia.org/wiki/EFI_system_partition EFI Partition], only has support for existing ones or manually created.

Started '''in the [https://alpinelinux.org/posts/Alpine-3.8.0-released.html Alpine 3.8.0 new mayor release] support in the installer for the GRUB boot loader was added''' so now Linux experimental users can play with combinations of solutions and proper
[https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface UEFI] complete installations. Please refer to [[Alpine_and_UEFI#UEFI_and_BIOS_definitions_and_introduction|UEFI_and_BIOS section of this page]] first.

'''[https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#EFI_system_partition EFI System Partition] are not the complete overall of the [https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface UEFI], it's just the need minimal infrastructure to property boot by and [https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Implementation_and_adoption UEFI modern machine]. See the [[Alpine_and_UEFI#UEFI_mandatory_partition_mechanics|Alpine UEFI partition mechanics notes]] section in this page for details.'''

Please read carefully the [[Alpine_and_UEFI#UEFI_and_BIOS_definitions_and_introduction|UEFI_and_BIOS section of this page]].

== Minimum Alpine partition scheme ==

Alpine Linux requires a root partition, but on UEFI systems an EFI System Partition is also required. The EFI System Partition must contain a bootloader program in {{path|\EFI\$bootloader.efi}}. The current status of that mechanics to boot '''in Alpine Linux are still in development and only basic support to existing mades are provided'''. See [[Alpine_and_UEFI#UEFI_mandatory_partition_mechanics|UEFI_mandatory_partition_mechanics]] for details.

== Notes about the boot flags and boot partition ==

UEFI booting does not involve any "boot" flag, that's it's a need only for BIOS booting. The UEFI booting relies solely on the boot entries in NVRAM. Parted and its front-ends use a "boot" flag on GPT to indicate that a partition is an EFI system partition.

A BIOS boot partition is only required when using GRUB for BIOS booting from a GPT disk. The partition has nothing to do and it must not be formatted with a file system or mounted.

== Alpine disk layout for UEFI ==

You will need a disk layout that your system firmware is capable of booting, you '''will need a boot partition and a root partition'''. Other architectures may have different requirements and not all are supported, please read [[Alpine_and_UEFI#UEFI_mandatory_partition_mechanics|UEFI_mandatory_partition_mechanics]] for details.

If you don't already know what filesystem format you want your boot partition, choose '''ext2'''. The '''root partition, and any additional partitions or LVM volume groups, may be in any format that the kernel is capable of reading'''.

==== UEFI/GPT minimal layout ====

{| class="wikitable"
! Mount point
! Partition
! Partition type Purpose
! Recommended minimum size
|-
| /boot or /efi
| /dev/sda1
| Boot system partition for EFI
| 260 MiB
|-
| /
| /dev/sda2
| Alpine Linux root system OS
| 1–32 GiB
|-
| none
| /dev/sda3
| Linux swap memory
| 1-2Gb
|}

==== BIOS/MBR minimal layout ====

{| class="wikitable"
! Mount point
! Partition
! Partition type Purpose
! Recommended minimum size
|-
| /boot
| /dev/sda1
| Boot grub partition (optional)
| 100 MiB
|-
| /
| /dev/sda2
| Alpine Linux root system OS
| 1–32 GiB
|-
| none
| /dev/sda3
| Linux swap memory
| 1-2Gb
|}

==== BIOS/GPT minimal layout ====

{| class="wikitable"
! Mount point
! Partition
! Partition type Purpose
! Recommended minimum size
|-
| None
| /dev/sda1
| BIOS boot partition
| 8 MiB
|-
| /
| /dev/sda2
| Alpine Linux root system OS
| 1–32 GiB
|-
| none
| /dev/sda3
| Linux swap memory
| 1-2Gb
|}

= BIOS boot process for newbies =

BIOS mainly supports two methods of booting - loading approximately 448 bytes of 8088 machine code from the start of a floppy disk, or the same from the start of a fixed IDE disk.

BIOS can only assume one boot loader occupying the start of hard drive. So each OS overwrites it with its own boot loader. This is very messy. There's also the 2 TiB issue with MBR.

In order to make your drive more useful, it's split up into partitions - chunks of disk space which can be treated as independent drives from inside your OS. Windows (following on from MS-DOS) only supports one method for partitioning its boot drive on BIOS systems, which is MBR.

MBR cannot handle disks larger than 2 TiB (232 × 512 bytes). Therefore, it is impossible to use any drive space beyond 2 TiB using MBR layout. So if you're booting from it and use BIOS, you MUST use MBR - and you simply can't use any space beyond that if your boot drive is 2TB or bigger.

Modern motherboards (since approximately 2011 onwards) are using UEFI natively, but most can emulate BIOS through the CSM (Compatibility Support Module) to maintain support for BIOS-style booting.

= UEFI boot process explained =

Well, let's start with installers. It'll read a UDF or FAT32-formatted USB drive or DVD, and look for the file /efi/boot/bootx64.efi and run it. An app, written in the UEFI "OS". It can be anything! Here's classic text adventure Zork, as a UEFI app.

It's possible to make boot media which is valid for both UEFI and BIOS. Unfortunately, in a slightly user-unfriendly twist, you (the user) need to pick the right boot entry. For example, on the wife's PC, a USB stick gets listed as both "UEFI: Sandisk Cruzer Edge" and "USB: Sandisk Cruzer Edge". Just... make sure you pick the right entry. It's impossible to change mode after this point.

It uses a different partitioning system called GPT instead of MBR, and secondly it creates an extra ~100 meg partition called the "EFI System Partition" - a FAT32 partition where the boot loader apps get installed to (no more boot sectors).

Each OS will stick its boot loader somewhere in the ESP, then send a signal to the firmware to write this new loader's location into the CMOS. Each entry installed in this manner will get its own listing in your "boot devices" list on the firmware - so if you installed MACOSX, you'll have "MACOSX Boot Manager" as an entry next to your DVD drive and hard drive after you reboot. This is why you don't do the old "unplug drive A when installing a different OS to drive B" thing, or swap cables, or anything like that. You should only have one ESP, the one on drive A.

== UEFI mandatory partition mechanics ==

Regular UEFI boot has several lists of possible boot entries, stored in UEFI config variables (normally in NVRAM), and boot order config variables stored alongside them. Unfortunately, a lot of PC UEFI implementations have got this wrong and so don't work properly.

The correct way for this to work when booting off local disk is for a boot variable to point to a vendor-specific bootloader program in <code>\EFI\$bootloader.efi</code> on the EFI System Partition (ESP), a specially tagged partition (Some OS's formatted as Fat32.. that's are unnecessary due it's just to able to poor OS's to boot like M$ Redmond OS's). The current status of that mechanics to boot in Alpine Linux are still in development and only basic support to existing made are provided.

== What's this infamous "Secure Boot"? ==

It's a way for your motherboard to prevent tampering of your OS (e.g. boot-sector viruses, or backdoors installed without your knowledge). You can provide a list of certificates you trust, then the firmware enforces that everything involved with the boot process (not just the boot loader, but the OS kernel itself, and all your device firmware like your GPU BIOS) are signed with a trusted key.

It works using cryptographic checksums and signatures. It '''stops your system from booting unsigned code'''. You can sign your own, and trust the certificate you used to do that signing. Or you can get the boot code signed by Microsoft - every motherboard has a small list of pre-trusted certificates which almost (always) includes Microsoft's certificates, which they currently let anyone use for a small fee.

Most of the programs that are expected to run in the UEFI environment are boot loaders, but others exist too. There are also programs to deal with firmware updates before operating system startup (like fwupdate and fwupd), and other utilities may live here too.

Due the "Unsigned code curse", Alpine linux [https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#EFI_system_partition EFI System Partition] '''are not the complete overall of the [https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface UEFI], it's just the need minimal infrastructure to property boot''' it!

== How to boot unsigned code? ==

'''You must disable Secure Boot. Alpine has no support for Secure Boot as it does not have a certificate''' which some other Linux distributions (mostly enterprise-related) have. This means that on many new computer systems, users have to first disable Secure Boot to be able to install Alpine Linux and the methods for doing this vary massively from one system to another, making this potentially quite difficult for users.

This is due to Microsoft's actions as a Certification Authority (CA) for Secure Boot. They sign programs/bootloaders on behalf of other trusted organizations so that their programs will run, but at great cost.. and there's nothing related to free software but affects to.. There's no Alpine Linux Certification like are with other enterprise related Linux.

Take in consideration that for Alpine linux [https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#EFI_system_partition EFI System Partition] are not the complete overall of the [https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface UEFI], it's '''just the need minimal infrastructure to property boot''' by an [https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Implementation_and_adoption UEFI modern machine]. See the [[Alpine_and_UEFI#UEFI_mandatory_partition_mechanics|Alpine UEFI partition mechanics notes]] section in this page for details.

= Overall notes and conclusions =

Currently Alpine UEFI and Secure Boot are very early stage.. Initial support was added and enabled for UEFI, but Secure Boot must be disabled.

BIOS computers (or UEFI computers with Compatibility Support Module) are the easiest and most reliable way to install Linux distributions in general. They do not need the new EFI partition to boot nor new special files.

UEFI-only computers are very common nowadays and are more challenging machines in which to install Alpine linux. They will need the the new EFI partition to boot containing special files.

= See Also =

* [[Create a Bootable Compact Flash]]
* [[Create a bootable SDHC from a Mac]]
* [[Create a Bootable USB]]
* [[Create UEFI boot USB]]
* [[Create UEFI secureboot USB]]

[[Category:Installation]]

Gitea

2022-01-06T14:36:11Z

Mckaygerhard: remove newbie reference to stop the discussion

[https://gitea.io Gitea] is a community managed lightweight code hosting solution written in Go. It is a fork of Gogs.

{{Note|This guide is not for installing Gitea in Docker. If you want to install Gitea in a Docker container, follow [https://docs.gitea.io/en-us/install-with-docker/ the official documentation]}}

== Installation ==

First, [[Enable Community Repository | Enable the Community Repository]]

Then install the {{pkg|gitea}} package:
{{cmd|apk add gitea}}

== Setting up the Database ==

{{Note|These instructions are for MariaDB. If you would like to set up another database, follow [https://docs.gitea.io/en-us/database-prep/ the official documentation]}}

Install the MariaDB and {{pkg|mariadb-client}} packages:
{{cmd|apk add mariadb mariadb-client}}

Set up the MariaDB installation and secure it:
{{cmd|<nowiki>mysql_install_db --user=mysql --datadir=/var/lib/mysql</nowiki>
service mariadb start
rc-update add mariadb
mysql_secure_installation}}

Create the <code>gitea</code> database and a user with access to it:
{{Note|Everything after the <code>mysql -u root -p</code> should be typed in the MariaDB prompt (looks like <code>MariaDB [(none)]></code>)}}
{{Note|Replace the above username 'giteauser' and password 'giteapassword' with something secure. Remember these settings. You will need them later when setting up Gitea.}}
{{cmd|mysql -u root -p

CREATE DATABASE gitea DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
GRANT ALL ON gitea.* TO 'giteauser'@'localhost' IDENTIFIED BY 'giteapassword';
FLUSH PRIVILEGES;
EXIT}}

If you want, you can uninstall the <code>mariadb-client</code> now as it's not needed anymore:
{{cmd|apk del mariadb-client}}

In {{path|/etc/gitea/app.ini}}, replace the contents of the <code>[database]</code> section with the following:
<pre>
DB_TYPE = mysql
HOST = /var/run/mysqld/mysqld.sock
NAME = gitea ; The database name set with 'CREATE DATABASE'
USER = giteauser ; The database user
PASSWD = giteapassword ; The password for the database user
</pre>

== Configurations ==

The Gitea service can be configured using {{path|/etc/conf.d/gitea}}:

{| class="wikitable"
|-
! Description !! Configuration Variable !! Default Value
|-
| User to run Gitea under || GITEA_USER || gitea
|-
| Gitea working directory || GITEA_WORK_DIR || /var/lib/gitea/
|-
| Gitea configuration file || GITEA_CONF || /etc/gitea/app.ini
|}

Some additional settings in {{path|/etc/gitea/app.ini}}:

{| class="wikitable"
|-
! Description !! Configuration Variable !! Default Value
|-
| Gitea customization directory || <code>Cannot be configured</code> || /var/lib/gitea/custom/
|-
| Web files || STATIC_ROOT_PATH || /usr/share/webapps/gitea/
|-
| Data files || APP_DATA_PATH || /var/lib/gitea/data/
|-
| Git repository storage directory || ROOT || /var/lib/gitea/git/
|-
| Log directory || ROOT_PATH || /var/log/gitea/
|}

{{Note|Gitea has a built-in web server, so there is no need to configure one. However, you can [https://docs.gitea.io/en-us/reverse-proxies/ set up a reverse proxy].}}

{{Note|To customize the look and feel of Gitea, find the correct path in {{path|/usr/share/webapps/gitea/}} and make the same path in {{path|/var/lib/gitea/custom/}}. For example, to add a new Gitea theme, create the {{path|/var/lib/gitea/custom/public/css/}} directory, then add the css for the theme there.}}

== Controlling and starting gitea ==

You should not start Gitea without setting certain environment variables and passing some options, since it won't know where to store data and logs, so it is recommended to start gitea using the init script:
{{cmd|service gitea start}}

To add Gitea to the default runlevel (such that it runs automatically on every boot):
{{cmd|rc-update add gitea}}

To stop the Gitea service:
{{cmd|service gitea stop}}

=== Running Gitea without the init script ===

If (for whatever reason), you would like to start Gitea without using the initscript, you should first stop the Gitea service:
{{cmd|service gitea stop}}

Then, run Gitea with this command (as the <code>gitea</code> user):
{{cmd|<nowiki>GITEA_WORK_DIR=/var/lib/gitea gitea web --config /etc/gitea/app.ini</nowiki>}}

This will use the correct configuration file and write to the correct directories.

== Post installation ==

{{Expand}}

After installing Gitea, go to http://localhost:3000 and start the post-installation process.

== Setting up SSH Git access ==

'''Do not''' try to be clever and use <code>ssh-copy-id</code>, as it will not have the correct command set.

As an example, if this is the public key:
<pre>
ssh-ed25519 ******************************************************************** **********@gmail.com
</pre>

The line in {{path|.ssh/authorized_keys}} needs to be:
<pre>
command="/usr/bin/gitea --config=/etc/gitea/app.ini serv key-2",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-ed25519 ******************************************************************** **********@gmail.com
</pre>

In order to do this, [https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent generate a SSH key], then go to the Gitea settings panel and click the <code>Add Key</code> button, then paste in your public key.

Now, once you've added your private key to the SSH agent, you can use SSH with Gitea like you normally would with GitHub, GitLab, etc.

[[Category:Server]]
[[Category:Git]]

AwesomeWM

2022-01-06T14:06:07Z

Mckaygerhard: remove newbie reference to stop the discussion

[[file: awesome-01.png |thumb |Screenshot]]
{{TOC right}}

= Prerequisites =
* [[Installation|Install]] Alpine Linux
* [https://wiki.alpinelinux.org/wiki/Post_installation#Creating_a_new_user_account Create a user account] (optional but recommended)
* Enable the [[Enable_Community_Repository|Community Repository]]

= Install packages =
Install awesome, xterm, lua and terminus font. 
Depending on your network speed, it might take a few minutes.
{{Cmd|# apk add awesome xterm lua terminus-font}}

== Optional packages ==
=== Video and Input packages ===
You might want to install a package suitable for your video chipset and input devices. 
For example, if you have an Sis video chipset, install 'xf86-video-sis'. For Intel video chipset, install 'xf86-video-intel'. 
{{Cmd|# apk add xf86-video-sis}}
and / or
{{Cmd|# apk add xf86-input-synaptics}}

Run 'apk search xf86-video*' to see available xf86-video packages. 
Run 'apk search xf86-input*' to see available xf86-input packages. 

=== acpid ===
If you installed your Alpine Linux as a VirtualBox or VMWare guest, you might find it handy to be able execute an ACPI shutdown. 
{{Cmd|# rc-update add acpid}}

= Configure xorg-server =
On most systems, xorg should be able to autodetect all devices. However, you can still configure xorg-server manually by launching:
{{Cmd|# setup-xorg-base}}

= Start your desktop =
{{Cmd|$ echo 'awesome' >> /home/<newuser>/.xinitrc}}
{{Cmd|$ mkdir /home/<newuser>/.config}}
{{Cmd|$ cp -r /etc/xdg/awesome /home/<newuser>/.config}}
{{Cmd|$ vi /home/<newuser>/.config/awesome/rc.lua}}

Start awesome.
{{Cmd|$ startx}}

= Troubleshooting =

D-Bus problems:

{{Cmd|D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory}}

If startx fails and returns an error about D-Bus failed to read machine uuid, as shown above, proceed as follows:

Install dbus from apk (you must be logged in as root for the step shown below)
{{Cmd|# apk add dbus}}

Log in or su to the root account, then launch the following command (Note: sudo does not work for this step):
{{Cmd|# dbus-uuidgen > /var/lib/dbus/machine-id}}

Now if startx is launched, it should load the desktop correctly

= See also =
* [[Installation]]
* [[Post installation]]
* [[Desktop environments and Window managers]]

[[Category:Desktop]]
[[Category:Lua]]

Lighttpd

2022-01-06T14:05:39Z

Mckaygerhard: remove newbie reference to stop the discussion

Its name is a portmanteau of "light" and "httpd": [http://www.lighttpd.net/ lighttpd] is a simple, standards-compliant, secure, and flexible web server.

'''lighttpd is a powerful server, made long ago to handle upwards of 10,000 connections in parallel on one server'''. It was used in wikipedia server a log time ago and also some google services.

{{Note|As for minimal sites and quick-start purposes, it is recommended due to its easy configuration process and excellent performance without much configuration. Check https://w3techs.com/technologies/details/ws-lighttpd and note that it is used in high traffic and important sites like postgresql.org}}

== General information ==

{| class="wikitable"
|-
! Feature/Artifact !! Value/Name !! Observations
|-
| Main package name || lighttpd || <code><nowiki>apk add lighttpd</nowiki></code>
|-
| Manpages and DOCs packages || lighttpd-doc || <code><nowiki>apk add lighttpd-doc</nowiki></code>
|-
| Configuration file || {{Path|/etc/lighttpd/lighttpd.conf}} || A vanilla default configuration
|-
| Html place for system pages || {{Path|/var/www/localhost/htdocs/}} || Each web server in alpine has own path for that
|-
| Dynamic files (cache, extra) || {{Path|/var/lib/lighttpd/}} || Created dynamically, each server in alpine has own path for that
|-
| Log files (error, access, etc) || {{Path|/var/log/lighttpd/}} || Each web server in alpine has own path for that
|-
| User running the webserver || lighttpd || Others Linux used "www-data" alpine has as a group
|-
| Group to common to webserver || www-data || Used to share things amont others daemons or services, like redis or apache files
|-
| Programed on || C and lua || Main engine code in C, modules and config in Lua variants
|}

==== Important Limitations ====

Some common hosting panels do not handle {{Pkg|lighttpd}} configuration management.

No HTTP/3 support.

As we read previously.. main purpose was handle several request on one server, so are focused on high load.

As main front end web server are perfect and it's '''recommended as reverse proxy server for {{Pkg|apache2}} or {{Pkg|nginx}}'''.

== Install Lighttpd ==

The installation works just out of the box for only static pages, just with install you can see webserver in action by put any file inside the {{Path|/var/www/localhost/htdocs/}} directory.

Per user web files are supported by default in {{Path|/home/<user>/public_html}} directory by default if we enable it (process are described below in further section "Lighttpd configuration".

{{Pkg|lighttpd}} is available in the Alpine Linux repositories. To install, simple launch the commands below:

<pre>
<nowiki>
apk add lighttpd

rc-update add lighttpd default

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

== Testing Lighttpd ==

This section is assuming that lighttpd is running. If you now launch a web browser from a remote system and point it to your web server, you will see a page that says "404 - Not Found". Well, at the moment there is no content available but the server is up and running.

Let's add a simple test page to get rid of the "404 - Not Found page".

{{Cmd|echo "Lighttpd is running..." > /var/www/localhost/htdocs/index.html}}

'''For testing open a browser and go to <code><nowiki>http://127.0.0.1/</nowiki></code> and you will see "Lighttpd is running..."'''. Note that we used "127.0.0.1" if you are using alpine as the only machine for all as your main desktop/pc/machine.

If you are using alpine remotelly as web server and just install it the package, '''open a browser in your desktop machine, and go to <code><nowiki>http://<webserveripaddres>/</nowiki></code>. The "webserveripaddres" are the ip address of your setup/server machine.

== Lighttpd Configuration ==

'''If you just want to serve simple HTML pages lighttpd can be used out-of-box. No further configuration needed.'''

For production purposes the [[Production LAMP system: Lighttpd + PHP + MySQL]] wiki page will explain in details all the needs, there's the [[Production Lets Encrypt: dehydrated]] wiki page with futher information to use HTTPS and lets encrypt certificates.

Due to the minimalism of alpine linux, '''unfortunately the lighttpd packaging only provided vanilla configurations not close to alpine or easy admin maintenance''', see the [[Production LAMP system: Lighttpd + PHP + MySQL]] wiki page to goin in deep about configuring lighttpd web server.

==== Controlling Lighttpd ====

'''''Start lighttpd''''': After the installation {{Pkg|lighttpd}} is not running. As we made in first section was started already but if you want to start {{Pkg|lighttpd}} manually use:

{{Cmd|rc-service lighttpd start}}

You will get a feedback about the status.

<pre>
* Caching service dependencies [ ok ]
* Starting lighttpd... [ ok ]
</pre>

'''''Stop lighttpd''''': If you want to stop the web server use ''stop'' in the same way of previous command:

{{Cmd|rc-service lighttpd stop}}

'''''Restart lighttpd''''': After changing the configuration file lighttpd needs to be restarted.

{{Cmd|rc-service lighttpd restart}}

'''''Proper Runlevel''''': By default no services are added to start process, sysadmin must know what we want and what will services do, also other main reason are due in dockers there's no runlevels per se and Alpine linux are mostly used in dockers containers. You must added the servide only to the default runlevel, not to boot, because need networking activated

{{Cmd|rc-update add lighttpd default}}

= See Also =

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:

* [[Setting_Up_Lighttpd_with_PHP|Setting Up Lighttpd with PHP]]
* [[Lighttpd Advanced security]]

[[Category:Server]]
[[Category:Web_Server]]
[[Category:Development]]

Cacti: traffic analysis and monitoring network

2022-01-06T14:04:30Z

Mckaygerhard: remove newbie reference to stop the discussion

Cacti is a complete network monitoring and data analyzing solution using RRDTool's data storage and graphing functionality. It is the most widely used monitoring tool by ISPs to see the network graphically.

== Dedicated host pre configuration ==

'''Cacti has very special and fixed requirements''' from the host. For production systems, it must be installed on a dedicated host machine.

{{Note|here we use "venenux.net" as the domain. please change to your domain. if you are installing locally, use "localdomain"}}

=== Hostname setup ===

<pre><nowiki>
hostname monitor

echo 'hostname="monitor"' > /etc/conf.d/hostname

echo "monitor" > /etc/hostname

cat > /etc/hosts << EOF
127.0.0.1 monitor.venenux.net monitor localhost.localdomain localhost
151.101.128.249 dl-cdn.alpinelinux.org
::1 localhost localhost.localdomain
EOF
</nowiki></pre>

We added the ip address of cdn Alpine Linux to reduce DNS server traffic.

=== Repositories and packages ===

Unfortunately, some commands are more complex. We must take into consideration that common commands are just busybox minimalist versions, so we must make changes to ensure we are using the real ones. The following commands install bash as well as some other system tools as shown below. If they aren't present, Catci will fail randomly:

<pre><nowiki>
cat > /etc/apk/repositories << EOF
http://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release | cut -d'.' -f1,2)/main
http://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release | cut -d'.' -f1,2)/community
EOF

apk update

apk add bash attr dialog binutils findutils readline lsof less nano curl

export PAGER=less

cat > /etc/apk/repositories << EOF
http://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release | cut -d'.' -f1,2)/main
http://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release | cut -d'.' -f1,2)/community
http://uk.alpinelinux.org/alpine/edge/main
http://uk.alpinelinux.org/alpine/edge/community
EOF

apk update

apk add utmps

cat > /etc/apk/repositories << EOF
http://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release | cut -d'.' -f1,2)/main
http://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release | cut -d'.' -f1,2)/community
EOF

apk update
</nowiki></pre>

Take into consideration that if one package is retrieved, it must be the only package! i.e. not all the packages. First install all the dependencies and related files from the normal repository and later install only the required extras from edge! For that, you must visit https://pkgs.alpinelinux.org/packages and search for all the requirements of the involved package from edge. like <code>utmps</code>.

== Requirements ==

Before installing Cacti, many other packages must be installed and configured.

* A web server e.g. ''lighttpd''
* The ''PHP'' scripting language
* A database engine e.g. ''mariadb''
* To retreive data, ''net-snmp'' tools
* To graph the data, the ''rrdtool'' package

{{Warning|These complex configurations '''will be necessary''', as Cacti is demanding in its installation requirements to ensure complete functionality.}}

=== The web server: Lighttpd installation and configuration ===

Cacti runs as a web program, so we need the web server configured, Because Apache2 is so well known, we will document only lighttpd. There is a lot of info available about configuration options:

* setup port, cache engine, event handler of lighttpd, with htdocs
* setup web server status page
* setup alias mod for aliasing, cgi handler, and create the directories with the correct permissions
* setup the webserver start script and start the webserver to test it
* add network back-end handler. file descriptor setup and improve file cache retrieval time
* setup https and generate self signed certificate

<pre><nowiki>
apk add lighttpd gamin

mkdir -p /var/www/localhost/htdocs
sed -i -r 's#\#.*server.port.*=.*#server.port = 80#g' /etc/lighttpd/lighttpd.conf
sed -i -r 's#.*server.stat-cache-engine.*=.*# server.stat-cache-engine = "fam"#g' /etc/lighttpd/lighttpd.conf
sed -i -r 's#\#.*server.event-handler = "linux-sysepoll".*#server.event-handler = "linux-sysepoll"#g' /etc/lighttpd/lighttpd.conf

mkdir -p /var/www/localhost/htdocs/serverinfo
sed -i -r 's#\#.*mod_status.*,.*# "mod_status",#g' /etc/lighttpd/lighttpd.conf
sed -i -r 's#.*status.status-url.*=.*#status.status-url = "/serverinfo/server-status"#g' /etc/lighttpd/lighttpd.conf
sed -i -r 's#.*status.config-url.*=.*#status.config-url = "/serverinfo/server-config"#g' /etc/lighttpd/lighttpd.conf

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

mkdir -p /var/lib/lighttpd
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

checkset="";checkset=$(grep 'noatime' /etc/lighttpd/lighttpd.conf);[[ "$checkset" != "" ]] && \
echo listo || sed -i -r 's#server settings.*#server settings"\nserver.use-noatime = "enable"\n#g' /etc/lighttpd/lighttpd.conf

checkset="";checkset=$(grep 'network-backend' /etc/lighttpd/lighttpd.conf);[[ "$checkset" != "" ]] && \
echo listo || sed -i -r 's#server settings.*#server settings"\nserver.network-backend = "linux-sendfile"\n#g' /etc/lighttpd/lighttpd.conf

checkset="";checkset=$(grep 'max-fds' /etc/lighttpd/lighttpd.conf);[[ "$checkset" != "" ]] && \
echo listo || sed -i -r 's#server settings.*#server settings\nserver.max-fds = 2048\n#g' /etc/lighttpd/lighttpd.conf

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

{{Warning|Next steps are '''recommended''' but optional, Cacti can use only https for the traffic between the host monitor and the rest of monitored devices! Cacti should be accessed only over TLS. (https) Otherwise, passwords and user data will be exposed. The following steps will generate a self signed cert file that will require accepting a custom exception on the web browser, but all of the https traffic will use TLS/SSL.}}

<pre><nowiki>
apk add openssl

mkdir -p /etc/ssl/certs/

openssl req -x509 -days 1460 -nodes -newkey rsa:4096 \
-subj "/C=VE/ST=Bolivar/L=Upata/O=VenenuX/OU=Systemas:hozYmartillo/CN=localhost" \
-keyout /etc/ssl/certs/localhost.pem -out /etc/ssl/certs/localhost.pem

chmod 755 /etc/ssl/certs/localhost.pem

cat > /etc/lighttpd/mod_ssl.conf << EOF
server.modules += ("mod_openssl")
\$SERVER["socket"] == "0.0.0.0:443" {
ssl.engine = "enable"
ssl.pemfile = "/etc/ssl/certs/localhost.pem"
ssl.cipher-list = "ECDHE-RSA-AES256-SHA384:AES256-SHA256:RC4:HIGH:!MD5:!aNULL:!EDH:!AESGCM"
ssl.honor-cipher-order = "enable"
}
\$HTTP["scheme"] == "http" {
\$HTTP["host"] =~ ".*" {
url.redirect = (".*" => "https://%0\$0")
}
}
EOF

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

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

sed -i -r 's#ssl.pemfile.*=.*#ssl.pemfile = "/etc/ssl/certs/localhost.pem"#g' /etc/lighttpd/lighttpd.conf

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

=== The PHP: installation and configurations ===

Next requirement is the PHP scripting Language. Because Cacti are build with PHP, it has support for LDAP.

{{Note|Cacti supports PHP5 and PHP7. In the next section, we will only cover PHP7 because that's only version available that works with recent Alpine versions. If you use an older Alpine host for testing, you can use this command to detect what to install <code><nowiki>export phpmax=$(debver=$(cat /etc/alpine-release|cut -d '.' -f1);[ $debver -ge 6 ] && echo 7|| echo 5)</nowiki></code>, the shel var <code>phpmax</code> indicates based on Alpine version if 5 or 7 php will be used in command lines as: <code>apk add php$phpmax</code>.}}

The commit that mess is at, is: https://git.alpinelinux.org/aports/commit/community/cacti/cacti.php-fpm.conf?id=4272e802a1be191657becb739e6a248c1d0411a7 where a specific pool for php-fpm is made for cacti. It's a mess because it's not documented. We must avoid and ignore it if we are to properly configure the general pool:

<pre><nowiki>

apk add php7-fpm php7-bcmath php7-bz2 php7-ctype php7-curl php7-dom \
php7-enchant php7-exif 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-tokenizer \
php7-xml php7-xmlreader php7-xmlrpc php7-xmlwriter php7-xsl php7-zip php7-sqlite3 \
php7-gd php7-gmp php7-ldap php7-openssl php7-pdo_mysql php7-posix php7-sockets php7-xml

apk add php7-pdo php7-pdo_mysql php7-mysqli php7-pdo_sqlite php7-sqlite3 \
php7-odbc php7-pdo_odbc php7-dba
</nowiki></pre>

The following configurations are for high or huge loads on a 2G RAM server, for more information about configuring PHP on Alpine Linux see [[Production LAMP system: Lighttpd + PHP + MySQL]] wiki page.

<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 = 512M#g' /etc/php*/php.ini
sed -i -r 's#upload_max_filesize =.*#upload_max_filesize = 56M#g' /etc/php*/php.ini
sed -i -r 's#post_max_size =.*#post_max_size = 128M#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 = 90#g' /etc/php*/php.ini
sed -i -r 's#^max_input_time =.*#max_input_time = 90#g' /etc/php*/php.ini
sed -i -r 's#.*date.timezone =.*#date.timezone = America/Panama#g' /etc/php*/php.ini

sed -i -r 's|.*events.mechanism =.*|events.mechanism = epoll|g' /etc/php*/php-fpm.conf
sed -i -r 's|.*emergency_restart_threshold =.*|emergency_restart_threshold = 12|g' /etc/php*/php-fpm.conf
sed -i -r 's|.*emergency_restart_interval =.*|emergency_restart_interval = 1m|g' /etc/php*/php-fpm.conf
sed -i -r 's|.*process_control_timeout =.*|process_control_timeout = 8s|g' /etc/php*/php-fpm.conf

sed -i -r 's|^.*pm.max_requests =.*|pm.max_requests = 10000|g' /etc/php*/php-fpm.d/www.conf
sed -i -r 's|^.*pm.max_children =.*|pm.max_children = 12|g' /etc/php*/php-fpm.d/www.conf
sed -i -r 's|^.*pm.start_servers =.*|pm.start_servers = 4|g' /etc/php*/php-fpm.d/www.conf
sed -i -r 's|^.*pm.min_spare_servers =.*|pm.min_spare_servers = 4|g' /etc/php*/php-fpm.d/www.conf
sed -i -r 's|^.*pm.max_spare_servers =.*|pm.max_spare_servers = 8|g' /etc/php*/php-fpm.d/www.conf
sed -i -r 's|^.*pm.process_idle_timeout =.*|pm.process_idle_timeout = 8s|g' /etc/php*/php-fpm.d/www.conf
sed -i -r 's|^.*pm =.*|pm = ondemand|g' /etc/php*/php-fpm.d/www.conf

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#^user =.*#user = lighttpd#g' /etc/php*/php.ini
sed -i -r 's#^group =.*#group = lighttpd#g' /etc/php*/php.ini
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-update add php-fpm7 default

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

After you have php ready, let's integrate it into the current preinstalled web server. We've chosen lighttpd, so the commands are:

<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 'php-fpm7 restart

rc-service lighttpd restart

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

To test PHP is working correctly, browse to <code><nowiki>http://ipaddress/info.php</nowiki></code> Change "ipaddrs" to the web server's ip address.

=== The Database: MariaDB installation and configuration ===

{{Warning|Cacti also can run with PostgreSQL, it's a better choice for heavily loaded production and huge data systems. We documented mysql only because postgresql needs complex tunning parameters}}

{{Note|You can install '''adminer to manage the database''' via a web browser. See [[Production LAMP system: Lighttpd + PHP + MySQL#adminer:_Web_Frontend_administration|Adminer in production LAMP systems]] that can manage any kind of database via a GUI}}

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

mysql_install_db --user=mysql --datadir=/var/lib/mysql

rc-service mariadb start

mysql_tzinfo_to_sql /usr/share/zoneinfo/ | mysql -u root mysql

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

[mysql]
default-character-set = utf8mb4
EOF

cat > /etc/my.cnf.d/mariadb-server-default-highload.cnf << EOF
[mysqld]
collation_server = utf8mb4_unicode_ci
character_set_server = utf8mb4
max_heap_table_size = 32M
tmp_table_size = 32M
join_buffer_size = 62M
innodb_file_format = Barracuda
innodb_large_prefix = 1
innodb_buffer_pool_size = 512M
innodb_flush_log_at_timeout = 3
innodb_read_io_threads = 32
innodb_buffer_pool_instances = 1
innodb_io_capacity = 5000
innodb_io_capacity_max = 10000
EOF

rc-service mariadb restart

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

After those commands run the <code>mysql_secure_installation</code> script, and answer as follows:

# '''Enter current password for root (for none, enter):''' it must be provided because we've set it previously. Correct response is <code>OK, successfully used password, moving on...</code>
# '''Switch to unix_socket authentication [Y/n]''' Not used. Must be disabled, '''answer NO''', the response will be <code>... skipping.</code>
# '''Change the root password? [Y/n]''' Press "n" only if you provided a good password, otherwise change it!
# '''Remove anonymous users? [Y/n]''' In a '''production system, we must remove them, so answer Y''' the correct response is <code>... Success!</code>.
# '''Disallow root login remotely? [Y/n]''' Answer Y''' proper response is <code>... Success!</code>.
# '''Remove test database and access to it? [Y/n]''' You should removed it, so answer Y''' the proper response is <code>... Success!</code>.
# '''Reload privilege tables now? [Y/n]''' Aanswer Y''' proper response is <code>... Success!</code>.

After you respond to all of the questions, restart the service with <code>rc-service mariadb restart</code>

=== The tools: net-snmp and rrdtool ===

{{Warning|do no set <code><nowiki>agentAddress tcp:161,tcp6:[::1]:161</nowiki></code>, by default the package adds the udp 161 protocol, so if you set it, it will only listen and show info using ipv6 only}}

<pre><nowiki>
apk add net-snmp net-snmp-tools rrdtool

cat > /etc/snmp/snmpd.conf << EOF
view systemonly included .1.3.6.1.2.1.1
view systemonly included .1.3.6.1.2.1.25.1
rocommunity public localhost
rocommunity public default -V systemonly
sysLocation Bolivar Upata Venezuela
sysContact infoadmin <info@pacificnetwork.com>
sysServices 72
EOF

rc-update add snmpd default

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

Here we need only the commands for cacti. For more info about the topic see:

* [[Setting_up_traffic_monitoring_using_rrdtool_(and_snmp)]]
* [[Setting_up_monitoring_using_rrdtool_(and_rrdcollect)]]
* [[Setting_up_A_Network_Monitoring_and_Inventory_System]]

== Cacti Installation ==

As of Alpine 3.12, Cacti still is in the edge branch, so first we pre-install the dependency packages. Afterward, from edge, we install only cacti.

=== Installing Cacti Packages ===

{{Warning|As of Alpine 3.5, Cacti was a only one package, i.e. "cacti". Beginning with Alpine 3.6, The cacti package is split into more than obe package. The commit that mess all is where a specific pool for php-fpm is made for cacti. It's a mess because it's not documented. We must avoid and ignore it if we are to properly configure the general pool:}}

<pre><nowiki>
cat > /etc/apk/repositories << EOF
http://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release | cut -d'.' -f1,2)/main
http://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release | cut -d'.' -f1,2)/community
EOF

apk update

apk add bash busybox coreutils net-snmp-tools perl rrdtool ttf-dejavu php7-snmp

apk add cacti cacti-setup cacti-php7 cacti-lang
</nowiki></pre>

== Cacti pre Configuration ==

Cacti is run under the cacti user. We temporally set the file permissions to world writeable, then later, we'll set them correctly.

<pre><nowiki>
cat > /etc/lighttpd/mod_cacti.conf << EOF
alias.url += (
"/cacti/" => "/usr/share/webapps/cacti/"
)
\$HTTP["url"] =~ "^/cacti/" {
dir-listing.activate = "disable"
}
EOF

sed -i -r 's#\#.*mod_alias.*,.*# "mod_alias",#g' /etc/lighttpd/lighttpd.conf
sed -i -r 's#\#.*mod_accesslog.*,.*# "mod_accesslog",#g' /etc/lighttpd/lighttpd.conf
sed -i -r 's#\#.*mod_setenv.*,.*# "mod_setenv",#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_cacti.conf' /etc/lighttpd/lighttpd.conf);[[ "$checkssl" != "" ]] && echo listo || sed -i -r 's#.*include "mod_cgi.conf".*#include "mod_cgi.conf"\ninclude "mod_cacti.conf"#g' /etc/lighttpd/lighttpd.conf

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

Cacti runs under the cacti user, but web server user (apache2, lighttpd) also needs access. So enable group access and as we said, temporally set world-writeable file permissions permissions:

# grant temporary access to the web server
# Create the cacti database and populate it
# Grant Cacti MySQL user access (give it a more secure password):
# Quit from Mysql command prompt:
# Import the initial Cacti MySQL database
# set the user, password, and database name to the cacti config file
# temporarily grant world-write permission to the cacti log and lib directories

<pre><nowiki>
chown -R cacti:lighttpd /usr/share/webapps/cacti/;chown -R cacti:lighttpd /var/lib/cacti/

mysql -u root -p -e "CREATE DATABASE cacti;"

mysql -u root -p -e "GRANT ALL ON cacti.* TO 'cactiuser'@'localhost' IDENTIFIED BY 'cactipassword';FLUSH PRIVILEGES;

mysql -u root -p -e "GRANT GRANT OPTION ON cacti.* TO 'cactiuser'@'localhost';FLUSH PRIVILEGES;"

mysql -u root -p -e "GRANT SELECT ON mysql.time_zone_name TO 'cactiuser'@'localhost';"

mysql --user=cactiuser -p cactipassword cacti < /usr/share/webapps/cacti/cacti.sql

sed -i -r 's#\$database_default.*=.*;#\$database_default = 'cacti';#g' /etc/cacti/config.php
sed -i -r 's#\$database_username.*=.*;#\$database_username = 'cactiuser';#g' /etc/cacti/config.php
sed -i -r 's#\$database_password.*=.*;#\$database_password = 'cactipassword';#g' /etc/cacti/config.php

chmod 777 /var/log/cacti
chmod 666 /var/log/cacti/*.log
</nowiki></pre>

=== Cacti web setup install ===

Login using:
Password= admin user= admin
Next will be prompted to change password:
change password. 

In the web page click:
: -> Next
Then select new install if+ it's not selected:
: -> New install, Next

{{Warning|take note since cacti 1.2.8 and still at cacti 1.2.10, installer have several errors for <code>Cacti_Stats.xml.gz</code> template, so last "check" has no description. You must uncheck last as described here: https://github.com/Cacti/cacti/issues/3313#issuecomment-594114681 Th template can be installed later via the cli as: <code><nowiki>php -d max_execution_time=90 /usr/share/webapps/cacti/cli/import_package.php
--filename=Cacti_Stats.xml.gz</nowiki></code> under the templates directory of the cacti install, but currently it hangs and never gets installed. Reported at https://github.com/Cacti/cacti/issues/3313#issuecomment-601508135 }}

Then finish
: -> Finish
Add to crontab: 

== Cacti post configuration ==

<pre><nowiki>
chmod 775 /var/log/cacti
chmod 664 /var/log/cacti/*.log
</nowiki></pre>

=== Pooler and crontab ===

As we said, cacti needs a crontab for pool collection of data! These steps are not necesary as of Alpine 3.7 because the cacti package installs all necesary files.

{{Note|These steps are only for older cacti packages up to Alpine version 3.6. Starting with version 3.7, cacti packages install a crontab for data collection}}

cd /etc/crontabs
vi root
copy to the end of the file:
*/5 * * * * lighttpd php /var/www/localhost/htdocs/cacti/poller.php > /dev/null 2>&1
In case you are using another web server, you have to modify the "lighttpd" user.
*/5 * * * * "web server user" php /var/www/localhost/htdocs/cacti/poller.php > /dev/null 2>&1

'''Add your devices and you're ready to start monitoring!'''

=== cacti plugins ===

If you used the latest cacti, you must use the latest development version of each plugin especially if you're using php7 on your webserver:

00<pre><nowiki>
cd /usr/share/webapps/cacti/plugins/

wget https://github.com/Cacti/plugin_mikrotik/archive/master.tar.gz -O cacti-1.2.11-plugin-monitor.tar.gz
wget https://github.com/Cacti/plugin_gexport/archive/master.tar.gz -O cacti-1.2.11-plugin-gexport.tar.gz
wget https://github.com/Cacti/plugin_routerconfigs/archive/master.tar.gz -O cacti-1.2.11-plugin-routerconfigs.tar.g
wget https://github.com/Cacti/plugin_monitor/archive/master.tar.gz cacti-1.2.11-plugin-reportit.tar.gz
wget https://github.com/Cacti/plugin_reportit/archive/master.tar.gz -O cacti-1.2.11-plugin-reportit.tar.gz
</nowiki></pre>

After extract all of the files, change and fix permissions:

<pre><nowiki>
cd /usr/share/webapps/cacti/plugins/

chown -R cacti:lighttpd /usr/share/webapps/cacti/

chown -R cacti:lighttpd /var/lib/cacti/
</nowiki></pre>

Go to cacti configuration and plugins via the web interface to install and enable all of them.

== Re-installing Cacti ==

Let's suppose you make a mess of everything and want to reinstall all of it from the beginning. Let's get started:

=== Erase everything cacti related ===

# remove istalled packages
# remove configuration files
# remove databases and users from mysql/postgresql (here only mysql for example)
# reconfigure to not load the cacti web server configuration
# restart services because the cacti pool was erased and lighttpd must reload its config files

<pre><nowiki>
apk del cacti cacti-setup cacti-php7 cacti-lang

rm -rf /var/log/cacti

rm -rf /usr/share/webapps/cacti

rm -rf /etc/cacti

mysql -u root -p -e "DROP DATABASE cacti;"

mysql -u root -p -e "DROP USER 'cactiuser'@'localhost'"

sed -i "/include \"mod_cacti.conf\"/d" /etc/lighttpd/lighttpd.conf

rc-service php-fpm7 restart

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

After you complete all of these steps, repeat all the steps from [[Cacti:_traffic_analysis_and_monitoring_network#Cacti_Installation|Cacti_Installation section]].

= See Also =

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

Enable Community Repository

2022-01-06T13:42:21Z

Mckaygerhard: remove newbie reference to stop the discussion

Alpine software repositories have main packages and contributions made. Each Alpine release has two branches of repositories. The '''/community''' repository of each Alpine release contains community supported packages that were accepted from the '''/testing''' repository. Only '''/main''' repository of each version of Alpine release are supported for some Main Alpine Developers and Man Powers.

* '''Main packages''' are the Alpine package software that have direct support and updates from the Alpine core and main team, also have official documentation. Are always available for all releases and will have substitutions if some are not continued from upstream. Commonly those packages are selected due their responsibility and stability respecting upstream availability. Packages from ''testing'' that performs well or are mature goes to ''main'' branch.

* '''Community packages''' are those made by users in team with the official developers and well near integrated to the Alpine packages. Those have supported by those user contributions and could end if the user also ends respect with Alpine work, but may be removed in a future release due lack of support by upstream author. Packages from ''testing'' that are accept goes to ''community'' branch.

* '''Testing''' packages come into testing or edge repositories and are those made by any contributor on Alpine, the edge, this branch of repository has no release linked or related of Alpine. Those are in ''edge'' and when accepted goes to ''testing''.

== Using community repositories ==

The '''community''' repository was introduced with Alpine Linux version 3.3.

To enable the repository, edit the file {{Path|/etc/apk/repositories}} and add (or uncomment) a line that points to the "community" directory.

Its format is:

<code>'''https://<mirror-server>/alpine/<version>/community'''</code>

{{Tip|A usable editor is {{Pkg|nano}}, and it can be installed with <code>apk add nano</code>.}}

After enabling the community repository, one needs to update the index of available packages with:
{{Cmd|apk update}}
And then it's possible to install packages from the community repository.

=== Adding community repositories with a script ===

The following commands will add the main and community repositories for the Alpine version you're using. It will overwrite your existing repository settings.

{{cmd|cat > /etc/apk/repositories << EOF; $(echo)
<nowiki>
http://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release | cut -d'.' -f1,2)/main
http://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release | cut -d'.' -f1,2)/community
http://dl-cdn.alpinelinux.org/alpine/edge/testing
</nowiki>
EOF

}}

Dont forget to run this after:.
{{Cmd|apk update}}

== Using specific package versions ==

You can specify or pin "sticky" package versions like this:

* <code><nowiki>apk add packagename=1.2.3-suffix</nowiki></code>
* <code><nowiki>apk add 'packagename<1.2.3-suffix'</nowiki></code>

That will upgrade these packages only until the specified version.

It's then safe to use <code>apk upgrade</code> to upgrade all packages, while packages with versions will remain on the specified version.

To set a minimum version just add <code>…</code>.

{{Warning|Pinning a package to an exact version carries the risk that the package will be dropped from the repo, and at some time can't be downloaded anymore (e.g. during boot or Dockerfile build).

The official recommendation can be read here, citation below.
Alternately, you could simply set a minimum package version
instead of an exact version.

We don't at the moment have resources to store all built packages
indefinitely in our infrastructure. Thus we currently keep only
the latest for each stable branch.
}}

== Using testing repositories ==

The '''testing''' repository was introduced with Alpine Linux edge development. To enable the repository, edit the file {{Path|/etc/apk/repositories}} using an editor ({{Pkg|nano}} for instance) and add a line that points to the "testing" directory, formatted as in:

<code>'''https://<mirror-server>/alpine/edge/testing'''</code>

After enabling the testing repository, one needs to obtain the latest index of available packages with:
{{Cmd|apk update}}

Inexperienced users should not enable this.

=== Using packages from testing (edge) ===

Never pin packages from the "edge" branch of the alpine package repo, as these are in test and may be revoked. (At pkgs.alpinelinux.org/packages, click "edge" and change it to the alpine image version you use, and click "search" again.)

Inexperienced users should not enable this.

= See also =

[[Category:Package Manager]]

Alpine Linux:Overview

2022-01-06T13:41:46Z

Mckaygerhard:

Alpine uses [http://musl-libc.org/ muslc] as libc, and [https://en.wikipedia.org/wiki/BusyBox BusyBox] as core utilities. These choices tend to make Alpine especially minimalist and secure.

== General overview ==

Alpine Linux has one of the '''fastest boot times''' of any operating system.

Famous because of its small size, it's '''heavily used in containers'''.

Also well know for '''wide use in embedded devices''' and as a '''base system for many enterprise routers'''.

The postmarketOS project which is designed to run on mobile devices is based on Alpine Linux.

=== Distinctive ===

Alpine Linux follows the principles of '''the SSS distro: Simple+Small+Secure''': due to usage of [http://musl-libc.org/ muslc] as the minimalist libc, BusyBox simple coreutils (with possibilities to alternate on inflated original packages of each coreutils tools also) and userland binaries compiled as Position Independent Executables (PIE) with stack smashing protection.

=== Efficient ===

Some main reasons:

# Usage of [http://musl-libc.org/ muslc] as the minimalist libc
# Its own package manager called {{Pkg|apk}},
# the {{Pkg|openrc}} init system, script driven set-ups and that’s it!
# {{Pkg|busybox}} simple coreutils (with possibilities to alternate on inflated original packages of each coreutils tools also)

This provides you with a simple, '''crystal-clear Linux environment without all the noise''', nothing else will get in the way.

=== Secure ===

All userland binaries are compiled as Position Independent Executables (PIE) with stack smashing protection.

== Technical overview ==

<ol>
</li><li>'''The OS design'''

Alpine uses '''Linux''' as OS kernel, and their focus are '''SSS distribution, Simple Small and Secure'''

A variety of architectures are officially supports:
* '''x86_64''': The popular AMD64 compatible 64-bit x86 based machines, i386 are not recommended for newer/lasted hardware.
* '''x86''': (i386 pc 32bit) and x86_64 (i686 pc 64bit and amd64)
* '''armhf''': The newer ARM hard-float for newer, more powerful 32-bit devices alongside 64-bit
* '''armv7''': The 32-bit ARM only execution state of the ARMv7 devices machines.
* '''aarch64''': The 64-bit ARM only execution state of the ARMv8 device machines.
* '''ppc64le''': For 64-bit PowerPC devices with pure little-endian mode, mostly for POWER8 and POWER9.
* '''s390x''': For IBM Z mainframes, especially IBM Z and IBM LinuxONE.

It can be installed to a hard disk/SSD/other storage medium like any other distro; (sys mode). The storage medium in question can be any block device (USB, Flash, SDD, HDD). Always in start, the base Alpine system and all your changes will be unpacked into a memory-based filesystem. If run some install script process (data mode) will keep your setup on a hard disk/SSD/other storage medium, rather than unpacking into memory. The default setup here is to store your /var partition directly on the hard storage medium. But as in the diskless mode, your root system still comes from a static ISO image.


</li><li>'''The installation'''

In Alpine's case, '''the installer consists of the {{Path|/sbin/setup-*}} scripts''', which are also part of the {{Pkg|alpine-conf}} package.

'''A base Alpine install will include only needed packages''' such like {{Pkg|alpine-base}}, {{Pkg|syslinux}}, {{Pkg|linux-lts}} (or another kernel package), and depending of purpose some like {{Pkg|openssh}}/{{Pkg|chrony}}.

Alpine's boot loader case this is {{Pkg|syslinux}}, or its companions <code>isolinux</code> or <code>extlinux</code>. Lasted releases has Grub and [[Alpine and UEFI|UEFI support]].

</li><li>'''The init system'''

An "init system" includes several different components. First, there is the initramfs loaded by the bootloader. Alpine's tool for generating these is {{Path|/sbin/mkinitfs}}, part of the {{Pkg|mkinitfs}} package, which is required by Alpine's kernel packages and by its {{Pkg|syslinux}} package. This tool's settings are read from {{Path|/etc/mkinitfs/*}}, and it installs the initscript {{Path|/usr/share/mkinitfs/initramfs-init}} into the initramfs.

Second, Alpine uses [[Alpine Linux Init System|OpenRC]] to handle the rest of its initscripts. The base framework of this is in the {{Pkg|openrc}} package, which is required by {{Pkg|alpine-conf}}.


</li><li>'''The packaging and development system'''

The last important distinguishing feature of a Linux distro is its packaging and development systems.

In Alpine's case, these are something a hybrid between [https://www.archlinux.org/ ArchLinux]'s, on the one hand, and [http://www.gentoo.org/ Gentoo] and [http://www.freebsd.org/ FreeBSD]'s, on the other. Our package-management and build utilities work much like Arch's:

* {{Pkg|mkinitfs}}, mentioned above, rebuilds Alpine's initramfs, like Arch's "mkinitcpio"
* '''apk''' from {{Pkg|apk-tools}} is Alpine's package manager, like Arch's "pacman"; see [[Alpine Linux package management]]
* {{Pkg|abuild}} is Alpine's build utility, like Arch's "makepkg"; see [[Abuild and Helpers]]
* Alpine's package-building scripts are named APKBUILD, like Arch's "PKGBUILD"

What Alpine borrows from Gentoo and FreeBSD is a tree of all the package-building scripts. We call this our [[Aports tree]], and we keep it as a git repository. (Compare Gentoo's "Portage" and FreeBSD's "ports". You can setup something similar with Arch's "abs", but it's not as tightly integrated with their package manager and build utilities.)

If you're only planning to install packages on a given system, and not do any development there, then the only pieces of this you'll need are {{Pkg|mkinitfs}} and {{Pkg|apk-tools}}, both included in a base Alpine install. If you do plan to do development, install {{Pkg|alpine-sdk}}, which includes gcc, git, abuild, and the like, and see [[Developer Documentation]].


</li></ol>

= See Also =

* [[Comparison with other distros]]
* [[Tutorials and Howtos]]

[[Category:Installation]]

Alpine configuration management scripts

2022-01-06T13:39:47Z

Mckaygerhard: remove newbie reference to stop the discussion

Feature descriptions for available Alpine Linux setup scripts ({{Path|/sbin/setup-*}}).

These scripts can be installed from alpine-conf package using apk.

== setup-alpine ==

This is the main Alpine configuration and installation script.

The script interactively walks the user through executing several auxiliary <code>setup-*</code> scripts, in the order shown below.

The bracketed options represent example configuration choices, formatted as they may be supplied when manually calling the auxiliary setup scripts, or using a <code>setup-alpine</code> "answerfile" (see below).

# <code>setup-keymap</code> [us us]
# [[#setup-hostname|setup-hostname]] [-n alpine-test]
# [[#setup-interfaces|setup-interfaces]] [-i < interfaces-file]
# <code>/etc/init.d/networking --quiet start &</code>
# if none of the networking interfaces were configured using dhcp, then: <code>[[#setup-dns|setup-dns]]</code> [-d example.com -n "192.168.0.1 [...]"]
# set the root password
# if not in quick mode, then: <code>[[#setup-timezone|setup-timezone]]</code> [-z UTC | -z America/New_York | -p EST+5]
# enable the new hostname (<code>/etc/init.d/hostname --quiet restart</code>)
# add <code>networking</code> and <code>urandom</code> to the '''boot''' rc level, and <code>acpid</code> and <code>crond</code> to the '''default''' rc level, and start the '''boot''' and '''default''' rc services
# extract the fully-qualified domain name and hostname from {{Path|/etc/resolv.conf}} and <code>hostname</code>, and update {{Path|/etc/hosts}}
# <code>[[#setup-proxy|setup-proxy]]</code> [-q <nowiki>"http://webproxy:8080"</nowiki>], and activate proxy if it was configured
# <code>setup-apkrepos</code> [-r (to select a mirror randomly)]
# if not in quick mode, then: <code>[[#setup-sshd|setup-sshd]]</code> [-c openssh | dropbear | none]
# if not in quick mode, then: <code>setup-ntp</code> [-c chrony | openntpd | busybox | none]
# if not in quick mode, then: <code>DEFAULT_DISK=none</code> <code>[[#setup-disk|setup-disk]]</code> <code>-q</code> [-m data /dev/sda] (see [[Installation#Installation_Overview]] about the disk modes)
# if installation mode selected during setup-disk was "data" instead of "sys", then: <code>setup-lbu</code> [/media/sdb1]
# if installation mode selected during setup-disk was "data" instead of "sys", then: <code>setup-apkcache</code> [/media/sdb1/cache | none]

<code>setup-alpine</code> itself accepts the following command-line switches

{{Define|-h|Shows the up-to-date usage help message.}}

{{Define|-a|Create an overlay file: this creates a temporary directory and saves its location in ROOT; however, the script doesn't export this variable so I think this feature isn't currently functional.}}
;-c <var>answerfile</var>
:Create a new "answerfile", with default choices. You can edit the file and then invoke <code>setup-alpine -f <var>answerfile</var></code>.
;-f <var>answerfile</var>
:Use an existing "answerfile", which may override some or all of the interactive prompts.
{{Define|-q|Run in "quick mode".}}

 

== setup-hostname ==

:<code>setup-hostname</code> [-h] [-n hostname]

Options:

'''-h''' <var>Show help</var>

'''-n''' <var>Specify hostname</var>

This script allows quick and easy setup of the system hostname by writing it to {{Path|/etc/hostname}}. The script prevents you from writing an invalid hostname (such as one that used invalid characters or starts with a '-' or is too long).
The script can be invoked manually or is called as part of the <code>setup-alpine</code> script.

 

== setup-interfaces ==
{{Cmd|setup-interfaces [-i < <var>interfaces-file</var>]}}

Note that the contents of <var>interfaces-file</var> has to be supplied as stdin, rather than naming the file as an additional argument. The contents should have the format of {{Path|/etc/network/interfaces}}, such as:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
hostname alpine-test

 

== setup-dns ==

:<code>setup-dns</code> [-h] [-d domain name] [-n name server]

Options:

'''-h''' <var>Show help</var>

'''-d''' <var>specify search domain name</var>

'''-n''' <var>name server IP</var>

The setup-dns script is stored in {{Path|/sbin/setup-dns}} and allows quick and simple setup of DNS servers (and a DNS search domain if required). Simply running <code>setup-dns</code> will allow interactive use of the script, or the options can be specified.

The information fed to this script is written to {{Path|/etc/resolv.conf}}

Example usage (with 192.168.0.1 being the local router/dns-forwarder): {{Cmd|setup-dns -d example.org -n 192.168.0.1}}

Example {{Path|/etc/resolv.conf}}:

search example.org
nameserver 192.168.0.1

It can be run manually but is also invoked in the <code>setup-alpine</code> script unless interfaces are configured for DHCP.

 

== setup-timezone ==
:<code>setup-timezone</code> [-z UTC | -z America/New_York | -p EST+5]

Can pre-select the timezone using either of these switches:

'''-z''' <var>subfolder of</var> {{Path|/usr/share/zoneinfo}}

'''-p''' <var>POSIX TZ format</var>

 

== setup-proxy ==
:<code>setup-proxy</code> [-hq] [PROXYURL]

Options:

'''-h''' <var>Show help</var>

'''-q''' <var>Quiet mode</var> prevents changes from taking effect until after reboot

This script requests the system proxy to use in the form <code>http://<proxyurl>:<port></code> for example:
<code><nowiki>http://10.0.0.1:8080</nowiki></code>

To set no system proxy use <code>none</code>.
This script exports the following environmental variables:

<code>http_proxy=$proxyurl</code>

<code>https_proxy=$proxyurl</code>

<code>ftp_proxy=$proxyurl</code>

where <code>$proxyurl</code> is the value input.
If <code>none</code> was chosen then the value it is set to a blank value (and so no proxy is used).

 

== setup-apkrepos ==
:<code>setup-apkrepos</code> [-fhr] [REPO...]

Setup <code>apk</code> repositories.

options:

'''-f''' <var>Detect and add fastest mirror</var>

'''-r''' <var>Add a random mirror and do not prompt</var>

'''-1''' <var>Add first mirror on the list (normally a CDN)</var>

This is run as part of the <code>setup-alpine</code> script.

 

== setup-sshd ==

:<code>setup-sshd</code> [-h] [-c choice of SSH daemon]

Options:

'''-h''' <var>Show help</var>

'''-c''' <var>SSH daemon</var> where SSH daemon can be one of the following:

<code>openssh</code> install the {{Pkg|openSSH}} daemon

<code>dropbear</code> install the {{Pkg|dropbear}} daemon

<code>none</code> Do not install an SSH daemon

Example usage: {{Cmd|setup-sshd -c dropbear}}

The setup-sshd script is stored in {{Path|/sbin/setup-sshd}} and allows quick and simple setup of either the OpenSSH or Dropbear SSH daemon & client.
It can be run manually but is also invoked in the <code>setup-alpine</code> script.

 

== setup-ntp ==

''From [https://en.wikipedia.org/wiki/Network_Time_Protocol Wikipedia]'':

The '''Network Time Protocol (NTP)''' is a networking protocol for clock synchronization between computer systems over packet-switched, variable-latency data networks.

 

{{Cmd|usage: setup-ntp [-h] [-c choice of NTP daemon]

Setup NTP time synchronization

options:
-h Show this help
-c Choice of NTP daemon: busybox openntpd chrony none}}

<code>setup-ntp</code> script is stored in {{Path|/sbin/setup-ntp}} and allows quick and simple setup of the NTP client,
It can be run manually but is also invoked in the <code>setup-alpine</code> script.

 

== setup-disk ==

:<code>DEFAULT_DISK=none setup-disk -q</code> [-m data | sys] [<var>mountpoint directory</var> | /dev/sda ...]

In "sys" mode, it's an installer, it permanently installs Alpine on the disk, in "data" mode, it provides a larger and persistent /var volume.

This script accepts the following command-line switches:

;-k <var>kernel flavor</var>
;-o <var>apkovl file</var>
:Restore system from <var>apkovl file</var>
;-m data | sys
:Don't prompt for installation mode. With '''-m data''', the supplied devices are formatted to use as a {{Path|/var}} volume.
{{Define|-r|Use RAID1 with a single disk (degraded mode)}}
{{Define|-L|Create and use volumes in a LVM group}}
;-s <var>swap size in MB</var>
:Use 0 to disable swap
{{Define|-q|Exit quietly if no disks are found}}
{{Define|-v|Verbose mode}}

The script also honors the following environment variables:

<code>BOOT_SIZE</code>
:Size of the boot partition in MB; defaults to 100. Only used if '''-m sys''' is specified or interactively selected.

<code>SWAP_SIZE</code>
:Size of the swap volume in MB; set to 0 to disable swap. If not specified, will default to twice RAM, up to 4096, but won't be more than 1/3 the size of the smallest disk, and if less than 64 will just be 0. Only used if '''-m sys''' is specified or interactively selected.

<code>ROOTFS</code>
:Filesystem to use for the / volume; defaults to ext4. Only used if '''-m sys''' is specified or interactively selected. Supported filesystems are: ext2 ext3 ext4 [[Btrfs|btrfs]] xfs.

<code>BOOTFS</code>
:Filesystem to use for the /boot volume; defaults to ext4. Only used if '''-m sys''' is specified or interactively selected. Supported filesystems are: ext2 ext3 ext4 [[Btrfs|btrfs]] xfs.

<code>VARFS</code>
:Filesystem to use for the /var volume; defaults to ext4. Only used if '''-m data''' is specified or interactively selected. Supported filesystems are: ext2 ext3 ext4 [[Btrfs|btrfs]] xfs.

<code>SYSROOT</code>
:Mountpoint to use when creating volumes and doing traditional disk install ('''-m sys'''). Defaults to {{Path|/mnt}}.

<code>MBR</code>
:Path of MBR binary code, defaults to {{Path|/usr/share/syslinux/mbr.bin}}.

<code>BOOTLOADER</code>
:Bootloader to use, defaults to syslinux. Supported bootloaders are: grub syslinux zipl.

<code>DISKLABEL</code>
:Disklabel to use, defaults to dos. Supported disklabels are: dos gpt eckd.



=== Partitioning ===

If you have complex partitioning needs, that go beyond above alpine-disk options, you can partition, format, and mount your volumes manually, and then just supply the root mountpoint to <code>setup-disk</code>. Doing so implicitly behaves as though '''-m sys''' had also been specified.

See [[Setting up disks manually]] for more information.

==== RAID ====
<code>setup-disk</code> will automatically build a RAID array if you supply the '''-r''' switch, or if you specify more than one device. The array will always be [https://en.m.wikipedia.org/wiki/Standard_RAID_levels#RAID_1 RAID1] (and [https://raid.wiki.kernel.org/index.php/RAID_superblock_formats#The_version-0.90_Superblock_Format --metadata=0.90]) for the /boot volumes, but will be [https://en.m.wikipedia.org/wiki/Standard_RAID_levels#RAID_5 RAID5] (and [https://raid.wiki.kernel.org/index.php/RAID_superblock_formats#The_version-1_Superblock_Format --metadata=1.2] for non-boot volumes when 3 or more devices are supplied.

If you instead want to build your RAID array manually, see [[Setting up a software RAID array]]. Then format and mount the disks, and supply the root mountpoint to <code>setup-disk</code>.

==== LVM ====
<code>setup-disk</code> will automatically build and use volumes in a LVM group if you supply the '''-L''' switch. The group and volumes created by the script will have the following names:

* volume group: '''vg0'''
* swap volume: '''lv_swap''' (only created when swap size > 0)
* root volume: '''lv_root''' (only created when '''-m sys''' is specified or interactively selected)
* var volume: '''lv_var''' (only created when '''-m data''' is specified or interactively selected)

The '''lv_var''' or '''lv_root''' volumes are created to occupy all remaining space in the volume group.

If you need to change any of these settings, you can use <code>vgrename</code>, <code>lvrename</code>, <code>lvreduce</code> or <code>lvresize</code>.

If you instead want to build your LVM system manually, see [[Setting up Logical Volumes with LVM]]. Then format and mount the disks, and supply the root mountpoint to <code>setup-disk</code>.



 

== setup-lbu ==

This script will only be invoked for by <code>setup-alpine</code> when installing <code>data</code> installation types (ramdisk)

It configures where <code>lbu commit</code> will store the .apkovl backup. See [[Alpine local backup]] for more information.

When started, <code>setup-lbu</code> will prompt where to store your data. The options it will prompt for will be taken from the directories found in <code>/media</code> (except for <code>cdrom</code>). [not sure how these are mounted: are they automatically mounted by setup-lbu? Does the user have to manually mount using another tty?]

 

== setup-apkcache ==

This script will only be invoked for by <code>setup-alpine</code> when installing <code>data</code> installation types (ramdisk)

It configures where to save the apk package files. The apkcache is where apk stores downloaded packages, such that the system does not need to download them again on each reboot, and doesn't have to depend on the network. See [[Local APK cache]] for a detailed explanation.

You should be able to use a partition that you set up in the previous steps.

 

== setup-bootable ==
This is a standalone script; it's not invoked by <code>setup-alpine</code> but must be run manually.

It allows to create boot media that boots the system running from RAM memory (diskless) like the installation images, but using a writable (i.e. not iso9660) filesystem. So that it can also serve to store local customizations (e.g. apkovl files and cached packages).

First, the script copies files from an ISO image (as file on a CD/DVD/USB etc.) onto a USB-Stick/CompactFlash/SDCard etc., or harddisk partition. And then, it installs the syslinux bootloader to make the device bootable.

However, its current syslinux installation seems to fail on non-FAT32 partitions. So in these cases, you may start over with a FAT32 filesystem, or rather with the desired filesystem and using <code>setup-bootable</code> only with the <code>-u</code> option, to skip the syslinux install, and then refer to the [[Create_a_Bootable_Device#Manually_copying_Alpine_files|manual method]] to fix the problem, or use one of the other bootloader options, instead.

{{Tip| The [[Bootloaders]] page shows different ways to setup booting, and multi-boot menus!}}

The setup-bootable script accepts the following arguments and command-line switches (you can run <code>setup-bootable -h</code> to see a usage message).

{{Cmd|setup-bootable <var>source</var> [<var>dest</var>]}}

The argument <var>source</var> can be a directory or an ISO (will be mounted to <code>MNT</code> or {{Path|/mnt}}) or a URL (will be downloaded with <code>WGET</code> or <code>wget</code>). The argument <var>dest</var> can be a directory mountpoint, or will default to {{Path|/media/usb}} if not supplied.

{{Define|-k|Keep alpine_dev in {{Path|syslinux.cfg}}; otherwise, replace with UUID.}}
{{Define|-u|Upgrade mode: keep existing {{Path|syslinux.cfg}} and don't run <code>syslinux</code>}}
{{Define|-f|Overwrite {{Path|syslinux.cfg}} even if '''-u''' was specified.}}
{{Define|-s|Force the running of <code>syslinux</code> even if '''-u''' was specified.}}
{{Define|-v|Verbose mode}}

The script will ensure that <var>source</var> and <var>dest</var> are available; will copy the contents of <var>source</var> to <var>dest</var>, ensuring first that there's enough space; and unless '''-u''' was specified, will make <var>dest</var> bootable.

Suppose the target device is /dev/sdXY, then this partition can be prepared for booting with
{{Cmd|# setup-bootable -v /media/<installation-media-device> /dev/sdXY
}}

For the manual way to set up boot media see [[Create_a_Bootable_Device#Manually_copying_Alpine_files|Manually_copying_Alpine_files]].

 

== setup-xorg-base ==

This is a standalone script; it's not invoked by <code>setup-alpine</code> but must be run manually.

It configures a graphical environment, installing basic Xorg packages and udev (replacing mdev), and is also required for Wayland sessions.

The script installs, among other packages, e.g.: <code>xorg-server xf86-input-libinput xinit udev</code>.

Additional packages to install may be supplied as arguments.
{{cmd|setup-xorg-base [additional package(s) to install]}}

==== Video packages (optional) ====

You may install specific xf86 xorg driver packages for your video card's chipset, as they may support specific features, effects and acceleration modes, and avoid error messages during X initialization.

However, the most basic X features should work fine with just using the default kernel video-modesetting drivers.

Info about the particular video cards that are installed in the computer may be found in the list of PCI devices:
{{cmd|# apk add pciutils
$ lspci}}

To see available video driver packages run:
{{cmd|$ apk search xf86-video}}

For example,
* For an Sis video chipset install 'xf86-video-sis'.
{{Cmd|# apk add xf86-video-sis}}

Others:
* For Intel video chipsets install 'xf86-video-intel' and see [[Intel Video]].
{{Tip|In some cases, freezes on suspend/resume stop happening when changing the video port the monitor is connected to.}}
* For AMD Radeon Video see [[Radeon_Video]]
* For Alix1D use xf86-video-geode.
* In KVM/QEMU guests see [[QEMU#Using_Xorg_inside_Qemu|Xorg within KVM/QEMU]]
* In VirtualBox guests use xf86-video-vboxvideo, and install the [[VirtualBox_guest_additions|VirtualBox guest additions]] as well. They contain important parts for the driver.
* In VMware guests use xf86-video-vmware
* In Hyper-V guests use xf86-video-fbdev and install the [[Hyper-V_guest_services|Hyper-V guest services]] as well.

==== Input packages ====

If the Numlock settings are not working, or getting 'setleds not found' errors:

{{cmd|# apk add kbd}}

If some input device is not working at all, the available xf86-input drivers can be listed with:
{{cmd|$ apk search xf86-input}}

Typical legacy drivers:

{{cmd|# apk add xf86-input-mouse xf86-input-keyboard}}

And for touchpad tapping support on many laptops, also:

{{Cmd|# apk add xf86-input-synaptics}}

==== Configure xorg-server (optional) ====

On most systems, xorg should be able to autodetect all devices. However you can still configure xorg-server by hand by launching:
{{Cmd|# Xorg -configure}}
This will create a `/root/xorg.conf.new` file. You can modify this file to fit your needs. 
(When finished modifying and testing the above configuration file, move it to `/etc/X11/xorg.conf` for normal usage.)

==== Keyboard Layout (optional) ====

If you use a keyboard layout different than "us", and you are using a window manager or desktop environment that does not support to configure the keyboard layout itself, then you need to

* [[Enable_Community_Repository#Using_community_repositories|Enable the "community" repository]]

and install setxkbmap:

{{Cmd|# apk add setxkbmap}}

Then try
# setxkbmap <%a language layout from /usr/share/X11/xkb/rules/xorg.lst%>

In order to make it persistent add this section to /etc/X11/xorg.conf:
{{Cmd|Section "InputClass"
Identifier "Keyboard Default"
MatchIsKeyboard "yes"
Option "XkbLayout" "<%a language layout from /usr/share/X11/xkb/rules/xorg.lst%>"
EndSection
}}

Another way to change the keymap when logging into X is to use ~/.xinitrc. The following example loads a British keymap, simply add this line to the beginning of the file:
<code>setxkbmap gb &</code>

If you need to create the ~/.xinitrc file, you may also want to add a second line like <code>exec openbox-session</code> to still start the window manager with <code>startx</code> or <code>xinit</code>.

 

== Documentation needed ==

=== setup-xen-dom0 ===

 

=== setup-mta ===
Uses ssmtp.

This is a standalone script; it's not invoked by <code>setup-alpine</code> but must be run manually.

 

=== setup-acf ===
This is a standalone script; it's not invoked by <code>setup-alpine</code> but must be run manually.

This script was named <code>setup-webconf</code> before Alpine 1.9 beta 4.

See [[:Category:ACF|ACF pages]] for more information.

= See also =
* [[Installation]]
* [[Post installation]]

[[Category:Installation]]

KDE

2022-01-06T13:39:07Z

Mckaygerhard: remove newbie reference to stop the discussion

KDE is a software project comprising a desktop environment known as Plasma, a collection of libraries and frameworks known as KDE Frameworks, and several applications known as KDE Applications. Their [https://userbase.kde.org/Welcome_to_KDE_UserBase UserBase wiki] has detailed information about most KDE Applications.

{{Note|the {{Pkg|plasma}} package isn't available for the <code>ppc64le</code> and <code>s390x</code> architectures due to the {{Pkg|kdeplasma-addons}} dependency not being available there. However, the rest of Plasma can be installed separately to get a functional desktop.}}

 

== Prerequisites ==

* [[Installation|Install]] AlpineLinux
* [[Post_installation#Creating_a_new_user_account|Create a user account]] (optional but recommended)
* [[Post_installation#Repositories|Enable the Community repository]]
* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]

{{Note|[[Wayland]] can be used but may be less stable and Plasma may still require Xorg}}

 

== Installation ==

==== Standard plasma installation ====

{{Cmd|# apk add plasma elogind polkit-elogind dbus}}

This will install the required Plasma packages, {{Pkg|sddm}} and pre-configure it to use the Breeze theme.

 

==== Lightweight plasma installation ====

Alternatively, a smaller installation can be done:

{{Cmd|# apk add plasma-desktop systemsettings sddm breeze elogind polkit-elogind dbus}}

 

{{Note|If you are missing something that is in a standard Plasma installation check out the dependencies of the {{Pkg|plasma}} package because it is likely you will find whatever your missing there.}}

 

For both installation methods you need to enable the following services:

{{Cmd|# rc-update add dbus}}
{{Cmd|# rc-update add elogind}}
{{Cmd|# rc-update add polkit}}
{{Cmd|# rc-update add udev}}

 

{{Note|'''polkit''' and '''udev''' are technically optional (or have other alternatives) but if they are not installed/started features (or the system) may not work properly, modify this at your own risk!}}

 

== KDE Applications ==

To install the full set of KDE Applications, install {{Pkg|kde-applications}}. You can also choose to install a smaller set of applications by installing any of the subpackages:

* {{Pkg|kde-applications-accessibility}}
* {{Pkg|kde-applications-admin}}
* {{Pkg|kde-applications-base}}
* {{Pkg|kde-applications-edu}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-games}}
* {{Pkg|kde-applications-graphics}}
* {{Pkg|kde-applications-multimedia}}
* {{Pkg|kde-applications-network}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-pim}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-sdk}}
* {{Pkg|kde-applications-utils}}
* {{Pkg|kde-applications-webdev}}

 

== Starting Plasma ==

Plasma can be started using a display manager or from the console.

==== Using a display manager ====

When Plasma is installed via the {{Pkg|plasma}} meta-package, the display manager is set up using {{Pkg|sddm}}.

Make sure you enable and start the SDDM service.

<pre>
rc-update add sddm
rc-service sddm start
</pre>

* Select ''Plasma'' to launch a new session in Wayland
* Select ''Plasma (X11)'' to launch a new session in Xorg

==== From the console ====

The Xorg session can be launched by installing {{Pkg|xinit}} and appending <code>exec startplasma-x11</code> to your <code>.xinitrc</code> file. To start X:
{{Cmd|xinit}}

For the Wayland session run
<pre>
XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland
</pre>

 

== See also ==
* [[Post installation]]
* [[Flatpak]]

[[Category:Desktop]]

Alpine Linux in a chroot

2022-01-06T13:38:42Z

Mckaygerhard: remove newbie reference to stop the discussion

{{TOC right}}

Inside the chroot environment, you can build, debug, and run Alpine packages or develop things. It's the most known way to do so without replacing your system or using a Virtual Machine.
This document explains how to set up an Alpine build environment in a chroot under a host Linux distro, that can also be used to install Alpine Linux from a non-Alpine Linux system or live environment.

== Requirements ==

* Working Linux instalation where to perform all the process
* Linux kernel 2.6.22, with <code>curl</code> and <code>chroot</code> binary installed
* target media with at least 100M, 900MB for more complete solution as minimum
* internet connection

== Prerequisites ==

The variables below:

*'''${chroot_dir}''' = Should point to the new root directory
*'''${mirror}''' = Should be replaced with [http://nl.alpinelinux.org/alpine/MIRRORS.txt one of the available Alpine Linux mirrors].
*'''${arch}''' = Should be the cpu architecture like x86 (i386) or amd64(x86_64)..

== Set up APK ==

Download the latest apk static package (replace <tt>${version}</tt> with actual version):

{{Cmd|curl -LO ${mirror}/latest-stable/main/${arch}/apk-tools-static-${version}.apk}}

.apk packages are just gzipped tarballs, you can unpack them using:
{{Cmd|tar -xzf apk-tools-static-*.apk}}

== Install the alpine base installation onto the chroot ==

{{Cmd|./sbin/apk.static -X ${mirror}/latest-stable/main -U --allow-untrusted -p ${chroot_dir} --initdb add alpine-base}}

== Seting up the chroot ==

Before you change root to the new directory, you need to create the required devices

===== Method 1.a Simple way: Using the host's /dev =====

{{Cmd|mount -o bind /dev ${chroot_dir}/dev}}

{{Note|Bind mounts can be made read-only which would limit the chroot from writing to the devices}}

===== Method 1.b Manual way: Creating needed nodes =====

{{Warning|Manually creating devices will only provide the ones that have been created}}

{{Cmd|mknod -m 666 ${chroot_dir}/dev/full c 1 7
mknod -m 666 ${chroot_dir}/dev/ptmx c 5 2
mknod -m 644 ${chroot_dir}/dev/random c 1 8
mknod -m 644 ${chroot_dir}/dev/urandom c 1 9
mknod -m 666 ${chroot_dir}/dev/zero c 1 5
mknod -m 666 ${chroot_dir}/dev/tty c 5 0}}

If you need SCSI disc access you can create the device nodes like this:

{{Note|Every device can have 15 sub-nodes, you should always increment by 16 for every new device}}

{{Cmd|mknod -m 666 ${chroot_dir}/dev/sda b 8 0
mknod -m 666 ${chroot_dir}/dev/sda1 b 8 1
mknod -m 666 ${chroot_dir}/dev/sda2 b 8 2
mknod -m 666 ${chroot_dir}/dev/sda3 b 8 3
mknod -m 666 ${chroot_dir}/dev/sdb b 8 16
mknod -m 666 ${chroot_dir}/dev/sdb1 b 8 17}}

==== Make the process fs and /sys fs available ====

{{Cmd|mount -t proc none ${chroot_dir}/proc
mount -o bind /sys ${chroot_dir}/sys}}

==== Set up name resolution ====

A resolv.conf is needed for name resolution:

You can either copy your host's resolv.conf:
{{Cmd|cp -L /etc/resolv.conf ${chroot_dir}/etc/}}

or instead you can create a new one (this example uses OpenDNS):
{{Cmd|echo -e 'nameserver 8.8.8.8\nnameserver 2620:0:ccc::2' > ${chroot_dir}/etc/resolv.conf}}

==== Prepare the APK repositories ====

Set up APK main repository (replace <tt>${branch}</tt> with the latest stable branch name, e.g. v3.3):

{{Cmd|mkdir -p ${chroot_dir}/etc/apk
echo "${mirror}/${branch}/main" > ${chroot_dir}/etc/apk/repositories}}

{{Warning|The chroot methods are commonly used to have Alpine installed in a existing system. Because of this, the steps for preparing a bootloader are not included.}}

==== Entering your chroot ====

You then can enter your chroot by running this command as the root user (UID 0).

{{Cmd|chroot ${chroot_dir} /bin/ash -l}}

==== Preparing init services ====

If you plan to use your chroot with a init system or setup a new system on another device you should add these services:

{{Cmd|rc-update add devfs sysinit
rc-update add dmesg sysinit
rc-update add mdev sysinit

rc-update add hwclock boot
rc-update add modules boot
rc-update add sysctl boot
rc-update add hostname boot
rc-update add bootmisc boot
rc-update add syslog boot

rc-update add mount-ro shutdown
rc-update add killprocs shutdown
rc-update add savecache shutdown}}


= Troubleshooting =

== Hardened kernels or alpine as chroot host ==

If you are using Alpine as a native build system you will have to make sure that you can run <code>chmod</code> from a chroot. Add the following to <code>/etc/sysctl.conf</code>

<code>kernel.grsecurity.chroot_deny_chmod = 0</code>

Then reload the sysctl configuration

<code>sysctl -p</code>

== chroot: cannot run command ' ... Exec format error ==

This usually indicates that you booted with one architecture (e.g. armf) and are trying to chroot into another (e.g. x86_64). The binaries must be built for the architecture that the host runs!

Note that with '''one exception you can run 32 bit x86 chroot in x86_64, but not viceversa'''!

== WARNING: Ignoring APKINDEX.xxxx.tar.gz ==

Make sure <code>${chroot_dir}/etc/apk/repositories</code> is valid and run:

<code>apk update</code>

= External links =

* You can also use script [https://github.com/alpinelinux/alpine-chroot-install/ alpine-chroot-install]
* https://web.archive.org/web/20190808203313/https://isc.sans.edu/forums/diary/Forensic+use+of+mount+bind/22854/
* Alpine Linux in a chroot on Fedora : http://git.alpinelinux.org/cgit/user/fab/scripts/tree/alpine-chroot.sh script
* Alpine Linux aarch64 in a chroot on AWS Linux : https://gist.github.com/emolitor/0567e51c0ce04f4b025fc78d2cf0b4f1 script

[[Category: Installation]]
[[category: System Administration]]

Tutorials and Howtos

2022-01-06T13:33:18Z

Mckaygerhard: /* Beginners and Newbies */

{{Todo|This material needs to be re-organized .. as '''Howtos are smaller articles''' and '''tutorials are more detailed document''' both need to be reordered as independent sections }}

[[Image:package_edutainment.svg|right|link=]]
{{TOC left}}
'''Welcome to Tutorials and Howtos, a place of basic and advanced configuration tasks for your Alpine Linux.'''

'''The tutorials are hands-on''' and the reader is expected to try and achieve the goals described in each step, possibly with the help of a good example. The output in one step is the starting point for the following step.

'''Howtos are smaller articles''' explaining how to perform a particular task with Alpine Linux, that expects a minimal knowledge from reader to perform actions.

'''IMPORTANT:''' contributions on those pages must be complete articles as well as requesting topics to be covered, don't override already made contributions. If you want to request a topic, please add your request in this page's [[Talk:Tutorials_and_Howtos|Discussion]].

{{Clear}}

==== Postinstall: desktops and applications ====

* [[Desktop environments and Window managers]] (overall information only)
** [[Xfce]]
** [[LXQt]]
** [[Openbox]]
** [[MATE]]
* [[Alpine and UEFI|Alpine and UEFI Support Status and related topics]]

==== Developers: compilers, IDEs and tools ====

* [[Alpine newbie developer]]
** [[Alpine newbie developer: gitea|Alpine newbie developer: Git management web frontend gitea]]
** [[Alpine newbie developer: full stack web]]

==== Servers: deploy in production ====

* [[Alpine production deploy]]
** [[Production Web server: Lighttpd‎‎]]
** [[Production DataBases : mysql]]
** [[Production LAMP system: Lighttpd + PHP + MySQL‎‎]]
* Alpine production monitoring
** [[Cacti: traffic analysis and monitoring network]]
** [[Zabbix|Zabbix - the professional complete manager]]

== Storage ==

* [[Alpine local backup|Alpine local backup (lbu)]] ''(Permanently store your modifications in case your box needs reboot)'' 
** [[Back Up a Flash Memory Installation]] 
** [[Manually editing a existing apkovl]]

* [[Setting up disks manually]] 
* [[Setting up a software RAID array]]

* [[Raid Administration]]
* [[Setting up encrypted volumes with LUKS]]
* [[Setting up LVM on LUKS]]
* [[Setting up Logical Volumes with LVM]]
** [[Setting up LVM on GPT-labeled disks]]
** [[Installing on GPT LVM]]
* [[Filesystems|Formatting HD/Floppy/Other]] 

* [[Setting up iSCSI]]
** [[iSCSI Raid and Clustered File Systems]]
* [[Setting up NBD]]
* [[Setting up ZFS on LUKS]]
* [[Setting up ZFS with native encryption]]
* [[High performance SCST iSCSI Target on Linux software Raid]] ''(deprecated)'' 
* [[Linux iSCSI Target (TCM)]]
* [[Disk Replication with DRBD]] 

* [[Burning ISOs]] 
* [[Partitioning and Bootmanagers]]
* [[Migrating data]]
* [[Create a bootable SDHC from a Mac]]
* [[Alpine on ARM]]

== Networking ==

* [[Configure Networking]]
* [[Connecting to a wireless access point]]
* [[Bonding]]
* [[Vlan]]
* [[Bridge]]
* [[Bridge wlan0 to eth0]]
* [[OpenVSwitch]]
* [[How to configure static routes]]
* [[Configure a Wireguard interface (wg)]]

* [[Alpine Wall]] - [[How-To Alpine Wall]] - [[Alpine Wall User's Guide]] ''(a new firewall management framework)''

* [[PXE boot]]

* [[Using serial modem]]
* [[Using HSDPA modem]]
* [[Setting up Satellite Internet Connection]]
* [[Using Alpine on Windows domain with IPSEC isolation]]

* [[Setting up a SSH server]] ''(Using SSH is the preferred way to administer your box remotely)'' 
** [[HOWTO OpenSSH 2FA with password and Google Authenticator]] ''(A simple two factor setup for OpenSSH)''
* [[How to setup a wireless access point]] ''(Setting up Secure Wireless AP w/ WPA encryption with bridge to wired network)''
* [[How to set up Alpine as a wireless router]] ''(Setting up a firewalled, Wireless AP with wired network on a Pi Zero W)''
* [[Setting up a OpenVPN server with Alpine]] ''(Allowing single users or devices to remotely connect to your network)''

* [[Experiences with OpenVPN-client on ALIX.2D3]] 

* [[Generating SSL certs with ACF]] 
* [[Setting up unbound DNS server]]
* [[Setting up nsd DNS server]]
* [[TinyDNS Format]]
* [[Fault Tolerant Routing with Alpine Linux]] 
* [[Freeradius Active Directory Integration]]
* [[Multi_ISP]] ''(Dual-ISP setup with load-balancing and automatic failover)''
* [[OwnCloud]] ''(Installing OwnCloud)''

* [[Seafile: setting up your own private cloud]]

* [[GNUnet]]

== Post-Install ==


* [[Setting up a new user]]
* [[Enable Community Repository]] ''(Providing additional packages)''
* [[Alpine Linux package management|Package Management (apk)]] ''(How to add/remove packages on your Alpine)''

** [[Comparison with other distros]]
* [[Alpine local backup|Alpine local backup (lbu)]] ''(Permanently store your modifications in case your box needs reboot)''
** [[Back Up a Flash Memory Installation]] 
** [[Manually editing a existing apkovl]]
* [[Alpine Linux Init System|Init System (OpenRC)]] ''(Configure a service to automatically boot at next reboot)''
** [[Multiple Instances of Services]]

* [[Alpine setup scripts#setup-xorg-base|Setting up Xorg]]
* [[Upgrading Alpine]]


* [[Setting up a ssh-server]] ''(Using ssh is a good way to administer your box remotely)''
** [[HOWTO OpenSSH 2FA with password and Google Authenticator]] ''(A simple two factor setup for OpenSSH)''
* [[setup-acf]] ''(Configures ACF (webconfiguration) so you can manage your box through https)''
* [[Changing passwords for ACF|Changing passwords]]
* [[Ansible]] ''(Configuration management)''

* [[Enable Serial Console on Boot]]

* [[How to get regular stuff working]] ''some notes on need-to-know topics''
* [[Installing Oracle Java]]
* [[Rsnapshot|Setting up periodic backups with <samp>rsnapshot</samp>]]

== Virtualization==

* [[Xen Dom0]] ''(Setting up Alpine as a dom0 for Xen hypervisor)''
* [[Xen Dom0 on USB or SD]]
* [[Create Alpine Linux PV DomU]]
* [[Xen PCI Passthrough]]
* [[Xen LiveCD]]
* [[QEMU]]
* [[KVM]] ''(Setting up Alpine as a KVM hypervisor)''
* [[LXC]] ''(Setting up a Linux container in Alpine Linux)''
* [[Docker]]
* [[Install_Alpine_on_VirtualBox]]
* [[Install Alpine on VMWare]]

== Desktop Environment ==

* [[AwesomeWM]]
* [[dwm]]
* [[EyeOS]] ''(Cloud Computing Desktop)''
* [[Gnome]]
* [[KDE]]
* [[MATE]]
* [[Oneye]] ''(Cloud Computing Desktop - Dropbox Alternative)''
* [[Nextcloud]] ''(Self hostable cloud suite - Dropbox Alternative)''
* [[Remote Desktop Server]]
* [[River]]
* [[Suspend on LID close]]
* [[Sway]]
* [[Xfce Desktop]]
* [[Sound Setup]]
* [[PipeWire]]
* [[Printer Setup]]
* [[Default applications]]

== Raspberry Pi ==

* [[Raspberry Pi|Raspberry Pi (Installation)]]
* [[Raspberry Pi - Headless Installation]]
* [[Classic install or sys mode on Raspberry Pi]]
* [[RPI Video Receiver]] ''(network video decoder using Rasperry Pi and omxplayer)''
* [[Linux Router with VPN on a Raspberry Pi]]
* [[Linux Router with VPN on a Raspberry Pi (IPv6)]]
* [[Raspberry Pi 4 - Persistent system acting as a NAS and Time Machine]]
* [[Raspberry Pi 3 - Configuring it as wireless access point -AP Mode]]
* [[Raspberry Pi 3 - Setting Up Bluetooth]]
* [[Raspberry Pi 3 - Browser Client]] - kiosk or digital sign
* [[Raspberry Pi Zero W - Installation]]
* [[Raspberry Pi Bluetooth Speaker]]

== PowerPC ==

* [[Ppc64le|Powerpc64le (Installation)]]

== IBM Z (IBM z Systems) ==

* [[s390x|s390x (Installation)]]

== Applications ==

=== Telephony ===
* [[Setting up Zaptel/Asterisk on Alpine]]
** [[Setting up Streaming an Asterisk Channel]]
* [[Freepbx on Alpine Linux]]
* [[FreePBX_V3]] ''(FreeSWITCH, Asterisk GUI web acces tool)''
* [[2600hz]] ''(FreeSWITCH, Asterisk GUI web access tool)''
* [[Kamailio]] ''(SIP Server, formerly OpenSER)''

=== Mail ===
* [[Hosting services on Alpine]] ''(Hosting mail, webservices and other services)''
** [[Hosting Web/Email services on Alpine]]
* [[ISP Mail Server HowTo]] 
** [[ISP Mail Server Upgrade 2.x]]
** [[ISP Mail Server 2.x HowTo]] ''(Beta, please test)''
** [[ISP Mail Server 3.x HowTo]]
* [[Roundcube]] ''(Webmail system)''
* [[Setting up postfix with virtual domains]]
* [[Protecting your email server with Alpine]]
* [[Setting up clamsmtp]]
* [[Setting up dovecot with imap and ssl]]
* [[relay email to gmail (msmtp, mailx, sendmail]]

=== HTTP ===
* [[Lighttpd]]
** [[Lighttpd Https access]]
** [[Setting Up Lighttpd with PHP]]
** [[Setting Up Lighttpd With FastCGI]]
* [[Cherokee]]
* [[Nginx]]
** [[Nginx_with_PHP#Nginx_with_PHP|Nginx with PHP]]
** [[Nginx as reverse proxy with acme (letsencrypt)]]
* [[Apache]]
** [[Apache with php-fpm]]
** [[Setting Up Apache with PHP]]
** [[Apache authentication: NTLM Single Signon]]

* [[High Availability High Performance Web Cache]] ''(uCarp + HAProxy for High Availability Services such as Squid web proxy)'' 

* [[Setting up Transparent Squid Proxy]] 
** [[SqStat]] ''(Script to look at active squid users connections)''
** [[Obtaining user information via SNMP]] ''(Using squark-auth-snmp as a Squid authentication helper)'' 
* [[Setting up Explicit Squid Proxy]]

* [[Drupal]] ''(Content Management System (CMS) written in PHP)''
* [[WordPress]] ''(Web software to create website or blog)''
* [[MediaWiki]] ''(Free web-based wiki software application)''
* [[DokuWiki]]
* [[Darkhttpd]]
* [[Tomcat]]
* [[Kopano]] ''(Microsoft Outlook compatible Groupware)''

=== Other Servers ===
* [[Setting up a ssh-server]] ''(Using ssh is a good way to administer your box remotely)''
** [[HOWTO OpenSSH 2FA with password and Google Authenticator]] ''(A simple two factor setup for OpenSSH)''

* [[Setting up a nfs-server]]
* [[Setting up a samba-server]] ''(standard file sharing)''
* [[Setting up a samba-ad-dc]] ''(Active Directory compatible domain controller)''
* [[Phpizabi]] ''(Social Networking Platform)''
* [[Statusnet]] ''(Microblogging Platform)''
* [[Pastebin]] ''(Pastebin software application)''
* [[Setting up Transmission (bittorrent) with Clutch WebUI]]

* [[Patchwork]] ''(Patch review management system)''
* [[Redmine]] ''(Project management system)''
* [[Request-Tracker]] ''(Ticket system)''
* [[OsTicket]] ''(Ticket system)''
* [[Setting up trac wiki|Trac]] ''(Enhanced wiki and issue tracking system for software development projects)''

* [[Alpine_newbie_developer: gitea|Setting up Git management web frontend gitea]]
* [[Cgit]]
** [[Setting up a git repository server with gitolite and cgit]] 
* [[Roundcube]] ''(Webmail system)''
* [[Glpi]] ''(Manage inventory of technical resources)''

* [[How to setup a Alpine Linux mirror]]
* [[Cups]]
* [[NgIRCd]] ''(Server for Internet Relay Chat/IRC)''
* [[How To Setup Your Own IRC Network]] ''(Using {{Pkg|charybdis}} and {{Pkg|atheme-iris}})''
* [[OpenVCP]] ''(VServer Control Panel)''
* [[Mahara]] ''(E-portfolio and social networking system)''
* [[Chrony and GPSD | Using chrony, gpsd, and a garmin LVC 18 as a Stratum 1 NTP source ]]
* [[Sending SMS using gnokii]]
* [[IPTV How To|Internet Protocol television (IPTV)]]
* [[UniFi_Controller]]
* [[DNSCrypt-Proxy]] ''Encrypt and authenticate DNS calls from your system''
* [[Odoo]]

=== Monitoring ===
* Setting up [[collectd]]
* [[Traffic monitoring]] 
* [[Setting up traffic monitoring using rrdtool (and snmp)]] 
* [[Setting up monitoring using rrdtool (and rrdcollect)]]
* [[Cacti: traffic analysis and monitoring network]] ''(Front-end for rrdtool networking monitor)''
* [[LTTng]] ''(Kernel and userspace tracing)''
* [[Zabbix|Zabbix - the professional complete manager]] ''(Monitor and track the status of network services and hardware)''
* [[Setting up A Network Monitoring and Inventory System]] ''(Nagios + OpenAudit and related components)'' 
** [[Setting up NRPE daemon]] ''(Performs remote Nagios checks)'' 
* [[Setting up Smokeping|Smokeping]] ''(Network latency monitoring)'' 
** [[Setting up MRTG and Smokeping to Monitor Bandwidth Usage and Network Latency]]
* [[Setting Up Fprobe And Ntop|Ntop]] ''(NetFlow collection and analysis using a remote fprobe instance)'' 
* [[Cvechecker]] ''(Compare installed packages for Common Vulnerabilities Exposure)'' 

* [[IP Accounting]] 
* [[Obtaining user information via SNMP]] ''(Using squark-auth-snmp as a Squid authentication helper)'' 
* [[SqStat]] ''(Script to look at active squid users connections)''

* [[Piwik]] ''(A real time web analytics software program)''
* [[Awstats]] ''(Free log file analyzer)''
* [[Intrusion Detection using Snort]]
** [[Intrusion Detection using Snort, Sguil, Barnyard and more]]
* [[Dglog]] ''(Log analyzer for the web content filter DansGuardian)''

* [[Webmin]] ''(A web-based interface for Linux system)''
* [[PhpPgAdmin]] ''(Web-based administration tool for PostgreSQL)''
* [[PhpMyAdmin]] ''(Web-based administration tool for MYSQL)''
* [[PhpSysInfo]] ''(A simple application that displays information about the host it's running on)''
* [[Linfo]]

* [[Setting up lm_sensors]]

* [[ZoneMinder video camera security and surveillance]]

== Misc ==

* [[:Category:Shell]]
* [[:Category:Programming]]
* [[Running glibc programs]]
* [[:Category:Drivers]]
* [[:Category:Multimedia]]
* [[Kernel Modesetting]]
* [[CPU frequency scaling]]

== Complete Solutions ==
* [[DIY Fully working Alpine Linux for Allwinner and Other ARM SOCs]]
* [https://codeberg.org/AVG7/alpine-sway-x86_64 DIY Live-USB-Stick with Sway]
* [[Alpine on the Aopen Chromebase or Chromebox Mini with Mainline Kernel]]
* [[Replacing non-Alpine Linux with Alpine remotely]]
* [[High performance SCST iSCSI Target on Linux software Raid]]
* [[Fault Tolerant Routing with Alpine Linux]]
* [[Experiences with OpenVPN-client on ALIX.2D3]]
* [[Building a cloud with Alpine Linux]]

* [[ISP Mail Server HowTo]] ''(Postfix+PostfixAdmin+DoveCot+Roundcube+ClamAV+Spamd - A full-serivce ISP mail server)''
** [[ISP Mail Server Upgrade 2.x]]
** [[ISP Mail Server 2.x HowTo]] ''(Beta, please test)''
* [[High Availability High Performance Web Cache]] ''(uCarp + HAProxy for High Availability Services such as Squid web proxy)''
* [[Setting up A Network Monitoring and Inventory System]] ''(Nagios + OpenAudit and related components)'' 
* [[Streaming Security Camera Video with VLC]]
* [[Dynamic Multipoint VPN (DMVPN)]] combined with [[Small_Office_Services]]



== Newbies ==

* [[Alpine_newbie]] (for overall information in funny sections)

* [[Alpine_newbie_apk_packages|Alpine newbie users post install and easy setups]]
** [[Alpine_newbie_apk_packages#New_users:_hostname_and_network_wired_connection|First steps at post install]]
** [[Alpine_newbie_apk_packages#New_users:_common_needed_package_to_install|Enable repositories]]
** [[Alpine_newbie_apk_packages#New_users:_management_of_users_and_logins|Added the first user to use the system]]
** [[Alpine_newbie_apk_packages#install_basic_tools|First packages to install]] (need the previous [[Alpine_newbie_apk_packages#New_users:_common_needed_package_to_install|Enable repositories]]) already done!

==== Installation: Use cases ====

* [[Alpine newbie install manual]]
** [[Alpine Install: from a disc to a new computer single only boot]]
** [[Alpine Install: from a disc to a old computer single only boot]]
** [[Alpine Install: from a disc to a virtualbox machine single only]]
** [[Alpine Install: from a iso to a virtualbox machine with external disc]]
* [[Alpine_newbie_install_manual#Ways_to_install_Alpine_listed_by_architectures|Ways to install listed by architectures]]
** [[Alpine_newbie_install_manual#x86_64_x86_32_x86|x86_64 x86_32 x86 s390]]
** [[Alpine_newbie_install_manual#armhf_armv7|armhf armv7 aarch64]]
** [[Alpine_newbie_install_manual#ppc64le|ppc64le others PPC]]

[[Category:Newbie]]
[[Category:System_Administration]]
[[Category:Installation]]

Desktop environments and Window managers

2022-01-06T13:32:50Z

Mckaygerhard:

Desktop environments and Window managers

2022-01-06T13:32:38Z

Mckaygerhard: please do not mix my newbie categories..

User talk:Guest09248

2022-01-05T19:50:31Z

Mckaygerhard:

Hello, thank you for proposing several articles for deletion on the wiki, this calls attention to the fact that some of these articles need help. Please when doing so do not blank or replace the entire article; simply add the proposal for deletion template to the top of the article, and then add your rationale to the article talk page so that a consensus can be reached.

For instance, I have no idea why you want [[HOWTO OpenSSH 2FA with password and Google Authenticator]] deleted, so I have reverted your blanking there. That article is, to my knowledge, up-to-date.

Thanks, [[User:Zcrayfish|zcrayfish]] ([[User talk:Zcrayfish|talk]]) 22:40, 8 December 2021 (UTC)

--

hey .. thanks for grammar fixes, i appreciate your contributions to Alpine newbie section but take a look at:

[[File:Poolwikialpineinteelgram2021.png|frameless|center|Last pool about wiki pages, it seems my ones are the best]]

that was from 2021 Dec, the 2019 is worse, i made a new pool about my pages and it seems in 2019 were better than today and the newbie pages are a still in progress structure.. please dont move structure and mix with official wiki pages..

By example my LAMP (the worse software piece of) page is a well received only by noobs.. but xperts will hate it! (in few days will have more negative reactions):

[[File:Poolaboutlampwikipage.png|frameless|center|pool about reception of my worse wiki made page!]]

take more at: https://t.me/s/alpine_linux/539 noobs will said "good" and people that are envy will compared with arch.. that's why you must explain why and all those comments has a piece of true.. and yes.. is more for noobs cos it said "newbie" .. experts users just read their own wikis as i made for my job..

[[User:Mckaygerhard|Mckaygerhard]] ([[User talk:Mckaygerhard|talk]]) 12:40, 5 Jan 2022 (UTC)

User talk:Guest09248

2022-01-05T19:49:48Z

Mckaygerhard:

Hello, thank you for proposing several articles for deletion on the wiki, this calls attention to the fact that some of these articles need help. Please when doing so do not blank or replace the entire article; simply add the proposal for deletion template to the top of the article, and then add your rationale to the article talk page so that a consensus can be reached.

For instance, I have no idea why you want [[HOWTO OpenSSH 2FA with password and Google Authenticator]] deleted, so I have reverted your blanking there. That article is, to my knowledge, up-to-date.

Thanks, [[User:Zcrayfish|zcrayfish]] ([[User talk:Zcrayfish|talk]]) 22:40, 8 December 2021 (UTC)

--

hey .. thanks for grammar fixes, i appreciate your contributions to Alpine newbie section but take a look at:

[[File:Poolwikialpineinteelgram2021.png|frameless|center|Last pool about wiki pages, it seems my ones are the best]]

that was from 2021 Dec, the 2019 is worse, i made a new pool about my pages and it seems in 2019 were better than today and the newbie pages are a still in progress structure.. please dont move structure and mix with official wiki pages..

By example my LAMP (the worse software piece of) page is a well received:

[[File:Poolaboutlampwikipage.png|frameless|center|pool about reception of my worse wiki made page!]]

take more at: https://t.me/s/alpine_linux/539 noobs will said "good" and people that are envy will compared with arch.. that's why you must explain why and all those comments has a piece of true.. and yes.. is more for noobs cos it said "newbie" .. experts users just read their own wikis as i made for my job..

[[User:Mckaygerhard|Mckaygerhard]] ([[User talk:Mckaygerhard|talk]]) 12:40, 5 Jan 2022 (UTC)

User talk:Guest09248

2022-01-05T18:36:43Z

Mckaygerhard:

Hello, thank you for proposing several articles for deletion on the wiki, this calls attention to the fact that some of these articles need help. Please when doing so do not blank or replace the entire article; simply add the proposal for deletion template to the top of the article, and then add your rationale to the article talk page so that a consensus can be reached.

For instance, I have no idea why you want [[HOWTO OpenSSH 2FA with password and Google Authenticator]] deleted, so I have reverted your blanking there. That article is, to my knowledge, up-to-date.

Thanks, [[User:Zcrayfish|zcrayfish]] ([[User talk:Zcrayfish|talk]]) 22:40, 8 December 2021 (UTC)

--

hey .. thanks for grammar fixes, i appreciate your contributions to Alpine newbie section but take a look at:

[[File:Poolwikialpineinteelgram2021.png|frameless|center|Last pool about wiki pages, it seems my ones are the best]]

that was from 2021 Dec, the 2019 is worse, i made a new pool about my pages and it seems in 2019 were better than today and the newbie pages are a still in progress structure.. please dont move structure and mix with official wiki pages..

By example my LAMP (the worse software piece of) page is a well received:

[[File:Poolaboutlampwikipage.png|frameless|center|pool about reception of my worse wiki made page!]]

take more at: https://t.me/s/alpine_linux/539

[[User:Mckaygerhard|Mckaygerhard]] ([[User talk:Mckaygerhard|talk]]) 12:40, 5 Jan 2022 (UTC)

User talk:Guest09248

2022-01-05T18:33:45Z

Mckaygerhard:

Hello, thank you for proposing several articles for deletion on the wiki, this calls attention to the fact that some of these articles need help. Please when doing so do not blank or replace the entire article; simply add the proposal for deletion template to the top of the article, and then add your rationale to the article talk page so that a consensus can be reached.

For instance, I have no idea why you want [[HOWTO OpenSSH 2FA with password and Google Authenticator]] deleted, so I have reverted your blanking there. That article is, to my knowledge, up-to-date.

Thanks, [[User:Zcrayfish|zcrayfish]] ([[User talk:Zcrayfish|talk]]) 22:40, 8 December 2021 (UTC)

--

hey .. thanks for grammar fixes, i appreciate your contributions to Alpine newbie section but take a look at:

[[File:Poolwikialpineinteelgram2021.png|frameless|center|Last pool about wiki pages, it seems my ones are the best]]

that was from 2021 Dec, the 2019 is worse, i made a new pool about my pages and it seems in 2019 were better than today and the newbie pages are a still in progress structure.. please dont move structure and mix with official wiki pages..

By example my LAMP (the worse software piece of) page is a well received:

[[File:Poolaboutlampwikipage.png|frameless|center|pool about reception of my worse wiki made page!]]

take more at: https://t.me/s/alpine_linux/541

[[User:Mckaygerhard|Mckaygerhard]] ([[User talk:Mckaygerhard|talk]]) 12:40, 5 Jan 2022 (UTC)

User talk:Guest09248

2022-01-05T18:32:39Z

Mckaygerhard:

Hello, thank you for proposing several articles for deletion on the wiki, this calls attention to the fact that some of these articles need help. Please when doing so do not blank or replace the entire article; simply add the proposal for deletion template to the top of the article, and then add your rationale to the article talk page so that a consensus can be reached.

For instance, I have no idea why you want [[HOWTO OpenSSH 2FA with password and Google Authenticator]] deleted, so I have reverted your blanking there. That article is, to my knowledge, up-to-date.

Thanks, [[User:Zcrayfish|zcrayfish]] ([[User talk:Zcrayfish|talk]]) 22:40, 8 December 2021 (UTC)

--

hey .. thanks for grammar fixes, i appreciate your contributions to Alpine newbie section but take a look at:

[[File:Poolwikialpineinteelgram2021.png|frameless|center|Last pool about wiki pages, it seems my ones are the best]]

that was from 2021 Dec, the 2019 is worse, i made a new pool about my pages and it seems in 2019 were better than today and the newbie pages are a still in progress structure.. please dont move structure and mix with official wiki pages..

By example my LAMP (the worse software piece of) page is a well received:

[[File:Poolaboutlampwikipage.png|thumb|pool about reception of my worse wiki made page!]]

[[User:Mckaygerhard|Mckaygerhard]] ([[User talk:Mckaygerhard|talk]]) 12:40, 5 Jan 2022 (UTC)

User talk:Guest09248

2022-01-05T18:31:49Z

Mckaygerhard: thanks but please mantain structure of newbie pages separate from wiki ones

Hello, thank you for proposing several articles for deletion on the wiki, this calls attention to the fact that some of these articles need help. Please when doing so do not blank or replace the entire article; simply add the proposal for deletion template to the top of the article, and then add your rationale to the article talk page so that a consensus can be reached.

For instance, I have no idea why you want [[HOWTO OpenSSH 2FA with password and Google Authenticator]] deleted, so I have reverted your blanking there. That article is, to my knowledge, up-to-date.

Thanks, [[User:Zcrayfish|zcrayfish]] ([[User talk:Zcrayfish|talk]]) 22:40, 8 December 2021 (UTC)

hey .. thanks for grammar fixes, i appreciate your contributions to Alpine newbie section but take a look at:

[[File:Poolwikialpineinteelgram2021.png|frameless|center|Last pool about wiki pages, it seems my ones are the best]]

that was from 2021 Dec, the 2019 is worse, i made a new pool about my pages and it seems in 2019 were better than today and the newbie pages are a still in progress structure.. please dont move structure and mix with official wiki pages..

By example my LAMP (the worse software piece of) page is a well received:

[[File:Poolaboutlampwikipage.png|thumb|pool about reception of my worse wiki made page!]]

File:Poolaboutlampwikipage.png

2022-01-05T18:31:13Z

Mckaygerhard:

Pool about the newbie version of LAMP mysql + php wiki page made by mckaygerhard respect rest of wiki.

User:Mckaygerhard

2022-01-05T18:26:48Z

Mckaygerhard:

= "PICCORO" Герхард Lenz McKAY =

For spanish users: https://mckayemu.github.io/alpineinstalls/

* https://gitlab.alpinelinux.org/mckaygerhard/alpine-newbie

Documenting in proper way the lack of alpine documentation.

[[File:Poolwikialpineinteelgram2021.png|frameless|center|Last pool about wiki pages, it seems my ones are the best]]

User:Mckaygerhard

2022-01-05T18:24:24Z

Mckaygerhard:

= "PICCORO" Герхард Lenz McKAY =

For spanish users: https://mckayemu.github.io/alpineinstalls/

* https://gitlab.alpinelinux.org/mckaygerhard/alpine-newbie

Documenting in proper way the lack of alpine documentation.

[[File:Poolwikialpineinteelgram2022.png|Last 2021 pool about wiki pages, it seems my editing are the only good!]]