Self-Hosting

Self-Hosting Domain Locker

Important Disclaimer

⚠️ The self-hosted edition comes with no warranty. There are no guarantees for functionality and maintaining, securing and managing the infrastructure will be your responsibility. The developer cannot be held liable for any damages or losses caused by the use of the self-hosted edition.
‼️ Domain Locker is not intended to be publicly exposed to the internet. It is up to you to secure your own instance and implement proper access controls.

Prerequisites

In order to self-host Domain Locker, you will need a server (such as a Raspberry Pi, laptop, VM or VPS). Domain Locker is intended to be run with Docker, so you will need to have Docker and Docker Compose installed.


Deployment

From Source

Alternatively you can build and run Domain Locker from source. Following the this guide, along with a database:


Resolving Issues

  • Debugging Docs - Walk through of diagnosing issues
  • Checking Logs - How view and understand the build and runtime logs
  • Troubleshooting - Solutions for common issues and outline of known limitations
  • 3rd-party Docs - Signposting to docs for related packages and services
  • Support - Contact details for support queries (currently unavailable for free users)

Developing


See Also