# Deploying the TX Text Control Document Editor Backend Web Server in Docker > This article describes how to deploy the TX Text Control Document Editor backend web server in Docker. The backend web server is a .NET Core application that provides the required synchronization and the rendering engine. - **Author:** Bjoern Meyer - **Published:** 2025-04-10 - **Modified:** 2025-11-16 - **Description:** This article describes how to deploy the TX Text Control Document Editor backend web server in Docker. The backend web server is a .NET Core application that provides the required synchronization and the rendering engine. - **6 min read** (1088 words) - **Tags:** - ASP.NET - ASP.NET Core - Backend - Docker - **LLMs.txt URL:** https://www.textcontrol.com/blog/2025/04/10/deploying-the-tx-text-control-document-editor-backend-web-server-in-docker/llms.txt - **LLMs-full.txt URL:** https://www.textcontrol.com/blog/2025/04/10/deploying-the-tx-text-control-document-editor-backend-web-server-in-docker/llms-full.txt - **Canonical URL:** https://www.textcontrol.com/blog/2025/04/10/deploying-the-tx-text-control-document-editor-backend-web-server-in-docker/ --- TXTextControl.Web.Server.Core is a lightweight, cross-platform .NET 8 application introduced with TX Text Control 33.0 to serve as the backend for the TX Text Control Document Editor. This new architecture replaces the previous Windows-only synchronization service with a more flexible and modern solution. The key features of TXTextControl.Web.Server.Core include: - **Cross-platform compatibility**: TXTextControl.Web.Server.Core can run on any platform that supports .NET 8 or better, including Windows and Linux. - **Versatile deployment options**: Can be deployed on Azure App Services, virtual machines, containers (such as Docker and Kubernetes), or on bare-metal servers. - **Flexible execution modes**: Capable of running as a standalone application, or a Linux daemon. - **Lightweight and scalable design**: Tailored for modern cloud and containerized environments, ensuring efficient resource utilization and scalability. > **Learn More** > > With the release of TX Text Control 33.0, we are excited to introduce TXTextControl.Web.Server.Core, a major upgrade in the way the document editor works on the backend. This article provides an overview of the new architecture and how to deploy the backend on Linux using Docker. > > [Introducing TXTextControl.Web.Server.Core: A Cross-Platform Backend for TX Text Control Document Editor ](https://www.textcontrol.com/blog/2025/03/13/introducing-txtextcontrol-web-server-core-a-cross-platform-backend-for-tx-text-control-document-editor/llms-full.txt) In most Getting Started tutorials, we describe how to deploy the required backend with the actual ASP.NET application that uses the Document Editor. In this case, the backend is launched from within the same application. But what if the consuming application uses a different technology stack, such as Angular or JavaScript, and runs on a completely different server or instance? In this case, the backend can be hosted on a separate server or in a Docker container. This tutorial shows how to deploy the backend using Docker. #### Preparing the Docker Image As a prerequisite, you must install the TX Text Control .NET Server setup to access the required files. Follow these steps to prepare the Docker image. 1. In a folder of your choice, create a new folder called *TXTextControl.Web.Server*. 2. **TXTextControl.Web.Server.Core Files** Copy the following files from the TX Text Control installation folder to the new folder. *C:\\Program Files\\Text Control GmbH\\TX Text Control 33.0.NET Server for ASP.NET\\Assembly\\net8.0\\* - **TXTextControl.Web.Server.Core.dll** - **TXTextControl.Web.Server.Core.Process.dll** - **TXTextControl.Web.Server.Core.config.json** - **TXTextControl.Web.Server.Core.deps.json** - **TXTextControl.Web.Server.Core.Process.deps.json** - **TXTextControl.Web.Server.Core.Process.runtimeconfig.json** - **TXTextControl.Web.Server.Core.runtimeconfig.json** 3. **TX Text Control Files** Copy the following files from the same folder. *C:\\Program Files\\Text Control GmbH\\TX Text Control 33.0.NET Server for ASP.NET\\Assembly\\net8.0\\* - **TXDocumentServer.Core.dll** - **TXTextControl.Core.dll** - **TXTextControl.Server.Core.dll** From the *Assembly* folder, the following files are required: *C:\\Program Files\\Text Control GmbH\\TX Text Control 33.0.NET Server for ASP.NET\\Assembly\\* - **TXBarcode.dll** - **TXDrawing.dll** - **TXImageProvider.dll** - **txpdf.dll** - **TXSVGResources.dll** 4. **TX Text Control Native Dependencies** **For Linux**: Copy the following files from the *binunix* folder: *C:\\Program Files\\Text Control GmbH\\TX Text Control 33.0.NET Server for ASP.NET\\Assembly\\binunix\\* - **tx33core.so** - **tx33core\_tls.so** - **tx33\_css.so** - **tx33\_dox.so** - **tx33\_htm.so** - **tx33\_ic.so** - **tx33\_pdf.so** - **tx33\_pdfdata.so** - **tx33\_xlx.so** - **txdomprs.so** - **txfntmgr.so** - **txsvggen.so** - **txwndmgr.so** **For Windows**: Copy the following files from the *bincore64* folder: *C:\\Program Files\\Text Control GmbH\\TX Text Control 33.0.NET Server for ASP.NET\\Assembly\\bincore64\\* - **tx33core.dll** - **tx33core\_css.dll** - **tx33core\_dox.dll** - **tx33core\_htm.dll** - **tx33core\_ic.dll** - **tx33core\_pdf.dll** - **tx33core\_tls.dll** - **tx33core\_xlx.dll** - **tx33\_pdfdata.dll** - **txfntmgr.dll** - **txwndmgr.dll** The following files from the *bin64* folder are also required: *C:\\Program Files\\Text Control GmbH\\TX Text Control 33.0.NET Server for ASP.NET\\Assembly\\bin64\\* - **txdomprs.dll** - **txsvggen.dll** 5. **TX Text Control Fonts** Copy the complete *fonts* folder from the TX Text Control installation folder: *C:\\Program Files\\Text Control GmbH\\TX Text Control 33.0.NET Server for ASP.NET\\Assembly\\fonts\\* Be sure to copy the entire folder, not just the files. The fonts are required for rendering documents and must be in the same folder structure as the installation folder. #### Creating the Dockerfile In the same folder, create a new file named *Dockerfile* (without any file extension). The Dockerfile contains the instructions for building the Docker image. Here is an example of a Dockerfile for TXTextControl.Web.Server.Core: ``` ### Use the official .NET 8.0 runtime image FROM mcr.microsoft.com/dotnet/aspnet:8.0 AS base ### Set the working directory inside the container WORKDIR /app ### Copy the TXTextControl.Web.Server folder contents to the container COPY TXTextControl.Web.Server/ . ### Expose default ASP.NET port (optional, depending on your app config) EXPOSE 4282 ### Start the application ENTRYPOINT ["dotnet", "TXTextControl.Web.Server.Core.dll"] ``` > **Linux Containers** > > This description shows how to host the backend on a Linux container. Make sure that Linux containers are enabled on Docker. In this example, we use the **mcr.microsoft.com/dotnet/aspnet:8.0** image as the base image. This image contains the ASP.NET Core runtime and is suitable for running .NET applications. We copy the required files into the image and set the working directory to */app*. The **ENTRYPOINT** instruction specifies the command to run when the container starts. In this case, we use **dotnet TXTextControl.Web.Server.Core.dll** to start the TXTextControl.Web.Server.Core application. #### Building the Docker Image To build the Docker image, open a terminal or command prompt and navigate to the folder where you created the Dockerfile. Run the following command: ``` docker build -t txtextcontrol-webserver . ``` This command builds the Docker image and tags it as **txtextcontrol-webserver**. The **.** at the end specifies the current directory as the build context. #### Running the Docker Container After creating the Docker image, you can run a container based on the image. Use the following command: ``` docker run -p 4282:4282 txtextcontrol-webserver ``` This command runs the container and maps port 4282 on the host to port 4282 in the container. You can access the TXTextControl.Web.Server.Core backend endpoints at **http://localhost:4282**. #### Testing the Backend In your ASP.NET Core application, where you added the *TX Text Control WebSocket Middleware*, add the container as the host name and port number. ``` app.UseTXWebSocketMiddleware("localhost", 4282); ``` --- ## About Bjoern Meyer As CEO, Bjoern is the visionary behind our strategic direction and business development, bridging the gap between our customers and engineering teams. His deep passion for coding and web technologies drives the creation of innovative products. If you're at a tech conference, be sure to stop by our booth - you'll most likely meet Bjoern in person. With an advanced graduate degree (Dipl. Inf.) in Computer Science, specializing in AI, from the University of Bremen, Bjoern brings significant expertise to his role. In his spare time, Bjoern enjoys running, paragliding, mountain biking, and playing the piano. - [LinkedIn](https://www.linkedin.com/in/bjoernmeyer/) - [X](https://x.com/txbjoern) - [GitHub](https://github.com/bjoerntx) --- ## Related Posts - [Announcing the Official DS Server Docker Image on Docker Hub](https://www.textcontrol.com/blog/2025/05/02/announcing-the-official-ds-server-docker-image-on-docker-hub/llms.txt) - [Using a Private NuGet Feed to Build and Restore .NET Apps for Docker Deployment](https://www.textcontrol.com/blog/2025/04/11/using-a-private-nuget-feed-to-build-and-restore-dotnet-apps-for-docker-deployment/llms.txt) - [Configuring the TX Text Control Document Editor Backend Web Server, including Port and Logging](https://www.textcontrol.com/blog/2025/03/28/configuring-the-tx-text-control-document-editor-backend-web-server-including-port-and-logging/llms.txt) - [Designing a Maintainable PDF Generation Web API in ASP.NET Core (Linux) C# with Clean Architecture and TX Text Control](https://www.textcontrol.com/blog/2025/03/27/designing-a-maintainable-pdf-generation-web-api-in-asp-net-core-linux-c-sharp-with-clean-architecture-and-tx-text-control/llms.txt) - [Using TX Text Control with Ultra-Minimal Chiseled Linux Containers](https://www.textcontrol.com/blog/2025/03/12/using-tx-text-control-with-ultra-minimal-chiseled-linux-containers/llms.txt) - [Getting Started: Document Editor with ASP.NET Core and Docker Support with Linux Containers](https://www.textcontrol.com/blog/2025/03/12/getting-started-document-editor-with-asp-net-core-and-docker-support-with-linux-containers/llms.txt) - [Why an Unlimited Runtime License (OEM) for TX Text Control is Perfect for Cloud Deployments](https://www.textcontrol.com/blog/2025/01/08/why-an-unlimited-runtime-license-oem-for-tx-text-control-is-perfect-for-cloud-deployments/llms.txt) - [Building an ASP.NET Core Backend Application to Host the Document Editor and Document Viewer](https://www.textcontrol.com/blog/2024/03/14/building-an-asp-net-core-backend-application-to-host-the-document-editor-and-document-viewer/llms.txt) - [Deploying an ASP.NET Core Web App to Azure App Services](https://www.textcontrol.com/blog/2023/09/23/deploying-an-aspnet-core-web-app-to-azure-app-services/llms.txt) - [Deploying an ASP.NET Core Web App with Docker](https://www.textcontrol.com/blog/2023/09/23/deploying-an-aspnet-core-web-app-with-docker/llms.txt) - [Document Editor Deployment with Docker and Windows Server Core 2019 and 2022 including Fonts](https://www.textcontrol.com/blog/2023/06/02/document-editor-deployment-with-docker-and-windows-server-core-2019-and-2022/llms.txt) - [Deploying an ASP.NET Core Web Application using the Document Editor with Docker](https://www.textcontrol.com/blog/2022/09/02/deploying-an-aspnet-core-application-with-docker/llms.txt) - [Load Balancing: Using Different TCP Service Locations using a Custom WebSocketHandler](https://www.textcontrol.com/blog/2021/11/02/using-different-tcp-service-locations/llms.txt) - [Extracting Structured Table Data from DOCX Word Documents in C# .NET with Domain-Aware Table Detection](https://www.textcontrol.com/blog/2026/04/03/extracting-structured-table-data-from-docx-word-documents-in-csharp-dotnet-with-domain-aware-table-detection/llms.txt) - [Introducing Text Control Agent Skills](https://www.textcontrol.com/blog/2026/03/27/introducing-text-control-agent-skills/llms.txt) - [Deploying the TX Text Control Document Editor from the Private NuGet Feed to Azure App Services (Linux and Windows)](https://www.textcontrol.com/blog/2026/03/25/deploying-the-tx-text-control-document-editor-from-the-private-nuget-feed-to-azure-app-services-linux-and-windows/llms.txt) - [Why Structured E-Invoices Still Need Tamper Protection using C# and .NET](https://www.textcontrol.com/blog/2026/03/24/why-structured-e-invoices-still-need-tamper-protection-using-csharp-and-dotnet/llms.txt) - [AI Generated PDFs, PDF/UA, and Compliance Risk: Why Accessible Document Generation Must Be Built Into the Pipeline in C# .NET](https://www.textcontrol.com/blog/2026/03/23/ai-generated-pdfs-pdf-ua-and-compliance-risk-why-accessible-document-generation-must-be-built-into-the-pipeline-in-c-sharp-dot-net/llms.txt) - [File Based Document Repository with Version Control in .NET with TX Text Control](https://www.textcontrol.com/blog/2026/03/20/file-based-document-repository-with-version-control-in-dotnet/llms.txt) - [Create Fillable PDFs from HTML Forms in C# ASP.NET Core Using a WYSIWYG Template](https://www.textcontrol.com/blog/2026/03/17/create-fillable-pdfs-from-html-forms-in-csharp-aspnet-core-using-a-wysiwyg-template/llms.txt) - [Why HTML to PDF Conversion is Often the Wrong Choice for Business Documents in C# .NET](https://www.textcontrol.com/blog/2026/03/13/why-html-to-pdf-conversion-is-often-the-wrong-choice-for-business-documents-in-csharp-dot-net/llms.txt) - [Inspect and Process Track Changes in DOCX Documents with TX Text Control with .NET C#](https://www.textcontrol.com/blog/2026/03/10/inspect-and-process-track-changes-in-docx-documents-with-tx-text-control-with-dotnet-csharp/llms.txt) - [Text Control at BASTA! Spring 2026 in Frankfurt](https://www.textcontrol.com/blog/2026/03/06/text-control-at-basta-spring-2026-in-frankfurt/llms.txt) - [From Legacy Microsoft Office Automation to a Future-Ready Document Pipeline with C# .NET](https://www.textcontrol.com/blog/2026/03/02/from-legacy-microsoft-office-automation-to-a-future-ready-document-pipeline-with-csharp-dot-net/llms.txt) - [We are Gold Partner at Techorama Belgium 2026](https://www.textcontrol.com/blog/2026/02/26/we-are-gold-partner-techorama-belgium-2026/llms.txt)