- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 294
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
Feature Request: Client / Server, remote location, multiple users #586
Comments
for now, no. i don't recommend to add any new feature request for bukuserver until the required package is update for multiple user, the only way to do it is to use multiple ip and port combination with DB_FILE env variable point to different files |
Please don't add any authentication, user management or other features like this to Buku. I like Buku because it is inherently single-user only and local-first, unlike many other bookmarking systems. Those features make installation more complex and are hard to get right, both from a UX perspective and security. |
Should there be a need for authentication (i.e. to limit external access), such a thing can probably be achieved by proxying the access through a proper web-server (such as nginx); so I don't believe there's any reason to add it into the app itself. |
@mitchweaver please test my bot. It creates databases under The bot is still under testing, and namely needs interface improvements. If the developers would allow, I intend to integrate the bukuserver with XMPP too, so it would have access to XMPP PubSub Nodes on which data can be shared publicly. Integrating the bukuserver with XMPP would also allow to remotely operate the bukuserver of any machine, even when port-forwarding is not allowed on a network. |
Apologize if I'm misunderstanding, but is there no way to install buku as a server to enable for remote-access and/or multiple user connections?
I'm imagining for example a buku "instance" installed and an exposed port you could do
buku --remote ip:port
to access.Currently this is theoretically possible by using the
--db
tag and having an NFS mount of the server's db, on each client. This works... but is messy.Any plans to support this more natively?
The text was updated successfully, but these errors were encountered: