multiple-domain | multiple domains in a single WordPress | Content Management System library

Create a separate folder for each site/app, and then deploy hosting for each site/app. When you click the "add custom domain" button, type in the subdomain that you want to use. Example

mysubdomain.mydomain.com

When you add the 2 A records to your domain registrar make the host name your subdomain instead of @ or www.

This is one of the frustrating things about the Ingress abstraction. It was built be a minimalist system so that it could be easily implemented by multiple controllers (which worked), but that means a lot of features are stuck being implemented by annotations which usually don’t match up against the abstraction very well since those are a generic key/value pair system.

You have many questions in one.

Should I execute the ./certbot-auto command from PHP using the exec()/shell_exec() command? Should I write a separate bash script and run the bash script instead?

In a generic case: no.

PHP is executed once a webpage has been reached, hence it lives inside the current HTTP session, and the browser at the other end will wait for some kind of response back, in some kind of limited time (and users get angry if they do not see something appearing "fast").

If you exec things you have two options:

1. you wait for completion of external program: problem, this can be after an "undefinite" time, so if this is not taken into account, user will never see anything back in their browser
2. you start it in the background, and you do not wait for its completion: problem, you do not need if it succeeds or not, so even if you are then able to reply "something" to the browser, how will you handle failures?

The generic solution to cases like this is:

1. The action triggered by the HTTP visit just records the request, like in a DB or something
2. Separately a process polls the DB for tasks to do and executes them; this is completely separate from any webserver; when job has completed (success or failure), the DB will be updated in the same way
3. The process at 1) can regularly poll the DB to see the status (pending or completed or failed) and show user a message, like during its visit, with some kind of auto-refresh, and/or provide a specific separate page where the user would be able to track status of its operation

Should I use an ACME PHP library recommended by LetsEncrypt - https://letsencrypt.org/docs/client-options/

You can use any library in any language that properly implements the ACME protocol.

Let's Encrypt only recommends one software: certbot. All the rest listed in that page are examples of client libraries/programs that are expected to work.

Do I need to create virtual hosts for each domain pointing to www.mywebapp.example?

Yes, specially if they are using each of them a specific certificate, otherwise the webserver will not be able to identify the proper certificate to return at the beginning of the TLS handshake based on which hostname the browser gave (inside the SNI extension used at beginning of TLS handshake)

Or you can use some Apache features of mass virtual hosting, such as https://httpd.apache.org/docs/2.4/mod/mod_vhost_alias.html As is however this may probably mean a single certificate with all names added to it, which can technically work until some amount of names, but can create non technical problems (like seeing all the names, etc.)

Of course other software, like Nging/HAProxy can provide more advanced features, where you do not need to configure things virtual host per virtual host, even with different certificates, you just put things in place with specific naming and the webserver will match things as needed.

Do I need to edit /etc/httpd/conf.d/ssl.conf to add the new virtual hosts?

Yes, or any other file as long as you use Include or similar.

If you manage many different and separate websites, it may be simpler to have one configuration file per website, including its certificate paths and so on, many Linux distributions install Apache in such a way that you have /etc/httpd/sites-enabled/ for that feature. If not, you can do the same yourself.

Can multiple domains use the same DocumentRoot path?

Of course yes.

PS: please stop saying SSL, the protocol is named TLS, invented 20 years ago. SSL is long gone, current recommandations are to run TLS 1.2 except if good reasons to also allow 1.1 and 1.0 which have vulnerabilities. There are no "SSL certificate" either for this reason and because they are a misnommer. TLS can work without certificates and these certificates can be used outside of TLS, like in S/MIME. They are X.509 certificates.

In Apache Tomcat you can configure multiple virtual hosts that each deploy the same .war file (or document base) wile having different context configuration parameters like JDBC connection, ressources, esternal JAR files and others.

To stick with your scenario (1), in server.xml configure both domains' host elements:

NUnit provides no way to do this. When running using the console runner (nunit3-console.exe) all the tests in a particular assembly run in the same AppDomain. The MultipleDomainTestRunner you found is used when NUnit wants to run each assembly in its own AppDomain within the same process and so has no bearing on what you want to do.

Given that you can't change the class you are testing, running each test method within it's own AppDomain seems like a good solution. You would have to provide the infrastructure for creating the AppDomain yourself and you would need to make sure that you were not referencing the class itself within the original AppDomain. This is non-trivial but can generally be accomplished.

An alternative would be to use reflection to modify the static state field, assuming you are running tests with sufficient permission to do that. You would have to make sure that you didn't enable any parallelism in order to avoid multiple tests that change the shared state running at the same time.

It is required to have two ports for two separate instances of an HTTP server, but it's generally not required to have two instances of an HTTP server simply to host two domain names.

Any release of IBM HTTP Server (IHS) can serve two certificates on two domains in one instance if the domains use a different IP address.

If they share an IP address, IHS prior to 9.0 requires a single certificate to be valid for both domains (wildcard, SubjectAltName).

IHS 9.0 supports SNI and 2 certs can be used on 2 domains with just a single IP address. The 9.0 manual has many examples. You'd be using 2 *:443 Virtual Hosts.

First and most important point: Domain and range for a property hasName in OWL semantics are not restrictions on hasName! Instead, those axioms are used to infer types of individuals that are related via the property hasName.

Regarding your example, it declares multiple domains for the property hasName, which means the intersection of those classes, i.e. A and B.

This is indeed the most common way.

I don't get what you're doing here. But in OWL the Open World Assumption (OWA) holds, which means unknown information is not considered to be false. It's just unknown. Thus, if you have an individual a that is only related to an individual x via property hasName a standard OWL reasoner cannot (and must not) conclude that a belongs to class A.

Note, the semantic equivalent subClassOf axiom for a domain axiom in OWL is (in pseudo Manchester Syntax)

hasName Domain: A

(hasName some owl:Thing) SubClassOf: A