Feat: v4 self-hosting

.cursorignore

@@ -5,4 +5,5 @@ apps/coordinator/
 packages/rsc/
 .changeset
 .zed
-.env
+.env
+!.env.example

docker/README.md

@@ -0,0 +1,3 @@
+# Internal Docker files
+
+If you're looking for self-hosting files you're in the wrong place. Have a look [here](../hosting/).

docs/cli-preview-archive.mdx

@@ -2,6 +2,7 @@
 title: "CLI preview archive command"
 sidebarTitle: "preview archive"
 description: "The `trigger.dev preview archive` command can be used to archive a preview branch."
+tag: "v4"
 ---
 
 import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";

docs/deployment/preview-branches.mdx

@@ -1,6 +1,7 @@
 ---
 title: "Preview branches"
 description: "Create isolated environments for each branch of your code, allowing you to test changes before merging to production. You can create preview branches manually or automatically from your git branches."
+tag: "v4"
 ---
 
 import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";

docs/docs.json

@@ -171,14 +171,25 @@
             ]
           },
           {
-            "group": "Open source",
+            "group": "Self-hosting",
             "pages": [
-              "open-source-self-hosting",
-              "open-source-contributing",
-              "github-repo",
-              "changelog",
-              "roadmap"
-            ]
+              "self-hosting/overview",
+              "self-hosting/docker",
+              {
+                "group": "Environment variables",
+                "pages": ["self-hosting/env/webapp", "self-hosting/env/supervisor"]
+              }
+            ],
+            "tags": ["v4"],
+            "tag": "v4"
+          },
+          {
+            "group": "Self-hosting",
+            "pages": ["open-source-self-hosting"]
+          },
+          {
+            "group": "Open source",
+            "pages": ["open-source-contributing", "github-repo", "changelog", "roadmap"]
           },
           {
             "group": "Help",

docs/github-actions.mdx

@@ -130,6 +130,10 @@ When self-hosting, you will have to take a few additional steps:
 - Add your registry credentials to the GitHub secrets.
 - Use the `--self-hosted` and `--push` flags when deploying.
 
+<Tip>
+  If you're self-hosting v4, the `--self-hosted` and `--push` flags are **NOT** needed.
+</Tip>
+
 Other than that, your GitHub action file will look very similar to the one above:
 
 <CodeGroup>

docs/guides/example-projects/human-in-the-loop-workflow.mdx

@@ -2,6 +2,7 @@
 title: "Human-in-the-loop workflow with ReactFlow and Trigger.dev waitpoint tokens"
 sidebarTitle: "Human-in-the-loop workflow"
 description: "This example project creates audio summaries of newspaper articles using a human-in-the-loop workflow built with ReactFlow and Trigger.dev waitpoint tokens."
+tag: "v4"
 ---
 
 import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";

docs/guides/example-projects/meme-generator-human-in-the-loop.mdx

@@ -2,6 +2,7 @@
 title: "Meme generator with human-in-the-loop approval"
 sidebarTitle: "AI meme generator"
 description: "This example project creates memes using OpenAI's DALL-E 3 with a human-in-the-loop approval workflow built using Trigger.dev waitpoint tokens."
+tag: "v4"
 ---
 
 import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";

docs/limits.mdx

@@ -39,7 +39,7 @@ The number of queued tasks by environment.
 
 | Pricing tier | Limit              |
 | :----------- | :----------------- |
-| Free         | 10 per project      |
+| Free         | 10 per project     |
 | Hobby        | 100 per project    |
 | Pro          | 1,000+ per project |
 

docs/open-source-self-hosting.mdx

@@ -1,8 +1,10 @@
 ---
-title: "Self-hosting"
-description: "You can self-host Trigger.dev on your own infrastructure."
+title: "Docker (legacy)"
+description: "You can self-host Trigger.dev on your own infrastructure using Docker."
 ---
 
+<Tip>This guide is for v3, you can find the v4 guide [here](/self-hosting/docker).</Tip>
+
 <Warning>Security, scaling, and reliability concerns are not fully addressed here. This guide is meant for evaluation purposes and won't result in a production-ready deployment.</Warning>
 
 <Note>This guide is for Docker only. We don't currently provide documentation for Kubernetes.</Note>