Community Forum (Discourse)

The powerful, open platform for communities
The powerful, open platform for communities
The powerful, open platform for communities
The powerful, open platform for communities
The powerful, open platform for communities

Project information

  • Category: Web
  • Client: INSTAR Deutschland GmbH (Waletech) Shenzhen, China
  • Project date: 01 March, 2018
  • Project URL: www.discourse.org

The problem: every "how do I connect my camera?" question landed on my desk as a Tier-1 ticket.

What I did: Deployed and configured Discourse as the customer forum on the same hardened infrastructure stack as the rest of INSTAR: a Nomad-managed container with a canary-safe rollout, a dedicated namespace + node pool, its own ACL policy, and a hardened nginx ingress (TLS 1.3, HSTS, Let's Encrypt via a scheduled certbot job) in front. Seeded with integration guides and FAQ threads and wired into the product docs, the forum became the community's front door.

The payoff: a measurable drop in repetitive Tier-1 volume, because customers and integrators now answer each other. I remain the escalation point for forum-reported bugs that point at firmware or the API — and I use the forum to push new-feature guides.

Before this, every "how do I connect my camera to Home Assistant?" question landed on my desk as a Tier-2 ticket. I deployed and configured Discourse as the customer community forum, seeded it with integration guides and FAQ threads, and wired it into the product documentation. The direct impact: a measurable reduction in repetitive Tier-1 support volume, because customers and integrators now answer each other. I remain the escalation point for forum-reported bugs that trace back to firmware or API-level issues.

Designed with BootstrapMade