Add palinks-dev host to allowed hosts #46

Merged
ldraney merged 1 commit from add-palinks-dev-host into main 2026-06-13 06:35:00 +00:00
Owner

Summary

  • Add palinks-dev.tail5b443a.ts.net to Rails config.hosts so the dev funnel works

Changes

  • config/environments/development.rb -- add one line to allowed hosts list

Test Plan

  • Navigate to https://palinks-dev.tail5b443a.ts.net -- app loads (verified via chrome-devtools)
  • No blocked host error

Review Checklist

  • No secrets committed
  • No unnecessary file changes
  • Commit messages are descriptive
  • Feature flag needed? No -- config fix
  • Closes #45
  • palinks -- project this affects
## Summary - Add `palinks-dev.tail5b443a.ts.net` to Rails `config.hosts` so the dev funnel works ## Changes - `config/environments/development.rb` -- add one line to allowed hosts list ## Test Plan - [x] Navigate to `https://palinks-dev.tail5b443a.ts.net` -- app loads (verified via chrome-devtools) - [x] No blocked host error ## Review Checklist - [x] No secrets committed - [x] No unnecessary file changes - [x] Commit messages are descriptive - [x] Feature flag needed? No -- config fix ## Related Notes - Closes #45 - `palinks` -- project this affects
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Author
Owner

PR #46 Review

DOMAIN REVIEW

Stack: Ruby on Rails (development environment config)

The change adds one line to config/environments/development.rb:

config.hosts << "palinks-dev.tail5b443a.ts.net"

This follows the exact same pattern as the two existing host entries immediately above it (palinks.tail5b443a.ts.net and dev-tunnel-palinks.tail5b443a.ts.net). The hostname is a Tailscale funnel domain, consistent with the existing naming convention.

  • Pattern consistency: PASS -- identical config.hosts << syntax, same Tailscale domain suffix
  • No security concern: this is a development-only config file; adding an allowed host in dev does not affect production
  • No hardcoded secrets: the hostname is a Tailscale machine name, not a credential
  • Scope: exactly one line, exactly one file -- no scope creep

BLOCKERS

None.

This is a one-line config addition with no new functionality, no new code paths, and no security surface. The "no tests" criterion does not apply -- there is no testable behavior change; this is a Rails host allowlist entry for a dev environment.

NITS

None.

SOP COMPLIANCE

  • Branch named after issue (add-palinks-dev-host -- descriptive, relates to #45)
  • PR body follows template (Summary, Changes, Test Plan, Review Checklist, Related Notes all present)
  • Closes #45 present in Related Notes
  • Test plan documented (manual verification via chrome-devtools that the dev funnel loads)
  • No secrets committed
  • No unnecessary file changes (1 file, 1 line)
  • Commit messages are descriptive

PROCESS OBSERVATIONS

Low-risk, minimal-diff config fix. No deployment frequency or change failure risk concerns. Manual test plan (navigate to the dev funnel URL) is appropriate for a host allowlist change where automated testing would add no value.

VERDICT: APPROVED

## PR #46 Review ### DOMAIN REVIEW **Stack:** Ruby on Rails (development environment config) The change adds one line to `config/environments/development.rb`: ```ruby config.hosts << "palinks-dev.tail5b443a.ts.net" ``` This follows the exact same pattern as the two existing host entries immediately above it (`palinks.tail5b443a.ts.net` and `dev-tunnel-palinks.tail5b443a.ts.net`). The hostname is a Tailscale funnel domain, consistent with the existing naming convention. - Pattern consistency: PASS -- identical `config.hosts <<` syntax, same Tailscale domain suffix - No security concern: this is a development-only config file; adding an allowed host in dev does not affect production - No hardcoded secrets: the hostname is a Tailscale machine name, not a credential - Scope: exactly one line, exactly one file -- no scope creep ### BLOCKERS None. This is a one-line config addition with no new functionality, no new code paths, and no security surface. The "no tests" criterion does not apply -- there is no testable behavior change; this is a Rails host allowlist entry for a dev environment. ### NITS None. ### SOP COMPLIANCE - [x] Branch named after issue (`add-palinks-dev-host` -- descriptive, relates to #45) - [x] PR body follows template (Summary, Changes, Test Plan, Review Checklist, Related Notes all present) - [x] `Closes #45` present in Related Notes - [x] Test plan documented (manual verification via chrome-devtools that the dev funnel loads) - [x] No secrets committed - [x] No unnecessary file changes (1 file, 1 line) - [x] Commit messages are descriptive ### PROCESS OBSERVATIONS Low-risk, minimal-diff config fix. No deployment frequency or change failure risk concerns. Manual test plan (navigate to the dev funnel URL) is appropriate for a host allowlist change where automated testing would add no value. ### VERDICT: APPROVED
ldraney deleted branch add-palinks-dev-host 2026-06-13 06:35:00 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ldraney/palinks!46
No description provided.