<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Introduction on ownscale Documentation</title><link>/</link><description>Recent content in Introduction on ownscale Documentation</description><generator>Hugo</generator><language>en-US</language><atom:link href="/index.xml" rel="self" type="application/rss+xml"/><item><title>Getting Started</title><link>/docs/getting-started/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/getting-started/</guid><description>&lt;h1 id="getting-started"&gt;Getting Started&lt;a class="anchor" href="#getting-started"&gt;#&lt;/a&gt;&lt;/h1&gt;&#10;&lt;p&gt;Welcome to the ownscale documentation.&lt;/p&gt;&#10;&lt;p&gt;ownscale is a self-hosted control plane and web console for&#10;&lt;a href="https://github.com/juanfont/headscale"&gt;Headscale&lt;/a&gt;, an open-source&#10;implementation of the Tailscale coordination server. This section&#10;covers the core concepts you&amp;rsquo;ll run into once ownscale is installed;&#10;head to &lt;a href="/docs/installation/"&gt;Installation&lt;/a&gt; first if&#10;you haven&amp;rsquo;t deployed it yet.&lt;/p&gt;&#10;&lt;h2 id="organizations"&gt;Organizations&lt;a class="anchor" href="#organizations"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Each organization is an independent tailnet, backed by its own&#10;Headscale instance and reachable at its own subdomain (e.g.&#10;&lt;code&gt;acme.&amp;lt;base_domain&amp;gt;&lt;/code&gt;). Users, machines, ACLs, and DNS settings are all&#10;scoped to a single organization.&lt;/p&gt;</description></item><item><title>Installation</title><link>/docs/installation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/installation/</guid><description>&lt;h1 id="installation"&gt;Installation&lt;a class="anchor" href="#installation"&gt;#&lt;/a&gt;&lt;/h1&gt;&#10;&lt;p&gt;ownscale ships as a Docker Compose stack: an &lt;code&gt;ownscale&lt;/code&gt; container (the&#10;console + API + per-organization Headscale management), a &lt;code&gt;caddy&lt;/code&gt;&#10;container (TLS termination and reverse proxying for the console, this&#10;documentation site, and every organization&amp;rsquo;s subdomain), and one&#10;Headscale container per organization it provisions.&lt;/p&gt;&#10;&lt;h2 id="prerequisites"&gt;Prerequisites&lt;a class="anchor" href="#prerequisites"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Docker and Docker Compose&lt;/strong&gt;, running on the host that will serve&#10;traffic.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;A domain you control&lt;/strong&gt;, with a wildcard DNS record&#10;(&lt;code&gt;*.example.com&lt;/code&gt;) pointing at this host. Each organization and Funnel&#10;gets its own subdomain (e.g. &lt;code&gt;acme.example.com&lt;/code&gt;,&#10;&lt;code&gt;console.example.com&lt;/code&gt;), so a single A/AAAA record per host isn&amp;rsquo;t&#10;enough.&#10;&lt;ul&gt;&#10;&lt;li&gt;For local development, use a private,&#10;&lt;a href="https://www.rfc-editor.org/rfc/rfc2606"&gt;RFC 2606&lt;/a&gt;-reserved TLD&#10;like &lt;code&gt;ownscale.test&lt;/code&gt; instead of a real domain &amp;ndash; see&#10;&lt;a href="#local-development"&gt;Local development&lt;/a&gt; below.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;An OIDC identity provider&lt;/strong&gt; to authenticate against (Google, Okta,&#10;a self-hosted &lt;a href="https://dexidp.io/"&gt;Dex&lt;/a&gt; instance, or any standard&#10;OIDC issuer). ownscale federates login to it rather than managing&#10;passwords itself.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="quick-start"&gt;Quick start&lt;a class="anchor" href="#quick-start"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-sh" data-lang="sh"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;git clone https://github.com/ownscalenet/ownscale.git&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;cd ownscale&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;cp .env.example .env &lt;span style="color:#75715e"&gt;# edit BASE_DOMAIN, OWNSCALE_AUTH_*, etc. -- see below&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;docker compose up -d --build&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Once the stack is up, sign in at &lt;code&gt;https://console.&amp;lt;base_domain&amp;gt;/login&lt;/code&gt;&#10;and create your first organization from the console.&lt;/p&gt;</description></item><item><title>FAQs</title><link>/docs/faqs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/faqs/</guid><description>&lt;h1 id="faqs"&gt;FAQs&lt;a class="anchor" href="#faqs"&gt;#&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="funnel-machine"&gt;Funnel machine&lt;a class="anchor" href="#funnel-machine"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;When creating a funnel, ownscale will automatically create a new user and a new&#10;machine. These will show up in your listings marked as internal resources.&lt;/p&gt;</description></item></channel></rss>