Description of the issue:

When deploying a project from a Template that has HTTP Public networking enabled, the RAILWAY_PUBLIC_DOMAIN environment variable is always empty. This issue occurs specifically with Templates and does not happen when creating a project from scratch.

Steps to reproduce:

1. Deploy a project using a Template that has HTTP Public networking enabled

2. Check the RAILWAY_PUBLIC_DOMAIN environment variable

3. Observe that the variable is empty

Expected behavior:

The RAILWAY_PUBLIC_DOMAIN environment variable should contain the public domain assigned to the project.

Actual behavior:

The RAILWAY_PUBLIC_DOMAIN environment variable is empty.

Workaround:

If you remove the public networking configuration and then re-add it, the RAILWAY_PUBLIC_DOMAIN variable is populated correctly.

Additional notes:

- This issue only occurs with Templates that have HTTP Public networking enabled.

- Projects created from scratch do not exhibit this behavior.

- The problem seems to be related specifically to the initial deployment from a Template.

Possible impact:

This issue can affect applications that rely on the RAILWAY_PUBLIC_DOMAIN variable for configuration or routing purposes, potentially causing deployment failures or unexpected behavior in deployed applications.

Request for investigation:

Could the Railway team please investigate why the RAILWAY_PUBLIC_DOMAIN variable is not being set correctly when deploying from Templates with HTTP Public networking enabled? It would be helpful to understand if this is a known issue and if there are any plans to address it in the near future.