teamspace (and the technically identical projectfacts) can be self-hosted – on your own server under Linux, Windows or as a Docker container. This topic is aimed at administrators who set up, run and update an on-premises installation.
Using the cloud? If you use teamspace as a cloud product, there is nothing to install – it runs on the servers of 5 POINT AG. The articles here apply exclusively to self-hosting (on-premises).
What is installed technically
teamspace is a Java web application that runs inside an Apache Tomcat and stores its data in a MySQL/MariaDB database. An upstream reverse proxy (Apache or Nginx) handles TLS encryption and forwards the requests to the Tomcat. How these building blocks work together is explained in the article How teamspace is built.
The key components at a glance:
- Apache Tomcat 10 – the application server in which the teamspace
.waris deployed. - OpenJDK 17 (Temurin) – the Java runtime.
- MySQL 8 / MariaDB 10.5 – the database.
- Apache 2.4 or Nginx 1.24 – the reverse proxy (TLS, ports 80/443).
- userfiles directory – the file storage area of the file module (can be moved to a separate disk).
What you need to get started
- A server that meets the system requirements (Debian/Ubuntu or Windows Server, sufficient RAM and disk space, and an SMTP relay for sending mail).
- An SSL certificate for the connection between client and server (or a free one via Let’s Encrypt/Certbot).
- A teamspace-classic account. Through teamspace-classic.de you obtain the installation files (
projectfacts.war, deploy scripts, database template, Jasper font, userfiles template) and, later, the updates. We will set up the account for you on request.
A guide through this topic
Understand & prepare
- How teamspace is built – components, configuration files and data flow.
- System requirements – hardware and software, ports, required files.
Install (choose one path depending on your platform)
Set up a reverse proxy (exactly one)
Additional services & special cases
- Connecting LDAP login
- Setting up the PDF processing service
- Additional server configurations (SSL truststore, OAuth 2.0 for Microsoft 365, installing Tomcat 9 manually under Debian 12)
Keep it up to date
Notes
- The guides consistently use the name projectfacts. If you have teamspace, replace the name accordingly – the steps are identical.
- Create a backup before every update. A downgrade to an older version is not permitted and can render the system unusable.
- You can find current update notes at any time on the “Notice board” in teamspace-classic.
Related topics
- How teamspace is built Installation Concept
- System requirements Installation Reference
- Installing teamspace on Linux Installation Configuration