Din pålitliga taxi i Borlänge website

Description and use

The taxi website was routed to the correct domain, frontend and API paths were separated, and all routes were verified for accessibility.

Problem

Ensuring the correct website appears at the custom domain and routing works for a multi‑app Replit project.

Outcome

The taxi website now loads correctly at the custom domain, with proper routing for the main site, secondary app, and API, enabling functional booking and contact forms.

Workflow

• 1. Identify visitor needs and design clear pages.
• 2. Build frontend with React/Vite and backend Node API.
• 3. Verify domain DNS points to Replit.
• 4. Publish the project and check the build.
• 5. Adjust route assignments: taxi site to /, Daylight to /daylight/, API to /taxi-api/api.
• 6. Separate router base from API base to avoid routing bugs.
• 7. Test homepage, secondary apps, API reachability, and domain publishing.
• 8. Iterate until all checks pass.

Evidence

The domain had been verified, so I expected the taxi site to appear there. But when I checked the live domain, it showed a different app already in the project.

Source

I wanted the taxi site to be the homepage without deleting Daylight, so I changed the route assignments: Din Borlänge Taxi now uses /, Daylight remains available at /daylight/, The taxi API uses /taxi-api/api.

Source

The app used a base-path variable both for API requests and for the client-side router. When I changed the API prefix, the router started treating /taxi-api/ as the website’s base route. The page loaded blank.

Source