Alpine Linux - User contributions [en]

User:Fab

2021-01-12T19:09:09Z

Fab: Update xmpp

My Name is Fabian Affolter and I'm living in Berne/Switzerland. One of my passions is free software and open source. I'm a long time contributor to various free and open source software projects. A big bunch of my spare time is spent on the [https://fedoraproject.org Fedora Project] and [https://home-assistant.io Home Assistant].

By the way, my first system was a Amiga 2000 but this is a long long time ago ;-).

My area of interest are computer aided design (CAD), computer algebra system (CAS), provisioning, automatic configuration management, version control systems, software packaging and microcontrollers.

Apart from spending time at the computer, I like to read, to listen to music and to hike in the Swiss mountains.

== more personal stuff ==

* ''' Location''': [http://en.wikipedia.org/wiki/Berne Berne] [http://de.wikipedia.org/wiki/Bern Bern], [http://en.wikipedia.org/wiki/Switzerland Switzerland] [http://de.wikipedia.org/wiki/Schweiz Schweiz]
* ''' Time zone''' : UTC +01:00 (CET) or UTC +02:00 (CEST)
* ''' Languages''' : German (it's more Swiss German), English, and French
* ''' Profession''' : Senior Engineer, B.Sc. [http://www.ti.bfh.ch/en/bachelor/mechanical.html ME] and [http://www.ti.bfh.ch/en/bachelor/computer_science.html CS] [http://www.ti.bfh.ch/ Berne University of Applied Sciences] - Engineering and Information Technology

== Contact ==

* '''Postal address''' :
::ask for the street
::CH-3000 Berne
::Switzerland
* '''Blog''' : [http://blog.fabian-affolter.ch/ My blog] (be aware...some parts are in german)
* '''Websites''': [http://fabian-affolter.ch/ fabian-affolter.ch]
* '''Email''': [mailto:fabian%affolter-engineering%2ench fabian AT affolter-engineering DOT ch]
* '''GPG/PGP''' : [http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x36A4397F 0x36A4397F]
* '''Jabber''' : fab AT jabber DOT dk
* '''IRC''' : faffolter (or fabian_a) on FreeNode

== Misc ==
* [[Alpine_Security_and_Rescue|Alpine Security Flavor]]
* [[User:Fab/Personal_aports_repo|Personal aport repo]]
* [[User:Fab/Stats|Stats]]
* [[User:Fab/Cleanup|Cleanup]]
* [[User:Fab/msg.alpinelinux.org|msg.alpinelinux.org]]
* [[User:Fab/Notifications|Notifications]]

=== Configuration management ===

* [[User:Fab/Ansible|Ansible]]
* [[User:Fab/Bcfg2|Bcfg2]]
* [[User:Fab/Salt|Salt]]

=== Other docs ===
* [[User:Fab/Nodejs|Node.js]]
* [[User:Fab/Ocr|OCR]]
* [[User:Fab/Tryton|Tryton]]
* [[User:Fab/Metasploit|Metasploit]]
* [[User:Fab/Beeswarm|Beeswarm]]

Include:Setup your system and account for building packages

2020-12-21T11:28:42Z

Fab: Later visudo is used

The {{Pkg|alpine-sdk}} is a metapackage that pulls in the most essential packages used to build new packages. Install those packages now:

{{Cmd|apk add alpine-sdk sudo}}

This would be a good time to create a normal user account for you to work in. (You weren't going to develop as root now, were you!) To create the user:

{{Cmd|adduser <yourusername>}}

To make life easier later, it's a good idea to add this user to {{Path|/etc/sudoers}}. Append the line

<yourusername> ALL=(ALL) ALL

using the command:

{{Cmd|visudo}}

Now logout of the root account, and login as <yourusername>. From here on everything can be done in a normal user account, and operations that require superuser privileges can be done with sudo.

The [[Aports_tree|aports tree]] is in git so before we clone the it, let's configure git.

{{Cmd|git config --global user.name "Your Full Name"
git config --global user.email "your@email.address"}}

Read carefully [[Development using git]] to grasp basic Git operations and how to configure for sending email patches.

Now we can clone the [[Aports_tree|aports tree]].

NOTE: You can also clone aports from our github https://github.com/alpinelinux/aports

{{Cmd|git clone git://git.alpinelinux.org/aports}}

Before we start creating or modifying [[APKBUILD_Reference|APKBUILD]] files, we need to setup abuild for our system and user. Edit the file {{Path|abuild.conf}} to your requirements:

{{Cmd|sudo $EDITOR /etc/abuild.conf}}

Most of the defaults can be left alone, unless you are developing for a custom platform, in which case the comments in the file should guide you. The one field to edit is PACKAGER, so that you can get credit (or blame) for packages you create.

To use 'abuild -r' command to install dependency packages automatically.
{{Cmd|sudo addgroup <yourusername> abuild}}

We also need to prepare the location where the build process caches files when they are downloaded. By default this is {{Path|/var/cache/distfiles/}}. To create this directory and ensure that it is writeable, enter the following commands:

{{Cmd|sudo mkdir -p /var/cache/distfiles
sudo chmod a+w /var/cache/distfiles}}

As an alternative to the second command, you can add yourself to the abuild group:

{{Cmd|sudo chgrp abuild /var/cache/distfiles
sudo chmod g+w /var/cache/distfiles}}

{{Note|Remember to logout and login again for the group change to have effect.}}

The last step is to configure the security keys with the [[Abuild-keygen|abuild-keygen]] script for [[Abuild|abuild]] with the command:

{{Cmd|abuild-keygen -a -i}}

[[Category:Development]]

Alpine Linux:Trivia

2020-06-12T14:48:35Z

Fab: /* Packages per release */ Update diagram

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* https://gitlab.alpinelinux.org/alpine/aports can give you a little insight

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.12'''
| 4832
| 3172
| 500
| 1073
| 87
|-
| '''3.11'''
| 5352
| 3430
| 620
| 1211
| 91
|-
| '''3.10'''
| 5669
| 3724
| 631
| 1224
| 90
|-
| '''3.9'''
| 5703
| 3721
| 652
| 1241
| 89
|-
| '''3.8'''
| 5674
| 3652
| 663
| 1272
| 87
|-
| '''3.7'''
| 5699
| 3629
| 683
| 1298
| 89
|-
| '''3.6'''
| 5548
| 3510
| 681
| 1271
| 86
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:202006-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 9065
2017 : 11661
2018 : 9546
2019 : 18759
2020 : 10597 (so far)
</pre>

== "High score list" of committer to aports ==

Don't get this the wrong way...those are just numbers. Every single contributions is making a difference.

<pre>
35479 Natanael Copa
9036 Leo
5382 Francesco Colista
3699 Jakub Jirutka
3429 Leonardo Arena
3033 Carlo Landmeter
2857 Timo Teräs
2382 Fabian Affolter
2145 Sören Tempel
1971 William Pitcock
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

File:202006-aports.png

2020-06-12T14:48:04Z

Fab:

Alpine Linux:Trivia

2020-06-12T09:53:56Z

Fab: /* Commit per year to aports */ Update list

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* https://gitlab.alpinelinux.org/alpine/aports can give you a little insight

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.12'''
| 4832
| 3172
| 500
| 1073
| 87
|-
| '''3.11'''
| 5352
| 3430
| 620
| 1211
| 91
|-
| '''3.10'''
| 5669
| 3724
| 631
| 1224
| 90
|-
| '''3.9'''
| 5703
| 3721
| 652
| 1241
| 89
|-
| '''3.8'''
| 5674
| 3652
| 663
| 1272
| 87
|-
| '''3.7'''
| 5699
| 3629
| 683
| 1298
| 89
|-
| '''3.6'''
| 5548
| 3510
| 681
| 1271
| 86
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201806-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 9065
2017 : 11661
2018 : 9546
2019 : 18759
2020 : 10597 (so far)
</pre>

== "High score list" of committer to aports ==

Don't get this the wrong way...those are just numbers. Every single contributions is making a difference.

<pre>
35479 Natanael Copa
9036 Leo
5382 Francesco Colista
3699 Jakub Jirutka
3429 Leonardo Arena
3033 Carlo Landmeter
2857 Timo Teräs
2382 Fabian Affolter
2145 Sören Tempel
1971 William Pitcock
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

Alpine Linux:Trivia

2020-06-12T09:51:46Z

Fab: /* "High score list" of committer to aports */ Update list

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* https://gitlab.alpinelinux.org/alpine/aports can give you a little insight

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.12'''
| 4832
| 3172
| 500
| 1073
| 87
|-
| '''3.11'''
| 5352
| 3430
| 620
| 1211
| 91
|-
| '''3.10'''
| 5669
| 3724
| 631
| 1224
| 90
|-
| '''3.9'''
| 5703
| 3721
| 652
| 1241
| 89
|-
| '''3.8'''
| 5674
| 3652
| 663
| 1272
| 87
|-
| '''3.7'''
| 5699
| 3629
| 683
| 1298
| 89
|-
| '''3.6'''
| 5548
| 3510
| 681
| 1271
| 86
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201806-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 9065
2017 : 11661
2018 : 5339 (so far)
</pre>

== "High score list" of committer to aports ==

Don't get this the wrong way...those are just numbers. Every single contributions is making a difference.

<pre>
35479 Natanael Copa
9036 Leo
5382 Francesco Colista
3699 Jakub Jirutka
3429 Leonardo Arena
3033 Carlo Landmeter
2857 Timo Teräs
2382 Fabian Affolter
2145 Sören Tempel
1971 William Pitcock
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

Alpine Linux:Trivia

2020-06-12T08:22:58Z

Fab: /* Packages per release */ Add data

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* https://gitlab.alpinelinux.org/alpine/aports can give you a little insight

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.12'''
| 4832
| 3172
| 500
| 1073
| 87
|-
| '''3.11'''
| 5352
| 3430
| 620
| 1211
| 91
|-
| '''3.10'''
| 5669
| 3724
| 631
| 1224
| 90
|-
| '''3.9'''
| 5703
| 3721
| 652
| 1241
| 89
|-
| '''3.8'''
| 5674
| 3652
| 663
| 1272
| 87
|-
| '''3.7'''
| 5699
| 3629
| 683
| 1298
| 89
|-
| '''3.6'''
| 5548
| 3510
| 681
| 1271
| 86
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201806-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 9065
2017 : 11661
2018 : 5339 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
29557 Natanael Copa
3996 Francesco Colista
2850 Jakub Jirutka
2827 Leonardo Arena
2744 Carlo Landmeter
2707 Timo Teräs
2220 Fabian Affolter
1952 William Pitcock
1490 Sören Tempel
1349 Bartłomiej Piotrowski
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

Alpine Linux:Trivia

2020-06-12T08:21:36Z

Fab: /* Packages */ Ohloh is gone

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* https://gitlab.alpinelinux.org/alpine/aports can give you a little insight

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.8'''
| 5674
| 3652
| 663
| 1272
| 87
|-
| '''3.7'''
| 5699
| 3629
| 683
| 1298
| 89
|-
| '''3.6'''
| 5548
| 3510
| 681
| 1271
| 86
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201806-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 9065
2017 : 11661
2018 : 5339 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
29557 Natanael Copa
3996 Francesco Colista
2850 Jakub Jirutka
2827 Leonardo Arena
2744 Carlo Landmeter
2707 Timo Teräs
2220 Fabian Affolter
1952 William Pitcock
1490 Sören Tempel
1349 Bartłomiej Piotrowski
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

Setting Up Lighttpd With FastCGI

2020-03-26T08:57:34Z

Fab: Update to 3.11

For installing the additional packages first activate community packages:
{{Cmd|vi /etc/apk/repositories}}
Uncomment the following:
{{Cmd|http://pkg.example.com/alpine/v3.11/community}}

Update the packagelist:
{{Cmd|apk update}}

Install the additional packages:
{{Cmd|apk add lighttpd php7-common php7-iconv php7-json php7-gd php7-curl php7-xml php7-mysqli php7-imap php7-cgi fcgi php7-pdo php7-pdo_mysql php7-soap php7-xmlrpc php7-posix php7-mcrypt php7-gettext php7-ldap php7-ctype php7-dom}}

==Configure Lighttpd==
'''Edit lighttpd.conf'''
{{Cmd|vi /etc/lighttpd/lighttpd.conf}}
Uncomment line:
include "mod_fastcgi.conf"

'''Edit mod_fastcgi.conf'''
{{Cmd|vi /etc/lighttpd/mod_fastcgi.conf}}
Edit the section:
/usr/bin/php-cgi
To:
/usr/bin/php-cgi7

==Start lighttpd service and add to needed runlevel==

{{Cmd|rc-service lighttpd start && rc-update add lighttpd default}}

[[Category:Server]]
[[Category:PHP]]

PhpMyAdmin

2020-03-26T08:56:01Z

Fab: phpMyAdmin < 5.0.2 has SQL injection vulnerabilities

[http://www.phpmyadmin.net phpMyAdmin] is a free software tool written in PHP intended to handle the administration of MySQL over the World Wide Web. phpMyAdmin supports a wide range of operations with MySQL. The most frequently used operations are supported by the user interface (managing databases, tables, fields, relations, indexes, users, permissions, etc), while you still have the ability to directly execute any SQL statement.

== Install lighttpd, PHP and MySql ==
{{:Setting Up Lighttpd With FastCGI}}

Install extra packages:
{{Cmd|apk add mysql mysql-client php-mysql php-mysqli}}

== Configuring MySql ==

{{Cmd|<nowiki>/usr/bin/mysql_install_db --user=mysql
/etc/init.d/mysql start && rc-update add mysql default
/usr/bin/mysqladmin -u root password 'password'</nowiki>}}

== Installing phpMyAdmin ==

Create a directory named {{Path|webapps}}

{{Cmd|mkdir -p /usr/share/webapps/}}
Download the source code

{{Cmd|cd /usr/share/webapps
wget http://files.directadmin.com/services/all/phpMyAdmin/phpMyAdmin-5.0.2-all-languages.tar.gz}}

Unpack the archive and remove the archive

{{Cmd|tar zxvf phpMyAdmin-5.0.2-all-languages.tar.gz
rm phpMyAdmin-5.0.2-all-languages.tar.gz}}

Rename the folder

{{Cmd|mv phpMyAdmin-5.0.2-all-languages phpmyadmin}}

Change the folder permissions

{{Cmd|chmod -R 777 /usr/share/webapps/}}

Create a symlink to the ''phpmyadmin'' folder

{{Cmd|ln -s /usr/share/webapps/phpmyadmin/ /var/www/localhost/htdocs/phpmyadmin}}

== Log on your phpMyAdmin ==

Browse to: http://WEBSERVER_IP_ADDRESS/phpmyadmin and logon to phpMyAdmin using your MySQL user and password.

[[Category:PHP]]
[[Category:SQL]]

Talk:Python package policies

2019-03-11T17:30:13Z

Fab: Created page with "This page duplicates quite a bit of details which are already present: - https://wiki.alpinelinux.org/wiki/Package_policies - https://wiki.alpinelinux.org/wiki/APKBUILD_examp..."

This page duplicates quite a bit of details which are already present:

- https://wiki.alpinelinux.org/wiki/Package_policies
- https://wiki.alpinelinux.org/wiki/APKBUILD_examples:Python

Instead of creating a new page the existing information should be updated.

Alpine Linux:Trivia

2018-07-01T15:40:50Z

Fab: /* Packages per release */ New diagram

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* [https://www.ohloh.net/p/aports aports] statistics provided by Ohloh.

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.8'''
| 5674
| 3652
| 663
| 1272
| 87
|-
| '''3.7'''
| 5699
| 3629
| 683
| 1298
| 89
|-
| '''3.6'''
| 5548
| 3510
| 681
| 1271
| 86
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201806-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 9065
2017 : 11661
2018 : 5339 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
29557 Natanael Copa
3996 Francesco Colista
2850 Jakub Jirutka
2827 Leonardo Arena
2744 Carlo Landmeter
2707 Timo Teräs
2220 Fabian Affolter
1952 William Pitcock
1490 Sören Tempel
1349 Bartłomiej Piotrowski
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

File:201806-aports.png

2018-07-01T15:39:08Z

Fab:

Alpine Linux:Trivia

2018-07-01T15:34:24Z

Fab: /* "High score list" of committer to aports */ update

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* [https://www.ohloh.net/p/aports aports] statistics provided by Ohloh.

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.8'''
| 5674
| 3652
| 663
| 1272
| 87
|-
| '''3.7'''
| 5699
| 3629
| 683
| 1298
| 89
|-
| '''3.6'''
| 5548
| 3510
| 681
| 1271
| 86
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201705-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 9065
2017 : 11661
2018 : 5339 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
29557 Natanael Copa
3996 Francesco Colista
2850 Jakub Jirutka
2827 Leonardo Arena
2744 Carlo Landmeter
2707 Timo Teräs
2220 Fabian Affolter
1952 William Pitcock
1490 Sören Tempel
1349 Bartłomiej Piotrowski
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

Alpine Linux:Trivia

2018-07-01T15:31:22Z

Fab: /* Commit per year to aports */ update

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* [https://www.ohloh.net/p/aports aports] statistics provided by Ohloh.

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.8'''
| 5674
| 3652
| 663
| 1272
| 87
|-
| '''3.7'''
| 5699
| 3629
| 683
| 1298
| 89
|-
| '''3.6'''
| 5548
| 3510
| 681
| 1271
| 86
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201705-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 9065
2017 : 11661
2018 : 5339 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
26715 Natanael Copa
2938 Francesco Colista
2477 Carlo Landmeter
2369 Timo Teräs
2312 Leonardo Arena
1971 Fabian Affolter
1571 William Pitcock
1350 Jakub Jirutka
1349 Bartłomiej Piotrowski
1037 Sören Tempel
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

Alpine Linux:Trivia

2018-07-01T15:28:27Z

Fab: /* Packages per release */ update

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* [https://www.ohloh.net/p/aports aports] statistics provided by Ohloh.

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.8'''
| 5674
| 3652
| 663
| 1272
| 87
|-
| '''3.7'''
| 5699
| 3629
| 683
| 1298
| 89
|-
| '''3.6'''
| 5548
| 3510
| 681
| 1271
| 86
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201705-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 9065
2017 : 4901 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
26715 Natanael Copa
2938 Francesco Colista
2477 Carlo Landmeter
2369 Timo Teräs
2312 Leonardo Arena
1971 Fabian Affolter
1571 William Pitcock
1350 Jakub Jirutka
1349 Bartłomiej Piotrowski
1037 Sören Tempel
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

User:Fab

2018-07-01T15:27:07Z

Fab: Update

My Name is Fabian Affolter and I'm living in Berne/Switzerland. One of my passions is free software and open source. I'm a long time contributor to various free and open source software projects. A big bunch of my spare time is spent on the [https://fedoraproject.org Fedora Project] and [https://home-assistant.io Home Assistant].

By the way, my first system was a Amiga 2000 but this is a long long time ago ;-).

My area of interest are computer aided design (CAD), computer algebra system (CAS), provisioning, automatic configuration management, version control systems, software packaging and microcontrollers.

Apart from spending time at the computer, I like to read, to listen to music and to hike in the Swiss mountains.

== more personal stuff ==

* ''' Location''': [http://en.wikipedia.org/wiki/Berne Berne] [http://de.wikipedia.org/wiki/Bern Bern], [http://en.wikipedia.org/wiki/Switzerland Switzerland] [http://de.wikipedia.org/wiki/Schweiz Schweiz]
* ''' Time zone''' : UTC +01:00 (CET) or UTC +02:00 (CEST)
* ''' Languages''' : German (it's more Swiss German), English, and French
* ''' Profession''' : Senior Engineer, B.Sc. [http://www.ti.bfh.ch/en/bachelor/mechanical.html ME] and [http://www.ti.bfh.ch/en/bachelor/computer_science.html CS] [http://www.ti.bfh.ch/ Berne University of Applied Sciences] - Engineering and Information Technology

== Contact ==

* '''Postal address''' :
::ask for the street
::CH-3000 Berne
::Switzerland
* '''Blog''' : [http://blog.fabian-affolter.ch/ My blog] (be aware...some parts are in german)
* '''Websites''': [http://fabian-affolter.ch/ fabian-affolter.ch]
* '''Email''': [mailto:fabian%affolter-engineering%2ench fabian AT affolter-engineering DOT ch]
* '''GPG/PGP''' : [http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x36A4397F 0x36A4397F]
* '''Jabber''' : fab AT swissjabber DOT dk
* '''IRC''' : faffolter (or fabian_a) on FreeNode

== Misc ==
* [[Alpine_Security_and_Rescue|Alpine Security Flavor]]
* [[User:Fab/Personal_aports_repo|Personal aport repo]]
* [[User:Fab/Stats|Stats]]
* [[User:Fab/Cleanup|Cleanup]]
* [[User:Fab/msg.alpinelinux.org|msg.alpinelinux.org]]
* [[User:Fab/Notifications|Notifications]]

=== Configuration management ===

* [[User:Fab/Ansible|Ansible]]
* [[User:Fab/Bcfg2|Bcfg2]]
* [[User:Fab/Salt|Salt]]

=== Other docs ===
* [[User:Fab/Nodejs|Node.js]]
* [[User:Fab/Ocr|OCR]]
* [[User:Fab/Tryton|Tryton]]
* [[User:Fab/Metasploit|Metasploit]]
* [[User:Fab/Beeswarm|Beeswarm]]

APKBUILD examples:Python

2017-11-17T14:48:00Z

Fab: add check()

A lot of Python packages use the ''setuptools'' or ''distutils'' framework. This mean that the build() and the package() section looks a bit different compared to an application which uses ''make''.

== Considerations ==

=== Python 2 vs. Python 3 ===

Python 3 should be the default option.
If the project support both Python 2 and Python 3, then the Alpine package may provide both variants as ''py2-'' and ''py3-'' subpackages.
You may omit ''py2'' variant, but never omit ''py3'' variant if it's supported by the project.

=== pkgname ===

Package name for a Python ''library'' must be prefixed with ''py-'', ''py2-'', or ''py3-''.

; py- : Use if the project supports both Python 2 and Python 3, even if it does not support Python 3 yet, but may in future.
; py2- : TODO
; py3- : Use if the project does not support Python 2.

There’s no exact rule if the prefix should be used for tools and applications written in Python, it varies.

=== arch ===

; noarch : Use for pure Python packages (i.e. without compiled code). Also add python2, or python3 to <tt>depends=</tt>.
; all (and others) : Use for packages with native extensions (i.e. with compiled code). '''Do not''' add python2/python3 to <tt>depends=</tt> (it's auto-detected via dynamic linking to python library).

=== source ===

Basically all Python are published in [https://pypi.python.org/pypi PyPI] (the Python Package Index).
If the package has a source tarball available in PyPI (that’s true for most packages), you should reference it in <tt>source=</tt> as:

<pre>
https://files.pythonhosted.org/packages/source/${_pkgname:0:1}/$_pkgname/$_pkgname-$pkgver.tar.gz
</pre>

where <tt>_pkgname</tt> is a real name of the Python package.

== Examples ==

Comments marked with <tt>##</tt> should not be copied into final APKBUILD!

=== Package for single Python version ===

If the project supports only Python 3 (or 2), then the APKBUILD is very simple:

<pre>
pkgname="py3-foo"
_pkgname="foo"
...
depends="python3"
makedepends="python3-dev"
...

build() {
cd "$builddir"
python3 setup.py build
}

check() {
cd "$builddir"
python3 setup.py test
}

package() {
cd "$builddir"
python3 setup.py install --prefix=/usr --root="$pkgdir"
}
</pre>

=== Multiversion package without executables ===

Use this variant if the package does not install any files outside of <tt>/usr/lib/pythonX.Y/site-packages</tt>.
If the build modifies source code, e.g. using 2to3, read the last section!

<pre>
pkgname="py-foo"
_pkgname="PyFoo"
...
depends="py-bar py-baz"
makedepends="python2-dev python3-dev py-setuptools"
subpackages="py2-${pkgname#py-}:_py2 py3-${pkgname#py-}:_py3"
...

build() {
cd "$builddir"
python2 setup.py build
python3 setup.py build
}

check() {
cd "$builddir"
python2 setup.py test
python3 setup.py test
}

package() {
mkdir -p "$pkgdir"
}

_py2() {
replaces="$pkgname"
depends="${depends//py-/py2-}" ## remove if there are no common Python dependencies
_py python2
}

_py3() {
depends="${depends//py-/py3-}" ## remove if there are no common Python dependencies
_py python3
}

_py() {
local python="$1"
pkgdesc="$pkgdesc (for $python)"
depends="$depends $python" ## remove if arch isn't noarch
install_if="$pkgname=$pkgver-r$pkgrel $python"

cd "$builddir"
$python setup.py install --prefix=/usr --root="$subpkgdir"
}
</pre>

=== Multiversion package with executables ===

Use this variant if the packages installs some executables into <tt>/usr/bin</tt>.
If the build modifies source code, e.g. using 2to3, read the last section!

'''Note:''' This is just mere workaround that will not be needed in future once we add needed features to apk.

<pre>
pkgname="py-foo"
_pkgname="PyFoo"
...
depends="py-bar py-baz"
makedepends="python2-dev python3-dev py-setuptools"
subpackages="py2-${pkgname#py-}:_py2 py3-${pkgname#py-}:_py3"
...

build() {
cd "$builddir"
python2 setup.py build
python3 setup.py build
}

package() {
mkdir -p "$pkgdir"/usr/bin

# Create unsuffixed symlinks for executables from py3 subpackage.
local name; for name in foo bar baz; do
ln -s $name-3 "$pkgdir"/usr/bin/$name
done
}

_py2() {
replaces="$pkgname"
depends="${depends//py-/py2-}" ## remove if there are no common Python dependencies
_py python2
}

_py3() {
depends="${depends//py-/py3-}" ## remove if there are no common Python dependencies
_py python3
}

_py() {
local python="$1"
local pyver="${1:6:1}"
pkgdesc="$pkgdesc (for $python)"
depends="$depends $python" ## remove if arch isn't noarch
install_if="$pkgname=$pkgver-r$pkgrel $python"

cd "$builddir"
$python setup.py install --prefix=/usr --root="$subpkgdir"

# Add version suffix to executable files.
local path; for path in "$subpkgdir"/usr/bin/*; do
mv "$path" "$path-$pyver"
done
}
</pre>

=== Multiversion package for project using 2to3 ===

Some Python projects use 2to3 (or similar tools) during build phase to make the code-base compatible with Python 3.
Since it modifies sources during build, you cannot run <tt>setup.py build</tt> with python2 and python3 one after another with the same source files.
You must duplicate the buildir and run them separately.

<pre>
prepare() {
default_prepare

# Soure files are modified during build with 2to3 tool, so we cannot
# build it for both Python versions in the same location.
local python; for python in python2 python3; do
cp -r "$builddir" "$builddir-$python"
done
}

build() {
local python; for python in python2 python3; do
cd "$builddir"-$python
$python setup.py build
done
}

_py() {
...

cd "$builddir"-$python
$python setup.py install --prefix=/usr --root="$subpkgdir"
}
</pre>

[[Category:Development]] [[Category:Python]]

Alpine Linux:Trivia

2017-05-31T07:09:12Z

Fab: /* Packages per release */ new graph

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* [https://www.ohloh.net/p/aports aports] statistics provided by Ohloh.

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.6'''
| 5548
| 3510
| 681
| 1271
| 86
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201705-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 9065
2017 : 4901 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
26715 Natanael Copa
2938 Francesco Colista
2477 Carlo Landmeter
2369 Timo Teräs
2312 Leonardo Arena
1971 Fabian Affolter
1571 William Pitcock
1350 Jakub Jirutka
1349 Bartłomiej Piotrowski
1037 Sören Tempel
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

File:201705-aports.png

2017-05-31T07:08:24Z

Fab:

Alpine Linux:Trivia

2017-05-31T07:05:52Z

Fab: /* Packages per release */ update

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* [https://www.ohloh.net/p/aports aports] statistics provided by Ohloh.

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.6'''
| 5548
| 3510
| 681
| 1271
| 86
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201612-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 9065
2017 : 4901 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
26715 Natanael Copa
2938 Francesco Colista
2477 Carlo Landmeter
2369 Timo Teräs
2312 Leonardo Arena
1971 Fabian Affolter
1571 William Pitcock
1350 Jakub Jirutka
1349 Bartłomiej Piotrowski
1037 Sören Tempel
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

Alpine Linux:Trivia

2017-05-31T07:03:03Z

Fab: /* Commit per year to aports */ update

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* [https://www.ohloh.net/p/aports aports] statistics provided by Ohloh.

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201612-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 9065
2017 : 4901 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
26715 Natanael Copa
2938 Francesco Colista
2477 Carlo Landmeter
2369 Timo Teräs
2312 Leonardo Arena
1971 Fabian Affolter
1571 William Pitcock
1350 Jakub Jirutka
1349 Bartłomiej Piotrowski
1037 Sören Tempel
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

Alpine Linux:Trivia

2017-05-31T07:01:56Z

Fab: /* "High score list" of committer to aports */ update

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* [https://www.ohloh.net/p/aports aports] statistics provided by Ohloh.

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201612-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 1383 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
26715 Natanael Copa
2938 Francesco Colista
2477 Carlo Landmeter
2369 Timo Teräs
2312 Leonardo Arena
1971 Fabian Affolter
1571 William Pitcock
1350 Jakub Jirutka
1349 Bartłomiej Piotrowski
1037 Sören Tempel
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

APKBUILD examples:Simple

2017-05-31T06:57:59Z

Fab: add builddir

Simple APKBUILD with -doc subpackage, using abuild's default ''doc()'' and ''prepare()'' functions:
<pre>
# Contributor: William Pitcock <nenolod@dereferenced.org>
# Maintainer:
pkgname=gnuplot
pkgver=4.4.4
pkgrel=0
pkgdesc="Utility for plotting graphs"
url="http://www.gnuplot.info/"
arch="all"
license="GPL"
depends=""
depends_dev="cairo-dev pango-dev gd-dev lua-dev readline-dev libpng-dev jpeg-dev"
makedepends="$depends_dev"
install=""
subpackages="$pkgname-doc"
source="http://downloads.sourceforge.net/project/$pkgname/$pkgname/$pkgver/$pkgname-$pkgver.tar.gz"
builddir="$srcdir/$pkgname-$pkgver"

prepare() {
default_prepare || return
}

build() {
cd "$builddir"
./configure --prefix=/usr \
--sysconfdir=/etc \
--mandir=/usr/share/man \
--infodir=/usr/share/info \
--localstatedir=/var \
--disable-wxwidgets \
--disable-qt || return 1
make || return 1
}

check() {
cd "$builddir"
make check || return 1
}

package() {
cd "$builddir"
make DESTDIR="$pkgdir" install || return 1
}

sha512sums="d65a43b834b1926097...c0b8c6017ffc6d9e011217fb7e86e80 gnuplot-4.4.4.tar.gz"
</pre>

[[Category:Development]]

APKBUILD examples:Simple

2017-05-31T06:23:23Z

Fab: update

Simple APKBUILD with -doc subpackage, using abuild's default ''doc()'' and ''prepare()'' functions:
<pre>
# Contributor: William Pitcock <nenolod@dereferenced.org>
# Maintainer:
pkgname=gnuplot
pkgver=4.4.4
pkgrel=0
pkgdesc="Utility for plotting graphs"
url="http://www.gnuplot.info/"
arch="all"
license="GPL"
depends=""
depends_dev="cairo-dev pango-dev gd-dev lua-dev readline-dev libpng-dev jpeg-dev"
makedepends="$depends_dev"
install=""
subpackages="$pkgname-doc"
source="http://downloads.sourceforge.net/project/$pkgname/$pkgname/$pkgver/$pkgname-$pkgver.tar.gz"
builddir="$srcdir/$pkgname-$pkgver"

prepare() {
default_prepare || return
}

build() {
cd "$builddir"
./configure --prefix=/usr \
--sysconfdir=/etc \
--mandir=/usr/share/man \
--infodir=/usr/share/info \
--localstatedir=/var \
--disable-wxwidgets \
--disable-qt || return 1
make || return 1
}

check() {
make check || return 1
}

package() {
cd "$builddir"
make DESTDIR="$pkgdir" install || return 1
}

sha512sums="d65a43b834b1926097...c0b8c6017ffc6d9e011217fb7e86e80 gnuplot-4.4.4.tar.gz"
</pre>

[[Category:Development]]

APKBUILD Reference

2017-05-29T06:33:51Z

Fab: /* User-defined functions */ for copy-&-paste

APKBUILDs are the scripts that are created in order to build Alpine packages using the [[abuild]] tool.

See [[aports]] for details on Alpine's official ports repository.

This page is intended to serve as a reference for creating APKBUILDs; if this is your first time creating a package for Alpine Linux, please see [[Creating an Alpine package]].

= Legend =
The following notes will assist you in understanding this document.

In description text:
* If a variable is not prefixed with a ''$'', it will be represented by italics (i.e., ''srcdir'' ).
* Functions will also be represented by italics, but will also end with a pair of parentheses (i.e., ''build()'' ).
* Shell commands will be represented <code>like this</code>.

= Variables =
{{Note|Variables that contain a path (e.g. ''$srcdir'' and ''$pkgdir'') should always be quoted using double quotes (i.e., ''"$srcdir"''). This is done to prevent things from breaking, should the user have the APKBUILD in a directory path that contains spaces.}}
{{Note|All arbitrary variable and function names should be prefixed with an underscore character ( _ ) to avoid name clashes with the internals of abuild (for example, ''_luaversions'').}}

== abuild-defined variables ==
The following variables are defined by abuild:

==== startdir ====
: The directory where the APKBUILD script is.
==== srcdir ====
: The directory where sources, from the ''source'' variable, are downloaded to and unpacked to.
==== pkgdir ====
: This directory should receive the files for the main package. For example, a normal [http://en.wikipedia.org/wiki/GNU_build_system autotools] package would have <code>make DESTDIR="$pkgdir" install</code> in the ''package()'' function.
==== subpkgdir ====
: This directory should receive the files for a subpackage. This variable should only be used from subpackage functions.
==== builddir ====
: This variable should point to the directory inside the ''srcdir'' where the main package source is unpacked. This is typically ''$srcdir/$pkgname-$pkgver''. It’s used by the default ''prepare()'' function as a working directory when applying patches.

== User-defined variables ==
The following variables should be defined by the user:
==== arch ====
: Package architecture(s) to build for. Can be one of: '''[[x86]], [[x86_64]], [[armhf]], [[aarch64]], [[ppc64le]], [[s390x]], all''', or '''noarch''', where '''all''' means all architectures, and '''noarch''' means it's architecture-independent (e.g., a pure-python package).
: {{Tip|To determine if your APKBUILD can use '''noarch''': First specify '''all''' and then build the package by executing <code>abuild -r</code>. Watch the output towards the end for warnings saying that '''noarch''' can be used. If the main package and all subpackages, if you have any subpackages, give a warning saying that '''noarch''' can be used, then you can use '''noarch'''.}}

==== depends ====
: Run-time dependency package(s) that are not shared-object dependencies. Shared objects dependencies are auto-detected and should not be specified here.
==== depends_dev ====
: Run-time dependency package(s) for the '''$pkgname-dev''' subpackage.

: {{Note|From ncopa on IRC: To find out if you need to add a package to depends_dev have a look at *requires* in usr/lib/pkgconfig/*.pc. With libtool it gets more complicated, but we should delete the .la files. Also check if there are any /usr/bin/*-configure #!/bin/bash #!/usr/bin/perl or Python. Sometimes scripts or similar are generated at build time (i.e autoconf automake) then you normally don't need add those to depends_dev. You can also just add all -dev makedepends to depends_dev but it will slow the build process a little bit (more build dependencies).}}
==== giturl ====
:Git repository from which <code>abuild checkout</code> checks out. You can checkout a specific branch in git by adding <code>-b $branch</code>.
==== install ====
: There are 6 different types of install scripts. Install scripts are named '''$pkgname.action''', where '''action''' can be: '''pre-install, post-install, pre-upgrade, post-upgrade, pre-deinstall''', or '''post-deinstall'''. For example, if ''pkgname'' is set to '''mypackage''' and ''install'' is set to '''$pkgname.post-install''', then a script named '''mypackage.post-install''' must exist along-side the APKBUILD.

: First, a few notes regarding install scripts:
<blockquote>{{Note|When using install scripts, ''$install'' should be included in ''source'' so that checksums can be generated and used for the install scripts specified in ''install''. For example:
<pre>
install="$pkgname.pre-install $pkgname.post-install"
source="http://....
$install"
</pre>}}
{{Note|Always use <code>/bin/sh</code> for the command-line interpreter on the [http://en.wikipedia.org/wiki/Shebang_%28Unix%29 shebang line] of your install scripts.}}</blockquote>

The following are the different types of install scripts in detail:

===== $pkgname.pre-install =====
: This script is executed ''before installing'' the package. Typical use is when the package needs a group and a user to be created. For example:
<blockquote><pre>
#!/bin/sh

addgroup -S clamav 2>/dev/null
adduser -S -D -H -s /bin/false -G clamav -g clamav clamav 2>/dev/null

exit 0
</pre>
{{Note|If the script exits with a failure (e.g., if the user already exists), the package will not be installed and <code>apk</code> will exit with failure, hence the <code>exit 0</code> at the end.}}</blockquote>

===== $pkgname.post-install =====
: This script is executed ''after installing'' the package.

===== $pkgname.pre-upgrade =====
: This script is executed ''before upgrading/downgrading/reinstalling'' the package. Note that exiting with failure will not cause apk to exit with failure, but will mark the package as broken.

===== $pkgname.post-upgrade =====
: This script is executed ''after upgrading/downgrading/reinstalling'' the package.

===== $pkgname.pre-deinstall =====
: This script is executed ''before uninstalling'' the package.
: {{Note|If the script exits with failure, <code>apk</code> will not uninstall the package.}}

===== $pkgname.post-deinstall =====
: This script is executed ''after uninstalling'' the package.

==== install_if ====
:install_if can be used when a package needs to be installed when some packages are already installed or are in the dependency tree. As example we could take open-vm-tools. Currently it contains the userspace tools and separate packages for the kernel modules (grsec and vserver). When we install the userspace tools, apk should automatically install the correct kernel modules and will need to figure out for which kernel. This is where install_if jumps in. For any of the kernel modules package we would use:

:<pre>install_if="linux-${_flavor}=${_kernelver} open-vm-tools"</pre>

:This will automatically install the package when the specified packages are installed or are in dependency tree.

==== license ====
: License(s) for the package.
==== makedepends ====
: Build-time dependency package(s).
==== md5sums ====
: Checksums for the files/URLs listed in ''source''. The checksums are normally generated and updated by executing <code>abuild checksum</code> and should be the last item in the APKBUILD.
==== options ====
: Build-time options for the package. Can be: '''!strip''' - to avoid stripping symbols from binaries.
==== pkgdesc ====
: A brief, one-line description of what the package does.

: Here's an example from the OpenSSH client package:
: <pre>pkgdesc="Port of OpenBSD's free SSH release - client"</pre>
==== pkggroups ====
: System group(s) to be created during build-time. System group(s) should also be created in the '''[[APKBUILD Reference#.24pkgname.pre-install|$pkgname.pre-install]]''' script, so that the system group(s) are also created prior to package installation for run-time use.
==== pkgname ====
: The name of the package. All letters should be lowercase.
: {{Note|When creating an APKBUILD of a module or library for another package, we use some common package prefixes, such as: ''lua-'', ''perl-'', ''php-'', and ''py-''. Search aports for other common prefixes.}}

==== pkgrel ====
: Alpine package release number. Starts at 0 (zero). Always increment ''pkgrel'' when making updates to an aport; reset ''pkgrel'' to 0 (zero) when incrementing ''pkgver''.
==== pkgusers ====
: System user(s) to be created during build-time. System user(s) should also be created in the '''[[APKBUILD Reference#.24pkgname.pre-install|$pkgname.pre-install]]''' script, so that the system user(s) are also created prior to package installation for run-time use.
==== pkgver ====
: The version of the software being packaged.
==== provides ====
: List of package names (and optionally version info) this package provides.

: If package with a version is provided (provides='foo=1.2') apk will consider it as an alternate name and it will automatically consider the package for installation by the alternate name, and conflict with other packages having the same name, or provides.

: If version is not provided (provides='foo'), apk will consider it as virtual package name. Several package with same non-versioned provides can be installed simultaneously. However, none of them will be installed by default when requested by the virtual name - instead, error message is given and user is asked to choose which package providing the virtual name should be installed.
==== replaces ====
: Package(s) that this package replaces. This package will "take over" files owned by packages listed in the ''replaces'' variable. This is useful when files move from one package to another, or when a package gets renamed.
==== replaces_priority ====
: The priority of the replaces. If multiple packages replace each other, then will the package with highest ''replaces_priority'' win.
==== source ====
: The source variable is not only used to list the remote source files to fetch, it is also used to list the local files that abuild will need in order to build the apk. Examples of such local files include: init.d files, conf.d files, install files (see [[APKBUILD Reference#install|install variable]]), patches, and all other necessary files.

: Here are few things to note:

:* When you are finished adding local and/or remote files to ''source'', you can execute the following command to add their checksums to the APKBUILD file:
:: {{Cmd|abuild checksum}}
:: {{Note|When later updating the content of ''source'', or updating a file that is listed in ''source'', you must also update their checksums again with the same command.}}

:* When the remote file is hosted at SourceForge, it's best to specify the special mirrors link used by SourceForge:
:: <pre>http://downloads.sourceforge.net/$pkgname/$pkgname-$pkgver.tar.gz</pre>
:: (or similar depending on the package).

:* You can set target filename (eg 'save as...') by prefixing the URI with ''filename::''. This is useful when the remote filename is not specified in the URI (ie, does not end in '/software-1.0.tar.gz'), such as:
:: <pre>http://oss.example.org/?get=software&ver=1.0</pre>
:: or when the filename is braindead, like githubs' download tags:
:: <pre>https://github.com/software/software/archive/v$pkgver.tar.gz</pre>
:: The above two examples needs a target filename prefix:
:: <pre>$pkgname-$pkgver.tar.gz::http://oss.example.org/?get=software&ver=$pkgver</pre>
:: and:
:: <pre>$pkgname-$pkgver.tar.gz::https://github.com/software/software/archive/v$pkgver.tar.gz</pre>

:* abuild currently supports the following protocols for remote file retrieval:
:** http
:** https
:** ftp

:* abuild currently supports the following archive types/archive file extensions:
:** .tar.gz / .tgz
:** .tar.bz2
:** .tar.lzma
:** .tar.xz
:** .zip

:: {{Note|Legacy APKBUILD scripts define ''source'' variable as "saveas-[brain-dead-url]/[target-filename]" format instead of the modern [target-filename]::[brain-dead-url]. ''BAD'': source="saveas-http://releases.ddvtech.com/download.php?pack=libmist_dist&ver=RC/$pkgname-$pkgver.tar.gz" ''GOOD'': source=$pkgname-$pkgver.tar.gz::http://releases.ddvtech.com/download.php?pack=libmist_dist&ver=RC"}}

==== subpackages ====
: Subpackages built from this APKBUILD. abuild will parse this variable and try to find a subpackage split function. The split function must ''move'' files that do not belong in the main package, from ''$pkgdir'' to ''$subpkgdir''. Files and directories can also be ''copied'' from ''$startdir'' and ''$srcdir'' to ''$subpkgdir''.

: The split function can be specified in 1 of 3 different methods:
:# subpkgname:'''splitfunc'''
:# $pkgname-'''splitfunc'''
:# '''splitfunc'''

: {{Note|Split function names '''cannot''' use hyphens; use the first method above if the subpackage name contains a hyphen (-) character, like this: ''subpkg-name:subpkg_name'', where <code>subpkg-name</code> is the name of the '''subpackage''' and <code>subpkg_name</code> is the name of the '''subpackage's split function'''.}}

: {{Tip|For more information, see the [[APKBUILD_examples:Subpackages|Subpackages example]].}}

==== triggers ====
: Apk-tools can "monitor" directories and execute a trigger if any package installed/uninstalled any file in the monitored dir. The triggers are always execute after the apk action (install, uninstall, upgrade).

: The triggers are specified in the format: ''scriptname''=''pathlist'' where ''scriptname'' is the (sub)package name + .trigger suffix and pathlist is : separated list of the dirs to monitor.

: The '''triggers''' variable must include the triggers for subpackages too if they have any.

: It is possible to use wildcards (*) in the dir list.

==== url ====
: The homepage for the package. This is to help users find upstream documentation and other information regarding the package.

= Functions =
{{Note|All functions should consider the current working directory as undefined, and should therefore use the [[APKBUILD Reference#abuild-defined_variables|abuild-defined directory variables]] to their advantage.}}

== abuild-defined functions ==
The following functions are provided by abuild and can be overridden:

==== fetch() ====
: Downloads remote sources listed in ''source'' to ''SRCDEST'' (''SRCDEST'' is configured in ''/etc/abuild.conf'') and creates symlinks in ''$srcdir''.
==== unpack() ====
: Unpacks .tgz, .tar.gz, .tar.bz2, .tar.lzma, .tar.xz, and .zip archives in ''$srcdir'' to ''$srcdir''.
==== dev() ====
: Subpackage function for the '''$pkgname-dev''' package. Without specifying a custom ''dev()'' function, abuild will call it's internal ''dev()'' function, which in turn calls ''default_dev()'', which will move ''"$pkgdir"/usr/include'', ''*.a'', ''*.la'' and similar files to ''$subpkgdir''.
==== doc() ====
: Subpackage function for the '''$pkgname-doc''' package. Without specifying a custom ''doc()'' function, abuild will call it's internal ''doc()'' function, which in turn calls ''default_doc()'', which will move ''"$pkgdir"/usr/share/doc'', ''"$pkgdir"/usr/share/man'' and similar to ''$subpkgdir''.

== User-defined functions ==
The following functions should be defined by the user:

==== prepare() ====
: '''''Optional''.''' Used for build preparation: patches, etc, should be applied here. This function is available for your convenience. It is better to use "default_prepare || return" to handle *.patch file, and the patch file should always be prepared as -p1 format.
==== build() ====
: '''Required.''' This is the compilation stage. This function will be called as the current user (unless the ''package()'' function is missing - for compatibility reasons). If no compilation is needed, this function can contain a single line: <code>return 0</code>
==== check() ====
: '''Recommended.''' This function is called right after the build stage. It should check that the packaged thing is actually working, typically by running (integration) tests, if provided by upstream. If there’s no (easy) way how to test the package, you can declare that it does not want to use ''check()'' by adding "!check" into the ''options'' variable (<code>options="!check"</code>).
==== package() ====
: '''Required.''' This is the packaging stage. Here, the built application and support files should be installed into '''$pkgdir'''. If this is a metapackage, this function can contain a single line: <code>mkdir -p "$pkgdir"</code>

{{Note|Building in fakeroot will reduce performance for parallel builds dramatically. It is for this reason that we split the build and package process into two separate functions.}}

= Examples =
The [[APKBUILD examples]] page will assist you in understanding how to create an APKBUILD.

[[Category:Development]]

Alpine Linux:Trivia

2017-01-04T14:30:33Z

Fab: /* Packages per release */ update graph

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* [https://www.ohloh.net/p/aports aports] statistics provided by Ohloh.

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201612-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 1383 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
22872 Natanael Copa
1873 Carlo Landmeter
1804 Timo Teräs
1725 Fabian Affolter
1637 Leonardo Arena
1317 William Pitcock
1230 Bartłomiej Piotrowski
1105 Francesco Colista
686 Ted Trask
562 Sören Tempel
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

File:201612-aports.png

2017-01-04T14:30:02Z

Fab:

Alpine Linux:Trivia

2017-01-04T14:24:27Z

Fab: update for 3.5

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* [https://www.ohloh.net/p/aports aports] statistics provided by Ohloh.

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.5'''
| 5643
| 3615
| 678
| 1264
| 86
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201608-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 1383 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
22872 Natanael Copa
1873 Carlo Landmeter
1804 Timo Teräs
1725 Fabian Affolter
1637 Leonardo Arena
1317 William Pitcock
1230 Bartłomiej Piotrowski
1105 Francesco Colista
686 Ted Trask
562 Sören Tempel
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

Development using git:Developer repositories

2016-11-06T14:02:38Z

Fab: Add tld

__TOC__
__FORCETOC__

Some git repositories of Alpine developer are hosted at [http://git.alpinelinux.org/ git.alpinelinux.org]. Developers who has no push access to the offical aports repo can has a developer aports repo that can be used as a staging area. Developers with push access, ''integration managers'', can review and pull from this or can choose to reject if the changes needs more fixing.

The git repos are to be used when there are many changes (more than 3) that need no or very little review. If comments are requested or if there are doubts, then its better to use ''git send-email''. It might also be better to use ''git send-email'' for single commits.

== Git Push (Distributed Workflows) ==
When working with [http://book.git-scm.com/3_distributed_workflows.html Distributed Workflows] you would 'pull' from public repository, 'push' to another publically accessible repository ''(where you have write access)'', main developeres or ''integration managers'' who have write access to public repository, 'pulls' you changes from your public accessed repository into the blessed official public repository.

To make it easier for you to work, you can configure 'git push' to push your work to your public developer repository ('git pull' would still pull from the blessed/official repository as you cloned from).
{{cmd|cd /your/private/repo/where/you/work/reponame
git config remote.origin.pushurl "ssh://user@dev.alpinelinux.org/home/user/cgit/reponame.git"}}
Now 'git pull' pulls the official, blessed, repository and 'git push' pushes to '''your''' public developer repository.
{{Note|The path where you want to push to should first be prepared with {{cmd|git clone --bare ...}} as described below in section 'Upload the new project'}}

== Requesting a pull from developer repo to official ==
Before asking for merging the developer repo into the official make sure that:
# All modified packages builds
# The commit history looks nice. You can use the [http://git.alpinelinux.org/cgit cgit interface] for this. It is a goal that it should be easy to revert single commits in case problems should appear in future so avoid changing multiple packages with single commits.

Before asking for a pull, rebase your public repo with the official repo. This is done with:
{{Cmd|git pull --rebase
git push}}

If there have been changes in official repo that conflicts with your work, then you have to resolve those conflicts. And maybe redo or drop some of your commits.

You can ask directly on IRC #alpine-devel or by sending an email to alpine-devel mailing list. Please include the git url (eg. git://git.alpinelinux.org/user/aports.git) that can easily be copied and pasted and please also mention ''why'' the merge is needed. This explanation is meant to be copied and pasted in the merge commit unless the pull is a fast-forward.

Example request on IRC:
<pre>
please git pull git://git.alpinelinux.org/ncopa/aports
It includes a new python application pyfoo with all its dependencies.
</pre>

Example email:
<pre>
Subject: please git pull git://git.alpinelinux.org/ncopa/aports

The libfoo was upgraded to 2.0. This upgrade breaks ABI so all packages linking
to libfoo was rebuilt. The rebuilt packages was:
- libbar
- bazapp
- bar-utils

</pre>

== Dealing with pull rejects ==
If the pull was rejected for some reason or you need change things, then you can do an interactive reabase.
{{Cmd|git rebase --interactive}}
This will let you go thru all you commits inteactively, fix up commits and/or commit messages (aka --ammend), merge commits etc. It might be the ''integration manager'' will see what you are trying to fix and just fix it there and then. In that case you might need drop your own commit. This can also be done with ''git rebase''.

When the needed changes have been done you again push to your public developer repo (and as always you ''git pull --rebase'' before pushing), but since the history have changed due to the rebase git might give you an error message when pushing. As long no-one else have cloned/pulled your repo, it should safe to use --force option.
{{Cmd|git push --force}}
Note that this will overwrite the changes and history on your public repo so make sure that your local work clone has all the commits that should be there. (use git log to verify).

This also means that only the ''integration managers'' should pull from the developers repo. All other developers should pull from the blessed repository. (In theory multiple developers can work on a bigger subproject but then one of the developers should work as a ''lieutenant'' in the [http://git-scm.com/book/ch5-1.html#Dictator-and-Lieutenants-Workflow dictator and lieutenants workflow].)

[[Category:Development]]
[[Category:Git]]

Alpine Linux:Trivia

2016-08-29T10:32:21Z

Fab: update graph

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* [https://www.ohloh.net/p/aports aports] statistics provided by Ohloh.

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201608-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 1383 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
22872 Natanael Copa
1873 Carlo Landmeter
1804 Timo Teräs
1725 Fabian Affolter
1637 Leonardo Arena
1317 William Pitcock
1230 Bartłomiej Piotrowski
1105 Francesco Colista
686 Ted Trask
562 Sören Tempel
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

File:201608-aports.png

2016-08-29T10:30:06Z

Fab:

Alpine Linux:Trivia

2016-08-29T10:25:28Z

Fab: add 3.4

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* [https://www.ohloh.net/p/aports aports] statistics provided by Ohloh.

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.4'''
| 5231
| 3253
| 664
| 1235
| 79
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201501-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 1383 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
22872 Natanael Copa
1873 Carlo Landmeter
1804 Timo Teräs
1725 Fabian Affolter
1637 Leonardo Arena
1317 William Pitcock
1230 Bartłomiej Piotrowski
1105 Francesco Colista
686 Ted Trask
562 Sören Tempel
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

User:Fab

2016-08-29T09:44:39Z

Fab: update

My Name is Fabian Affolter and I'm living in Berne/Switzerland. One of my passions is free software and open source. I'm a long time contributor to various free and open source software projects. A big bunch of my spare time is spent on the [https://fedoraproject.org Fedora Project] and [http://bcfg2.org Bcfg2].

By the way, my first system was a Amiga 2000 but this is a long long time ago ;-).

My area of interest are computer aided design (CAD), computer algebra system (CAS), provisioning, automatic configuration management, version control systems, software packaging, and microcontrollers.

Apart from spending time at the computer, I like to read, to listen to music, and to hike in the Swiss mountains.

== more personal stuff ==

* ''' Location''': [http://en.wikipedia.org/wiki/Berne Berne] [http://de.wikipedia.org/wiki/Bern Bern], [http://en.wikipedia.org/wiki/Switzerland Switzerland] [http://de.wikipedia.org/wiki/Schweiz Schweiz]
* ''' Time zone''' : UTC +01:00 (CET) or UTC +02:00 (CEST)
* ''' Languages''' : German (it's more Swiss German), English, and French
* ''' Profession''' : Senior Engineer, B.Sc. [http://www.ti.bfh.ch/en/bachelor/mechanical.html ME] and [http://www.ti.bfh.ch/en/bachelor/computer_science.html CS] [http://www.ti.bfh.ch/ Berne University of Applied Sciences] - Engineering and Information Technology

== Contact ==

* '''Postal address''' :
::ask for the street
::CH-3000 Berne
::Switzerland
* '''Blog''' : [http://blog.fabian-affolter.ch/ My blog] (be aware...some parts are in german)
* '''Websites''': [http://fabian-affolter.ch/ fabian-affolter.ch]
* '''Email''': [mailto:fabian%affolter-engineering%2ench fabian AT affolter-engineering DOT ch]
* '''GPG/PGP''' : [http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x36A4397F 0x36A4397F]
* '''Jabber''' : fab AT swissjabber DOT org
* '''IRC''' : faffolter (or fabian_a) on FreeNode

== Misc ==
* [[Alpine_Security_and_Rescue|Alpine Security Flavor]]
* [[User:Fab/Personal_aports_repo|Personal aport repo]]
* [[User:Fab/Stats|Stats]]
* [[User:Fab/Cleanup|Cleanup]]
* [[User:Fab/msg.alpinelinux.org|msg.alpinelinux.org]]
* [[User:Fab/Notifications|Notifications]]

=== Configuration management ===

* [[User:Fab/Ansible|Ansible]]
* [[User:Fab/Bcfg2|Bcfg2]]
* [[User:Fab/Salt|Salt]]

=== Other docs ===
* [[User:Fab/Nodejs|Node.js]]
* [[User:Fab/Ocr|OCR]]
* [[User:Fab/Tryton|Tryton]]
* [[User:Fab/Metasploit|Metasploit]]
* [[User:Fab/Beeswarm|Beeswarm]]

PhpSysInfo

2016-04-29T13:39:05Z

Fab: Update to 3.2.5

[http://phpsysinfo.sourceforge.net/ phpSysInfo] is a simple application that displays information about the host it's running on.

The following stuff is shown

* Uptime
* CPU
* Memory
* SCSI, IDE, PCI
* Ethernet
* Floppy
* Video Information

== Install lighttpd and PHP ==
{{:Setting_Up_Lighttpd_With_FastCGI}}

== Installation of pypSysInfo ==

Create a directory named {{Path|webapps}}

{{Cmd|mkdir -p /usr/share/webapps/}}

Now get the current release of phpSysInfo.

{{Cmd|cd /usr/share/webapps/
wget http://downloads.sourceforge.net/project/phpsysinfo/phpsysinfo/3.2.5/phpsysinfo-3.2.5.tar.gz}}

Unpack the archive in the current location

{{Cmd|tar -xzf phpsysinfo-3.2.5.tar.gz && rm phpsysinfo-3.2.5.tar.gz}}

A {{Path|config.php}} is needed to run phpSysInfo. The fastest way is to make a copy of the template file.

{{Cmd|cp phpsysinfo/config.php.new phpsysinfo/config.php}}

Create a symlink that point to the webserver directory.

{{Cmd|ln -s /usr/share/webapps/phpsysinfo/ /var/www/localhost/htdocs/phpsysinfo}}

Change the permission of the directory.

{{Cmd|chmod -R 777 /usr/share/webapps/}}

Restart lighttpd

{{Cmd|/etc/init.d/lighttpd restart}}

Now the page is up and running

http://IP-ADDRESS/phpsysinfo

[[Category:Monitoring]] [[Category:PHP]]

User:Fab/Stats

2016-03-30T10:50:13Z

Fab: update

Some ideas to gether data for statistics about Alpine Linux.

The data are presented at the [[Alpine_Linux:Trivia|Trivia]] page. A git repository is available [http://git.alpinelinux.org/cgit/fab/alpine-stats/ here].

= Packages =

== Ancient releases ==

See: http://ancient.alpinelinux.org/alpine/

* Grab INDEX.md5.gz (e.g. http://ancient.alpinelinux.org/alpine/v1.1/apks/INDEX.md5.gz)
* Count the entries
* Print the number of packages

== Newer releases ==

* Grab APKINDEX.tar.gz (e.g. http://nl.alpinelinux.org/alpine/v2.4/main/x86/APKINDEX.tar.gz)
* Count the lines which starts with P: (e.g. P:libxinerama-dev, P:postfix) in APKINDEX
* Perhaps separate packages (-dev, -doc, -lang)
* Print the data

== "High score list" of committer ==

{{Cmd|git shortlog -s -n | head}}

== Commit per year ==
To grab the data use the command below:

{{Cmd|<nowiki>git log --after="2016/1/1" --until="2016/12/31" --pretty=format:'' | wc -l</nowiki>}}

= Tools =
Some tools which could help to generate statistics.

* [http://gitstats.sourceforge.net/ GitStats] - git history statistics generator
{{Cmd|apk add gitstats -U -X http://dl-3.alpinelinux.org/alpine/edge/testing/ --allow-untrusted}}

Alpine Linux:Trivia

2016-03-22T07:32:02Z

Fab: update

This page contains only irrelevant and unhelpful information and statistics about Alpine Linux. If you are going to prepare a talk about Alpine Linux, perhaps some information mentioned here can be used for the intro.

= The first release =
* Archives going back to 1.1 are (currently) at http://ancient.alpinelinux.org
* First public mention of "Alpine Linux" is archived here: http://comments.gmane.org/gmane.linux.leaf.devel/1183 (2005)
* The first saved [[Release_Notes_for_Alpine_1.7.3|release notes]] were made for 1.7.3.

= The name =
"Alpine" originally stood for '''A''' '''L'''inux '''P'''owered '''I'''ntegrated '''N'''etwork '''E'''ngine. The idea was that the distribution would be focused on networking, and be a tiny "engine" or framework, which larger systems could be built upon. Today, "Alpine" is nothing more than a name.

= Who is working on Alpine Linux? =

* Check the statistics of cgit, e. g. [http://git.alpinelinux.org/cgit/aports/stats/?period=y&ofs=50 aports]

= Packages =

* [https://www.ohloh.net/p/aports aports] statistics provided by Ohloh.

== Packages per release ==

{| cellpadding="5" border="1" class="wikitable"
|-
! Release
! Total
! normal
! dev
! doc
! libs
|-
| '''3.3'''
| 5314
| 3328
| 676
| 1239
| 71
|-
| '''3.2'''
| 5277
| 3343
| 684
| 1189
| 61
|-
| '''3.1'''
| 4860
| 3075
| 620
| 1109
| 56
|-
| '''3.0'''
| 4410
| 2752
| 578
| 1029
| 51
|-
| '''2.7'''
| 4205
| 2605
| 570
| 982
| 48
|-
| '''2.6'''
| 3918
| 2405
| 534
| 943
| 36
|-
| '''2.5'''
| 3676
| 2233
| 498
| 912
| 33
|-
| '''2.4'''
| 3376
| 2021
| 457
| 874
| 24
|-

| '''2.3'''
| 3146
| 1866
| 435
| 827
| 18
|-
| '''2.2'''
| 2608
| 1502
| 444
| 652
| 10
|-
| '''2.1'''
| 2135
| 1222
| 365
| 547
| 1
|-
| '''2.0'''
| 1983
| 1139
| 332
| 511
| 1
|-
| '''1.10'''
| 1639
| 918
| 282
| 438
| 1
|-
| '''1.9'''
| 958
| 549
| 139
| 269
| 1
|}

[[File:201501-aports.png|center|Aports]]

== Commit per year to aports ==
<pre>
2008 : 146
2009 : 3122
2010 : 3365
2011 : 5561
2012 : 5312
2013 : 6597
2014 : 5759
2015 : 7315
2016 : 1383 (so far)
</pre>

== "High score list" of committer to aports ==

<pre>
22872 Natanael Copa
1873 Carlo Landmeter
1804 Timo Teräs
1725 Fabian Affolter
1637 Leonardo Arena
1317 William Pitcock
1230 Bartłomiej Piotrowski
1105 Francesco Colista
686 Ted Trask
562 Sören Tempel
</pre>

== First commit to aports ==
The first commit in git was made:

<pre>
commit 645531103b2ee8ef54d53a58eca3b52f7d3fb9ac
Author: Natanael Copa <ncopa@alpinelinux.org>
Date: Sat Oct 18 09:16:29 2008 +0000

added busybox
</pre>

1.9.0 package changes since 1.8.3

2016-03-07T12:31:03Z

Fab: Reverted edits by RuthHughes (talk) to last revision by Dubiousjim

= 1.9.0 Package changes since 1.8.3 =
<pre>
Removed packages:
acf-devtools-0.3.4
acf-fetch-crl-0.1.2
acf-gnats-0.3.6
acl-2.2.47
acpid-1.0.6-r1
aggregate-1.6
aggregate-flim-1.0.2
amap-5.2-r1
apcupsd-3.12.4
apg-2.3.0b-r4
arp-sk-0.0.16-r1
arpoison-0.6
asterisk-ldap-1.6.1_rc1-r1
asterisk-sounds-1.2.1
asterisk-sqlite-1.6.1_rc1-r1
atftp-0.7-r1
attr-2.4.41
audio-entropyd-1.0.1
authforce-0.9.9
barnyard-0.2.0-r1
bcm43xx-fwcutter-006
beecrypt-4.1.2-r1
bigeye-0.3-r1
bing-1.1.3
bmake-20080515
bnc-2.9.4
bonnie-2.0.6
braa-0.8-r1
btpd-0.13
bwbar-1.2.3
bwmon-1.3
calamaris-2.59
cdparanoia-3.10_pre2
chaosreader-0.94
chillispot-1.1.0
chntpw-080526
chpax-0.7
chrpath-0.13
clearsilver-0.10.5
clutch-0.4
cmix-1.6
com_err-1.41.2
cpio-2.9-r1
cpuburn-1.4
cryptsetup-1.0.5-r1
ctorrent-3.3.2
cups-1.3.9-r1
dante-1.1.19-r1
dash-0.5.4.11
debootstrap-1.0.10
dhclient-3.1.1
di-4.5
diffstat-1.45
disktype-9
distcc-client-3.0-r4
distcc-server-3.0-r4
dmidecode-2.9
dnrd-2.20.3-r1
dnstop-20070510-r1
dnstracer-1.9
dpkg-1.14.22
driftnet-0.1.6-r4
drupal-6.8
dspam-3.8.0-r15
dyntun-0.2
e2fsprogs-libs-1.41.2
ebtables-2.0.8.2
ed-1.0
eibd-0.0.3
ethloop-10-r1
ettercap-0.7.3-r2
ez-ipupdate-3.0.11_beta8-r4
faad2-2.6.1-r2
ferm-1.3.3
fetch-crl-2.7.0
ffmpeg-0.4.9_p20090201
findutils-4.4.0
flow-tools-0.68-r5
flyspray-0.9.9.5.1
fmtools-0.99.1
fprobe-1.1
fprobe-ulog-1.1
freeradius-2.0.5
freeradius-krb5-2.0.5
freeradius-ldap-2.0.5
freeradius-postgres-2.0.5
frox-0.7.18-r2
ftp-0.17-r7
fuse-2.7.0
gensink-4.1
giflib-4.1.6-r1
gmp-dev-4.2.2-r2
gnats-4.1.0
gradm-2.1.12.200805181037
gramofile-1.6
grub-0.97-r6
gsm-1.0.12-r1
gzsign-1.1
haproxy-1.3.15.5
haproxy-doc-1.3.15.5
hashalot-0.3-r2
hdparm-9.3
hexedit-1.2.12
hping-2.0.0_rc3-r1
hunt-1.5
hydra-5.4
icecast-2.3.2
ices-2.0.1-r1
ifenslave-1.1.0-r3
ifmetric-0.3
ii-1.4
imspector-0.7
ipac-ng-1.31-r2
ipband-0.8
ipcad-3.7
iperf-2.0.2
ipp2p-0.8.2-r4
ipsec-tools-cvs-0
ipvsadm-1.24
ircii-20060725
irda-utils-0.9.16-r1
iscsi-initiator-core-tools-2.3
isic-0.07
ivtv-1.2.0-r1
jfsutils-1.1.13
jpeg-6b-r8
kbd-1.15
keepalived-1.1.15
knock-0.5
lame-3.98.2
lft-3.0
libICE-1.0.4
libSM-1.0.3
libX11-1.1.4
libXau-1.0.3
libXdmcp-1.0.2
libXext-1.0.3
libaal-1.0.5
libao-0.8.8
libarchive-2.5.5
libart_lgpl-2.3.20
libconfig-1.2
libdvbpsi-0.1.5
libevent-1.4.7
libid3tag-0.15.1b-r2
liblockfile-1.06-r2
libmad-0.15.1b-r2
libpaper-1.1.23
libpcre-7.8
libshout-2.1
libssh-0.11
libtasn1-1.3
libtheora-1.0_beta3-r1
libtool-1.5.26
libusb-dev-0.1.12-r1
libuuid1-1.41.2
libvorbis-1.2.1_rc1
lilo-22.8-r2
linux-wlan-ng-0.2.3-r2
linux-wlan-ng-utils-0.2.2
linuxtv-dvb-apps-1.1.1.20080317
logsentry-1.1.1
lpeg-0.8.1
lsscsi-0.19
lua-discount-1.2.10
luafilesystem-1.4.1
lualdap-1.1.0
luasocket-2.0.2_p1
luasql-sqlite3-2.1.1
luatdb-20080214
luatdb-doc-20080214
luuid-20070925
lynx-2.8.6-r2
macchanger-1.5.0-r1
madwifi-ng-tools-0.9.4
mailbase-1
mailx-8.1.2.20050715-r1
mailx-support-20060102-r1
maradns-1.2.12.09
mawk-1.3.3
mcrypt-2.6.7
mediawiki-1.11.2
metalog-0.8-r1
metamail-2.7.45.3-r1
mgetty-1.1.36-r3
mhash-0.9.9-r1
mime-types-7
mingetty-1.08
minicom-2.3-r1
mjpegtools-1.8.0-r1
mktemp-1.5
motion-3.2.11
mp-3.3.18b
mpc-0.12.1
mpd-0.13.2
mpg321-0.2.10-r3
mping-2.01
mpt-status-1.2.0
mtx-1.2.18
mutt-1.5.16
mysql-init-scripts-1.2
nast-0.2.0
net-tools-1.60_p20071202044231-r1
netatalk-2.0.3-r2
netcat-110-r8
netkit-talk-0.17-r4
netwox-5.33.0
ngircd-0.12.0
ngrep-1.45-r1
nictools-20030719
ntfs3g-1.2531
ntfsprogs-2.0.0
obexftp-0.22
oftpd-0.3.7-r3
olsrd-0.5.6
open-iscsi-2.0.870-r1
opencdk-0.6.6
openct-0.6.14
openobex-1.3
opensc-0.11.6
openssh-kerberos-5.1_p1-r2
openssh-server-5.1_p1-r2
paxtest-0.9.6
pcalc-1.2
pcsc-lite-1.4.2
peercast-0.1218-r1
pfqueue-0.5.6
phpBB-3.0.3
pmacct-0.11.4
portage-utils-0.1.29
privoxy-3.0.10
procps-3.2.7
progsreiserfs-0.3.1_rc8
psmisc-22.6
psycopg-2.0.2
pthsem-2.0.7
pwcrypt-1.2.2
pwgen-2.06
python-dev-2.5.2-r7
rcs-5.7-r3
recaptcha-8.05.26
reiser4progs-1.0.6
reiserfsprogs-3.6.19-r2
rp-pppoe-3.8-r2
rrdcollect-0.2.3
rsyslog-3.21.9
rtapd-1.7
rtnppd-1.7b-r1
rxmtp-1.1.3
samba-ldap-3.0.33
sarg-2.2.5
sdparm-1.03
ser2net-2.3
setserial-2.17-r3
setuptools-0.6_rc8-r1
sg3_utils-1.25
sharutils-4.6.3
shorewall-doc-3.4.8
slmodem-2.9.11_pre20080417
smartmontools-5.38
smixer-1.0.1
snarf-7.0-r3
sox-14.2.0
speex-1.2_beta3_p2
squid-kerb-auth-2.7.6
squid-ldap-auth-2.7.6
ssmping-0.9-r1
stunnel-4.25
sysvinit-2.86-r10
tcc-0.9.23-r1
tcc-dev-0.9.23-r1
tcp-wrappers-7.6-r8
telnetd-1.2-r1
testdisk-6.8-r1
tftp-hpa-0.48
thttpd-2.25b-r7
tinc-1.0.8
tor-0.2.0.34
trac-0.11.2
traceroute-2.0.11
transmission-1.22
ucarp-1.3
uclibc++-dev-0.2.2-r1
ucspi-tcp-0.88-r16
ulogd-1.23-r1
umix-1.0.2
unbound-1.0.2
unixODBC-2.2.12
unzip-5.52-r2
up-imapproxy-1.2.5_rc2
usbd-0.1
usermode-utilities-20040406-r1
util-linux-2.13.1.1
util-vserver-0.30.215
valgrind-dev-3.3.1
vanessa-logger-0.0.7
varnish-1.1.2
vconfig-1.9
vifm-0.3a
vim-core-7.2
vixie-cron-4.1-r10
vlc-0.9.8a
vorbis-tools-1.2.0-r2
vpnc-0.5.1-r1
vtun-2.6-r1
which-2.19
wireless-tools-29
wireshark-1.0.5
x86info-1.21
xl2tpd-1.1.12-r1
xl2tpd-doc-1.1.12-r1
xssfilter-8.06.22
ytree-1.92
zgsmplay-1.4
zlib-dev-1.2.3-r1
zsh-4.3.4-r1

New packages:
abuild-2.0_rc9-r1
acct-6.3.2-r1
acct-doc-6.3.2-r1
acf-heimdal-0.1.0-r0
acf-iproute2-qos-0.1.1-r0
acf-postgresql-0.3.0-r0
acf-weblog-0.4.6-r1
alpine-base-2.0-r1
alpine-sdk-0.3-r0
alsa-lib-1.0.21a-r0
arpon-1.90-r1
aspell-0.60.6-r0
aspell-doc-0.60.6-r0
bash-doc-4.0.028-r0
bc-doc-1.06-r1
beep-doc-1.2.2-r0
bind-doc-9.6.1_p1-r1
bind-libs-9.6.1_p1-r1
binutils-doc-2.19.51.0.9-r0
bridge-utils-doc-1.4-r0
build-base-0.2-r0
busybox-initscripts-2.0-r7
bzip2-doc-1.0.5-r1
c-ares-doc-1.6.0-r1
ca-certificates-20090709-r0
ccache-2.4-r0
ccache-doc-2.4-r0
cdrkit-doc-1.1.9-r1
chrony-doc-1.23-r4
cksfv-1.3.13-r0
cksfv-doc-1.3.13-r0
clamav-doc-0.95.2-r1
clamsmtp-doc-1.10-r6
conntrack-tools-doc-0.9.13-r1
coreutils-doc-7.6-r0
cpufreqd-2.3.4-r1
cpufreqd-doc-2.3.4-r1
cpufrequtils-005-r0
cpufrequtils-doc-005-r0
ctags-5.8-r0
curl-doc-7.19.6-r0
cvs-doc-1.11.23-r0
cyrus-sasl-2.1.23-r1
cyrus-sasl-doc-2.1.23-r1
dahdi-linux-2.2.0-r1
dahdi-linux-dev-2.2.0-r1
dahdi-linux-grsec-2.2.0-r19
dahdi-linux-grsec-dev-2.2.0-r19
dahdi-tools-doc-2.2.0-r0
dansguardian-doc-2.10.1.1-r4
db-doc-4.7.25.4-r0
dhcp-doc-4.1.0_p1-r4
dhcpcd-doc-5.1.1-r0
dialog-doc-1.1.20080819-r0
diffutils-doc-2.8.1-r1
dircproxy-doc-1.1.0-r0
distcc-doc-3.1-r2
dnsmasq-doc-2.50-r1
dosfstools-doc-3.0.5-r0
dovecot-doc-1.2.5-r0
dtach-doc-0.8-r0
e2fsprogs-doc-1.41.9-r0
eggdrop-1.6.19-r1
eggdrop-gseen-1.6.19-r1
eggdrop-logs2html-1.6.19-r1
email-doc-3.1.2-r0
ethtool-doc-6-r0
expat-doc-2.0.1-r0
fakeroot-doc-1.13-r0
fcgi-2.4.0-r0
fetchmail-doc-6.3.9-r4
fetchmailconf-6.3.9-r4
file-doc-5.03-r0
flac-doc-1.2.1-r0
fping-doc-2.4_beta2-r1
freetds-doc-0.82-r1
g++-4.4.1-r3
gawk-doc-3.1.7-r0
gcc-doc-4.4.1-r3
gd-doc-2.0.35-r2
gdb-doc-6.8-r3
gettext-0.17-r2
gettext-doc-0.17-r2
ghostscript-8.70-r0
ghostscript-doc-8.70-r0
glib-doc-2.20.5-r0
gmp-doc-4.3.1-r0
gnupg-2.0.10-r0
gnupg-doc-2.0.10-r0
gnutls-doc-2.8.3-r0
gperf-3.0.4-r0
gperf-doc-3.0.4-r0
grep-doc-2.5.4-r1
groff-doc-1.20.1-r1
gross-doc-1.0.2-r0
gzip-doc-1.3.12-r2
haserl-doc-0.9.25-r1
heimdal-doc-1.2.1-r3
heimdal-ftp-1.2.1-r3
heimdal-kf-1.2.1-r3
heimdal-pagsh-1.2.1-r3
heimdal-rcp-1.2.1-r3
heimdal-rsh-1.2.1-r3
heimdal-su-1.2.1-r3
heimdal-telnet-1.2.1-r3
htop-0.8.3-r0
htop-doc-0.8.3-r0
hunspell-1.2.8-r0
hunspell-doc-1.2.8-r0
iaxmodem-1.2.0-r2
iaxmodem-doc-1.2.0-r2
imagemagick-doc-6.5.5.6-r0
ip6tables-1.4.5-r0
iproute2-doc-2.6.29.1-r0
iproute2-qos-0.2-r1
iptables-doc-1.4.5-r0
iptraf-doc-3.0.0-r0
irssi-0.8.14-r1
irssi-doc-0.8.14-r1
irssi-perl-0.8.14-r1
iscsitarget-doc-0.4.17-r3
iscsitarget-grsec-0.4.17-r17
kqemu-grsec-1.4.0_pre1-r10
ksymoops-2.4.11-r0
ksymoops-doc-2.4.11-r0
less-doc-436-r0
lftp-3.7.15-r0
lftp-doc-3.7.15-r0
libart-lgpl-2.3.20-r0
libblkid-2.16-r1
libcom_err-1.41.9-r0
libcrypto-0.9.8k-r7
libdnet-1.12-r0
libgcc-4.4.1-r3
libiconv-1.12-r0
libjpeg-7-r0
libksba-1.0.3-r0
libsasl-2.1.23-r1
libstdc++-4.4.1-r3
libusb-compat-0.1.0-r0
libuuid-2.16-r1
lighttpd-doc-1.4.23-r2
links-doc-2.2-r0
linux-firmware-2.6.30.8-r0
linux-grsec-2.6.30.8-r0
linux-grsec-dev-2.6.30.8-r0
lm_sensors-detect-3.1.1-r0
lm_sensors-doc-3.1.1-r0
logrotate-doc-3.7.8-r1
lua-dev-5.1.4-r3
lua-doc-5.1.4-r3
lvm2-doc-2.02.53-r0
m4-1.4.13-r0
m4-doc-1.4.13-r0
make-doc-3.81-r1
man-doc-1.6f-r1
mdadm-doc-2.6.9-r1
mini_httpd-doc-1.19-r3
miniperl-5.10.1-r0
mkinitfs-2.0_rc5-r2
mlmmj-doc-1.2.16-r0
mpfr-2.4.1-r0
mpfr-doc-2.4.1-r0
mpg123-doc-1.9.0-r0
mtools-doc-4.0.10-r2
mysql-client-5.0.83-r1
mysql-doc-5.0.83-r1
mysql-test-5.0.83-r1
nano-doc-2.0.9-r2
nasm-2.05.01-r0
nasm-doc-2.05.01-r0
ncftp-3.2.3-r0
ncftp-bookmarks-3.2.3-r0
ncftp-doc-3.2.3-r0
ncurses-doc-5.7-r1
ncurses-terminfo-5.7-r1
net-snmp-doc-5.4.2.1-r3
net-snmp-tools-5.4.2.1-r3
newt-doc-0.52.8-r0
nfs-utils-doc-1.2.0-r1
nmap-doc-5.00-r0
nmap-nse-5.00-r0
oidentd-2.0.8-r1
oidentd-doc-2.0.8-r1
openldap-doc-2.4.18-r0
openntpd-doc-3.9_p1-r4
openrc-0.5.0-r11
openrc-doc-0.5.0-r11
openssh-doc-5.2_p1-r3
openssl-doc-0.9.8k-r7
p7zip-4.65-r0
p7zip-doc-4.65-r0
parted-doc-1.8.8-r1
patch-doc-2.5.9-r0
pax-utils-doc-0.1.19-r0
paxctl-doc-0.5-r0
pciutils-doc-3.1.4-r0
pcmciautils-doc-015-r0
pcre-7.9-r0
perl-db-0.38-r0
perl-digest-sha1-2.12-r0
perl-doc-5.10.1-r0
perl-getopt-long-2.38-r0
perl-io-multiplex-1.10-r0
perl-net-server-0.97-r0
perl-uri-1.38-r0
perl-uri-doc-1.38-r0
perl-uri-escape-1.38-r0
perl-xml-parser-2.36-r0
php-apc-3.1.2-r1
php-bcmath-5.2.10-r2
php-bz2-5.2.10-r2
php-calendar-5.2.10-r2
php-curl-5.2.10-r2
php-dba-5.2.10-r2
php-dev-5.2.10-r2
php-doc-5.2.10-r2
php-exif-5.2.10-r2
php-fileinfo-1.0.4-r0
php-ftp-5.2.10-r2
php-gd-5.2.10-r2
php-gettext-5.2.10-r2
php-gmp-5.2.10-r2
php-iconv-5.2.10-r2
php-imap-5.2.10-r2
php-json-5.2.10-r2
php-ldap-5.2.10-r2
php-mcrypt-5.2.10-r2
php-mime_magic-5.2.10-r2
php-mysql-5.2.10-r2
php-mysqli-5.2.10-r2
php-odbc-5.2.10-r2
php-openssl-5.2.10-r2
php-pdo-5.2.10-r2
php-pdo_mysql-5.2.10-r2
php-pdo_odbc-5.2.10-r2
php-pdo_pgsql-5.2.10-r2
php-pdo_sqlite-5.2.10-r2
php-pgsql-5.2.10-r2
php-posix-5.2.10-r2
php-pspell-5.2.10-r2
php-shmop-5.2.10-r2
php-snmp-5.2.10-r2
php-soap-5.2.10-r2
php-sockets-5.2.10-r2
php-sqlite-5.2.10-r2
php-sysvmsg-5.2.10-r2
php-sysvsem-5.2.10-r2
php-sysvshm-5.2.10-r2
php-xml-5.2.10-r2
php-xmlrpc-5.2.10-r2
php-xsl-5.2.10-r2
php-zip-5.2.10-r2
php-zlib-5.2.10-r2
pinentry-0.7.6-r0
pinentry-doc-0.7.6-r0
pkgconfig-0.23-r0
pkgconfig-doc-0.23-r0
portmap-doc-6.0-r3
postfix-doc-2.6.5-r0
postfix-ldap-2.6.5-r0
postfix-mysql-2.6.5-r0
postfix-pcre-2.6.5-r0
postfix-pgsql-2.6.5-r0
postgresql-client-8.4.1-r1
postgresql-doc-8.4.1-r1
postgrey-1.32-r0
ppp-doc-2.4.4-r0
pth-2.0.7-r0
pth-doc-2.0.7-r0
python-doc-2.6.2-r1
quagga-doc-0.99.13-r2
razor-2.84-r0
roundcubemail-0.2.2-r0
rrdtool-doc-1.2.30-r0
rsync-doc-3.0.6-r1
ruby-1.8.7_p174-r2
ruby-dev-1.8.7_p174-r2
ruby-doc-1.8.7_p174-r2
rubygems-1.3.5-r1
run-parts-3.1.3-r0
run-parts-doc-3.1.3-r0
samba-common-3.3.7-r4
samba-doc-3.3.7-r4
samba-initscript-3.3.7-r4
screen-doc-4.0.3-r0
sed-doc-4.2.1-r0
sfdisk-2.16-r1
sfic-doc-0.1.7-r1
shorewall-common-4.2.10-r0
shorewall-common-doc-4.2.10-r0
shorewall-perl-4.2.10.3-r0
shorewall-shell-4.2.10-r0
sic-1.0-r0
sic-doc-1.0-r0
slang-doc-2.1.4-r0
snort-doc-2.8.4-r1
sntpc-0.9-r1
sqlite-doc-3.6.15-r0
squid-doc-2.7.6-r11
squid-errors-ukrainian-1251-2.7.6-r11
squid-errors-ukrainian-koi8-u-2.7.6-r11
squid-errors-ukrainian-utf8-2.7.6-r11
ssmtp-doc-2.62-r0
strace-doc-4.5.18-r0
subversion-doc-1.6.5-r1
sudo-doc-1.7.2_p1-r0
sysfsutils-doc-2.1.0-r3
sysklogd-doc-1.5-r3
syslinux-doc-3.82-r0
sysstat-doc-9.0.4-r0
tar-doc-1.22-r0
tcl-doc-8.5.7-r0
tcpdump-doc-4.0.0-r1
tinyproxy-doc-1.6.3-r3
udev-142-r0
udev-doc-142-r0
unfs3-0.9.22-r0
unfs3-doc-0.9.22-r0
unixodbc-2.2.14-r0
unrar-doc-3.9.6-r0
util-linux-ng-2.16-r1
v86d-0.1.9-r0
valgrind-doc-3.4.1-r1
vim-doc-7.2.245-r2
wget-doc-1.12-r0
winbind-3.3.7-r4
xfsprogs-doc-3.0.3-r0
xtables-addons-doc-1.17-r1
xtables-addons-grsec-1.17-r15
zip-doc-3.0-r0
zonenotify-0.1-r0

Upgraded/downgraded packages (from version):
acf-alpine-baselayout-0.5.7-r0 (0.4.12)
acf-alpine-conf-0.3.14-r0 (0.3.14)
acf-apk-tools-0.4.3-r0 (0.1.5)
acf-asterisk-0.2.0-r0 (0.1.1)
acf-chrony-0.2.0-r0 (0.1.12)
acf-clamav-0.2.1-r0 (0.1.1)
acf-clamsmtp-0.2.0-r0 (0.1.1)
acf-core-0.8.3-r0 (0.4.22)
acf-dansguardian-0.3.1-r0 (0.2.6)
acf-dhcp-0.4.2-r0 (0.3.10)
acf-dnscache-0.2.0-r0 (0.1.10)
acf-dnsmasq-0.2.0-r0 (0.1.2)
acf-dovecot-0.2.0-r0 (0.1.0)
acf-fetchmail-0.4.1-r0 (0.2.6)
acf-gross-0.2.0-r0 (0.1.0)
acf-ipsec-tools-0.4.0-r0 (0.3.17)
acf-iptables-0.2.0-r0 (0.1.0)
acf-lvm2-0.2.0-r0 (0.1.0)
acf-mdadm-0.2.0-r0 (0.1.0)
acf-opennhrp-0.4.0-r0 (0.3.12)
acf-openntpd-0.4.0-r0 (0.3.12)
acf-openssh-0.2.2-r0 (0.1.4)
acf-openssl-0.2.0-r0 (0.1.8)
acf-openvpn-0.4.3-r0 (0.4.1)
acf-pingu-0.2.0-r0 (0.1.0)
acf-postfix-0.2.3-r0 (0.1.2)
acf-ppp-0.1.2-r0 (0.1.0)
acf-quagga-0.4.0-r0 (0.3.4)
acf-samba-0.3.2-r0 (0.1.1)
acf-shorewall-0.5.0-r0 (0.4.5)
acf-skins-0.2.2-r0 (0.1.6)
acf-snort-0.4.0-r0 (0.3.10)
acf-squid-0.5.1-r0 (0.3.8)
acf-tcpproxy-0.1.0-r0 (0.0.4)
acf-tinydns-0.3.0-r0 (0.2.14)
alpine-baselayout-2.0_rc1-r0 (1.13.1)
alpine-conf-2.0_rc7-r1 (1.8.1)
apk-tools-2.0_rc5-r1 (0.15.2)
apr-1.3.8-r0 (1.3.2)
apr-util-1.3.9-r0 (1.3.2)
arpwatch-2.1a15-r1 (2.1.15-r5)
asterisk-1.6.0.15-r2 (1.6.1_rc1-r1)
asterisk-doc-1.6.0.15-r2 (1.6.1_rc1-r1)
asterisk-odbc-1.6.0.15-r2 (1.6.1_rc1-r1)
asterisk-pgsql-1.6.0.15-r2 (1.6.1_rc1-r1)
asterisk-tds-1.6.0.15-r2 (1.6.1_rc1-r1)
aumix-2.8-r1 (2.8-r4)
bash-4.0.028-r0 (3.2_p33)
bbsuid-0.3-r0 (0.1)
bc-1.06-r1 (1.06.95)
beep-1.2.2-r0 (1.2.2-r1)
bind-9.6.1_p1-r1 (9.4.3_p2)
bind-tools-9.6.1_p1-r1 (9.4.2_p2)
binutils-2.19.51.0.9-r0 (2.18-r3)
bitlib-25-r0 (23_p2)
bkeymaps-1.13-r0 (1.13)
bridge-utils-1.4-r0 (1.4)
busybox-1.14.4-r0 (1.13.2-r1)
bwm-ng-0.6-r0 (0.6)
c-ares-1.6.0-r1 (1.4.0)
cdrkit-1.1.9-r1 (1.1.8)
cgit-0.8.2.1-r1 (0.8.1)
chrony-1.23-r4 (1.23-r1)
clamav-0.95.2-r1 (0.94.2)
clamsmtp-1.10-r6 (1.9)
conntrack-tools-0.9.13-r1 (0.9.9)
coreutils-7.6-r0 (6.10-r2)
cracklib-2.8.13-r0 (2.8.12)
cracklib-words-20080507-r0 (20080507)
cramfs-1.1-r0 (1.1)
curl-7.19.6-r0 (7.19.4)
cvs-1.11.23-r0 (1.12.12-r4)
dahdi-tools-2.2.0-r0 (2.1.0-r1)
dansguardian-2.10.1.1-r4 (2.10-r1)
db-4.7.25.4-r0 (4.5.20_p2-r1)
device-mapper-2.02.53-r0 (1.02.24-r1)
dhcp-4.1.0_p1-r4 (3.1.1)
dhcpcd-5.1.1-r0 (4.0.2)
dialog-1.1.20080819-r0 (1.1.20080316)
diffutils-2.8.1-r1 (2.8.7-r2)
dircproxy-1.1.0-r0 (1.0.5-r1)
distcc-3.1-r2 (2.18.3-r10)
djbdns-1.05-r32 (1.05-r22)
dnscache-1.05-r32 (1.05-r22)
dnsmasq-2.50-r1 (2.45)
dosfstools-3.0.5-r0 (2.11-r3)
dovecot-1.2.5-r0 (1.1.7-r1)
dropbear-0.52-r2 (0.51)
dtach-0.8-r0 (0.8)
e2fsprogs-1.41.9-r0 (1.41.2)
email-3.1.2-r0 (2.5.0)
espeak-1.40.02-r0 (1.40.02)
ethtool-6-r0 (6)
expat-2.0.1-r0 (2.0.1)
fakeroot-1.13-r0 (1.9.1)
fetchmail-6.3.9-r4 (6.3.8-r2)
file-5.03-r0 (4.23)
flac-1.2.1-r0 (1.2.1-r3)
freetds-0.82-r1 (0.64)
freetype-2.3.8-r0 (2.3.7)
gawk-3.1.7-r0 (3.1.6)
gcc-4.4.1-r3 (3.4.6-r2)
gd-2.0.35-r2 (2.0.35)
gdb-6.8-r3 (6.7.1-r3)
gdbm-1.8.3-r0 (1.8.3-r3)
git-1.6.4.4-r0 (1.6.0.6)
glib-2.20.5-r0 (1.2.10-r5)
gmp-4.3.1-r0 (4.2.2-r2)
gnutls-2.8.3-r0 (2.4.1-r2)
grep-2.5.4-r1 (2.5.1a-r1)
groff-1.20.1-r1 (1.19.2-r1)
gross-1.0.2-r0 (1.0.1-r1)
gzip-1.3.12-r2 (1.3.12-r1)
haserl-0.9.25-r1 (0.9.24)
heimdal-1.2.1-r3 (0.7.2-r3)
hypermail-2.2.0-r0 (2.2.0)
imagemagick-6.5.5.6-r0 (6.4.4.6)
iproute2-2.6.29.1-r0 (2.6.22.20070710)
ipsec-tools-0.8_alpha20090903-r2 (0.8_alpha20090422-r2)
ipsec-tools-doc-0.8_alpha20090903-r2 (0.8_alpha20090422-r2)
iptables-1.4.5-r0 (1.4.2-r2)
iptraf-3.0.0-r0 (3.0.0-r4)
iputils-20071127-r1 (20071127)
iscsitarget-0.4.17-r3 (0.4.17)
json4lua-0.9.20-r0 (0.9.20)
less-436-r0 (418)
libcap-2.16-r1 (2.15)
libgcrypt-1.4.4-r1 (1.4.0-r1)
libgpg-error-1.7-r0 (1.6)
libldap-2.4.18-r0 (2.3.43)
libltdl-2.2.6a-r4 (1.5.26)
libmcrypt-2.5.8-r0 (2.5.8)
libmysqlclient-5.0.83-r1 (5.0.70-r1)
libnet-1.1.4-r0 (1.1.2.1-r1)
libnetfilter_conntrack-0.0.100-r0 (0.0.99)
libnfnetlink-1.0.0-r0 (0.0.39)
libogg-1.1.4-r0 (1.1.3)
libpcap-1.0.0-r2 (0.9.8-r2)
libpng-1.2.39-r0 (1.2.35)
libpq-8.4.1-r1 (8.2.7)
libusb-1.0.1-r0 (0.1.12-r1)
libxml2-2.7.3-r0 (2.7.2-r1)
lighttpd-1.4.23-r2 (1.4.20)
links-2.2-r0 (2.2)
linux-headers-2.6.30.5-r0 (2.6.23-r3)
lm_sensors-3.1.1-r0 (2.10.7)
logrotate-3.7.8-r1 (3.7.2)
lpc-1.0.0-r0 (1.0.0_p1)
lsof-4.82-r0 (4.78-r2)
lua-5.1.4-r3 (5.1.3-r3)
luaposix-5.1.4-r0 (5.1.4)
luasql-postgres-2.1.1-r1 (2.1.1)
lvm2-2.02.53-r0 (2.02.36)
lzo-2.03-r0 (2.02-r1)
make-3.81-r1 (3.81)
man-1.6f-r1 (1.6f-r2)
md5-1.1.2-r0 (1.1.2)
mdadm-2.6.9-r1 (2.6.4-r1)
mini_httpd-1.19-r3 (1.19)
mlmmj-1.2.16-r0 (1.2.12)
module-init-tools-3.10-r0 (3.4)
mpg123-1.9.0-r0 (1.7.2)
mtools-4.0.10-r2 (3.9.10)
mysql-5.0.83-r1 (5.0.70-r1)
nano-2.0.9-r2 (2.1.5)
ncurses-5.7-r1 (5.6-r2)
neon-0.28.6-r0 (0.28.3)
net-snmp-5.4.2.1-r3 (5.4.2.1)
newt-0.52.8-r0 (0.52.8)
nfs-utils-1.2.0-r1 (1.0.6-r6)
nmap-5.00-r0 (4.76)
openldap-2.4.18-r0 (2.3.43)
opennhrp-0.11.2-r1 (0.10.3)
opennhrp-doc-0.11.2-r1 (0.10.3)
openntpd-3.9_p1-r4 (3.9_p1-r1)
openssh-5.2_p1-r3 (4.7_p1-r3)
openssh-client-5.2_p1-r3 (5.1_p1-r2)
openssl-0.9.8k-r7 (0.9.8k)
openvpn-2.0.9-r2 (2.0.7-r2)
openvpn-doc-2.0.9-r2 (2.0.7-r2)
parted-1.8.8-r1 (1.8.8)
patch-2.5.9-r0 (2.5.9)
pax-utils-0.1.19-r0 (0.1.17)
paxctl-0.5-r0 (0.5)
pciutils-3.1.4-r0 (3.0.0)
pcmciautils-015-r0 (014-r1)
perl-5.10.1-r0 (5.8.8-r5)
php-5.2.10-r2 (5.2.8-r1)
pingu-0.3-r1 (0.3)
popt-1.14-r0 (1.10.7)
portmap-6.0-r3 (6.0)
postfix-2.6.5-r0 (2.5.5)
postgresql-8.4.1-r1 (8.2.7)
ppp-2.4.4-r0 (2.4.4-r21)
python-2.6.2-r1 (2.5.2-r7)
quagga-0.99.13-r2 (0.99.11-r4)
readline-6.0.004-r0 (5.2_p12-r1)
rrdtool-1.2.30-r0 (1.2.28-r1)
rsync-3.0.6-r1 (3.0.4)
samba-3.3.7-r4 (3.0.33)
screen-4.0.3-r0 (4.0.3)
sed-4.2.1-r0 (4.1.5-r1)
sfic-0.1.7-r1 (0.1.7)
shorewall-4.2.10-r0 (3.4.8)
shorewall-lite-4.2.10-r0 (3.4.8)
slang-2.1.4-r0 (2.1.3-r1)
snort-2.8.4-r1 (2.6.1.3-r1)
sqlite-3.6.15-r0 (3.5.9)
squid-2.7.6-r11 (2.7.6)
squid-errors-armenian-2.7.6-r11 (2.7.6)
squid-errors-azerbaijani-2.7.6-r11 (2.7.6)
squid-errors-bulgarian-2.7.6-r11 (2.7.6)
squid-errors-catalan-2.7.6-r11 (2.7.6)
squid-errors-czech-2.7.6-r11 (2.7.6)
squid-errors-danish-2.7.6-r11 (2.7.6)
squid-errors-dutch-2.7.6-r11 (2.7.6)
squid-errors-english-2.7.6-r11 (2.7.6)
squid-errors-estonian-2.7.6-r11 (2.7.6)
squid-errors-finnish-2.7.6-r11 (2.7.6)
squid-errors-french-2.7.6-r11 (2.7.6)
squid-errors-german-2.7.6-r11 (2.7.6)
squid-errors-greek-2.7.6-r11 (2.7.6)
squid-errors-hebrew-2.7.6-r11 (2.7.6)
squid-errors-hungarian-2.7.6-r11 (2.7.6)
squid-errors-italian-2.7.6-r11 (2.7.6)
squid-errors-japanese-2.7.6-r11 (2.7.6)
squid-errors-korean-2.7.6-r11 (2.7.6)
squid-errors-lithuanian-2.7.6-r11 (2.7.6)
squid-errors-polish-2.7.6-r11 (2.7.6)
squid-errors-portuguese-2.7.6-r11 (2.7.6)
squid-errors-romanian-2.7.6-r11 (2.7.6)
squid-errors-russian-1251-2.7.6-r11 (2.7.6)
squid-errors-russian-koi8-r-2.7.6-r11 (2.7.6)
squid-errors-serbian-2.7.6-r11 (2.7.6)
squid-errors-simplify_chinese-2.7.6-r11 (2.7.6)
squid-errors-slovak-2.7.6-r11 (2.7.6)
squid-errors-spanish-2.7.6-r11 (2.7.6)
squid-errors-swedish-2.7.6-r11 (2.7.6)
squid-errors-traditional_chinese-2.7.6-r11 (2.7.6)
squid-errors-turkish-2.7.6-r11 (2.7.6)
ssmtp-2.62-r0 (2.62-r4)
strace-4.5.18-r0 (4.5.18)
subversion-1.6.5-r1 (1.5.4)
sudo-1.7.2_p1-r0 (1.7.0)
sysfsutils-2.1.0-r3 (2.1.0)
sysklogd-1.5-r3 (1.4.2_pre20061230-r2)
syslinux-3.82-r0 (3.72)
sysstat-9.0.4-r0 (8.0.4-r1)
tar-1.22-r0 (1.20)
tcl-8.5.7-r0 (8.4.18)
tcpdump-4.0.0-r1 (3.9.8-r1)
tcpproxy-2.0.0_beta15-r0 (1.1.9)
tdb-3.3.7-r4 (1.0.6-r1)
tinydns-1.05-r32 (1.05-r22)
tinyproxy-1.6.3-r3 (1.6.3-r1)
uclibc++-0.2.2-r5 (0.2.2-r1)
uclibc-0.9.30.1-r18 (0.9.28.3-r7)
uclibc-dev-0.9.30.1-r18 (0.9.28.3-r7)
unrar-3.9.6-r0 (3.8.5)
usbutils-0.86-r0 (0.73)
valgrind-3.4.1-r1 (3.3.1)
vim-7.2.245-r2 (7.2)
vsftpd-2.1.0-r2 (2.0.6)
vsftpd-doc-2.1.0-r2 (2.0.6)
wget-1.12-r0 (1.11.3)
xfsprogs-3.0.3-r0 (2.7.11)
xtables-addons-1.17-r1 (1.10)
zip-3.0-r0 (2.32-r1)
zlib-1.2.3.3-r7 (1.2.3-r1)
</pre>

[[Category:News]]

1.9.0 package changes since 1.9.0 rc5

2016-03-07T12:30:59Z

Fab: Reverted edits by RuthHughes (talk) to last revision by Dubiousjim

= Package changes since 1.9.0_rc5 =
<pre>
Removed packages:

New packages:

Upgraded/downgraded packages (from version):
acf-apk-tools-0.4.3-r0 (0.4.2-r0)
acf-iproute2-qos-0.1.1-r0 (0.1.0-r0)
alpine-conf-2.0_rc7-r1 (2.0_rc6-r0)
dahdi-linux-grsec-2.2.0-r19 (2.2.0-r18)
dahdi-linux-grsec-dev-2.2.0-r19 (2.2.0-r18)
device-mapper-2.02.53-r0 (2.02.52-r0)
gross-1.0.2-r0 (1.0.1-r5)
gross-doc-1.0.2-r0 (1.0.1-r5)
ip6tables-1.4.5-r0 (1.4.4-r0)
ipsec-tools-0.8_alpha20090903-r2 (0.8_alpha20090903-r1)
ipsec-tools-doc-0.8_alpha20090903-r2 (0.8_alpha20090903-r1)
iptables-1.4.5-r0 (1.4.4-r0)
iptables-doc-1.4.5-r0 (1.4.4-r0)
iscsitarget-grsec-0.4.17-r17 (0.4.17-r16)
kqemu-grsec-1.4.0_pre1-r10 (1.4.0_pre1-r9)
libpq-8.4.1-r1 (8.4.1-r0)
linux-firmware-2.6.30.8-r0 (2.6.30.7-r2)
linux-grsec-2.6.30.8-r0 (2.6.30.7-r2)
linux-grsec-dev-2.6.30.8-r0 (2.6.30.7-r2)
lvm2-2.02.53-r0 (2.02.52-r0)
lvm2-doc-2.02.53-r0 (2.02.52-r0)
mkinitfs-2.0_rc5-r2 (2.0_rc5-r1)
opennhrp-0.11.2-r1 (0.11.1-r2)
opennhrp-doc-0.11.2-r1 (0.11.1-r2)
openrc-0.5.0-r11 (0.5.0-r10)
openrc-doc-0.5.0-r11 (0.5.0-r10)
postgresql-8.4.1-r1 (8.4.1-r0)
postgresql-client-8.4.1-r1 (8.4.1-r0)
postgresql-doc-8.4.1-r1 (8.4.1-r0)
xtables-addons-grsec-1.17-r15 (1.17-r14)
</pre>

[[Category:News]]

2600hz

2016-03-07T12:30:54Z

Fab: Reverted edits by RuthHughes (talk) to last revision by Fab

[http://www.2600hz.org blue.box] is an open source GUI for administration and configuration of FreeSWITCH and Asterisk based VoIP systems. It supports multi-tenancy and skinning, and is completely modular.

== Install Lighttpd ==

{{:Setting Up Lighttpd With FastCGI}}

== Configuring postgresql ==

{{Cmd|apk add postgresql postgresql-client git
/etc/init.d/postgresql setup}}

'''Starting http service and adding to boot'''

{{Cmd|/etc/init.d/postgresql start && rc-update add postgresql default}}

== Installing FreeSwitch ==

First use <code>apk</code> to install the needed software parts.

{{Cmd|apk add freeswitch freeswitch-flite freeswitch-sounds-en-us-callie-8000 freeswitch-sample-config}}

Change the permissions of {{Path|/etc/freeswitch/}}

{{Cmd|chown lighttpd:lighttpd /etc/freeswitch/
chmod 777 -R /etc/freeswitch/}}

== Starting ==

'''Starting http and sql server and adding to boot'''

{{Cmd|/etc/init.d/postgresql setup
/etc/init.d/postgresql start && rc-update add postgresql default
/etc/init.d/lighttpd start && rc-update add lighttpd default }}

== Installing 2600hz ==

Create a {{Path|webapps}} folder

{{Cmd|mkdir /usr/share/webapps/ -p}}

Checkout the source code from the git repository

{{Cmd|cd /usr/share/webapps/
git clone git://source.2600hz.org/bluebox.git bluebox/}}

Change the folder permissions

{{Cmd|chmod -R 777 /usr/share/webapps/bluebox}}

Create a symlink to the create directory

{{Cmd|ln -s /usr/share/webapps/bluebox/ /var/www/localhost/htdocs/bluebox}}

== Configuring bluebox ==

'''Log on your bluebox'''

Browse to: http://WEBSERVER_IP_ADDRESS/bluebox and start configuration.

* Welcome to Bluebox 1.0 Setup Wizard

Accept Terms and Conditions
Next

* Initial Configuration

Select pqsl as database server, '''bluebox''' as database name, '''postgres''' as user,''' no password'''
Set '''Default Timezone'''

'''Note:''' Set Port to 3306 (for mysql); see - http://tickets.2600hz.org/browse/BLUEBOX-445

Next

* Create Main Administrator

Master Administration Account

Email Address:'''youremail@yourserver.net'''
Password:'''adminpassword'''
Confirm Password:'''adminpassword'''

Next

* Telephony Engine

In ''Telephony Configuration''

Conf Directory: '''/etc/freeswitch'''

Global Sound File Directory: '''/usr/sounds'''

Next

Conflicting configuration files will be permanently erased if you continue!

Next

* Installation

Ready to Install

Next

After that you will see '''Click here to use Bluebox 1.0!'''

And you finish you Bluesbox installation.

'''Note:''' If you are using the Alpine ACF, or if you change the port in the lighttpd.conf file, the go to the port you set.
e.g: if you set the port to 8080, then browse to: http://WEBSERVER_IP_ADDRESS:8080/bluebox

'''Note:''' Needs PHP DOM package (apk add php-dom)

'''Note:''' This documentation need some minor fixes.

[[Category:SQL]]
[[Category:Telephony]]

ACF

2016-03-07T12:30:51Z

Fab: Reverted edits by RuthHughes (talk) to last revision by Fab

#REDIRECT [[Alpine_Configuration_Framework_Design]]

ACF Libraries

2016-03-07T12:30:48Z

Fab: Reverted edits by RuthHughes (talk) to last revision by Dubiousjim

= ACF Libraries =
Because of using lua, a very small language, the need arises to build everything from scratch. This can lead to some confusion, apprehension, or just feeling overwhelmed. Here is documentation on what we have now in the form of libraries and common functions. We hope to build some more and use this information to get the juices flowing in regard to ACF.

Some of these are lua libs or ones written for ACF.
We are also using as a standard the lposix library which is documented here [[LPOSIX]]

== Generic Libraries (acf-lib) ==

===[[apk.lua]]===
Functions to load/unload apk packages
* delete - Deletes a package
* install - Installs a package
* version - Checks a package's installed version

===[[date.lua]]===
Date and time functions
To be used with os.time() and os.date()
*date_to_seconds - Takes a date table and converts it to seconds from 1970
*seconds_to_date - Takes table of seconds values and converts to a date sorted smallest to largest
*string_to_table
*date_diff - Takes two values of seconds and gives back the difference
*num_month_name - Month number to name of month
*num_month_name_abr - Month number to abr of month
*name_month_num - Month name to number
*abr_month_num - Month abbreviation to number
*num_dow_name - Day of Week number to name
*num_dow_name_abr - Day of week number to abbreviation
*name_dow_num - Day of Week full name to number
*abr_dow_num - Day of week abbreviation to number
*what_tz - Checks to see what timezone the box is set to; /etc/TZ
*change_tz - Changes the timezone
**Tables are included with this information
***Timezones
***Days of Week
***Months of the Year

===[[format.lua]]===
Used to format tables and strings
*dostounix - Converts DOS line endings to Unix
*escapemagiccharacters - Escape Lua magic characters
*escapespecialcharacters - Escape shell special characters
*parse_lines - Takes out the blank and commented lines
*parse_linesandwords - Removes blanks and comments, and parses each line for words
*parse_configfile - Parses a config file for name/value pairs
*search_replace - Goes through a table of lines to search and replace
*search_for_lines - Goes through a file or table of lines and returns a table of matching lines
*cap_begin_word - Capitalizes beginning of words
*string_to_table - Takes a delimited string and turns it into a table
*expand_bash_syntax_vars - Takes a string and expands any ${...} constructs with the Lua variable
*replace_line - Removes the indicated line from a string and replaces it
*insert_line - Inserts a new line at the indicated location in a string
*get_line - Returns the specified line by number
*opts_to_table - Searches an option string for separate options and puts them in a table
*table_to_opts - Goes through an options table and creates the option string
*update_ini_file - Set a value in a particular ini section
*parse_ini_file - Read a value / values from an ini file
*get_ini_section - Read an entire section from an ini file
*set_ini_section - Set an entire section in an ini file
*get_ini_entry - Get an entry value from an ini file, accounting for parent sections and variables

=== [[fs.lua]] ===
Used for various filesystem specific functions
*is_dir - Test if the path is a directory
*is_file - Test if the path is a file
*is_link - Test if the path is a link
*create_directory - Creates a directory if it doesn't exist, including the parent dirs
*remove_directory - Deletes a directory along with its contents
*create_file - Creates a blank file (and the directory if necessary)
*copy_properties - Copies the permissions and ownership of one file to another
*copy_file - Copies a file to a directory or new filename (creating the directory if necessary)
*move_file - Moves a file to a directory or new filename (creating the directory if necessary)
*read_file / read_file_as_array - Reads a file as a string / array
*write_file - Replaces contents of a file
*write_line_file - Appends lines to a file
*find_files_as_array - Returns an array of files under "where" that match "what" (a Lua pattern)
*find - Give a path and a search string and iterate over matching files
*stat - Does almost the same as posix.stat, but instead it writes the output human readable

=== [[html.lua]] ===
Used to generate HTML code.
*cookie.set - Creates a cookie
*cookie.unset - Clears a cookie
*html_escape - Escapes HTML encoded strings
*entity - Outputs tags such as h1, h2, p, etc.
*link - Creates a link tag
*Form setup functions - Create form tags
**form.text
**form.longtext
**form.password
**form.hidden
**form.submit
**form.action
**form.file
**form.image
**form.select
**form.checkbox
**form.start
**form.stop

=== [[processinfo.lua]] ===
Manages processes
*package_version - Returns the version of an apk package
*process_autostart - Returns a string describing run level of a process
*read_initrunlevels - Returns all processes in all run levels
*add_runlevels - Add a process to a list of run levels
*delete_runlevels - Remove a process from a list of run levels
*daemoncontrol - Start/Stop/Restart/... a process (calls /etc/init.d/service)
*pidof - Find the process ID of a running program

=== [[validator.lua]] ===
This contains multiple different functions that each will validate input in there own way.
*is_string - Tests if a variable is of type string
*is_boolean - Tests if a variable is of type boolean
*is_number - Tests if a variable is of type number
*is_ipv4 - Tests if this is a valid ipv4 address
*is_partial_ipv4 - Tests if this is part of a valid ipv4 address
*is_mac - Tests to see if this is a valid mac address
*is_integer - Tests to see if a string contains an integer
*is_integer_in_range - Tests to see if a string contains an integer in a given range
*is_port - Tests to see if a string contains an integer in the IP port range
*is_valid_filename - Tests to see if a string is a valid filename and (optionally) located in a specified path

== ACF-specific Libraries (acf-core) ==
===[[authenticator.lua]]===
Authentication module. This module loads one sub-authenticator module and exposes its functionality via '''auth''' table.
* authenticate
* get_userinfo
* get_userinfo_roles
* list_users
* change_settings
* new_settings
* delete_user

===[[authenticator-plaintext.lua]]===
Authentication sub-module for plaintext database
* list_fields
* read_field
* delete_field
* write_entry
* read_entry
* delete_entry

===[[controllerfunctions.lua]]===
Controller helper functions
* handle_clientdata
* handle_form
* handle_startstop

=== menubuilder.lua ===
Written by nangel for ACF
*get_menuitems

=== [[modelfunctions.lua]] ===
*getenabled
*startstop_service
*getstatus
*getfiledetails
*setfiledetails
*validateselect
*validatemulti
*write_file_with_audit

=== [[roles.lua]] ===
*list_controllers
*get_controllers
*get_controllers_func
*get_controllers_view
*list_default_roles
*list_roles
*list_all_roles
*get_roles_perm
*get_role_perm
*delete_role
*set_role_perm

=== [[session.lua]] ===
Written by nangel for ACF.
*random_hash - will create a bash64-like hash from /dev/urandom
*hash_ip_addr - create a hash encoded ip address
*ip_addr_from_hash - take the hash encoded ip and give me the ip
*serialize - go through a table or set of tables and serialize
*save_session - save the session table
*load_session - load a saved session table
*unlink_session - delete a saved session table
*record_event - record an invalid login attempt
*count_events - check if there are too many invalid attempts
*expired_events - delete the expired invalid attempts and saved sessions

=== [[viewfunctions.lua]] ===
displayinfo - obsolete
displaymanagement - obsolete
*displayitem
*displayformitem
*displayform
*displaycommandresults

[[Category:ACF]] [[Category:Lua]]

ACF acf www-controller.lua reference

2016-03-07T12:30:45Z

Fab: Reverted edits by RuthHughes (talk) to last revision by Dubiousjim

== acf_www-controller.lua reference ==

The acf_www-controller.lua provides the basic dispatcher, exception handler, and application-wide functions for the acf web application.

=== build_menus ( self ) ===

''(internal function)'' Builds the permissions and menu tables and stores them in ''self.sessiondata'' for use on each page throughout the user session.

# Searches for roles files to determine which controllers and actions the current user has permission to view
# Searches for menu files to create the entire menu structure
# Removes from the menu any actions for which the user does not have permission

=== check_permission ( self, controller, action ) ===

''(internal function)'' Returns a boolean to tell whether or not this user is permitted to access this controller/action combo. The decision is based upon the permissions table in ''self.sessiondata''.

=== find_template ( appdir, prefix, controller, action, viewtype ) ===

''(internal function)'' Looks for a .lsp (Lua Server Page) template. Looks for the first matching:

# ''appdir/prefix''/template-''controller-action-viewtype''.lsp
# ''appdir/prefix''/template-''controller-viewtype''.lsp
# ''appdir/prefix''/template-''action-viewtype''.lsp
# ''appdir/prefix''/template-''viewtype''.lsp

It repeats through each upper level of prefix until prefix is "nil".
Returns the first found lsp, or false.

=== find_view ( appdir, prefix, controller, action, viewtype ) ===

''(internal function)'' Looks for a .lsp (Lua Server Page) view. Looks for the first matching:

# ''appdir/prefix/controller-action-viewtype''.lsp
# ''appdir/prefix/controller-viewtype''.lsp

=== has_view ( self ) ===

''(internal function)'' Returns true if there is a .lsp (Lua Server Page) view specifically for this action.

=== dispatch_component ( str, clientdata, suppress_view ) ===

''(internal function)'' This function is made available to each view file to allow loading of components (sub-actions). It will launch a new controller/action, passing any clientdata, and return the result of the action. If ''suppress_view'' is not true, it will display the component action's view.

=== create_helper_library ( self ) ===

''(internal function)'' Creates a helper library to be passed to each view. Currently, the only function passed is ''dispatch_component'', but in the future functions that need access to ''self'' may be added.

=== view_resolver ( self ) ===

''(internal function)'' Returns a function that will run the template and view. The template is found with ''find_template'', and the view with ''find_view''. Also generates and returns the view parameters besides viewtable.

=== mvc.on_load ( self, parent ) ===

Sets up ''self.conf'' and ''self.sessiondata''. If the client reports a session id, this function will attempt to load the existing session. If not, a new session is created and ''build_menus'' is called to fill in the permissions and menu tables.

=== mvc.on_unload ( self ) ===

Saves the session data before returning. This function will be called after the action is complete and before the view is displayed.

=== exception_handler ( self, message ) ===

If ''message'' is a table and ''message.type''="redir", then issues a 302 Moved to the client, with the target of the redirect being ''message.prefix/message.controller/message.action message.extra'' If found while displaying a component, an error message is output instead.

If the ''message.type'' is "redir_to_referrer", then issues a 302 Moved to the client, with the target of the redirect being the referring page.

If the ''message.type'' is "dispatch", then calls the parent (mvc.lua) exception handler.

Otherwise, calls the parent (mvc.lua) exception handler.

=== dispatch ( self, prefix, controller, action ) ===

Overload of the MVC ''dispatch'' function to check permissions (and redirect if not allowed), handle components, pass more data to the view, and allow display of views without actions. Controller actions are executed in a protected xpcall.

# Checks if user has permission to access this controller/action by calling ''check_permission''
## If no permission to action, redirects to default action
## If no permission to controller, redirects to default controller/action
# If the controller/action exists
## Creates a '''self:new ( prefix .. controller)''' mvc object
## Runs any existing ''worker.mvc.pre_exec'' function
## Runs the ''worker.'''action'''''
## Runs any existing ''worker.mvc.post_exec'' function
## Calls ''destroy'' to destroy the mvc object
# Gets the view function and parameters from ''view_resolver''
# Executes the view with the result of the ''worker.'''action'''''
# Returns the result of the ''worker.'''action'''''

If an error occurs, an exception_handler function is run. If possible, the exception handler of the new mvc object is run, otherwise ''self::exception_handler'' function handles the error. If an exception occurs after creating the new mvc object, ''mvc.on_unload'' is guaranteed to run, but ''mvc.post_exec'' is not.

=== redirect ( self, str ) ===

Cause a redirect to the specified path. If a prefix or controller is not found in the string, use the current prefix and/or controller. If an action is not found in the string, use the default action. The actual redirection is defined in ''exception_handler''. This function can be called by an action to redirect to another action rather than display it's own view. Note: The controller post_exec function will not be called after redirect is called.

=== redirect_to_referrer ( self ) ===

If we've acted on a command, put the result in the session and cause a redirect to the referring page (assuming it's different). If not, check to see if there is a result in the session from a previous redirection. The actual redirection is defined in ''exception_handler''. This function should be called by an action to redirect to the referring page rather than display it's own view. This allows actions that are used as components to display the container view after completing the requested command, and then display the result when reloaded as a component. Note: The controller post_exec function will not be called if redirect_to_referrer causes a redirection.

=== logevent ( message ) ===

Writes a message to the acf log file.

[[Category:ACF]] [[Category:Lua]]

ACF acf www example

2016-03-07T12:30:42Z

Fab: Reverted edits by RuthHughes (talk) to last revision by Ttrask

{{ Obsolete }}
= Set the hostname with a web interface =

In this example we will use the hostname-model.lua and hostname-controller.lua from the previous example to set the hostname using the acf web interface.

For this example, we will assume you have root access on the linux box you are running on (preferably an alpine box!)

== Use the existing code ==

We should have '''mvc.lua'' in the current directory, with the controller and model in ''helloworld/app'' The Controller and Model look the same as the end of the mvc.lua example, except we've taken out the on_load, pre_exec, post_exec, and on_unload methods.

=== helloworld/app/hostname-controller.lua ===
-- hostname controller code

module ( ... , package.seeall )

create = function (self )
return self.model.update(self.clientdata.hostname)
end

read = function (self)
return self.model.read()
end

update = create

delete = function (self )
self.clientdata.hostname=""
return self.worker:create()
end

=== helloworld/app/hostname-model.lua ===
-- Model functions for retrieving / setting the hostname
module ( ..., package.seeall )

-- All functions return a table with
-- A value, the type of the value, and a message if there was an error

local hosttype={ type="string" }

update= function ( name )
-- Check to make sure the name is valid

if (name == nil) then
hosttype.msg = "Hostname cannot be nil"
elseif (#name > 16) then
hosttype.msg = "Hostname must be less than 16 chars"
elseif (string.find(name, "[^%w%_%-]")) then
hosttype.msg = "Hostname can contain alphanumerics only"
end

-- If it is, set the hostname
if (hosttype.msg == nil ) then
local f = io.open("/etc/hostname", "w")
if f then
f:write(name .. "\n")
f:close()
end
f = io.popen ("/bin/hostname -F /etc/hostname")
f:close()
return read()
-- Otherwise, return the error message
else
hosttype.value = name
return hosttype
end
end

read= function ()
local f = io.popen ("/bin/hostname")
local n = f:read("*a") or "none"
f:close()
n=string.gsub(n, "\n$", "")
hosttype.value = n
return (hosttype)
end

== Get and configure ACF ==

1. Grab a copy of all the acf code and support libraries from svn and copy into an "/usr/share/acf" directory

svn export svn://svn.alpinelinux.org/acf/core/trunk /usr/share/acf

2. Copy the acf.conf file to /etc/acf

cp /usr/share/acf/acf.conf /etc/acf/acf.conf

3. Start the web server

You'll need haserl, lua, and mini_httpd installed to run acf. If not already done, please install them.

Start mini_httpd (by hand for now)

mini_httpd -d /usr/share/acf/www -c 'cgi-bin/**' start

4. Move your hostname model and controller

mkdir /usr/share/acf/app/sample
mv helloworld/app/hostname-* /usr/share/acf/app/sample/

5. Create a new view template, which is a "lua server page" Create the file as ''/usr/share/acf/app/sample/hostname-html.lsp''

<? local form = ... ?>
<h1>Hostname</h1>

<form action="update" method=post>
The Hostname is now <input name=hostname value="<?= form.value ?>"

input type=submit value=Submit>
</form>

6. Create a new roles file, which gives all users permission to access your actions. Create the file as ''/usr/share/acf/app/sample/hostname.roles''

GUEST=hostname/read,hostname/update

== Try the app ==

point your browser to your host/cgi-bin/acf/sample/hostname/read

You should now be able to update the hostname using the web interface, and your ''existing'' model and controller.

[[Category:ACF]]

ACF core principles

2016-03-07T12:30:38Z

Fab: Reverted edits by RuthHughes (talk) to last revision by Ttrask

While the mvc.lua code provides a generic framework for any lua "mvc"-based application, "acf" is the component that makes the mvc.lua framework into a web configuration Application. Some ideas and rationales for application-wide settings are discussed here.

= Use of ''cfe'' =

A ''cfe'' ('''C'''onfiguration '''F'''ramework '''E'''ntity) is a way to pass data between a model, controller and view in a common way. There are many ways to do this (e.g. closures, AKClass); use of cfe is an arbitrary decision just to keep development moving forward.

A cfe is a table with some fields guaranteed to exist. It is also a way to abstract user-modifiable data from view-centric HTML input types. ACF isn't necessarily web-only. With a different controller and views, it could be cli (or gui?!). The acf-cli application is an example of this.

== Fields in all cfes ==

cfe's are constructed from a function in <tt>mvc.lua</tt> that returns an anonymous table with the following fields

{| border=1
! Field !! Default !! Description
|-
|value || "" || The value of the cfe (e.g. the IP address, hostname, password, etc.)
|-
|type || "text" || The type of entity (see below)
|-
|label || "" || User-readable label for the value
|}

The reason for having these fields pre-defined is to allow models, controllers and views to use the indexes without having to first check if they exist. For example the entity will always have a value and type.

cfe's can have other fields. Some common fields that may, or may not, be present:

{| border=1
! Field !! Description
|-
|errtxt || Text explaining why validation failed
|-
|option || A list of options for this value
|-
|descr || User-readable description for the value
|-
|seq || Numeric sequence suggesting display order for cfe's in a group or form
|-
|default || Default value (can be displayed to user)
|-
|readonly || If present, indicates that the information is to be displayed, but not editable, typically used in forms
|}

To set fields or overwrite field defaults, specify a table in the argument list to the cfe constructor:

:mycfe = cfe({label="User", value="asdf", errtxt="Invalid User"})
is equivalent to
:mycfe = {label="User", value="asdf", type="text", errtxt="Invalid User"}

== cfe types ==

The ''type'' field of a cfe can be one of the following:

{| border=1
! type !! Description !! Modifiers
|-
| text || a text field, typically one line of text ||
|-
| longtext || a multi-line text field, like a textarea ||
|-
| select || a select list || ''value'' is the currently selected item ''option'' is an array of select options
|-
| multi || a multi-select list || ''value'' is an array of selected items ''option'' is an array of select options
|-
| list || a list || ''value'' is an array of strings
|-
| boolean || true or false ||
|-
| raw || raw binary data ||
|-
| form || a set of cfe's that make up a form || ''value'' is a table of cfe's that make up a form (the table should be name-indexed) ''option'' is the command name to save changes (button name for HTML) ''descr'' or ''errtxt'' may contain the result of a save attempt
|-
| group || a set of cfe's that make up an anonymous group || ''value'' is a table of grouped cfe's (can be used to pass several items to a view) (the table should be name-indexed)
|-
| structure || a Lua table with no further type info ||
|-
| password || a password which should not be readable by a user ||
|-
| hidden || a hidden field typically containing information used by ACF and not visible to a user ||
|}

= The Model defines the object set =

The model is responsible for writing and reading from the running system. The model typically does not need to know which part of a specific acf module it is running under. It is not mandatory that the model be lua "oop" as the rest of the system is. (the model may not have any need to know "self")

Since the model can choose how much or how little of the system to expose, the basic data set should be defined in the model.

[[Category:ACF]]

ACF css

2016-03-07T12:30:34Z

Fab: Reverted edits by RuthHughes (talk) to last revision by Ncopa

= Draft =

This is just a place where I want to write down some notes on css issues for Alpine. 
Don't consider this as a Alpine documentation until/if this heading saids otherwise.

= Design/coding questions =
Feel the need of some back-bone tabs that is general for all (or most) acf-modules. 
This results in that a user 'recognizes' the layout and information on every acf-module. 
This way user easy finds what he is looking for and feels that he doesn't accidentally change something that he doesn't want to change.
== View-files ==
=== Status tab ===
Display information in this order 
'''(H1)'''''(Description of the main function of this program)'''''(/H1)''' 
'''(H2)SYSTEM INFO(/H2)'''
* Status of the current program/process
* Version of program (if applicable)
'''(H3)PROGRAM SPECIFIC(/H3)'''
* ''(Some program specific information)''
* ''(Some program specific information)''
=== Config tab ===
'''(H1)'''''(Description of the main function of this program)'''''(/H1)''' 
''Above information is same for each tab (expert, status, config, whatever).'' 
'''(H2)CONFIGURATION(/H2)'''
'''(H3)GENERAL SETTINGS(/H3)'''
* '''Enable/Disable this process''' [ ]enable [x]disable
* ''(Some general settings)''
* ''(Some general settings)''
'''(H3)'''''(Some other category of settings)'''''(/H3)'''
* ''(Some specific settings)''
* ''(Some specific settings)''
'''(H3)'''''(Some other category of settings)'''''(/H3)'''
* ''(Some specific settings)''
* ''(Some specific settings)''
'''(H2)APPLY CHANGES(/H2)'''
* '''Apply above changes''' [Apply]
=== Expert tab ===
Show the config file(s) in plain text and let the 'expert' modify them as he wants (and hope that the 'expert' knows what he's doing)

= CSS =
== BR ==
I think that the use of BR is not that big. 
Instead you could do...
'''(P)''' your text '''(/P)''' '''(P)''' some other text '''(/P)'''
== H1,H2,H3 ==
These headings are (as most other things) defined by the css. 
By using these you can split your page into sections that handle different parts of functions or data.
* '''H1''' ''(Main data under the 'main' heading)''
** '''H2''' ''(Data related to the 'main' heading, but is sectioned into a sub-heading)''
*** '''H3''' ''(A sub-heading to previous heading)''

== PRE ==
'''PRE''' is used to display data 'as it comes out from the system'. 
'''PRE''' doesn't change the linefeed and other things.
== DL,DT,DD ==
When you want to present some data, your are limited to the '''(DIV ID=content)'''. 
Below you are supposed to use '<' and '>' instead of '(' and ')' when you use P, DL, DD or some other html tag. 
Often you present some information on a row, and on the next row you present the next information. 
* If you want to use 100% of available width you could...
'''(P)''' Whatever your text is that you want to present '''(/P)'''

In some cases you want to specify some description on what your data is (like a heading). Then you could...
* Use DT/DD fileds...
'''(DT)'''The value is:'''(/DT) (DD)'''1235'''(/DD)'''
The use of '''(DL)''' is still not defined. 
By using these above types of presenting data, you let the style sheet (css) present your output in a nice way. 
This also makes it possible to add new style sheets when needed. 
Try not to specify a width or other graphical settings in your view-files. Let the css do it for you (and if the css can't handle it for the moment... then we just fix the css)

== DIV ==
* ID
** This attribute assigns a name to an element.
** This name must be unique in a document
*** [http://www.w3.org/TR/html4/struct/global.html#h-7.5.2 w3.org]
* CLASS
** This attribute assigns a class name or set of class names to an element.
** Any number of elements may be assigned the same class name or names.
** Multiple class names must be separated by white space characters.
*** [http://www.w3.org/TR/html4/struct/global.html#h-7.5.2 w3.org]

=== DIV CLASS=... ===

==== leader/tailer(class) ====
Would it be a good idea to have a leader/tailer class inside every (DIV ID)?
* leader(class)
* Main content
* tailer(class)
The leader/tailer(class) could be used ether to display information or could be used for graphical changes (with the CSS)?!?!

==== hide(class) ====
By adding class='hide' to some object, you could hide it.

==== mute(class) ====
The '''mute''' class could be used to show "quiet" items that aren't quite hidden. Perhaps smaller font, greyed out, etc... "extra info".

==== header(class) ====
Could be used to decorate header rows in a table (e.g. colored background and bold text).

==== selected(class) ====
This could mark tabs/menus which is selected/current.

==== error(class) ====
This could mark text/background/whatever so your attention is drawn to this. 
Could indicate that you are forced to take some action or change something.

==== attention(class) ====
This could mark text/background/whatever so your attention is drawn to this.

=== DIV ID=... ===
==== header (id) ====
[Skip to main content] 
Alpine Linux ''(or maybe hostname)'' 

==== main (id) ====

===== nav (id) =====
Navigation (main) 
Where we have been 

===== subnav (id) =====
Navigation (subnav) 

===== content (id) =====
Main content of the page. 
This is where the interesting information is shown. 

==== footer (id) ====
Made with care by webconf

=== Graphical presentation ===
-------------------
/ header
| -----------------
| / leader (class)
| \ [Skip to main content]
| -----------------
| (H1)Alpine Linux(/H1) ''(or maybe hostname)''
|
| -----------------
| / trailer (class)
| \
| -----------------
\
-------------------
-------------------
/ main
| -----------------
| / leader (class)
| \
| -----------------
| -----------------
| / nav
| | ---------------
| | / leader (class)
| | \
| | ---------------
| | Navigation (main) (and its items)
| |
| | ---------------
| | / trailer (class)
| | \ Where we have been
| | ---------------
| \
| -----------------
| -----------------
| / subnav
| | ---------------
| | / leader (class)
| | \
| | ---------------
| | Navigation (subnav) (and its items)
| |
| | ---------------
| | / trailer (class)
| | \
| | ---------------
| \
| -----------------
| -----------------
| / content
| | ---------------
| | / leader (class)
| | \
| | ---------------
| | Main content of the page.
| |
| | ---------------
| | / trailer (class)
| | \
| | ---------------
| \
| -----------------
| -----------------
| / footer
| | ---------------
| | / leader (class)
| | \
| | ---------------
| | Made with care by webconf
| |
| | ---------------
| | / trailer (class)
| | \
| | ---------------
| \
| -----------------
| -----------------
| / tailer (class)
| \
| -----------------
\
-------------------

[[Category:ACF]]

ACF how to write

2016-03-07T12:30:31Z

Fab: Reverted edits by RuthHughes (talk) to last revision by Ttrask

=How to Write an ACF=

For some examples please see the Web Configuration Framework projects in the Alpine Linux git repository

http://git.alpinelinux.org/

*acf-unbound - a simple ACF to control a service
*acf-awall - a slightly more complicated ACF for a firewall
*acf-provisioning - a complicated database application based on ACF
*...

==From <nil> to a running ACF example application==

===Step 1 - The Programming Language===
* ACF uses lua as its programming language. Have a look at [http://www.lua.org/ lua.org] before starting.

===Step 2 - The Application Environment===
* Setup the ACF web application by running ''setup-acf''

===Step 3 - Create A Development Directory===
* In your user home create a directory for your application (e.g. mkdir ~/myapp)
* And cd into it (e.g. cd ~/myapp)

===Step 4 - MVC, How Does It Affect My Coding?===
ACF is an MVC based framework. What does this mean to you? Your application is separated into three layers: Model, View, Controller - each of which may have one or more files.
* Controller: The event dispatcher. Most of the controller functionality is handled by the ACF mvc.lua code and some standard controllers (such as acf_www-controller.lua or acf_cli-controller.lua). For the controller layer of your new ACF package, you must export one lua function per action in a lua module named 'myapp-controller.lua'. The ACF controller code will interpret the user interaction to load your new controller and fire the appropriate action - the same-named function in your controller will be called.
* View: The view layer defines what your application will look like. For most actions, such as forms, your application can use the built-in automatic view generation. For others, you can link to standard views which are included in the acf-core package. For other actions, such as lists of data, you may create view files, each presenting a dynamic HTML page with only as much code as necessary to display the data you receive from the controller.
* Model: The 'real work' is done in the Model (e.g. modifying config files, starting/stopping services etc.). Each action exported by your controller will call into model functions to retrieve data and carry out actions.

===Step 5 - The Example Files To Start With===
Now let us have a look at the files we need to place into our application directory:

* config.mk
* Makefile
* myapp-controller.lua
* myapp-model.lua
* myapp.roles
* myapp.menu

'''config.mk:'''
For use with the Makefile. Just copy/paste it. We will look at it later.
prefix=/usr
datadir=${prefix}/share
sysconfdir=${prefix}/etc
localstatedir=${prefix}/var
acfdir=${datadir}/acf
wwwdir=${acfdir}/www
cgibindir=${acfdir}/cgi-bin
appdir=${acfdir}/app
acflibdir=${acfdir}/lib
sessionsdir=${localstatedir}/lib/acf/sessions

'''Makefile:'''

The Makefile is called to install our ACF application so that we can see it working.
APP_NAME=myapp
PACKAGE=acf-$(APP_NAME)
VERSION=0.1

APP_DIST= \
myapp* \

EXTRA_DIST=README Makefile config.mk

DISTFILES=$(APP_DIST) $(EXTRA_DIST)

TAR=tar

P=$(PACKAGE)-$(VERSION)
tarball=$(P).tar.bz2
install_dir=$(DESTDIR)/$(appdir)/$(APP_NAME)

all:
clean:
rm -rf $(tarball) $(P)

dist: $(tarball)

install:
mkdir -p "$(install_dir)"
cp -a $(APP_DIST) "$(install_dir)"

$(tarball): $(DISTFILES)
rm -rf $(P)
mkdir -p $(P)
cp $(DISTFILES) $(P)
$(TAR) -jcf $@ $(P)
rm -rf $(P)

# target that creates a tar package, unpacks is and install from package
dist-install: $(tarball)
$(TAR) -jxf $(tarball)
$(MAKE) -C $(P) install DESTDIR=$(DESTDIR)
rm -rf $(P)

include config.mk

.PHONY: all clean dist install dist-install

'''myapp-controller.lua:'''
-- the myapp controller
local mymodule = {}

mymodule.default_action = "myaction"

mymodule.myaction = function(self)
-- self.clientdata contains the user data
-- self.model points to our model
-- use the helper function to implement our form
return self.handle_form(self, self.model.getdata, self.model.setdata, self.clientdata, "Submit", "Edit data", "Data Submitted")
end

return mymodule

'''myapp-model.lua:'''
-- acf model for myapp
local mymodule = {}

local cfgfile = "/tmp/myfile"

-- This function returns a cfe (table of values) containing the file's
-- value as a string. If the file does not exist, we'll
-- simply return "" (an empty string, but NOT nil)
mymodule.getdata = function(self, clientdata)
local retval = cfe({ type="group", value={}, label="Data" })
retval.value.data = cfe({ type="longtext", label="Data" })

local fileptr = io.open(cfgfile, "r")
if fileptr ~= nil then
retval.value.data.value = fileptr:read("*a") or ""
fileptr:close()
end

return retval
end

-- This function will write new contents into our file
-- The newdata parameter receives the same cfe as returned by getdata, now with the user data filled in
mymodule.setdata = function(self, newdata, action)
fileptr = io.open( cfgfile, "w+" )
if fileptr ~= nil then
fileptr:write(newdata.value.data.value)
fileptr:close()
else
newdata.errtxt = "Failed to save data"
end
return newdata
end

return mymodule

'''myapp.roles:'''
GUEST=myapp:myaction

'''myapp.menu:'''
# Cat Group Tab Action
Test MyApp MyAction myaction

===Step 6 - What Does It Do?===
This program just displays a <textarea> box and a "Submit" button. The user can enter text that is saved into a file once he presses "Submit".

====In Depth====
Now let us have a closer look at the different files' contents:

=====myapp-controller.lua=====
The controller is an event dispatcher. So, here you define all the actions that the user can call or that are defined in the menu. Each action is a separate function that will receive ''self'' as the only parameter.

In our case the action is ''myaction'' - a simple form.

This function can call the ''model's'' functions to update and/or retrieve data (e.g. self.model.getdata()).

Anything that this function returns will be passed on to the ''view''

=====myapp-model.lua=====
The functions defined in here can be accessed by the controller to update/set/retrieve data, start/stop services, basically do any 'real work'.

In our case, we have implemented the getdata/setdata functions required for a form.

The getdata function receives a copy of 'self', a clientdata table, and a string containing the submit action. It will generate a 'CFE' table defining the form and including the current data.

The setdata function is only called when the form is submitted, and it receives a copy of 'self' and the updated form 'CFE' now containing the submitted data. The setdata function will attempt to perform the action, returning the same form 'CFE'. If there is an error, it will fill in the errtxt field of the 'CFE'.

=====myapp.roles=====
This file determines which users have access to which controllers and views. A separate ''roles'' file is generally defined for each ACF. The format of the file is as follows:
group=controller:action[,controller:action]
Each line defines controller:action combinations that are permitted for a particular group. '''GUEST''' is a special group to which all users, including anonymous users, are members.

=====myapp.menu=====
In this file you define:
* '''The Category''' in which a menu entry for your program will appear
* '''The Group''' menu name under Category for this controller
* '''The Tab''' name on the controller page
* '''The Action''' with-in your controller that will be called once the user clicks on the menu entry or tab defined by Category, Group, and Tab.

===Step 7 - How To Get It Going?===
Once you have completed all the above mentioned steps, go on with:
* sudo make install (this will install your app)
* point your browser to https://ip-of-your-dev-host/

===More Info===
====Where is the View?====
The above example does not contain any code for a view. So, how is the action getting displayed?

For every action that you define in myapp-controller.lua, you can define a separate view file named: myapp-''action''-html.lsp

If there is no view file for a specific action, the application will look for a generic view file for the controller named: myapp-html.lsp

If that file does not exist, the ACF controller will attempt to display the 'CFE' using the built-in library functions. This works well for forms, and is what allows us to display our view here.

Here is a ''view'' file that displays our action using the built-in library functions. It looks exactly the same as when no view exists.

'''myapp-myaction-html.lsp:'''
<%
local form, viewlibrary, page_info, session = ...
htmlviewfunctions = require("htmlviewfunctions")

htmlviewfunctions.displayitem(form, page_info)
%>

The view receives the data to be displayed from the ''controller''. The view has access to the table returned by the controller action along with a helper library, a table of page information, and the session data ''(see the second line)''. The view can also load other libraries, but it should not directly access the ''controller'', ''model'', or any global variables.

====How to exchange data between model-view-controller?====
To exchange data between model, view, and controller ACF uses ''Configuration Framework Entities (CFEs)''.

Please see [[ACF_core_principles]] for further details on CFEs.

[[Category:ACF]]

ACF mvc.lua example

2016-03-07T12:30:24Z

Fab: Reverted edits by RuthHughes (talk) to last revision by Ttrask

= Set the hostname with mvc.lua =

In this example we will create a simple hostname-setting command-line application using mvc.lua. Once the controller/model are built, you can use ''the same code'' to set the hostname via the web with a web-based application controller.

For this example, we will assume you have root access on the linux box you are running on (preferably an Alpine Linux box!)

== Get the mvc.lua module ==

Get the mvc.lua module from the git repository.

wget http://git.alpinelinux.org/cgit/acf-core/plain/lua/mvc.lua

== Create a model and controller ==

Create a file '''hostname-controller.lua''', defining the functions that an "end user" could run. We will only create one action, edithostname, which will be used to read and update the hostname. Since the action makes changes to the system, it naturally takes the form of a 'form':

=== hostname-controller.lua ===
-- Controller for editing hostname
local mymodule = {}

mymodule.edithostname = function (self)
return self.handle_form(self, self.model.get_hostname, self.model.set_hostname, self.clientdata, "Edit", "Edit Hostname", "Hostname Updated")
end

return mymodule

Create a file '''hostname-model.lua''', defining the model functions to get and set the hostname. We return a cfe table for each function including the form with the one entry for hostname:

=== hostname-model.lua ===
-- Model functions for retrieving / setting the hostname
local mymodule = {}

-- Create a cfe defining the form for editing the hostname and containing the current value
mymodule.get_hostname = function(self, clientdata)
local retval = cfe({ type="group", value={}, label="Hostname" })

-- Warning - io.popen has security risks, never pass user data to io.popen
local f = io.popen ("/bin/hostname")
local n = f:read("*a") or "none"
f:close()
n=string.gsub(n, "\n$", "")

retval.value.hostname = cfe({ value=n, label="Hostname" })

return retval
end

-- Set the hostname from the value contained in the cfe created by get_hostname
mymodule.set_hostname = function(self, hostnameform, action)
local success = true

-- Check to make sure the name is valid
if (hostnameform.value.hostname.value == "") then
success = false
hostnameform.value.hostname.errtxt = "Hostname must not be blank"
elseif (#hostnameform.value.hostname.value > 16) then
success = false
hostnameform.value.hostname.errtxt = "Hostname must be 16 characters or less"
elseif (string.find(hostnameform.value.hostname.value, "[^%w%_%-]")) then
success = false
hostnameform.value.hostname.errtxt = "Hostname can contain alphanumerics only"
end

-- If it is valid, set the hostname
if ( success ) then
local f = io.open("/etc/hostname", "w")
if f then
f:write(hostnameform.value.hostname.value .. "\n")
f:close()
end
-- Warning - io.popen has security risks, never pass user data to io.popen
f = io.popen ("/bin/hostname -F /etc/hostname")
f:close()
else
hostnameform.errtxt = "Failed to set hostname"
end

return hostnameform
end

return mymodule

== Optionally test the model code (without mvc.lua) ==

If you want, you can create a '''test.lua''' script to validate the model code works on its own:

=== test.lua ===
require("mvc") -- Needed for cfe function definition
m=require("hostname-model")

local form = m.get_hostname()
form.value.hostname.value = arg[1] or ""
form = m.set_hostname(nil, form)

if form.errtxt then
print("FAILED: "..form.value.hostname.errtxt or form.errtxt)
end
form = m.get_hostname()
print(form.value.hostname.value)

You can then test this with:

#lua test.lua "Alpine"
Alpine

#lua test.lua "Invalid Name"
FAILED: Hostname can contain alphanumerics only
Alpine

== Add the package to the ACF framework ==

To make the model and controller work within the ACF mvc.lua framework, we must do several things.

1. Install the ACF core package:

apk add acf-core

Optionally, you can add the entire web-based ACF framework:

setup-acf

2. Modify the ACF configuration file to look in /etc/acf/app/ for additional packages. Edit the /etc/acf/acf.conf file to add the ''/etc/acf/app/'' directory to the ''appdir'' comma-separated list:

appdir=/etc/acf/app/,/usr/share/acf/app/

3. Move the model and controller to the new package directory. We will call the package "test":

mkdir -p /etc/acf/app/test
mv hostname-*.lua /etc/acf/app/test

4. Test the new package using the acf-cli application:

# acf-cli /test/hostname/edithostname
result = {}
result["label"] = "Edit Hostname"
result["option"] = "Edit"
result["type"] = "form"
result["value"] = {}
result["value"]["hostname"] = {}
result["value"]["hostname"]["label"] = "Hostname"
result["value"]["hostname"]["type"] = "text"
result["value"]["hostname"]["value"] = "Alpine"
# acf-cli /test/hostname/edithostname hostname=test submit=true
result = {}
result["descr"] = "Hostname Updated"
result["label"] = "Edit Hostname"
result["option"] = "Edit"
result["type"] = "form"
result["value"] = {}
result["value"]["hostname"] = {}
result["value"]["hostname"]["label"] = "Hostname"
result["value"]["hostname"]["type"] = "text"
result["value"]["hostname"]["value"] = "test"

Note that the first case read the existing hostname and the second case updated it. The output of the acf-cli application is a serialized version of the cfe form, which is good for testing but not too useful in real life.

== Enable the package in the ACF web interface ==

1. Add the web-based ACF framework:

setup-acf

2. Configure all users to have access to the new hostname action. Edit "/etc/acf/app/test/hostname.roles" file and add GUEST permission for the edithostname action:

echo "GUEST=hostname/edithostname" > /etc/acf/app/test/hostname.roles

The new action should now be visible by browsing to ''https://IP-of-host/cgi-bin/acf/test/hostname/edithostname''. Obviously you might want to reconsider providing GUEST access to this action, because this allows unauthenticated users to modify your hostname.

3. Add the new hostname action to the ACF menu. Edit "/etc/acf/app/test/hostname.menu" file and add a menu item:

echo "Test Hostname Edit edithostname" > /etc/acf/app/test/hostname.menu

You will need to log off from the ACF interface (or delete the session cookie) before the new menu item will be visible.

== Make an MVC based application ==
You have two options for creating an MVC based application of your own.

1. Use the ''dispatch'' function. This is the method used by the web interface and the acf-cli application. The action to be dispatched is passed in a string format ''/prefix/controller/action'' and the input values are passed in as a clientinfo table. Output is written to stdout.

2. Use the ''new'' function to load the desired controller and then directly call the controller actions. For handling forms and user input, the application will call the action once to retrieve the form cfe, then fill in the desired input values into the cfe and call the action again to submit the form and perform the desired action. The MVC application is responsible for any user interaction and display of the results.

=== Use the Dispatch method ===
Todo

=== Use the New method ===
Todo

{{Obsolete}}
4. Create a dispatch wrapper program, named '''helloworld.lua''' in the current directory:

-- Simple CLI based mvc application

-- this is to get around having to store
-- the config file in /etc/helloworld/helloworld.conf
ENV={}
ENV.HOME="."

-- load the module
require("mvc")

-- create an new "mvc object"
MVC=mvc:new()

-- load the config file so we can find the appdir
MVC:read_config("helloworld")

-- create an application container
APP=MVC:new("app")

-- dispatch the request
APP.clientdata.hostname=arg[2]
APP:dispatch( "", "hostname", (arg[1] or ""))

-- destroy the mvc objects
APP:destroy()
MVC:destroy()

This application loads the "mvc.lua" framework, creates an mvc "object" named "MVC", then reads the helloworld.conf file to find out where the app dir is (helloworld/app/). It then loads the '''app-controller.lua''' into a new "application level" object named '''APP'''. Finally, it sets the clientdata and dispatches the hostname-controller/model pair.

5. Test the application:
# hostname
Alpine
# lua helloworld.lua no-such-function foo
The following unhandled application error occured:

controller: "hostname" does not have a "no-such-function" action.
# hostname
Alpine

# hostname
Alpine
# lua helloworld.lua update Alline
Your controller and application did not specify a view resolver.
The MVC framework has no view available. sorry.
# hostname
Alline

Note in the second case the hostname ''was'' changed, although the application does not know how to report success.

== Create a view resolver and view formatter ==

The view resolver is a function that returns a function that processes the view. The returned function receives input from the controller and generates the output to be displayed.

We will build a very simple view resolver and view processor for our application. Add this to the end of '''helloworld/app/hostname-controller.lua'''

local private = {}

private.view = function (f)
if (f.msg) then
print( (f.value or "") .. " is not a valid hostname ")
else
print ("Hostname is currently " .. f.value )
end
end

view_resolver = function (self)
return private.view
end

Now we can test:

# lua helloworld.lua update "1 2 3"
1 2 3 is not a valid hostname
# lua helloworld.lua update
is not a valid hostname
# lua helloworld.lua update Alpine
Hostname is currently Alpine

But we have two problems:

1. We now have to make a view resolver and view function for every controller. If we add a ''date'' setting controller, we'll have to make a view resolver and view function for it, and so on.

2. Perhaps more importantly, view_resolver is now an "action" in our appliction. Recall that invalid actions are captured, but try this:

# lua helloworld.lua no_such_action Alpine
The following unhandled application error occured:

controller: "hostname" does not have a "no_such_action" action.

# lua helloworld.lua view_resolver Alpine
The following unhandled application error occured:

./helloworld/app/hostname-controller.lua:27: attempt to index local 'f' (a function value)
stack traceback:
./helloworld/app/hostname-controller.lua:27: in function 'viewfunc'
./mvc.lua:139: in function <./mvc.lua:90>
[C]: in function 'xpcall'
./mvc.lua:90: in function 'dispatch'
helloworld.lua:23: in main chunk
[C]: ?

Because view_resolver is an action in the worker table, the '''mvc.lua''' runs it; but it returns a function, not a table, and causes an unhandled exception in the view.

== Move the view resolver to the application level ==

The solution to both problems is to move the view resolver and the view function out of the controller's worker table, into the next higher level, in this case, the application's worker table:

1. Delete the private.view and view_resolver functions from '''helloworld/app/hostname-controller.lua'''

2. Add the following to '''helloworld/app/app-controller.lua'''

local private = {}

private.view = function ( controller, action, viewtable )
io.write(string.format("Controller: %s Action: %s\n",
controller or "", action or ""))
io.write ("Returned a table with the following values:\n")

for k,v in pairs(viewtable) do
io.write(string.format("%s\t%s\n", k, v))
end
end

view_resolver = function (self)
return function (viewtable)
return private.view (self.conf.controller, self.conf.action, viewtable)
end
end

This creates a more "generic" view, but one that will work for any controller - not just '''hostname'''.

Now things work as they should:

# lua helloworld.lua update "one two"
Controller: hostname Action: update
Returned a table with the following values:
value one two
type string
msg Hostname can contain alphanumerics only

# lua helloworld.lua view_resolver "Alpine"
The following unhandled application error occured:

controller: "hostname" does not have a "view_resolver" action.

= mvc load & exec special functions =

The '''mvc.lua''' module has a provision for executing code on module load, prior to executing the controller's action, just after executing the controller's action, and on module unload.

This is done with the mvc table in the controller. To demonstrate, let's add a few functions to '''helloworld/app/app-controller.lua'''

mvc = {}
mvc.on_load = function (self, parent)
print ("This is the app controller's on_load function")
end

mvc.pre_exec = function (self)
print ("This is the app controller's pre_exec function")
end

mvc.post_exec = function (self)
print ("This is the app controller's post_exec function")
end

mvc.on_unload = function (self)
print ("This is the app controller's on_unload function")
end

Now running our script shows when the functions get called:

# lua helloworld.lua update "Alpine"
This is the app controller's on_load function
This is the app controller's pre_exec function
This is the app controller's post_exec function
Controller: hostname Action: update
Returned a table with the following values:
value Alpine
type string
This is the app controller's on_unload function

We can add mvc functions to a specific controller, as well. Add this to '''helloworld/app/hostname-controller.lua'''

mvc = {}
mvc.on_load = function (self, parent)
print ("This is the hostname controller's on_load function")
end

mvc.pre_exec = function (self)
print ("This is the hostname controller's pre_exec function")
end

mvc.post_exec = function (self)
print ("This is the hostname controller's post_exec function")
end

mvc.on_unload = function (self)
print ("This is the hostname controller's on_unload function")
end

And this happens:

# lua helloworld.lua update "Alpine"
This is the app controller's on_load function
This is the hostname controller's on_load function
This is the hostname controller's pre_exec function
This is the hostname controller's post_exec function
This is the hostname controller's on_unload function
Controller: hostname Action: update
Returned a table with the following values:
value Alpine
type string
This is the app controller's on_unload function

Note that both the ''app'' and ''hostname'' '''on_load''' and '''on_unload''' functions were run, but only the ''hostname'' '''pre_exec''' and '''post_exec''' functions ran. This is because the pre and post exec functions are run as part of the "action", and the '''dispatch''' function looks in the lowest-level controller for the pre/post_exec function. Since ''hostname'' now defines those functions, it runs them.

To run both the ''hostname'' and ''app'' pre_exec function, you must arrange for the ''hostname'' pre_exec function to call it's parent pre_exec:

mvc = {}
mvc.on_load = function (self, parent)
print ("This is the hostname controller's on_load function")
mvc.parent_pre_exec = parent.worker.mvc.pre_exec
end

mvc.pre_exec = function (self)
mvc.parent_pre_exec (self)
print ("This is the hostname controller's pre_exec function")
end

[[Category:ACF]] [[Category:Lua]]

ACF mvc.lua reference

2016-03-07T12:30:21Z

Fab: Reverted edits by RuthHughes (talk) to last revision by Ttrask

== mvc.lua function reference ==

This lua module provides the basics for creating an mvc application. It is patterned
loosely after the Ruby on Rails pattern - but much more simplistic.

The general pattern is to use the mvc '''new''' function to create a set of tables,
and then use '''new'' within those tables to create sub "objects". By using
metatable .__index methods, function references flow up through the parent tables.

=== new( self, modname ) ===

Returns 3 values: an ''mvc'' table and 2 booleans ( true or false if the ''modname''-controller and ''modname''-model.lua were loaded)

The ''mvc'' table contains:

{|
! table !! used for !! comments !! .__index points to
|-
|conf
|configuration items
|only created if a ''conf'' table does not exist in a parent
| n/a
|-
|clientdata
|data sent from the client
|only created if a ''clientdata'' table does not exist in a parent
| n/a
|-
|worker
|the "controller" methods
|if '''modname''' is given, then '''''modname'''-controller.lua'' module is loaded into this table. Otherwise, an empty table is returned.
|'''self''' (parent mvc object)
|-
|worker.mvc
|special methods run by the mvc dispatch function
|If the '''modname'''-controller.lua module does not initalize a .mvc table, an empty one is created
|'''self.mvc''' (parent mvc object's mvc table)
|-
|model
|the "model" methods
|if '''modname''' is given, then '''''modname'''-model.lua'' module is loaded into this table. Otherwise, an empty table is returned.
|'''worker''' (this mvc object's worker table)
|}

The returned table has a .__index method that points to '''worker''', so this table can
inherit values from the parent table.

If the '''''modname'''-controller.lua'' contains a .mvc.on_load function, the function is run before ''new'' returns.

The .__index metamethods mean that this code will set up inheritance as shown in the diagram:

require("mvc")
MVC=mvc:new()
APP=MVC:new()
controller=APP:new()
subcontroller=controller:new()

If you try to run '''subcontroller.model.somefunction()''', and it does not exist, the inheritance will look for somefunction() in ...

# subcontroller.worker
# controller
# controller.worker
# APP
# APP.worker
# MVC
# MVC.worker

This allows, for instance, the application to set a default method that is available to all child controllers. The reason the model looks to its parent worker table first is that controller methods are usually in the worker table, and models do not normally inherit from each other.

The calling code should be sure to call the ''destroy'' function when done with this object.

=== destroy ( self ) ===

Calls the ''mvc.on_unload'' function, if it exists, to close any resources opened by the object.

=== dispatch ( self, prefix, controller, action, clientdata ) ===

The gateway for executing controller actions in a protected xpcall.

# If no controller specified, use default prefix/controller
# Creates a '''self:new ( prefix .. controller)''' mvc object
# If no action specified, use controller default_action
# runs any existing ''worker.mvc.pre_exec'' function
# runs the ''worker.'''action'''''
# runs any existing ''worker.mvc.post_exec'' function
# gets the view function from ''view_resolver''
# executes the view with the results of the ''worker.'''action'''''
# and calls ''destroy'' to destroy the mvc object

If an error occurs, an exception_handler function is run. If possible, the exception handler of the new mvc object is run, otherwise ''self::exception_handler'' function handles the error. If an exception occurs after creating the new mvc object, ''mvc.on_unload'' is guaranteed to run, but ''mvc.post_exec'' is not.

=== soft_require ( self, modname ) ===

Looks for '''''modname'''.lua'' in ''self.conf.appdir'' and returns the results of a ''require()'' If the '''modname''' does not exist, returns nil.

This function allows modules to be loaded without generating an exception if they do not exist.

=== read_config ( self, modname ) ===

Looks in various places for a '''''modname'''.conf'' file and parses its contents into the '''self.conf''' table.

=== parse_path_info ( string ) ===

Returns 3 strings: a prefix, controller, and action. Given a string in the format of a URI or pathspec, returns the ''basename'' as the action, the last component of the ''dirname'' as the controller, and the
rest as the prefix. Missing components are returned as empty strings.

=== find_view ( appdir, prefix, controller, action, viewtype ) ===

Returns a string with the view filename for this combination of prefix/controller/action/viewtype or nil if no view file exists.

=== create_helper_library ( self ) ===

Returns a table of function pointers to be passed to each view.

=== auto_view (viewtable, viewlibrary, pageinfo, session) ===

This functions is used as the view of last resort. If no view file is found, this function is called to display the CFE resulting from the invoked action. The following 'viewtype's are supported:

* html
* json
* stream
* serialized

=== view_resolver ( self ) ===

Returns a function pointer to display the view, a table of functions made available to the view function, a table containing values of interest to the view, and a table containing the session data. The last three return values are designed to be the last three parameters to the view function pointer.

=== soft_traceback ( self, message ) ===

If called with no arguments, returns a ''debug.traceback'', otherwise returns "message".

=== exception_handler ( self, message ) ===

Prints an error message and then re-asserts the exception. Called if the xpcall in ''dispatch'' has an error.
This is the exception_handler of last resort. The application should provide
a more robust exception handler.

=== cfe ( table ) ===

Returns a table with ''value'', ''type'', and ''label'' values. If an input table is given in the call, those key/value pairs are added as well.
Guarantees the view will not get a "nil" on value, type, or label.
This function is added to the global (_G) environment so it is available to the entire application.

=== logevent ( message ) ===

Logs the message to syslog.

=== handle_clientdata ( form, clientdata ) ===

This is a helper function for controllers to implement forms. It parses the form CFE and applies any changes submitted by the user in clientdata.

=== handle_form ( self, getFunction, setFunction, clientdata, option, label, descr ) ===
This is a helper function for controllers to implement forms. It calls the getFunction to get the form CFE. If the form is submitted, it will call handle_clientdata and the setFunction to submit the form. The form CFE is returned.

[[Category:ACF]] [[Category:Lua]]

ACF packages

2016-03-07T12:30:18Z

Fab: Reverted edits by RuthHughes (talk) to last revision by Ncopa

{{TOC right}}
== Networking ==

Networking related modules.

=== Interfaces (acf-alpine-baselayout) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Local interface management
|}

*Create/Edit/Delete interfaces
*Bring up/down interfaces and restart networking

=== Dialup/PPPoE (acf-ppp) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure Dialup/PPP/PPPoE connectivity
|}

*Create/Edit/Delete peers
*Edit PAP/CHAP configuration

=== Quality of Service (acf-iproute2-qos) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Ready for Beta test
|-
| '''Summary:'''
| Configure Quality of Service settings on each interface
|}

*Enable/Configure/Disable QOS on each interface

=== IPtables (acf-iptables) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Ready for Beta test
|-
| '''Summary:'''
| Configure '''iptables'''.
|}

*Edit configuration (rules-save file)
*Create/Edit/Delete chains and rules

=== Firewall (acf-shorewall) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''shorewall'''.
|}

*Edit configuration
*View logfile

=== DNS (acf-tinydns) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''tinydns'''.
|}

*View current DNS configuration/information
*Create/Edit/Delete domain files
*Per user and per role permissions
*Multiple-instance capable

=== DNScache (acf-dnscache) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''dnscache'''.
|}

*Edit configuration
*Edit allowed clients
*Create/Edit/Delete DNS server entries

=== DNSmasq (acf-dnsmasq) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''dnsmasq'''.
|}

*Edit configuration
*View leases
*View logfile

=== DHCP server (acf-dhcp) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''isc-dhcp'''.
|}

*Edit global settings
*Create/Edit/Delete subnets and hosts
*View leases

=== Chrony (acf-chrony) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''chrony'''.
|}

*Edit configuration
*View logfile

=== NTPD (acf-openntpd) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure timeserver '''openntpd'''.
|}

*Edit configuration
*View logfile

=== IPsec (acf-ipsec-tools) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''ipsec-tools'''.
|}

*Edit configuration
*Upload/View/Delete certificates
*View logfile

=== OpenVPN (acf-openvpn) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Ready for Beta test
|-
| '''Summary:'''
| Configure '''openvpn'''.
|}

*Edit config
*View connected clients
*Manage certificates
*View logfile
*Multiple-instance capable

=== NHRP (acf-opennhrp) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''opennhrp'''.
|}

*Edit configuration

=== Zebra and BGP (acf-quagga) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''quagga''' zebra and bgp functionality.
|}

*View routes
*Edit configuration

=== TCPproxy (acf-tcpproxy) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''tcpproxy'''.
|}

*Edit configuration
*Create/Edit/Delete STMP Proxy entries and files

 

== Applications ==

Application related modules

=== SSH (acf-openssh) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''openssh'''.
|}

*View connections
*Edit configuration
*Edit authorized keys

=== Kerberos (acf-heimdal) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Ready for Beta test
|-
| '''Summary:'''
| Configure '''heimdal'''.
|}

*Obtain/View/Destroy kerberos tickets
*Edit configuration

=== Samba (acf-samba) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''samba'''.
|}

*Edit configuration
*Create/Edit/Delete shares
*Join domain

=== Postgresql (acf-postgresql) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''postgresql'''.
|}

*Setup postgresql
*View logfile

=== Web Proxy (acf-squid) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''squid'''.
|}

*Edit configuration
*Edit user list
*Edit associated files

=== Content Filter (acf-dansguardian) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''dansguardian'''.
|}

*Edit configuration

=== Web Log application (acf-weblog) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Import '''squid''' and '''dansguardian''' logs into a database for auditing.
|}

*Create postgres database
*Manage logfile sources
*Audit blocks and bypasses
*View web viewing activity
*View web usage statistics
*Query database

=== ClamAV (acf-clamav) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Manage '''clamav'''.
|}

*Edit configuration
*View logfile

=== ClamSMTP (acf-clamsmtp) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Manage '''clamsmtp'''.
|}

*Edit configuration
*View logfile

=== Postfix (acf-postfix) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Manage '''postfix'''.
|}

*View/flush mail queue
*Edit configuration
*View logfile

=== Amavis (acf-amavis) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Manage '''amavis'''.
|}

*Edit configuration

=== Dovecot (acf-dovecot) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Manage '''dovecot'''.
|}

*Edit configuration
*View logfile

=== Gross (acf-gross) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Manage '''gross'''.
|}

*Edit configuration
*View logfile

=== Fetchmail (acf-fetchmail) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''fetchmail'''.
|}

*Edit global settings
*Create/Edit/Delete mailbox/domain entries

=== Snort (acf-snort) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''snort'''.
|}

*View alerts
*Edit configuration

=== Asterisk (acf-asterisk) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''asterisk'''.
|}

*Edit configuration

=== Kamailio (acf-kamailio) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''kamailio'''.
|}

*Edit configuration

=== Freeswitch (acf-freeswitch) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| ''Work in progress''
|-
| '''Summary:'''
| Configure '''freeswitch'''.
|}

*Edit configuration

=== Certificate Authority (acf-openssl) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Generate / sign certificates using '''openssl'''.
|}

*Edit configuration
*View/Create/Upload CA certificate
*Edit certificate defaults
*Generate/View/Delete/Approve requests
*View/Download/Renew/Revoke certificates
*Generate and download CRLs

=== Gnats ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| ''Obsolete''
|-
| '''Summary:'''
| Configure '''gnats'''.
|}

*Edit configuration
*Report a bug
*Query problem reports

 

== Storage ==

Storage related modules

=== MDADM (acf-mdadm) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| ''Work in progress''
|-
| '''Summary:'''
| Raid storage.
|}

*Show status

=== LVM (acf-lvm) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| ''Work in progress''
|-
| '''Summary:'''
|
|}

*Show status

== System ==

System/Other related modules

=== General health (acf-alpine-baselayout) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Show status on your running system.
|}

*Show system status
*Show storage status
*Show network status
*Graph network activity
*Show modules status
*Show proc status

=== User Management (acf-core) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| ACF User management
|}

*Edit self
*Create/Edit/Delete ACF users
*View roles for user

=== Roles Management (acf-core) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| ACF Roles management
|}

*View own permissions
*Create/Edit/Delete ACF roles
*View all possible permissions

=== Packages (acf-apk-tools) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Manage system packages ('''apk-tools''')
|}

*View/Delete loaded packages
*View/Install available packages
*Manage package cache
*Manage repositories
*Edit configuration

=== Modules (acf-alpine-baselayout) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Manage system modules
|}

*View loaded modules
*Edit/Reload modules file

=== Init (acf-alpine-baselayout) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Manage system startup with openrc
|}

*View/Edit service runlevels

=== Cron (acf-alpine-baselayout) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Manage periodic jobs ('''cron''')
|}

*Edit configuration
*Create/Edit/Delete periodic jobs

=== System logging (acf-alpine-baselayout) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Configure '''syslog'''.
|}

*Edit configuration

=== Logfiles (acf-alpine-baselayout) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Manage logfiles.
|}

*View/Tail/Download/Delete logfiles

=== Skins (acf-core) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Switch ACF skin
|}

*Select ACF skin

=== Local Backups (acf-alpine-conf) ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| Released
|-
| '''Summary:'''
| Saves your settings to floppy/usb/other media ('''lbu''').
|}

*Show unsaved changes
*Edit configuration
*Commit/Save changes to media
*Select backup archives
*Generate and download overlay

 

== DevTools ==

DevTools is a (set of) ACF(s) that could come in handy when developing ACF.

=== SVN status ===

{| class="FCK__ShowTableBorders"
|-
| '''Status:'''
| ''Obsolete''
|-
| '''Summary:'''
| Different information/functions related to the SVN-tree
|}

*svn status (Shows whats changed since last 'svn update')
*svn diff (Shows difference on your computer and on svn-server)
*svn log (Shows the changelog 1 week back in time)
*svn update (Fetch all available updates)

 

== ToDo ==

=== Diagnostic ===

Stats/Resource use/maybe graphs-rrd. Ability to run ''ping'' command.

[[Category:ACF]]