YOURLS / YOURLS/YOURLS

Request for support of multiple domains with separate namespaces for paths

Open
#3,600 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
PHP
Stars
12.2k
Forks
2.1k
Avg merge
6h 15m
Merged PRs (30d)
7

Description

Code of Conduct
Submission validity
  • This is not a personal support request, that should be posted on discussions community.
  • I checked current issues and this request isn't a duplicate of an existing issue, opened or closed.
Summary

Several discussions have appeared over the years relating to the use of the same application deployment on multiple domains. Such operation is available through virtual domains on the web host.

However, operation of the same deployment on multiple virtual hosts is functionally different than of multiple deployments, because path remapping occurs on the basis of deployment instance.

It is not possible to deploy a single application instance across multiple domains, yet maintain separate mapping tables for each instance.

Motivation

Clustering of domains may simplify bulk deployments, for example, if the administrator wishes to provide users with choices over URL appearance or other operational characteristics of the application, without maintaining distinct application deployments.

Describe the solution

Requested is an administrative options to define multiple zones of address mapping, each zone assignable to a different domain name (or base URL inclusive of a base path).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue describes an administrative design for assigning separate URL-mapping zones to multiple domains or base paths within one deployment. It names no files, tests, or entry points to inspect, so begin by locating the application's domain and path-mapping configuration and request handling. Done would require an agreed design and working isolated mappings for each configured domain.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.