Advanced configuration

The configuration on this page is for self-hosted deployments that have a commercial license. See Commercial licensing.

Subpath deployment

To host AskTable under a subpath (e.g. https://example.com/asktable), add BASE_PATH to the asktable service in the Self-hosting docker-compose.yaml, and add a Caddy reverse proxy:

services:
  asktable:
    environment:
      BASE_PATH: /asktable   # subpath prefix

  caddy:
    image: caddy:2-alpine
    container_name: caddy
    restart: unless-stopped
    ports:
      - "8080:80"
    volumes:
      - ./Caddyfile:/etc/caddy/Caddyfile:ro
    depends_on:
      - asktable

Add a Caddyfile in the same directory:

Caddyfile

:80 {
    redir /asktable /asktable/ permanent

    handle /asktable/* {
        uri strip_prefix /asktable
        reverse_proxy asktable:80
    }
}

Then access it at http://<server>:8080/asktable/. In production you usually add your own gateway in front, exposing 80/443.

White-labeling

Set brand info under the asktable service’s environment:

APP_NAME=MyBrand          # Brand name in the sidebar, share pages, etc.
APP_TITLE=My App          # Browser tab title
APP_DESCRIPTION=My desc   # SEO description

Replace the logo and favicon via volume mounts (on the asktable service):

services:
  asktable:
    volumes:
      - ./asktable_data:/asktable
      - ./mylogo.png:/usr/share/nginx/html/logo.png:ro
      - ./myfavicon.png:/usr/share/nginx/html/favicon.png:ro

If you set APP_NAME, mount a custom logo too — otherwise the brand name clashes with the default logo.

​Subpath deployment

​White-labeling

Subpath deployment

White-labeling