Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wildcard for 3rd level domains #1194

Open
Wolwer1nE opened this issue Nov 4, 2024 · 0 comments
Open

Wildcard for 3rd level domains #1194

Wolwer1nE opened this issue Nov 4, 2024 · 0 comments

Comments

@Wolwer1nE
Copy link

Hi! Here is what I got

Current Setup

  • Rails application with implemented user subdomain functionality
  • Kamal 2 deployment with Thruster reverse proxy
  • DNS records configured for wildcard domain
  • Current deploy.yml configuration:
proxy: 
  ssl: true
  host: mysite.com

Goal
Enable support for user-specific subdomains in the format:

name.mysite.com
another_name.mysite.com

What is the correct approach to handle wildcard subdomains with Kamal/Thruster?

Option 1: Remove host from deploy.yml completely (concerns about SSL certificate compatibility)
Option 2: Use wildcard notation '*.mysite.com'
Option 3: There is no such possibility, go back to nginx/traefik and suffer.

Kamal version: 2.2.2
Rails version: 8.0.0.beta1
Thruster version: 0.1.8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant