Recent changes to Home

Home modified by Ingo

Ingo — Fri, 07 Feb 2020 18:31:31 -0000

--- v13
+++ v14
@@ -1,8 +1,8 @@
 [[download url=https://forge.codesys.com/download/tol,wharfie,code//wharfie.deb label="debian package"]]

+[[drone]]
+
 [TOC]
-
-[[drone]]

 [[include ref=IndexMain]]

Home modified by Ingo

Ingo — Fri, 07 Feb 2020 18:30:44 -0000

--- v12
+++ v13
@@ -1,6 +1,8 @@
 [[download url=https://forge.codesys.com/download/tol,wharfie,code//wharfie.deb label="debian package"]]

 [TOC]
+
+[[drone]]

 [[include ref=IndexMain]]

Home modified by Ingo

Ingo — Fri, 07 Feb 2020 14:59:40 -0000

--- v11
+++ v12
@@ -1,3 +1,5 @@
+[[download url=https://forge.codesys.com/download/tol,wharfie,code//wharfie.deb label="debian package"]]
+
 [TOC]

 [[include ref=IndexMain]]
@@ -56,3 +58,30 @@
 These commands are creating tarballs, containing all the source packages, or all the licenses of your system, which were installed through debian packages. This feature makes it very easy to prepare yourself for distributing such an image.

 You will need to be able to provide such packages when you plan to distribute the image as part of a product, as well as when you share it with others in form of a download on the internet. When you publish anything, which contains code that was released under a third party license, you are usually forced to provide at least a list of all those licenses, containing the license text.
+
+# Install
+
+## Debian
+
+Click on the download link at the top of the package.
+
+Install the package on the terminal, using dpkg:
+
+~~~sh
+sudo dpkg -i wharfie.deb
+~~~
+
+## Other distributions
+
+Use SVN to checkout the repository:
+
+~~~
+svn checkout https://forge.codesys.com/svn/tol,wharfie,code/trunk wharfie-code
+~~~
+
+Enter the directory and install the files under /usr/local/
+
+~~~
+cd wharfie
+./install.sh
+~~~

Home modified by Ingo

Ingo — Tue, 19 Nov 2019 06:21:30 -0000

--- v10
+++ v11
@@ -53,6 +53,6 @@
 * LICENSE <filename>
 * SOURCE <filename>

-These commands are creating tarballs, containing all the source packages, or all the licenses of your system, which where installed through debian packages. This feature makes it very easy to prepare yourself for distributing such an image.
+These commands are creating tarballs, containing all the source packages, or all the licenses of your system, which were installed through debian packages. This feature makes it very easy to prepare yourself for distributing such an image.

-You will need to be able to provide such packages when you plan to distribute the image as part of a product, as well as when you share it with others in form of a download on the internet. When you publish anything, which contains code that was released under a third party license, you are often forced to provide a list of all those licenses, containing the license text.
+You will need to be able to provide such packages when you plan to distribute the image as part of a product, as well as when you share it with others in form of a download on the internet. When you publish anything, which contains code that was released under a third party license, you are usually forced to provide at least a list of all those licenses, containing the license text.
</filename></filename>

Home modified by Ingo

Ingo — Sat, 20 Jul 2019 18:35:25 -0000

--- v9
+++ v10
@@ -8,7 +8,9 @@

 While "docker" is focusing on scalable web services, "wharfie" is focusing on embedded linux systems.

-With "wharfie" you can easily build a root filesystem, based on the Debian distribution from scratch. You can then configure it in an appropriate way. This whole configuration, you don't do at the living system, but you describe this like a recipe.
+With "wharfie" you can easily build a root filesystem, based on the Debian distribution from scratch. To configure the system for your needs, you just write all necessary configuration steps into a configuration file. You don't do this configuration at the live system.
+
+Those configuration files are called Dockerfile in the docker eco-system. It's pendent in the world of wharfie is called Wharfile.

 # Automate Building of Image
@@ -46,11 +48,11 @@
 TOOLCHAIN toolchain_debian_armhf_stretch.tar
 ~~~
 # Legal concerns
-When using the linux OS for embeddded systems, a lot of legal issues have to be respected. Luckily wharfie contains two additional commands to face these issues:
+When using the linux OS for embeddded systems, a lot of legal issues have to be respected. Wharfie contains two additional commands to face these issues:

 * LICENSE <filename>
 * SOURCE <filename>

 These commands are creating tarballs, containing all the source packages, or all the licenses of your system, which where installed through debian packages. This feature makes it very easy to prepare yourself for distributing such an image.

-You will need to be able to provide such packages when you plan to distribute the image as part of a product, as well as when you share it with others in form of a download on the internet. When you publish anything, which contains Code that war released under a third party license, you are forced to provide a list of all those licenses, containing the license text.
+You will need to be able to provide such packages when you plan to distribute the image as part of a product, as well as when you share it with others in form of a download on the internet. When you publish anything, which contains code that was released under a third party license, you are often forced to provide a list of all those licenses, containing the license text.
</filename></filename>

Home modified by Ingo

Ingo — Fri, 19 Jul 2019 06:06:01 -0000

--- v8
+++ v9
@@ -3,14 +3,49 @@
 [[include ref=IndexMain]]

 [[img src=wharfie-terminal.gif]]
-# Build System
+# Build Embedded Linux
 Wharfie is a modern build system for embedded devices. The concept is very similar to "docker". Both, "docker" and "wharfie", are using a simple format to describe custom linux system configurations and rebuild those easily. Wharfie uses basically the same syntax, while it is not fully compatible.

 While "docker" is focusing on scalable web services, "wharfie" is focusing on embedded linux systems.

 With "wharfie" you can easily build a root filesystem, based on the Debian distribution from scratch. You can then configure it in an appropriate way. This whole configuration, you don't do at the living system, but you describe this like a recipe.

-#Legal concerns
+
+# Automate Building of Image
+When you install linux on an embedded target, it is very common, that you are first faced with a preconfigured system, which you have to configure manually. Doing this multiple times can become really anoying. Wharfie helps you in this process, as it can repeat all the configuration steps for you.
+
+~~~
+...
+# Set the locale
+RUN locale-gen en_US.UTF-8
+
+RUN git clone https://github.com/pyload/pyload.git /opt/pyload \
+        && cd /opt/pyload \
+        && git checkout stable \
+        && echo "/opt/pyload/pyload-config" > /opt/pyload/module/config/configdir
+
+ADD pyload-config/ /opt/pyload/pyload-config
+ADD ../common/files/pyload.service /etc/systemd/system/pyload.service
+...
+~~~
+
+# Role out up-to-date images
+Because the building process can be highly automated, you can easily just rebuild the images on a regular basis, and keep the images which you role out to new targets always up-to-date.
+
+~~~
+# rebuild
+$ wharfie --clean
+$ wharfie
+~~~
+
+# Get Cross-Toolchains
+Wharfie supports *armhf*, *armel*, *i386* and *amd64* from debian. At least for ARM it is always difficult to get cross-toolchains, which can be easily archived and reused on different hosts. But also for x86 it makes fully sense to archive a cross toolchain for the systems, which you are roling out somewhere. Otherwise it can become difficult to rebuild programs for your systems in a few years.
+
+~~~
+FROM debian_armhf_stretch
+TOOLCHAIN toolchain_debian_armhf_stretch.tar
+~~~
+# Legal concerns
 When using the linux OS for embeddded systems, a lot of legal issues have to be respected. Luckily wharfie contains two additional commands to face these issues:

 * LICENSE <filename>
</filename>

Home modified by Ingo

Ingo — Fri, 19 Jul 2019 05:22:24 -0000

--- v7
+++ v8
@@ -2,7 +2,8 @@

 [[include ref=IndexMain]]

-# What it is
+[[img src=wharfie-terminal.gif]]
+# Build System
 Wharfie is a modern build system for embedded devices. The concept is very similar to "docker". Both, "docker" and "wharfie", are using a simple format to describe custom linux system configurations and rebuild those easily. Wharfie uses basically the same syntax, while it is not fully compatible.

 While "docker" is focusing on scalable web services, "wharfie" is focusing on embedded linux systems.

Home modified by Ingo

Ingo — Sun, 23 Dec 2018 06:22:30 -0000

--- v6
+++ v7
@@ -7,7 +7,7 @@

 While "docker" is focusing on scalable web services, "wharfie" is focusing on embedded linux systems.

-With "wharfie" one can easily build a root filesystem, based on the Debian distribution from scratch. He can then configure it in an appropriate way.
+With "wharfie" you can easily build a root filesystem, based on the Debian distribution from scratch. You can then configure it in an appropriate way. This whole configuration, you don't do at the living system, but you describe this like a recipe.

 #Legal concerns
 When using the linux OS for embeddded systems, a lot of legal issues have to be respected. Luckily wharfie contains two additional commands to face these issues:

Home modified by Ingo

Ingo — Sun, 25 Feb 2018 13:09:57 -0000

--- v5
+++ v6
@@ -1,4 +1,5 @@
 [TOC]
+
 [[include ref=IndexMain]]

 # What it is

Home modified by Ingo

Ingo — Sun, 25 Feb 2018 13:09:44 -0000

--- v4
+++ v5
@@ -1,3 +1,4 @@
+[TOC]
 [[include ref=IndexMain]]

 # What it is