-
Notifications
You must be signed in to change notification settings - Fork 29
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
Support for self-hosted instances in the Mobile App/Browser extensions #65
Comments
Thanks for opening an issue! Happy to add this, though I have a bunch of things on my todo. If you're handy with JavaScript I'd welcome a PR, otherwise I'll probably take a stab at adding some instructions for building a copy of the extension yourself with a modified API URL. |
Sure, I can try helping you with this feature. Would you mind pointing me to the source code? |
Sorry! Missed this reply. You can find the associated source code for the webextension here: https://github.com/julianpoy/RecipeSage/tree/master/packages/webextension-v3 |
Is the Android app native, or a wrapper of the mobile website (I can't seem to find the source code)? Would like to take a stab at implementing this feature if I have the time :) |
The android app is just a wrapper of the website, so not much to implement there - just add your self hosted site to home screen and it'll be the same experience and the mobile app. For the webextension, there's an ongoing effort here to bring support but a few outstanding issues before it's ready to be merged. The author may have moved on, so you're welcome to take a stab at finishing it up if you'd like! |
Hello,
I haven't been able to find the code repositary for either the RecipeSage mobile app or browser extension, they might not be open source, so I'm posting it here, I hope it's fine. I think it would be nice to add the option to choose the RecipeSage instance that we want to connect to. As of right now, the app and browser extensions can't be used for selfhosted servers.
I think Bitwarden/Vaultwarden did it correctly for example with the default URL set to the official server.
The text was updated successfully, but these errors were encountered: