Update the "Exposing a Node.js App Over 80/443 on a Subdomain in DDEV" blog post #532
Conversation
…" blog post * Adjust the instructions to be compatible with the changes in ddev 1.25
|
🌐 Fork Preview for PR #532 https://pr-532.ddev-com-fork-previews.pages.dev This preview updates automatically when you push changes to your fork. |
Co-authored-by: Stanislav Zhuk <stasadev@gmail.com>
| title: "Exposing a Node.js App Over HTTP / HTTPS on a Subdomain in DDEV" | ||
| pubDate: 2025-04-10 | ||
| #modifiedDate: 2025-04-07 | ||
| modifiedDate: 2026-02-05 |
There was a problem hiding this comment.
modifiedComment: "DDEV v1.25.0 is more restrictive on project traefik configuration, so the .ddev/traefik/project.yaml has to be edited and have the #ddev-generated removed"
| If you want `frontend.example.ddev.site` to map to your Node.js app over HTTPS, you need a reverse proxy rule. | ||
| That’s where Traefik comes in. | ||
|
|
||
| > Please note: the procedure described here only works with versions of DDEV greater than 1.25. So it's recommended to add this constraint to your DDEV setup by issuing this command: |
There was a problem hiding this comment.
I don't think this is true at all. It should work for all versions of DDEV for a few years. Editing the project traefik config has always been something that was possible. The multiple config files thing was removed (but should make its way back in.)
|
I'm dragging my feet on this just a little because would restore the previous behavior I think, and it's likely to make it into v1.25.1 |
3 participants
The Issue
The existing instructions do not work anymore with DDEV > 1.25 because of Traefik changes.
How This PR Solves The Issue
The blog post is updated with instructions that work.
Related Issue Link(s)
ddev/ddev#8047 will probably make these instructions obsolete once completed. I have added a link to the issue.