---
title: "Comment by Luke Martin on \"Adding a Laravel backend to a Remix App\" | Hashnode"
description: "Do you serve the Laravel app on a subdomain? In the Remix + Laravel example, both the route and api are served under GET /users , presumably because it’s just e"
url: "https://hashnode.com/posts/adding-a-laravel-backend-to-a-remix-app/62a874fa0baf4306d9493798/comment/653b598799e256838d60981c"
---

[Discussion](https://hashnode.com/posts/adding-a-laravel-backend-to-a-remix-app/62a874fa0baf4306d9493798)

Comment [Adding a Laravel backend to a Remix App](https://hashnode.com/posts/adding-a-laravel-backend-to-a-remix-app/62a874fa0baf4306d9493798)

[Luke Martin](https://hashnode.com/@lukemartin)

[Oct 27, 2023](https://hashnode.com/posts/adding-a-laravel-backend-to-a-remix-app/62a874fa0baf4306d9493798/comment/653b598799e256838d60981c)

Do you serve the Laravel app on a subdomain?

In the Remix + Laravel example, both the route and api are served under `GET /users`, presumably because it’s just example code.

Curious how you have these running side by side for real.

Thanks 🙏

[Dave Calnan](https://hashnode.com/@davecalnan)

[Oct 28, 2023](https://hashnode.com/posts/adding-a-laravel-backend-to-a-remix-app/62a874fa0baf4306d9493798/comment/653b598799e256838d60981c#reply-653d9d5d8bb1c48f931a2af0)

They’re both on subdomains in my instance - so app.example.com and api.example.com.

For another project, I have deployed this architecture to a single server via Laravel Forge. The Remix web app is available at the root domain via an nginx reverse proxy to port 3000. The Laravel backend is only accessible over localhost on that server so the Remix backend makes calls to localhost:8000 on that same server.

That works fine for smaller projects where you don’t need to access the Laravel backend outside of the Remix backend.