[Docs] Add homelab deployment guide - #977
Draft
roomote-roomote[bot] wants to merge 1 commit into
Draft
Conversation
Contributor
|
1 issue outstanding. See task
Reviewed b232281 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why this change was made
The existing self-hosting guide covers the installer and production stack, but homelab operators still need help choosing VM resources, private access, public ingress, DNS, and tunnel behavior. This gives them an actionable path without duplicating the supported installer.
Impact
Homelab users can deploy Roomote with clearer infrastructure boundaries, understand why Tailscale complements rather than replaces public ingress, and hand safe host preparation steps to a local coding agent. The upstream Proxmox community helper script remains a separate follow-up and is not required by this guide.