Is exposing customized endpoints for organizations within scope of this project?

[sargunv]

Hey, I'm an ex-Bunny user, and I've been wanting to set up something similar to Bunny for both myself and for the team I work with now. Wondering if adding the ability to expose a custom endpoint for an organization is within scope for this project, or if I should look into self-hosting a customized fork instead.

[taneliang]

Hey, thanks for reaching out. Really cool that you're considering using this :D

Yeah, I think for now it'll be easiest to self host a fork so that you can add and update your handlers without going through me. It should be really easy to deploy this, but lmk if you run into any issues.

However, I've also started using Neh at work and I think it'll be a lot more useful if we had more custom handlers for the company that weren't also exposed to the general public.

To support that use case, I have been thinking of building in some sort of federation of multiple self-hosted Neh instances. For example, the "iron" handler I've built for my company could just 302 redirect to a company-hosted Neh instance, which could be built and secured as the company sees fit without adding too much complexity to Neh itself.

Having said that, this is a longer term idea and there's definitely no timeline for building this