starred/ntfy

Fork 0

mirror of https://github.com/binwiederhier/ntfy.git synced 2026-05-09 08:26:00 +02:00

[GH-ISSUE #256] Unable to host on a subdirectory. #199

New issue

Closed

opened 2026-05-07 00:21:22 +02:00 by BreizhHardware · 5 comments

BreizhHardware commented

2026-05-07 00:21:22 +02:00

Owner

Originally created by @ppebb on GitHub (May 16, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/256

Despite the base url option, when hosting somewhere that isn't the root directory, it will still load resources as if it was in the root directory.

Originally created by @ppebb on GitHub (May 16, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/256 Despite the base url option, when hosting somewhere that isn't the root directory, it will still load resources as if it was in the root directory.

BreizhHardware

2026-05-07 00:21:22 +02:00

closed this issue
added the
web-app

enhancement

server
labels

BreizhHardware commented

2026-05-07 00:21:22 +02:00

Author

Owner

@binwiederhier commented on GitHub (May 16, 2022):

Thank you for reporting.

I have tried semi-hard (may an hour of trying) to make the React app work with relative paths, when not all resources are embedded via JS import statements, nad it drove me up the wall. I figured nobody was asking for it yet so I shrugged it off.

I suppose I'll have to try again.

@binwiederhier commented on GitHub (May 16, 2022): Thank you for reporting. I have tried semi-hard (may an hour of trying) to make the React app work with relative paths, when not all resources are embedded via JS import statements, nad it drove me up the wall. I figured nobody was asking for it yet so I shrugged it off. I suppose I'll have to try again.

BreizhHardware commented

2026-05-07 00:21:23 +02:00

Author

Owner

@binwiederhier commented on GitHub (Mar 26, 2023):

Honestly I don't think I'll do this. It's tricky to know what will break with this and I think honestly it's not worth it. People have been fine so far, so I don't think it'll be too bad not to do this.

@binwiederhier commented on GitHub (Mar 26, 2023): Honestly I don't think I'll do this. It's tricky to know what will break with this and I think honestly it's not worth it. People have been fine so far, so I don't think it'll be too bad not to do this.

BreizhHardware commented

2026-05-07 00:21:23 +02:00

Author

Owner

@christaikobo commented on GitHub (Jan 15, 2024):

Just want to leave a note that people can make do but it is definitely not fine....

@christaikobo commented on GitHub (Jan 15, 2024): Just want to leave a note that people can make do but it is definitely not fine....

BreizhHardware commented

2026-05-07 00:21:23 +02:00

Author

Owner

@falkheiland commented on GitHub (Jan 22, 2024):

Just want to leave a note that people can make do but it is definitely not fine....

what purpose has your post, if you do not provide a way to do it?

@falkheiland commented on GitHub (Jan 22, 2024): > Just want to leave a note that people can make do but it is definitely not fine.... what purpose has your post, if you do not provide a way to do it?

BreizhHardware commented

2026-05-07 00:21:23 +02:00

Author

Owner

@christaikobo commented on GitHub (Jan 22, 2024):

Just want to leave a note that people can make do but it is definitely not fine....

what purpose has your post, if you do not provide a way to do it?

First of all, I'm not here to argue with you, I am just going to answer your question as is, and move on.

From my understanding, an issue or a ticket is where people discuss about a feature or a bug, and all kinds of people can participate as long as they provide feedback that positively contributes to the progression of said issue. This feedback is not necessarily limited to "provide a way to do it", just like in a normal project, PM, QA, dev, and marketing can all chime in from their perspective.

My post is just my feedback on the importance of this issue. I am not trying to force anything upon anyone, I just hope maybe when the maintainer got some free time and he may or may not think about this and give it another go. Maybe the possibility of him giving it another go increases a little bit based on my feedback.

I always have great appreciation towards people who work on open source projects. English is not my first language, so if my post came out wrong, it is not my true intention.

@christaikobo commented on GitHub (Jan 22, 2024): > > Just want to leave a note that people can make do but it is definitely not fine.... > > what purpose has your post, if you do not provide a way to do it? First of all, I'm not here to argue with you, I am just going to answer your question as is, and move on. From my understanding, an issue or a ticket is where people discuss about a feature or a bug, and all kinds of people can participate as long as they provide feedback that positively contributes to the progression of said issue. This feedback is not necessarily limited to "provide a way to do it", just like in a normal project, PM, QA, dev, and marketing can all chime in from their perspective. My post is just my feedback on the importance of this issue. I am not trying to force anything upon anyone, I just hope maybe when the maintainer got some free time and he may or may not think about this and give it another go. Maybe the possibility of him giving it another go increases a little bit based on my feedback. I always have great appreciation towards people who work on open source projects. English is not my first language, so if my post came out wrong, it is not my true intention.

BreizhHardware referenced this issue

2026-05-07 00:22:30 +02:00

[GH-ISSUE #346] Support Web Push + PWA, for background notifications #269

BreizhHardware referenced this issue

2026-05-07 00:25:16 +02:00

[GH-ISSUE #744] Web app build / dev tooling - Vite, prettier, eslint? #543

BreizhHardware referenced this issue

2026-05-07 01:01:57 +02:00

[PR #751] [MERGED] Add PWA manifest, service worker, and web push #1406