github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #3059] [Feature] Backup all budgets #42894

New Issue
Closed
opened 2026-04-26 03:04:03 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-26 03:04:03 -05:00
Owner
Copy Link

Originally created by @alarobric on GitHub (Jul 15, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/3059

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

I run Actual on my home server for my own use, but also provide access to my extended family to use for themselves. We've setup encryption on each budget, so I don't have access to their budget and vice versa. When it comes time to upgrade the system however, this means I can't backup their budget. On a previous upgrade this caused an issue when the data directories unexpectedly changed and we ended up losing data.
I'd like an ability to backup all budgets, so I can safely do an upgrade without having to ask my family members to backup their own budget individually.

I saw #826 which might help, but doesn't have quite the same use case.

Describe your ideal solution to this problem

  • Option to backup just one budget, or all budgets from the server.
  • Clearer documentation on what the docker data directories contain. Is it enough to backup this folder?

Teaching and learning

Some clearer documentation on how to manage an Actual server would help, i.e. what does the data layout look like, what operations should be done to upgrade and backup and restore and so on.

Originally created by @alarobric on GitHub (Jul 15, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/3059 ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? I run Actual on my home server for my own use, but also provide access to my extended family to use for themselves. We've setup encryption on each budget, so I don't have access to their budget and vice versa. When it comes time to upgrade the system however, this means I can't backup their budget. On a previous upgrade this caused an issue when the data directories unexpectedly changed and we ended up losing data. I'd like an ability to backup all budgets, so I can safely do an upgrade without having to ask my family members to backup their own budget individually. I saw #826 which might help, but doesn't have quite the same use case. ### Describe your ideal solution to this problem - Option to backup just one budget, or all budgets from the server. - Clearer documentation on what the docker data directories contain. Is it enough to backup this folder? ### Teaching and learning Some clearer documentation on how to manage an Actual server would help, i.e. what does the data layout look like, what operations should be done to upgrade and backup and restore and so on.
GiteaMirror added the needs votesfeature labels 2026-04-26 03:04:03 -05:00
GiteaMirror commented 2026-04-26 03:04:05 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 15, 2024):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

<!-- gh-comment-id:2229210179 --> @github-actions[bot] commented on GitHub (Jul 15, 2024): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#42894
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?