[{"data":1,"prerenderedAt":115},["ShallowReactive",2],{"seo-verification":3,"blog-huly-gestion-projet-self-hosted-vps-en":6},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"id":7,"slug":8,"title":9,"excerpt":10,"readTime":11,"views":12,"isPinned":13,"publishedAt":14,"category":15,"categories":20,"featuredImage":22,"bgImage":23,"posterImage":24,"relatedSolution":22,"intro":25,"sections":26,"ctaTitle":68,"ctaBody":69,"ctaButton":70,"ctaUrl":71,"relatedPosts":72},221,"huly-gestion-projet-self-hosted-vps","Huly: replace Linear, Notion and Slack on your VPS","Deploy Huly on your VPS to centralise issues, docs and chat in one open-source tool — no per-seat subscription required.",7,0,false,"2026-08-04T00:00:00+00:00",{"id":16,"name":17,"slug":18,"color":19,"icon":18},2,"Automation","automatisation","bg-brand-action\u002F10 text-brand-action",[21],{"id":16,"name":17,"slug":18,"color":19,"icon":18},null,"\u002Fblog\u002Fcovers\u002Fbg.svg","\u002Fblog\u002Fcovers\u002Fhuly-gestion-projet-self-hosted-vps-poster.svg","Running a development team often means juggling three or four separate SaaS subscriptions: an issue tracker, a wiki, a chat tool, a sprint board. Huly brings all of this into a single application under the EPL-2.0 licence, self-hosted on your own VPS. One server, zero seat fees, and your data stays inside your infrastructure.",[27,31,40,43,62,65],{"type":28,"title":29,"body":30},"h2","Why consolidate issues, docs and chat into one tool","A Linear subscription, a Notion workspace, a Slack plan and GitHub Projects can easily add up to €40–80 per developer per month. Beyond cost, each tool creates a silo: a decision made in chat is never linked to the issue it triggered, and the wiki lives separately from the kanban board. Huly is released under the EPL-2.0 licence, which is highly permissive for self-hosting and allows commercial deployment without any per-seat royalty.",{"type":32,"title":33,"items":34},"ul","What Huly consolidates in your infrastructure",[35,36,37,38,39],"**Issues and sprints** — create tickets, organise them into sprints and roadmaps with built-in Kanban boards, all without leaving the application.","**Wiki and documentation** — write structured pages directly in Huly; docs are versioned and linked to the relevant projects.","**Real-time chat** — channel and thread-based messaging with built-in video calls, replacing Slack without an additional subscription.","**Bidirectional GitHub sync** — Huly issues are mirrored in GitHub and vice-versa; GitHub pull requests appear automatically in their linked issues.","**Time tracking** — log time spent on each issue directly from the interface, with no third-party extension needed.",{"type":28,"title":41,"body":42},"Prerequisites before deploying","Huly runs on a VPS with at least 4 GB of RAM (8 GB recommended in production) and 2 vCPU. You will need Docker and Docker Compose installed on the host, a domain name pointing to your server, and a dedicated subdomain for the interface — the reverse proxy will expose ports 80 and 443 over HTTPS to the internal services.",{"type":44,"title":45,"steps":46},"steps","Deploy Huly on a VPS in five steps",[47,50,53,56,59],{"title":48,"body":49},"Clone the official repository","Fetch the Docker Compose configuration from the public repository: `git clone https:\u002F\u002Fgithub.com\u002Fhcengineering\u002Fhuly-selfhost.git && cd huly-selfhost`. The repository includes `docker-compose.yaml` and a ready-to-edit `.env.example` template.",{"title":51,"body":52},"Configure the `.env` file","Copy `.env.example` to `.env`, then set at minimum `HULY_HOST` (your public subdomain, e.g. `huly.example.com`), the JWT secrets (`SECRET`), and the MinIO credentials. Leave the internal ports unchanged if you are using a reverse proxy.",{"title":54,"body":55},"Start the services with Docker Compose","Bring up the full stack — front end, application server, MongoDB, Elasticsearch and MinIO — with `docker compose up -d`. On first start, Elasticsearch and MongoDB initialise their data stores; allow two to three minutes before the interface becomes available.",{"title":57,"body":58},"Configure the HTTPS reverse proxy","Point your reverse proxy (Nginx, Caddy or Traefik) to the internal port of the `huly-front` service (default `8083`). Enable TLS with a Let's Encrypt certificate for your chosen subdomain, and make sure WebSockets are correctly proxied (`Upgrade` and `Connection` headers).",{"title":60,"body":61},"Create the first workspace and invite your team","Open your subdomain in a browser, create an administrator account, then generate your first workspace. From the workspace settings, send email invitations to your team members. No seats are counted: you only pay for the storage and bandwidth consumed on your VPS.",{"type":63,"body":64},"tip","To enable GitHub synchronisation, go to Settings → Integrations in your Huly workspace. Connect your GitHub organisation in a few clicks via OAuth. Issues created in Huly then appear automatically in the matching repository, and GitHub pull requests are linked to their corresponding issues — no webhook configuration required.",{"type":28,"title":66,"body":67},"Which teams does Huly suit best?","Huly is a good fit for agencies and technical teams of 5 to 50 people who want to reduce their SaaS footprint without losing features. It also suits teams handling sensitive data for whom keeping communications and documentation on-premises is a regulatory or contractual requirement. If per-seat subscription costs are becoming a growth bottleneck, a single VPS is enough to cover the full collaborative toolset.","Lancez Huly sur un VPS ServOrbit","ServOrbit propose des VPS avec 4 à 32 Go de RAM, prêts à accueillir une pile Docker Compose comme Huly. Déployez en quelques minutes et gardez le contrôle total de vos données d'équipe.","Découvrir ServOrbit pour les agences","\u002Fsolutions\u002Fagences",[73,83,97],{"id":74,"slug":75,"title":76,"excerpt":77,"readTime":11,"views":12,"isPinned":13,"publishedAt":78,"category":79,"categories":80,"featuredImage":22,"bgImage":23,"posterImage":82,"relatedSolution":22},212,"woodpecker-ci-pipeline-vps-forgejo","Woodpecker CI and Forgejo: CI\u002FCD pipeline on a VPS","Deploy Woodpecker CI with Forgejo on your VPS for a self-hosted, lightweight and sovereign open source CI\u002FCD pipeline. Step-by-step Docker guide.","2026-08-02T00:00:00+00:00",{"id":16,"name":17,"slug":18,"color":19,"icon":18},[81],{"id":16,"name":17,"slug":18,"color":19,"icon":18},"\u002Fblog\u002Fcovers\u002Fwoodpecker-ci-pipeline-vps-forgejo-poster.svg",{"id":84,"slug":85,"title":86,"excerpt":87,"readTime":88,"views":89,"isPinned":13,"publishedAt":90,"category":91,"categories":92,"featuredImage":22,"bgImage":23,"posterImage":94,"relatedSolution":95},27,"installer-windmill-vps","Installing Windmill on a VPS: self-hosted automation","Install Windmill on your VPS: turn your Python, TypeScript and Bash scripts into internal workflows and UIs, self-hosted via Docker.",8,1880,"2026-05-24T00:00:00+00:00",{"id":16,"name":17,"slug":18,"color":19,"icon":18},[93],{"id":16,"name":17,"slug":18,"color":19,"icon":18},"\u002Fblog\u002Fcovers\u002Finstaller-windmill-vps-poster.svg",{"categorySlug":18,"appSlug":96},"windmill",{"id":98,"slug":99,"title":100,"excerpt":101,"readTime":88,"views":102,"isPinned":13,"publishedAt":103,"category":104,"categories":109,"featuredImage":22,"bgImage":23,"posterImage":111,"relatedSolution":112},99,"gitea-vs-gitlab","Gitea vs GitLab: Which Self-Hosted Git Forge on a VPS?","Gitea vs GitLab self-hosted: memory footprint, CI\u002FCD, registries, and scalability compared to choose your Git forge on a VPS.",263,"2026-03-13T00:00:00+00:00",{"id":105,"name":106,"slug":107,"color":108,"icon":107},5,"Comparison","comparatif","bg-info\u002F10 text-info",[110],{"id":105,"name":106,"slug":107,"color":108,"icon":107},"\u002Fblog\u002Fcovers\u002Fgitea-vs-gitlab-poster.svg",{"categorySlug":113,"appSlug":114},"self-hosting","gitea",1785852590457]