Operational

DocsGithub Open app

Operational

Github Articles Pitch Usecases Playground API

Contents

Start hereAPI DocsIntroductionSend your first eventEvent parametersStructured EventsActionsContextsCategoriesError handlingManualIntroductionBasicsConventionsSetupTest modeNotificationsPWASelf hostingIntroductionInstall locallyInstall on VPSInstall on RenderInstall via DockerInstall via Docker and CoolifyOnboardingSetup .envIntegrationsBest practicesOtherVisionRoadmapContributing

Install via Docker image & Coolify

Coolify is a Docker manager. It can control your VPS and install applications for you.

Here’s a video on setting up Operational via Coolify:

Steps

  1. Setup a VPS

  2. Connect Coolify to VPS

  3. Setup a Coolify project

  4. Create a mysql database Save the connection string for env vars

  5. Setup a Docker image Get the Docker image url from here.

  6. Enter env vars You’ll need these vars:

  • APP_URL: set this to the default url Coolify assigns(you can change this later on)
  • DATABASE_URL: set this as the connection string of the mysql database you’ve setup earlier
  • PORT: set this to 2000
  • VITE_API_URL: set this to the backend url

You’ll need to also create a backend url manually. In the video, I couldn’t get this to work via Coolify’s UI so I manually added container labels.

But you don’t need to do that. All you need to do is to add two domains in the domains input inside Coolify. One domain will be for your frontend, other will be for your backend. In the second domain, append :4337 port to the end of the domain. This will map the backend url to port 4337 which is used by the dockerfile for the backend.

If Coolify’s UI barfs, paste this code at the end of the container labels and replace api-yourfrontendurl with your backend:

traefik.http.routers.backend-4337.rule=Host(`api-yourfrontendurl`)
traefik.http.routers.backend-4337.entryPoints=http
traefik.http.routers.backend-4337.service=backend-4337
traefik.http.services.backend-4337.loadbalancer.server.port=4337
Copy

And paste the backend url in the VITE_API_URL env var as the value.

  1. Deploy your docker container.

Keeping your database seperate from the Docker application is a good idea because you can easily update your docker image in the future if needed, and your database will be intact.

If you’re using something like Dokploy, Komo.do, etc, the steps are almost same. What differs between these platforms is how they handle urls and ports.

Install on RenderInstall via Docker and Coolify

Operational

Event tracker for your product.

PrivacyTerms
About the product
  • Playground
  • API
  • Pitch
  • Wordpress plugin
  • Bubble plugin
Related to the product
  • VS Logsnag
  • Open Source
  • Articles
Useful articles for your business
  • Force post: The Payment Hack that lets Merchants charge you without approval
  • 6 Best practices for early stage B2B SaaS customer support
  • Setup event notifications for your SaaS
  • How to get high quality users for your B2B SaaS business?