v.01
@Tutorial

Hi there @Friendica Developers and @Friendica Admins.

The plan is to change this single domain ubunu 2022.04lts VPS hosting into a single IP multi domain VPS server. For that purpose some apache VPS server tutorials were checked out and the specific steps were singled out to achieve that goal.

A main question hasn't been solved to define the naming of the folder structure and .conf files themself:

• Can the domain name in VPS folder structure be:
  /var/www/domaincom/
  or does it have to be
  /var/www/domain.com/

Are both options possible or does the system, for a correct working environment, need the dot in the folder structure?

Are there any general discussions in the #apache #server environment that might lead to some standard in this regard in the future that makes it reasonable to consider one of the two above cited options as more logical to go for from the very beginning?

In the case of very long domain or subdomain names, isn't it more reasonable to choose the option without the real domain name including the dot?
Example:
https: //1dhfsbbdpv4wshuh7nymcfy66t5reqqkfvy9.domain.org/

Depending on the chosen naming syntax this would lead to the following folder structure options:
/var/www/1dhfsbbdpv4wshuh7nymcfy66t5reqqkfvy9.domain.org/
vs
/var/www/1d_domainorg/

Does the naming of the .conf file in /etc/apache2/sites-available/ refer to the actual domain name or to the folder name used in /var/www/?

In the first answer to this topic we'll address the question about:

• How to solve best a step by step change to migrate from a single VPS #hosting environment where one domain is served by one IP at:
  /var/www/html/
  to a multi domain VPS hosting were several domains are served by one IP on one #debian #ubuntu [2022.04lts] #VPS, leaving /html in place if a client request doesn’t match any other sites, like proposed in this digitalOcean tutorial:
  /var/www/html/ as fall back option
  /var/www/domaincom/index.html
/var/www/subdomaindomaincom/index.html
/var/www/domainorg/index.html
/var/www/subdomaindomainorg/index.html

Any comments hints and observations are really appreciated!
#admin #fediAdmin

Apache ACME (mod_md v2.5.0) now supports Let's Encrypt profiles. A short blog about this.
#apache #acme

https://github.com/icing/blog/blob/main/apache-acme-profiles.md

blog/apache-acme-profiles.md at main · icing/blog

Contribute to icing/blog development by creating an account on GitHub.

^GitHub

Daniel Walsh SELinux is a powerful tool for controlling what applications are allowed to do on your system. SELinux is a labeling system where every process and every object (files, directories, devices, network ports, etc.) gets a label. Then a large rules database, called policy, is loaded into the kernel. The kernel, based on the policy, control...