Skip to content
This repository was archived by the owner on Apr 25, 2023. It is now read-only.

Add caution about attaching subdomains to different projects #154

Merged
merged 4 commits into from
May 6, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions cookbooks/go_live.rst
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,15 @@ layer to route requests to the project for a specific domain:
Activity 22jdotpwtrxz6 succeeded
The domain example.com has been attached.

.. caution::

Let's say you own one TLD ``my-domain.com`` and have two SymfonyCloud projects running.
You may want to attach ``project1.my-domain.com`` to the first and ``project2.my-domain.com``
to the second project. While you can easily attach the first subdomain, this will not
work for the second domain out of the box.
This is due to SymfonyCloud's "subdomain hijacking protection", you need to create a support
ticket so that the support can manually whitelist the ``project2.my-domain.com`` subdomain.

.. tip::

Multiple domains can be attached to a project. :ref:`wildcard_routes` (like
Expand Down