Statusfy breaks in subfolder/ needs fixing

[weeblr]

Feature request

• I confirm that this is a feature request rather than a question. Well not really, your opinion will vary.

What problem does this feature solve?

Statusfy currently breaks when used in a subfolder instead of the usual root folder. The issue has been discussed here: #163

The outcome was that it was "too hard" to fix for coding reasons and there were many hosting alternatives that would not require using using subfolders.

I'd like to remind you of a coding/hosting configuration that's very common and require using subfolder: using an on-premise instance of Gitlab. When using Gitlab that way, ie on premise, the standard Gitlab pages configuration generate URLs like so:

group.domain.com/pages-project-name

It is not impossible to use a custom domain in such instance but it is really, really difficult and in most instances I would think any potential Statusfy user would skip it, as I am, because of this. As a reminder, here is what using a custom domain with self-hosted Gitlab entails:

In the case of custom domains (but not wildcard domains), the Pages daemon needs to listen on ports 80 and/or 443. For that reason, there is some flexibility in the way which you can set it up:

Run the Pages daemon in the same server as GitLab, listening on a secondary IP.
Run the Pages daemon in a separate server. In that case, the Pages path must also be present in the server that the Pages daemon is installed, so you will have to share it via network.
Run the Pages daemon in the same server as GitLab, listening on the same IP but on different ports. In that case, you will have to proxy the traffic with a loadbalancer. If you choose that route note that you should use TCP load balancing for HTTPS. If you use TLS-termination (HTTPS-load balancing) the pages will not be able to be served with user provided certificates. For HTTP it’s OK to use HTTP or TCP load balancing.

Either setting up a second IP, sharing the dist folder over a network share or setting up a load balancer with specific configuration just to be able to serve over HTTPS. Thank you, I'll jsut go back to using Cachet!

Not being able to operate on self-hosted Gitlab is a big when you consider potential Statusfy users I think. Please reconsider.

What does the proposed API look like?

How should this be implemented in your opinion?

Use nuxt.js router to properly link item when in subfolder.

Are you willing to work on this yourself?**

[open-collective-bot]

Hey @weeblr 👋, Thank you for opening an issue.

Check out our OpenCollective and consider backing us. Help us to continue developing this Amazing Project, we will appreciate it ❤️.

You can contribute from $2 🤓, less than a cup of coffee ☕ 😃

https://opencollective.com/statusfy

PS.: We offer priority support for all backers. Don't forget to add priority label when you start backing us 😄

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[kskarthik]

support for subpaths would be greatly appreciated 😄

[juliomrqz]

@kskarthik We’re reconsidering this feature for the next major release (v1)