Zotero self-hosted

Hello,

We are very interested in having our own self-hosted Zotero.

Based on the posts underneath and the two projects on Github I was wondering what the current status is of these projects is. Would one of the two be the (official?) Docker-version which adamsmith is referring to?

https://forums.zotero.org/discussion/comment/309275
https://forums.zotero.org/discussion/comment/316306

https://github.com/mrtcode/zotero-server
https://github.com/gfacciol/zotero_dataserver-docker

Thank you!
  • Neither of those would be the official Zotero docker image (that would be hosted at https://github.com/zotero).

    The Zotero server code is here:
    https://github.com/zotero/dataserver

    The first GitHub link you gave indicates that’s it’s Zotero 5.0-based, so it might work, but it’s not officially endorsed in any way by Zotero.
  • Thank you for your immediate reaction and explanation.

    From previous comments I read there is no actual ETA for the Docker; is it realistic to still put our hopes on this year?

  • Taken literally, the answer to your question is yes -- it is realistic to put your _hopes_ on this year, but you shouldn't plan on it. My impression is that the docker container isn't actually a ton of work in comparison, but it's also not super high on Zotero's priority list compared to issues affecting many thousands of users and that sometimes somewhat randomly pop-up and require attention.

    FWIW, mrtcode works for Zotero, so what you see on his repo is either a Zotero developer trying this out because they're curious, or an early attempt from Zotero. I'd give that version a shot.
  • Dan Stillman also indicated in February that official Docker support would be predicated on dropping sync support for Zotero 4.0. See https://github.com/zotero/dataserver/issues/75#issuecomment-368259275.

    I'm not aware of a public ETA for that, though, although it's been over a year since 5.0 was released, so most people likely have migrated by now.
  • 4.0 sync is no more as of end of August, so that's one checkmark.
  • We didn't plan on it, like you suggested, but now that Spring 2019 is here :-) I hope you don't mind me asking again regarding the self-hosted version and it's status and/or release date.

    Thank you!
  • As it is fall 2021 an no answer was given in spring 2019 - i'd like to re-ask the question.

    Maybe I missed another thread or any other information. I would be happy if someone could point me in the right direction.

    Thank you in advance!
  • There are no updates on this. Anything official would be easy to spot on Zotero's GitHub.
    https://github.com/ZotPrime/zotprime is the best maintained community option
  • Awesome, thank you for that hint!

    Best regards!
  • Any update on this question?
  • Nothing new since last September
  • I'm also interested in this. Would zotero developers (or others) be incentivized by a bounty?
  • Noting the earlier comment that "zotprime is the best maintained community option"
    I note that the last updates appear to be about 5 years ago.
    https://github.com/foxsen/zotero-selfhost is slightly newer. No experience (yet) of running it though...
  • Is there a plan to update here? Or is it still possible to use this project?
  • The official dataserver code (second post above) is up to date and, in principle, allows you to run on prem (with a patched client). I don't believe any of the current examples linked here are up to date, so you can look to them for general guidance, but probably to for actually running the project.
    Zotero has talked about potentially releasing a dataserver docker, but no idea if/when they'll do that.
  • Thanks. Would be a real plus for some organisations than needs to manage their data... If we can help, tell me.
  • All code is open, so you can absolutely work on this and release your custom version as others have done previously.
  • It would be amazing if it worked as flawlessly as self-hosting Bitwarden, being able to switch between servers using the official client software.
Sign In or Register to comment.