Support of base URL does not work as expected.

[Tchoupinax]

Description

Hello,

I try to setup homepage behind a subpath and for that I need to configure a base URL. I found into the documentation and Github issues that there are two options about that: base and startURL. However, any of thoses impact my configuration.

I found this discussion but the solution does not change.

I can see that the attribute base is correctly changed in my HTML page but resources URL are not impacted.

Also, I tried to edit the next configuration and build a new customized image:

• Before: Resources are not loaded (css, js) => the prefix misses
• After: Resources are loaded so the page works but api is not reachable, the prefix misses for api here

const nextConfig = {
   reactStrictMode: true,
   output: "standalone",
+  basePath: "/my-custom-path",
   images: {
     domains: ["cdn.jsdelivr.net"],
     unoptimized: true,
   },
   i18n,
};

When I add the base url, it's like this

and the result is here

homepage version

v0.8.9

Installation method

Docker

Configuration

settings.yaml


---
# For configuration options and examples, please see:
# https://gethomepage.dev/latest/configs/settings

title: My custom dashbaord
base: http://localhostd:3000/totot

disableCollapse: true
fiveColumns: true
headerStyle: clean
statusStyle: "dot"
useEqualHeights: true

Container Logs

No response

Browser Logs

No response

Troubleshooting

All API requests returns a 404 and it's normal because the frontend should prefix the request by the prefix (included in base or startUrl.

That's said, I reached out this state because I build a customized version with the prefix in the next config

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the context provided, it seems you are trying to set up the homepage application to work behind a subpath using Docker and are encountering issues with the base and startUrl settings not affecting your configuration as expected.

The base setting is indeed intended to change the base URL of your homepage instance, and the startUrl is used to customize the start URL for installable apps. However, it appears that setting these options in your settings.yaml file is not having the desired effect on resource URLs or API endpoints.

From the information provided, it seems you have attempted to modify the Next.js configuration directly by adding a basePath to the nextConfig object. This is a correct approach when you need to serve a Next.js application from a subpath. However, it's important to note that this change alone might not be sufficient if the application's server-side logic does not account for the new base path.

The images you've linked to show that the resources are not being loaded with the correct base path, which suggests that the application's static assets and API requests are not being properly prefixed.

To resolve this issue, you should ensure that:

1. The base setting in your settings.yaml file is correctly set to the subpath you want to use (e.g., /my-custom-path).
2. The basePath in the Next.js configuration is also set to the same subpath.
3. The application's server-side logic (including API endpoints) respects the basePath and correctly prefixes all routes with it.

If the application's server-side logic does not automatically handle the basePath, you may need to manually update the API endpoints and any other server-side routes to include the subpath.

Since you are building a customized version of the application, you may also need to review the server-side code to ensure that it is aware of the basePath and correctly constructs URLs for static assets and API requests.

If you continue to experience issues, you may want to reach out to the homepage community for support or consult the documentation for more detailed guidance on configuring the application for subpath deployment.

Unfortunately, without access to the actual repository and codebase, I cannot provide a more specific solution. Please ensure that you are following the latest documentation and consider opening an issue in the homepage repository if you believe there is a bug or if the documentation is lacking in this area.

This comment was generated by Glime.

[CosasDePuma]

Any update? This tips don't solve the issue.

[omidforoqi]

+1

[TomasMonkevic]

Having the same issue with traefik

[karco]

I'm very happy to find people with the same problem as my installation. I've spent a lot of time on it, but I still don't have a solution to display the page under .../homepage.

- “traefik.http.routers.homepage.rule=(Host($HOSTNAME.$DOMAINNAME_1) && PathPrefix(/homepage)) || Host(homepage.$DOMAINNAME_1)”