-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move rooter to own crate #156
Comments
Hi @kanongil , this is super 🦸♂️ and indeed in my mind I planned to move these 2 out to their own crates. Let me see if I can do this over the week-end for you. Thank you for helping further our vision as described here. You came as if you were sent! ![]() The Auth0 authenticator is especially one that I'd love to see out there. If you plan to move it to its own crate consider using our naming convention described in the contribution guide here. |
Cool. This is my first real rust project, so I'm not sure how far I will take it, but creating a version that can be published for others to use is definitely in my thoughts. At least I'm used to publishing / supporting node.js modules, so that part won't be all new. |
Hi @kanongil, see here: https://crates.io/crates/unftp-sbe-rooter Does it work for you? |
Awesome! Yes, it works as expected – thanks for the quick turnaround 👍 |
@kanongil great to hear! The documentation is lacking still |
I've split out the restrict.rs module to. See here: https://crates.io/crates/unftp-sbe-restrict |
I'm using libunftp and have developed a custom auth integration against Auth0. It authorises the user and returns the location of the user's dir on the local FS. However, there is no simple way to change the served dir.
I see that the unFTP storage/rooter.rs already handles this, and was wondering if you could move it to it's own crate that everyone can use?
FYI, the storage/restrict.rs module could probably be useful as an independent module as well, eg. to enable readonly access for the user.
The text was updated successfully, but these errors were encountered: