migrate outdated docs to private docs

Author: Campano

docs/docs/compatibility.md

@@ -23,14 +23,6 @@ for considered Simplicité version.
 
 :::
 
-Note that it is also still possible to deploy it as managed application container(s) on a wide range of platforms as a service (**PaaS**) such as
-
-- CloudFoundry flavor (see. [this document](/docs/operation/cloudfoundry) for details),
-- AWS ElasticBeanstalk (see. [this document](/docs/operation/aws-elasticbeanstalk) for details),
-- Heroku (see. [this document](/docs/operation/heroku) for details),
-- Openshift (see. [this document](/docs/operation/openshift) for details),
-- etc.
-
 Custom deployments
 ------------------
 

docs/docs/misc/projects-git-repositories.md

@@ -46,9 +46,7 @@ copy the content of the `app` in your Tomcat's `webapps` folder and start Tomcat
 
 :::note
 
-The instance templates are used by our [instance manager](https:/docs/misc/manager) and by our [Docker container](/docs/operation/docker)
-and other PaaS containers ([Bluemix](/docs/operation/cloudfoundry), [Pivotal](/docs/operation/cloudfoundry),
-[Heroku](/docs/operation/heroku), [OpenShift](/docs/operation/openshift), ...)
+The instance templates are used by our [instance manager](https:/docs/misc/manager) and by our [Docker container](/docs/operation/docker).
 
 :::
 

docs/docs/misc/root-deploy.md

@@ -30,7 +30,6 @@ The license key context path must be `/` or `*`.
 ### Embedded work and dbdoc folders
 
 When using "exploded" deployment  it is possible to embed the work and dbdoc folders in the `WEB-INF` folder.
-This approach is, for instance required, when deployng on CloudFoundry.
 
 To do so the default `dataDir` environment entry if defined in the `WEB-INF/web.xml` file must be changed to: