basics

PDF: 

cross-cooking.pdf — Downloaded 237 times

This recipe book is an international delight!

It was born out of a wish to ensure the continuation of traditional cooking and a need to find new ways to collect and record traditional knowledge. To achieve these aims each of the participating countries set up four cooking groups in their regions. We made friends across the generations and across borders and got to understand the idea of Europe a little better.

TODO translation
Die GNU General Public License (oft als GPL, GGPL oder auch GNU GPL abgekürzt ) ist eine von der Free Software Foundation herausgegebene Lizenz für die Lizenzierung freier Software.

Die vier Freiheiten (zusammengefasst)

1. Jeder darf das Programm für jeden Zweck auch kommerziell nutzen.
2. Kopien können kostenlos verteilt oder verkauft werden. Der Programm-Quellcode muss dabei sein.
3. Der Quellcode darf von jedem verändert werden.
4. Für die veränderten Versionen gelten auch die ersten drei Punkte (Copyleft-Prinzip).

Versionen

Es gibt drei Versionen der GPL. Die meisten Programme stehen unter der Version 1 oder 2. Die GPL Version 1 gibt es nur in englischer Sprache. Eine inoffizielle Übersetzung der Version 2 in die deutsche Sprache finden Sie hier.

Hier die Lizenzen verschiedener Projekte:

• Drupal: GPL Version 1
• Joomla!: GPL Version 2
• Wordpress: GPL Version 1
• Apache: GPL Version 2
• MySQL: GPL Version 1 und eine proprietäre Lizenz
• PHP: PHP-Lizenz (nicht kompatibel mit der GPL)

Machen Sie sich ruhig die Mühe, und schauen Sie sich die Texte der Lizenzen an. Es sind wohl mit die berühmtesten Texte in der Welt der Software.

You need all the components mentioned above to install a Joomla! system for yourself. PC, browser, and Internet connection are usually available. There are a number of options for web server, PHP interpreter, and database.

You can:

• set the system up locally on your PC
• set the system up on a server in a company's Intranet
• rent a virtual server from a provider
• rent or purchase a server from a provider (with root access)

You can also:

Have the web server and database located on computers that are physically separated from each other.
You can also, of course, use different:

• brands of web servers
• versions of PHP interpreters
• Versions of MySQL databases
• And on top of that, you can install and operate all these components on various operating systems.

This freedom in choice of resources can sometimes confuse a layman. Therefore, we will discuss a few typical scenarios.

Local Test Environment

If you are at home or in your office, for example, and want to set up a Joomla! website, you may use any of the following operating systems.

Windows Operating System

For a Windows operating system you can use either of two web servers:

Use the inbuild Internet Information Server, install PHP, MySQL and configure them or take a pre-configured package (XAMPP), unpack it on your computer, and everything you need is there (http://apachefriends.org).

Linux Operating System

Here it depends on the distribution version you have. All the distributions allow simple installation (with a click of the mouse) of the Apache, PHP, and MySQL packages. At times, depending on distribution, they may already be pre-installed. So you can use the programs contained in the distribution or a preconfigured package (XAMPP); extract it on your computer and everything you need is there (http://apachefriends.org).

Mac OS X Operating System

In Mac OS X operating system, you have a default web server (Apache) in your system that you have to activate, but unfortunately not PHP and no MySQL.
So you can use the installed Apache web server and install the missing software or the pre-configured XAMPP package for Mac OS X. Another complete package by the name of MAMP is also very popular with the Mac OS X environment (http://www.mamp.info).

Production Environment

You have several options here as well.

Rented Virtual Server

You rent a web-space package with database, PHP support, and often also your domain name from a provider. In this case you have a functional environment and you can install your Joomla! into it. Consult your provider as to the version choices (PHP, MySQL). Sometimes providers offer Joomla! pre-installed with various templates. IIf this is the case, all you have to do is activate Joomla! with a click of the mouse and it is ready for you.

Your Own Server

You rent a server from a provider and install the operating system of your choice. You are the administrator of the system and you can work on it, just like on your PC at home.
Before you venture into the wilderness of the Internet, you should first practice on your local computer. This has the advantage that there are no connection fees, it is very fast, and you can practice at a leisurely pace.
You may even have a small local network at home where you can install Joomla! on one computer and access it from another.
Remember that there are probably more current versions on the respective project sites on the Internet.

Stumbling stones

This topic is very complex because there is a vast number of providers and an even greater number of installed web server, PHP, MySQL versions and web space management tools. Crunchpoints during the installation often consist of:

• an activated PHP Safe Mode, preventing you to upload files,
• 'forbidden' rewrite paths with the Apache web server because the so-called Apache Rewrite Engine (mod_rewrite) is not activated,
• the directory permissions on Linux and OSX, which are set differently than in Windows.
• Basically, the easiest way that almost always works, is the following:
• Download the current file package from the project website to your home PC and unzip everything into a temporary directory.
• Load the unpacked files via FTP onto your rented server or to the directory of your local installation. The files must be installed in the public directory. These directories are usually called htdocs, public_html or html. If there already are other installations in that directory, you can specify a sub directory

As in real life, for a content management system, it is not as easy to decide who can do what.

User account

To create, modify and delete content in a content management system, you need a user account. This account contains at least a username and a password. Both are necessary for the system to remember who is the author or creator of that content. Often the e-mail address is queried to send an activation link to that e-mail address. If the potential user receives that e-mail and is able to answer or click on the activation link, most systems assume that this user is a "human being" and not a spam program.

Content Management System (CMS) contains the terms content and management, which imprecisely refer only to a system that manages content. Such a system could be a board and a piece of chalk (menu or school chalkboard), or some free online encyclopedia such as Wikipedia or an online auction house such as eBay. In all these examples contents are administered, in the last instance by numerous participants.

These participants play a major role in content management systems, on one hand as administrators and on the other as users and editors.

Apart from CMSs, there are terms such as Enterprise Resource Planning Systems (ERP systems - administration of corporate data), Customer Relationship Management Systems (CRM systems - maintenance of customer contacts), Document Management Systems (DMS systems—administration of documents), Human Resource Management Systems (HRM systems - administration of personnel), and many others.

It is difficult to define the term CMS because of its encompassing nature and variety of functions. Wikipedia's definition is my favorite:

A content management system, or CMS, is a computer software system used to enable and organize the joint process of creating and editing text and multimedia documents (content).

The abbreviation ECMS has established itself as the term for Enterprise Content Management Systems. The other abbreviations listed above are subsets of ECMS.

Drupal, Joomla! and Wordpress belong to the category of Web Content Management Systems (WCMS), since its functionality is administered in a Web browser.

In general, the term content management is used in connection with web pages that can be maintained by a browser. This doesn't necessarily make the definition any easier.

Each content management system has a backend and a frontend.

• The frontend is the real site, just like the user sees it. There, he can log in and then he sees the specific part of the site for him.
• The backend is the part of employees. Here, the content is managed and the parameters of the site are set.

Depending on the system front- and backend can be clearly separated or combined. Here are a few examples with their standard templates.

• Joomla - Separation of front- and backend.
  
  Figure 1 - Joomla! Frontend
  
  Figure 2 - Joomla! Backend
   
• Wordpress - Separation of front- and backend.
  
  Figure 3 - Wordpress Frontend
  
  Figure 4 - Wordpress Backend
   
• Drupal - Frontend and backend on one site, recognizable by different themes, and highlighting.
  
  Figure 5 - Drupal Frontend
  
  Figure 6 - Drupal Backend