DocKing - ShipSaaS
Docking GitHub
  • DocKing from ShipSaaS
  • Architecture
  • Requirements
  • PDF Engines
    • Gotenberg
    • WkHTMLtoPDF
    • mPDF
  • Upgrade Notes
    • v1.4.0
    • v1.3.2
    • v1.3.1
    • v1.3.0
    • v1.2.0
    • v1.1.2
    • v1.1.1
    • v1.1.0
  • Usage
    • Basic
    • Endpoints
    • Webhook
    • Maintain IDs/Keys from Services
  • Getting Started
    • Environment Variables
    • Run on Local
      • Normal Run
      • Docker
    • Storage
    • Console UI
    • Document Template
      • Gotenberg's Metadata
      • wkHTMLtoPDF's metadata
      • mPDF's metadata
    • Templating Mode
    • Fonts
    • Octane / High-perf mode
    • Localization
  • Deployment
    • Linux VPS / Dedicated Server
    • Docker
Powered by GitBook
On this page
  1. Deployment

Linux VPS / Dedicated Server

Deploy DocKing on a dedicated VPS/EC2/Compute Engine

PreviousLocalizationNextDocker

Last updated 1 year ago

The deployment steps are the same as the .

Different things here, you need to:

  • Setup your internal domain & connection between services

  • Uses NGINX/Apache to serve DocKing

New from v1.3.0

You can run the application in high-perf mode, check this out:

Note

As recommended, use DocKing as an Internal Microservice that empowers other microservices.

It is OK to publish DocKing externally (your choice). For the highest security & least concern, keep DocKing in your internal layer and let DocKing empower your other services.

Manual Local Setup
Octane