9392d9454c
Add configurable public-facing URL setting to fix issue where invite emails contained internal localhost addresses inaccessible to external users. Features: - New "Application URL" setting in System Settings (key: app.public_url) - Real-time URL validation with visual feedback and HTTP warnings - Test button to verify URL accessibility - Invite preview showing actual link before sending - Warning alerts when URL not configured - Fallback to request-derived URL for backward compatibility - Complete i18n support (EN, DE, ES, FR, ZH) Backend: - Created utils.GetPublicURL() for centralized URL management - Added POST /settings/validate-url endpoint - Added POST /users/preview-invite-url endpoint - Updated InviteUser() to use configured public URL Frontend: - New Application URL card in SystemSettings with validation - URL preview in InviteModal with warning banners - Test URL button and configuration warnings - Updated API clients with validation and preview functions Security: - Admin-only access for all endpoints - Input validation prevents path injection - SSRF-safe (URL only used in email generation) - OWASP Top 10 compliant Coverage: Backend 87.6%, Frontend 86.5% (both exceed 85% threshold) Refs: #application-url-feature
docs/issues - Issue Specification Files
This directory contains markdown files that are automatically converted to GitHub Issues when merged to main or development.
How It Works
- Create a markdown file in this directory using the template format
- Add YAML frontmatter with issue metadata (title, labels, priority, etc.)
- Merge to main/development - the
docs-to-issues.ymlworkflow runs - GitHub Issue is created with your specified metadata
- File is moved to
docs/issues/created/to prevent duplicates
Quick Start
Copy _TEMPLATE.md and fill in your issue details:
---
title: "My New Issue"
labels:
- feature
- backend
priority: medium
---
# My New Issue
Description of the issue...
Frontmatter Fields
| Field | Required | Description |
|---|---|---|
title |
Yes* | Issue title (*or uses first H1 as fallback) |
labels |
No | Array of labels to apply |
priority |
No | critical, high, medium, low |
milestone |
No | Milestone name |
assignees |
No | Array of GitHub usernames |
parent_issue |
No | Parent issue number for linking |
create_sub_issues |
No | If true, each ## Section becomes a sub-issue |
Sub-Issues
To create multiple related issues from one file, set create_sub_issues: true:
---
title: "Main Testing Issue"
labels: [testing]
create_sub_issues: true
---
# Main Testing Issue
Overview content for the parent issue.
## Unit Testing
This section becomes a separate issue.
## Integration Testing
This section becomes another separate issue.
Manual Trigger
You can manually run the workflow with:
# Dry run (no issues created)
gh workflow run docs-to-issues.yml -f dry_run=true
# Process specific file
gh workflow run docs-to-issues.yml -f file_path=docs/issues/my-issue.md
Labels
Labels are automatically created if they don't exist. Common labels:
- Priority:
critical,high,medium,low - Type:
feature,bug,enhancement,testing,documentation - Component:
backend,frontend,ui,security,caddy,database