From 2945a42b56c2a2afedf4afa850cbaaa26cdfb6ae Mon Sep 17 00:00:00 2001
From: Peter Boy <pb@resdigita.de>
Date: Mar 11 2021 10:50:59 +0000
Subject: [PATCH 1/4] Deleted renamed files


---

diff --git a/docs/modules/ROOT/nav.adoc b/docs/modules/ROOT/nav.adoc
deleted file mode 100644
index 72824cf..0000000
--- a/docs/modules/ROOT/nav.adoc
+++ /dev/null
@@ -1,15 +0,0 @@
-* xref:index.adoc[Welcome]
-* xref:serverAdministration.adoc[Server Administration]
-* xref:serverVirtualization.adoc[Virtualization]
-** xref:virtualizationInstall.adoc[Add Virtualization Support]
-** xref:virtualizationVMInstall.adoc[VM Installation Using Cockpit]
-** xref:virtualizationVMCloud.adoc[VM Installation Using Cloud Image]
-* xref:serverContainers.adoc[Containers]
-** xref:containerNspawn.adoc[Container systemd-nspawn]
-* xref:serverUseCases.adoc[Example Use Cases]
-* xref:serverTutorials.adoc[Tutorials]
-* xref:serverTroubleshooting.adoc[Troubleshooting / Known Issues]
-* xref:serverCommunity.adoc[Community, Policies, and working methods]
-* xref:serverFaq.adoc[FAQ]
-* xref:serverCommunicating.adoc[Getting in Touch]
-
diff --git a/docs/modules/ROOT/pages/containerNspawn.adoc b/docs/modules/ROOT/pages/containerNspawn.adoc
deleted file mode 100644
index a62cc21..0000000
--- a/docs/modules/ROOT/pages/containerNspawn.adoc
+++ /dev/null
@@ -1,14 +0,0 @@
-= Systemd Nspawn Container
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-Work in progress. Coming soon
-==== 
-
-
diff --git a/docs/modules/ROOT/pages/index.adoc b/docs/modules/ROOT/pages/index.adoc
deleted file mode 100644
index 11f0769..0000000
--- a/docs/modules/ROOT/pages/index.adoc
+++ /dev/null
@@ -1,60 +0,0 @@
-= Fedora Server Documentation
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-image::Logo_server2.png[Server] 
-
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: 2021-03-10 | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-First Draft! Please comment on server mailing list
-==== 
-
-== Our Mission
-
-*As a user, you gain the opportunity to use the server of the future right now.*
-
-Fedora Server provides a stable, flexible and universally adaptable basis for the everyday provision of digital services and information of all kinds by organizations and individuals, based on the latest technology and makes them available as early as possible. 
-
-*As a developer or system integrator, you gain an eye on the server of the future.*
-
-Fedora Server is a platform for developers and system integrators, which provides an implementation of the latest server technology for further evaluation and practical appropriation. 
-
-== Why Use Fedora Server
-
-Just a shot
-
-== What's Cooking
-
-Currently, we work on several projects
-
-- We are preparing Fedora Server 34
-- We are working on improving Server's documentation (you currently get a first glimpse)
-- We are exploring opportunities of aligning cloud images and server installation more closely with each other and further harmonizing technical details.
-- Technically we are revisiting defaults ... filesystem / partitioning
-
-Stay tuned. The results will soon be visible.
-
-== What You Will Find Here
-
-- Server Administration (todo: One sentence short description)
-- Example Use Cases (todo: One sentence short description)
-- Tutorials (todo: One sentence short description)
-- Trouble shooting guide / known issues  
-- People, policies, and working methods
-
-== How You Can Contribute
-
-- Please, tell us about your usage of Fedora Server
-- Tell us about problems you found and how you resolved it
-- (Easy Contact opportunity )
-
-== Where Else You Find Related Information
-
-- System Administration Guide
-- Wiki pages
-- General ongoing work / change requests?
\ No newline at end of file
diff --git a/docs/modules/ROOT/pages/serverAdministration.adoc b/docs/modules/ROOT/pages/serverAdministration.adoc
deleted file mode 100644
index a55dbe2..0000000
--- a/docs/modules/ROOT/pages/serverAdministration.adoc
+++ /dev/null
@@ -1,55 +0,0 @@
-= Fedora Server Administration Guides
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: 2021-03-10 | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-First Draft! Please comment on server mailing list
-==== 
-	
-== What You Find Here
-
-Basic installation and system administration is covered by Fedora's overall Installation Guide (link) and System Administration Guide (link). But there are several of Fedora Server specific topics which are not included. There are such basic items as harddisk partitioning to more advanced security considerations up to virtualisation.
-
-== Basic System Installation
-(to be decided: alternatively: expand Fedora central Installation and System Administration Guides)
-
-=== Disk Partitioning
-
-- What default partitioning does
-- Raid system 
-- Hard disk larger as 2 TB in Raid set ups
-- UEFI boot
-
-=== Networking
-- Static configuration, appropriate for servers 
-- Post F32 network config file locations
-
-== Post Installation security enhancements
-- Installing fail2ban (short step-by-step installation guide the Fedora way)
-- Disabling ssh password based login for all users but a small number of fallbacks (short guide how to do)
-- Protecting Cockpit password login
-- Don't deactivate SELinux but resolve issues (link to cockpit SELinux page and description how to resolve on CLI (or link) )
-- Reduce the number of system users (If certain system users are required, move each (or all) to a lightweight  system container, e.g. systemd-nspawn, or even a (semi-lightweight) Cloud Image VM)
-- Would be nice to offer some configurable Ansible scripts for those repetitive tasks (downloadable from server-wg home page)
-- links to existing script at github system roles und a guide how to use that script for this purpose
-
-== Specific System Administration Tasks
-
-=== Cockpit
-- recommended documentation for specific types of installation / use case
-- how to secure access / login page (integration into fail2ban, access via ssh tunnel, access via VPN)
-
-=== SELinux issues
-- How to fix
-
-=== How to manage storage
-
-
-
-
-Further topics of this kind to be added
diff --git a/docs/modules/ROOT/pages/serverCommunicating.adoc b/docs/modules/ROOT/pages/serverCommunicating.adoc
deleted file mode 100644
index f73dad3..0000000
--- a/docs/modules/ROOT/pages/serverCommunicating.adoc
+++ /dev/null
@@ -1,27 +0,0 @@
-= Communicating and Getting Help
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Jan Kuparinen (copperi) | Creation Date: 2021-03-09 | Last update: N/A | Related Fedora Version(s): All
-****
-[NOTE]
-====
-Placeholder! Please comment on server mailing list
-==== 
-
-
-	
-For general troubleshooting help related to Fedora, please refer to link:https://ask.fedoraproject.org[Ask Fedora Forum].
-	
-If you found a bug, report it!
-* link:https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/[How to file a bug].
-	
-* Issues about a server can be filed at link:https://pagure.io/fedora-server/issues[ticketing repository on Pagure].
-	
-* You can chat with us at link:https://webchat.freenode.net/?channels=#fedora-server[#fedora-server on irc.freenode.net].
-
-* You can discuss server issues at link:https://discussion.fedoraproject.org/c/server[Server Discussion Forum].
-	
-* You can e-mail us on the Server mailing list at link:https://lists.fedoraproject.org/admin/lists/server@lists.fedoraproject.org/[server@lists.fedoraproject.org].
\ No newline at end of file
diff --git a/docs/modules/ROOT/pages/serverCommunity.adoc b/docs/modules/ROOT/pages/serverCommunity.adoc
deleted file mode 100644
index 0747a80..0000000
--- a/docs/modules/ROOT/pages/serverCommunity.adoc
+++ /dev/null
@@ -1,23 +0,0 @@
-= Server Community, Policies, and Working Methods
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-First Collection of Ideas! Please comment on server mailing list
-==== 
-
-(We should make the working group more "tangible" and transparent, not just refer to an (anonymous) mailing list.)
-
-
-     1  SIG / Link to SIG Wiki
-         1.1  Members of SIG
-     2  WG / Link to WG Wiki
-         2.1  Members of WG incl. Tasks / area of commitment
-             2.1.1  Governance Charter
-     3  Product Requirements Document
-     4  Various other suitable contents of the Fedora Server Wiki pages
\ No newline at end of file
diff --git a/docs/modules/ROOT/pages/serverContainers.adoc b/docs/modules/ROOT/pages/serverContainers.adoc
deleted file mode 100644
index 9fc82a2..0000000
--- a/docs/modules/ROOT/pages/serverContainers.adoc
+++ /dev/null
@@ -1,14 +0,0 @@
-= Containerization
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-Work in progress. Coming soon
-==== 
-
-
diff --git a/docs/modules/ROOT/pages/serverFaq.adoc b/docs/modules/ROOT/pages/serverFaq.adoc
deleted file mode 100644
index aca6a19..0000000
--- a/docs/modules/ROOT/pages/serverFaq.adoc
+++ /dev/null
@@ -1,18 +0,0 @@
-= Frequently Asked Questions (FAQ)
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Jan Kuparinen (copperi) | Creation Date: 2021-03-09 | Last update: N/A | Related Fedora Version(s): All
-****
-[NOTE]
-====
-Placeholder! Please comment on server mailing list
-==== 
-
-[qanda]
-Can I see a built preview of this template to get a better idea about the result?::
-    Of course you can! Just look at the README of the repository — it should tell you everything.
-Is writing documentation hard and dreadful?::
-    Absolutely not (OK, just joking). Writing documentation in asciidoc is very simple and straightforward. And in fact, writing documentation makes you very happy. Just try and see for yourself!
diff --git a/docs/modules/ROOT/pages/serverTroubleshooting.adoc b/docs/modules/ROOT/pages/serverTroubleshooting.adoc
deleted file mode 100644
index c0edae2..0000000
--- a/docs/modules/ROOT/pages/serverTroubleshooting.adoc
+++ /dev/null
@@ -1,37 +0,0 @@
-= Communicating and Getting Help
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Jan Kuparinen (copperi) | Creation Date: 2021-03-09 | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-First Collection of Ideas! Please comment on server mailing list
-==== 
-	
-
-Some examples from the latest discussions
-
-1. The well known BIOSboot partition issue
-2. systemnd-oomd and httpd / jBoss/wildfly 
-3. UEFI – one ESP for /boot/efi requirement in software RAID 1 / RAID x  
-
-### Some generic information
-
-
-If you found a bug, report it!
-
-* link:https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/[How to file a bug].
-	
-* Issues about a server can be filed at link:https://pagure.io/fedora-server/issues[ticketing repository on Pagure].
-	
-* You can chat with us at link:https://webchat.freenode.net/?channels=#fedora-server[#fedora-server on irc.freenode.net].
-
-* You can discuss server issues at link:https://discussion.fedoraproject.org/c/server[Server Discussion Forum].
-	
-* You can e-mail us on the Server mailing list at link:https://lists.fedoraproject.org/admin/lists/server@lists.fedoraproject.org/[server@lists.fedoraproject.org].
-
-For general troubleshooting help related to Fedora, please refer to link:https://ask.fedoraproject.org[Ask Fedora Forum].
-	
\ No newline at end of file
diff --git a/docs/modules/ROOT/pages/serverTutorials.adoc b/docs/modules/ROOT/pages/serverTutorials.adoc
deleted file mode 100644
index ad1dd6f..0000000
--- a/docs/modules/ROOT/pages/serverTutorials.adoc
+++ /dev/null
@@ -1,24 +0,0 @@
-= Fedora Server Tutorials
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-First Collection of Ideas! Please comment on server mailing list
-==== 
-
-
-Some ideas:
-
-- Setting up a dedicated rented off premise Internet Server (example Hetzner)
-- Setting up a private local (on premise) Internet server
-- Setting up an Internet server for SMEs
-- Setting up a homelab / worklab Server
-- Setting up a simple private Mail Server
-- Setting up a full features Mail Server
-- Backup Guide
-- (more to come)
\ No newline at end of file
diff --git a/docs/modules/ROOT/pages/serverUseCases.adoc b/docs/modules/ROOT/pages/serverUseCases.adoc
deleted file mode 100644
index 0777080..0000000
--- a/docs/modules/ROOT/pages/serverUseCases.adoc
+++ /dev/null
@@ -1,27 +0,0 @@
-= Fedora Server Example Use Cases
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-First Collection of Ideas! Please comment on server mailing list
-==== 
-	
-     1  Setting up a Fedora Local Home Server, including
-         1.1  Security considerations
-         1.2  Considerations organizing storage
-         1.3  Configuring local network
-         1.4  file services Windows. Apple, Fedora Workstation
-         1.5  media server 
-         1.6  (personal web server, perhaps rather a bit off the mark)
-         1.7  Again, probably providing a configurable / adaptable Ansible playbook
-     2  Set up a Home Server Mail Service
-        (items according to above)
-     3  More to come (hopefully)
-
-
-
diff --git a/docs/modules/ROOT/pages/serverVirtualization.adoc b/docs/modules/ROOT/pages/serverVirtualization.adoc
deleted file mode 100644
index 8b36ace..0000000
--- a/docs/modules/ROOT/pages/serverVirtualization.adoc
+++ /dev/null
@@ -1,46 +0,0 @@
-# Virtualization
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: 2021-03-10 | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-First Draft! Please comment on server mailing list
-==== 
-
-
-Today's Hardware is pretty much powerful enough to run not only one server but many of them.
-
-Virtualization means that several complete and probably different operating systems run on one and the same hardware - as far as possible independently and isolated from each other.
-
-Containers are an alternative. Here, several containers use the kernel of the host system simultaneously. The mutual isolation is lower, but the performance overhead is also lower.
-
-Fedora Server uses KVM and the libvirt libraries for virtualization. Another alternative that is often used is XEN.
-
-System software required for virtualization is not automatically installed. It can be added as an option during installation. However, a more targeted installation is a subsequent, precisely fitting installation.
-
-After Fedora Server is enabled for virtualization, one or more virtual machines can be installed. This can also be Fedora Server, or any other distribution.
-
-## Adding Virtualization
-
-This step includes an installation of the libvirt software and further configuration steps. For example, external connectivity must be set up for virtual machines, e.g. through a virtual bridge. Often, an internal network is also required for protected communication between the virtual machines or with the host system.
-
-## Adding Virtual Machines
-
-There are two common ways to install virtual machines:
-
-- Use of the distribution-specific installation program with the help of specialized utilities
-- Installation of cloud (base) images, a variant of the operating system optimized for virtualization.
-
-### Distribution specific installation
-
-To do this, the standard ISO file is copied to the server and then executed via a utility. The web-based administration tool Cockpit is currently recommended for Fedora Server. An alternative is Virt-Manager, a graphical utility. However, it must be installed on the local workstation (Linux only) and then works via a ssh connection. Execution on the server itself is not supported, as Fedora Server is designed to be "headless", i.e. without a graphical user interface.
-
-Experienced administrators can also initialize an installation via the command line using VNC and virt-install. However, this is comparatively time-consuming and error-prone.
-
-### Cloud Base Images
-
-A special feature of cloud images is a configuration for a specific runtime environment and purpose with the help of a special program, cloud-init. The necessary information is provided by the cloud system, e.g. Open Stack. These are not readily available on an autonomous server. With Fedora 33 and version 3 of the virt-install program, the installation and use of cloud images and cloud-init has been greatly simplified. 
-
-Installation is now accomplished with a single and simple invocation of the virt-install CLI program. Currently, no support is available through a graphical or web-based program. 
\ No newline at end of file
diff --git a/docs/modules/ROOT/pages/virtualizationInstall.adoc b/docs/modules/ROOT/pages/virtualizationInstall.adoc
deleted file mode 100644
index 161377b..0000000
--- a/docs/modules/ROOT/pages/virtualizationInstall.adoc
+++ /dev/null
@@ -1,116 +0,0 @@
-= Adding Virtualization Support
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: 2021-03-10 | Last update: N/A | Affected Fedora Version(s): 33
-****
-[NOTE]
-====
-First Draft! Please comment on server mailing list
-====
-Libvirt is the standard virtualization method in Fedora and provides a management toolkit for KVM / QEMU. This includes a local virtual network for protected communication between the virtual guest systems with each other and with the host. 
-
-== Preparation
-
-Libvirt stores its data including the image files of the virtual hard disk(s) for the guest systems in /var/lib/libvirt. If you adhere to the default partitioning concept, the libvirt application data is stored in its own logical volume in the default volume group (fedora_fedora).
-
-Before starting the installation, a logical partition must be created. The easiest way is to use Cockpit to create a logical volume, e.g. named libvirt, format it with XFS and mount it at the position /var/lib/libvirt. Cockpit creates this directory automatically. 
-
-== Installing libvirt Virtualization Software
-
-Installing the software is quite simple.
-[source,]
-----
-[…]# dnf install qemu-kvm libvirt virt-install cockpit-machines libguestfs-tools
-----
-
-Package libguestfs-tools provides various useful tools to maintain virtual disks. It is recommended not to install the group @virtualization onto a Fedora Server. It includes various graphical programs and libraries that are not usable on headless servers.
-
-Next check the SELinux labels
-[source,]
-----
-[…]# ls -alZ /var/lib/libvirt
-----
-
-Usually, the installation adjusts the labels accordingly. Otherwise, an adjustment must be made manually.
-[source,]
-----
-[…]# /sbin/restorecon -R -vF /var/lib/libvirt
-----
-If everything is correct, libvirtd must be activated and started.
-[source,]
-----
-[…]# systemctl enable libvirtd  --now
-----
-
-By default, libvirt creates a bridge with an interface virbr0, the IP 192.168.122.1 and the internal name default. In addition, a separate firewall zone libvirt is set up. Check if everything is running as expected.
-[source,]
-----
-[…]# ip a
-[…]# firewall-cmd –get-active-zones
-----
-
-== Adjusting libvirt Configuration
-
-The internal network should be used for the internal, protected communication of the VMs with each other and with the host. For this purpose, it is advantageous to set up a DNS for the internal network so that the VMs can be addressed by their names.
-
-The first step is to decide about a domain name. A top-level ".local" is explicitly not recommended, nor taking one if the official top-level names. But for example, you can take the official domain name and replace the top-level domain with 'lan' or 'internal'. The example domain example.com then becomes example.lan. We use that one throughout this tutorial. The host gets the name  host.example.lan.
-
-Modify libvirt default network
-[source,]
-----
-[…]# virsh  net-edit  default
-<network>
-  <name>default</name>
-  <uuid>aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee</uuid>
-  <bridge name='virbr0' stp='on' delay='0'/>
-  <mac address='52:54:00:xx:yy:zz'/>
-  <forward mode='nat'/>
-  <mtu size='8000'/>
-  <domain name='example.lan'/>
-  <dns forwardPlainNames='no'>
-    <forwarder domain='example.lan' />
-    <forwarder addr='213.133.98.98'/>
-    <forwarder addr='213.133.99.99'/>
-    <host ip='192.168.122.1'>
-      <hostname>host</hostname>
-      <hostname>host.example.lan</hostname>
-    </host>
-  </dns>
-  <ip address='192.168.122.1' netmask='255.255.255.0'>
-    <dhcp>
-      <range start='192.168.122.2' end='192.168.122.254'/>
-    </dhcp>
-  </ip>
-</network>
-----
-
-Activate the modified configuration 
-[source,]
-----
-[…]# virsh net-destroy default 
-[…]# virsh net-start default 
-----
-
-== Converting the Hosts DNS Configuration
-[IMPORTANT]
-====
-Wait, systemd project is currently working to fix the resolved split-DNS bug
-====
-
-== Final Test
-
-Check the functionality of the name resolution with internal and external addresses.[source,]
-----
-[…]# ping host
-[…]# ping host.example.lan
-[…]# ping host.example.com
-[…]# ping guardian.co.uk
-----
-
-
-
-
-

From 601756a534e9ea6959fd377227b3b74d7879ca3b Mon Sep 17 00:00:00 2001
From: Peter Boy <pb@resdigita.de>
Date: Mar 11 2021 10:54:49 +0000
Subject: [PATCH 2/4] restored accidentally deleted file


---

diff --git a/docs/modules/ROOT/nav.adoc b/docs/modules/ROOT/nav.adoc
new file mode 100644
index 0000000..e009a13
--- /dev/null
+++ b/docs/modules/ROOT/nav.adoc
@@ -0,0 +1,14 @@
+* xref:index.adoc[Welcome]
+* xref:server-administration.adoc[Server Administration]
+* xref:server-virtualization.adoc[Virtualization]
+** xref:virtualization-install.adoc[Add Virtualization Support]
+** xref:virtualization-vminstall.adoc[VM Installation Using Cockpit]
+** xref:virtualization-vmcloud.adoc[VM Installation Using Cloud Image]
+* xref:server-containers.adoc[Containers]
+** xref:container-nspawn.adoc[Container systemd-nspawn]
+* xref:server-usecases.adoc[Example Use Cases]
+* xref:server-tutorials.adoc[Tutorials]
+* xref:server-troubleshooting.adoc[Troubleshooting / Known Issues]
+* xref:server-community.adoc[Community, Policies, and working methods]
+* xref:server-faq.adoc[FAQ]
+* xref:server-communicating.adoc[Getting in Touch]

From bb18d2873cc8b6f71f36a2a18fa471dee6e47598 Mon Sep 17 00:00:00 2001
From: Peter Boy <pb@resdigita.de>
Date: Mar 11 2021 11:03:21 +0000
Subject: [PATCH 3/4] Clearing up accidentally wrong/missed updates


---

diff --git a/docs/modules/ROOT/pages/virtualization-vmcloud.adoc b/docs/modules/ROOT/pages/virtualization-vmcloud.adoc
new file mode 100644
index 0000000..63c7cec
--- /dev/null
+++ b/docs/modules/ROOT/pages/virtualization-vmcloud.adoc
@@ -0,0 +1,14 @@
+= Virtual Machines based on Cloud Images
+Peter Boy; Jan Kuparinen
+:page-authors: {author}, {author_2}
+
+[sidebar]
+****
+Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
+****
+[NOTE]
+====
+Work in progress. Coming soon
+==== 
+
+
diff --git a/docs/modules/ROOT/pages/virtualization-vminstall.adoc b/docs/modules/ROOT/pages/virtualization-vminstall.adoc
new file mode 100644
index 0000000..a8b62c0
--- /dev/null
+++ b/docs/modules/ROOT/pages/virtualization-vminstall.adoc
@@ -0,0 +1,16 @@
+= Installing Virtual Machines using Cockpit
+Peter Boy; Jan Kuparinen
+:page-authors: {author}, {author_2}
+
+[sidebar]
+****
+Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
+****
+[NOTE]
+====
+Work in progress. Coming soon
+==== 
+
+
+
+
diff --git a/docs/modules/ROOT/pages/virtualizationVMCloud.adoc b/docs/modules/ROOT/pages/virtualizationVMCloud.adoc
deleted file mode 100644
index 63c7cec..0000000
--- a/docs/modules/ROOT/pages/virtualizationVMCloud.adoc
+++ /dev/null
@@ -1,14 +0,0 @@
-= Virtual Machines based on Cloud Images
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-Work in progress. Coming soon
-==== 
-
-
diff --git a/docs/modules/ROOT/pages/virtualizationVMInstall.adoc b/docs/modules/ROOT/pages/virtualizationVMInstall.adoc
deleted file mode 100644
index a8b62c0..0000000
--- a/docs/modules/ROOT/pages/virtualizationVMInstall.adoc
+++ /dev/null
@@ -1,16 +0,0 @@
-= Installing Virtual Machines using Cockpit
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-Work in progress. Coming soon
-==== 
-
-
-
-

From 4a5c2e23ba731d60530e79f8201badac3773ac45 Mon Sep 17 00:00:00 2001
From: Peter Boy <pb@resdigita.de>
Date: Mar 11 2021 11:28:12 +0000
Subject: [PATCH 4/4] Added accidentally deleted file


---

diff --git a/docs/modules/ROOT/pages/index.adoc b/docs/modules/ROOT/pages/index.adoc
new file mode 100644
index 0000000..7a2d2e4
--- /dev/null
+++ b/docs/modules/ROOT/pages/index.adoc
@@ -0,0 +1,60 @@
+= Fedora Server Documentation
+Peter Boy; Jan Kuparinen
+:page-authors: {author}, {author_2}
+	
+image::Logo_server2.png[Server] 
+
+
+[sidebar]
+****
+Creation Date: 2021-03-10 | Last update: N/A | Related Fedora Version(s): 33
+****
+[NOTE]
+====
+First Draft! Please comment on server mailing list
+==== 
+
+== Our Mission
+
+*As a user, you gain the opportunity to use the server of the future right now.*
+
+Fedora Server provides a stable, flexible and universally adaptable basis for the everyday provision of digital services and information of all kinds by organizations and individuals, based on the latest technology and makes them available as early as possible. 
+
+*As a developer or system integrator, you gain an eye on the server of the future.*
+
+Fedora Server is a platform for developers and system integrators, which provides an implementation of the latest server technology for further evaluation and practical appropriation. 
+
+== Why Use Fedora Server
+
+Just a shot
+
+== What's Cooking
+
+Currently, we work on several projects
+
+- We are preparing Fedora Server 34
+- We are working on improving Server's documentation (you currently get a first glimpse)
+- We are exploring opportunities of aligning cloud images and server installation more closely with each other and further harmonizing technical details.
+- Technically we are revisiting defaults ... filesystem / partitioning
+
+Stay tuned. The results will soon be visible.
+
+== What You Will Find Here
+
+- Server Administration (todo: One sentence short description)
+- Example Use Cases (todo: One sentence short description)
+- Tutorials (todo: One sentence short description)
+- Trouble shooting guide / known issues  
+- People, policies, and working methods
+
+== How You Can Contribute
+
+- Please, tell us about your usage of Fedora Server
+- Tell us about problems you found and how you resolved it
+- (Easy Contact opportunity )
+
+== Where Else You Find Related Information
+
+- System Administration Guide
+- Wiki pages
+- General ongoing work / change requests?
\ No newline at end of file

