Skip to main content
When a post contains a link, she can offer to shorten it and count the clicks. That offer only appears when a shortener is configured, which is why the option is missing on a fresh install rather than broken. Four services are supported. You pick one by setting its API key.

​
The rule that catches people

Set two keys and the first one silently wins. The provider is chosen by a first-match chain in this order, and nothing warns you that the others are being ignored:
  1. DUB_TOKEN
  2. SHORT_IO_SECRET_KEY
  3. KUTT_API_KEY
  4. LINK_DRIP_API_KEY
The choice is made once when she starts, so changing keys needs a restart, not just a save.
With none of them set, she uses a no-op provider: links go out at full length and she stops offering to shorten them at all.

​
Setting one up

Only the token is required. The endpoint defaults to Dub’s own API, and the domain to dub.sh; set DUB_SHORT_LINK_DOMAIN to a custom domain you have added in Dub if you want links on your own name.
Apply the change the usual way:

​
Checking it worked

Write a post containing a link. She asks whether to shorten it, which she does not do when no provider is configured. Say yes, and the published post carries the short domain you set. If she never asks, the key is not reaching her. Check for a typo in the variable name, and check you recreated the container rather than restarting it.

Writing a post

Where the shortening prompt appears while you write

Analytics

Click counts come from the shortener, not from PostQueen

Configuration reference

Every short-link variable in one table

Docker Compose

Where to put these variables and how to apply them