mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #951] .latest not loading latest built #673
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#673
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @yelch on GitHub (Apr 6, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/951
I am happily using bitwardenrs on my synology and it's working great. Thank you!
The only 'issue' I have is, that pulling .latest still pulls 1.13.1 instead of 1.14.1
@jjlin commented on GitHub (Apr 6, 2020):
I'm not familiar with how things work on Synology, but I assume ".latest" is a Synology thing? This is something you should take up with whoever is providing/packaging bitwarden_rs on Synology.
@yelch commented on GitHub (May 8, 2020):
(sorry for the late reply). This is my source: https://registry.hub.docker.com
I'll try to reach somebody there... Tnx
@dani-garcia commented on GitHub (May 13, 2020):
If you are using the docker hub images, bitwardenrs/server:latest will get you the latest commit, which is newer than 1.14.2, if it doesn't there's something weird in your docker config somewhere.
If you are using some synology package, then no idea because we don't maintain those.