Installing and Operating Txture
This part of the documentation deals with all kinds of operational concerns at a technical level.
Pre-Installation
Txture is available as Software-as-a-Service and as an on-premise solution. Both solutions have their merits, depending on your use case. Choose a SaaS deployment if you...
- are using Txture for non-import-intensive cases such as Enterprise Architecture Management
- want to use Txture for managing your cloud workloads
- do not want to be bothered with operations
If you have outsourced operations to a provider with access to your data center (via VPN), Txture can be deployed in their data center to leverage to benefits of both worlds.
An on-premise deployment might be more useful, if you...
- want to use data sources relying on access to your local systems, such as HyperV, VMware vSphere, Red Hat Virtualization
- need to access other internal data sources
- have particularly high requirements for security
If you intend to operate Txture on-premises, have a look at the system requirements.
Installation
When choosing to deploy Txture on-premise, you can use any container platform. Supported are Docker and Kubernetes.
Since Txture requires only a single component (itself) and a PostgreSQL server, deployment is typically straightforward.
Continuous Operation
After Txture was initially deployed, the two most important topics are backups and keep up with new versions: