Skip to content
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

Update guide_vaultwarden.rst #1568

Merged
merged 2 commits into from
Oct 11, 2023
Merged

Update guide_vaultwarden.rst #1568

merged 2 commits into from
Oct 11, 2023

Conversation

ppac
Copy link
Contributor

@ppac ppac commented Jul 22, 2023

data is stored in ~/vaultwarden/data/ instead of ~/vaultwarden/output/data

data is stored in ´~/vaultwarden/data/´ instead of ´~/vaultwarden/output/data´
@noave
Copy link
Contributor

noave commented Jul 25, 2023

I cannot really follow your approach here, as far as I see, the command ./docker-image-extract vaultwarden/server:alpine will install the vaultwarden code into the output folder. Is that something you want to change or you just want to put the backup somewhere else?

(I marked the PR as draft please change it back to ready if this is completed from your perspective)

@noave noave marked this pull request as draft July 25, 2023 11:55
@ppac
Copy link
Contributor Author

ppac commented Jul 25, 2023

Yes, Vaultwarden itself is installed into the vaultwarden/output-folder. The database is stored in the vaultwarden/data-folder as you can see here:

[isabell@stardust ~]$ export DATA_FOLDER=$HOME/vaultwarden/data

So, from my point of view, there is a need for an adjustment of the paths (which I have done). I've double-checked my own Vaultwarden-instance and there is no data stored in the vaultwarden/output-folder.

@escuco
Copy link
Contributor

escuco commented Jul 25, 2023

I can confirm that the backup won't work with the actual commands and this PR from @ppac makes sense. I hadn't noticed this before because I didn't used the backup in this way before.
(tested on my own installation)

@ppac
Copy link
Contributor Author

ppac commented Jul 26, 2023

That's just the paths, you also need to change the part for the cronjob. I could not use the command in the crontab, but had to create a bash script to do the magic.

@ppac ppac marked this pull request as ready for review July 26, 2023 15:41
added some more information for the CRON job
@kimdiallo kimdiallo self-requested a review October 10, 2023 10:48
@kimdiallo kimdiallo merged commit f310919 into Uberspace:main Oct 11, 2023
@kimdiallo
Copy link
Contributor

works, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants