Added option to run under subpath/basepath

[megamit]

Description

Can now pass in the BASE_PATH environment variable to tell overseerr to host under a sub path.
e.g. BASE_PATH=/request_some_stuff would run as example.com/request_some_stuff/

To-Dos

• Successful build yarn build

Issues Fixed or Closed

• Fixes Run overseerr on subpath, Base URL #274

[TheCatLady]

Looks pretty good 👍🏻

[TheCatLady]

Also, have you tested to verify the service worker still functions as expected when a base path is configured?

[megamit]

Also, have you tested to verify the service worker still functions as expected when a base path is configured?

I completely missed the service worker sorry. (was completely borked. wouldnt register either)
My new commit should fix it.

[TheCatLady]

I wonder if a wrapper for useRouter that sets the basePath property of the returned router object would work? 🤔 Then it wouldn't be necessary to add addBasePath to every router.push...

[megamit]

I wonder if a wrapper for useRouter that sets the basePath property of the returned router object would work? 🤔 Then it wouldn't be necessary to add addBasePath to every router.push...

Before doing the router.push/link wrapper i tried various incarnations of trying to monkey patch the basePath variable the router uses but the deeper i dug felt like it would be super hacky and fragile to implement. Internally the next/Link component is wrapper to router push/replace so if were able to patch router it would take care of those too.

Oh do you mean like a useRouter wrapper link the wrapper. Should be possible sure.

[stale]

This pull request 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.

[coder8338]

@megamit @TheCatLady Is there anything left to be done on this? Happy to help if you let me know what's remaining to get this merged.

[megamit]

@coder8338 This got stuck as i couldnt do this cleanly without messing with next.js internals using the approach i took.
It was fully working by my last commit (and i've been using it since) but would brittle to any refactoring nextjs could make to how they send rewrite logic to the ui router.
Next js would need to expose what i was attempting to modify as a proper api or this would be unmaintanable.

Most likely you would need to start from scratch on a different approach.

[crashkonijn]

Hi!

Would I be correct that this topic is about the same thing?

vercel/next.js#16059

Especially this topic (3 days old now) is about what we'd need for this to happen (if I understood it correctly)
vercel/next.js#41769

[danshilm]

@crashkonijn Yep that's exactly it