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 #7679] [Feature] Feasibility to rewrite codebase to use PostgreSQL and maintain a free web hosted version with auth? #117540

New Issue
Closed
opened 2026-06-11 12:46:18 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-06-11 12:46:18 -05:00
Owner
Copy Link

Originally created by @devpatel511 on GitHub (May 2, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7679

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'm a major mobile user (and see great benefit to having instantaneous access to your budget from wherever and whenever) and would love to access my budget through my phone and not have to worry about maintaining a personal server (a web app is technically easier to maintain and cheaper with available online services).

What do you guys think of this? I'm assuming this has probably been thought through by the creators, so I'm curious to know what major hindrances prevented this from being considered for development?

Describe your ideal solution to this problem

The current PWA already looks decent enough to use and would prevent any native code from being required to maintain a mobile app. I believe that to host this service, the only change would be to add a server database (PostgreSQL) and authentication.

How difficult would this be to implement/rewrite with the aid of AI tools? Any major obstacles I may be overseeing?

Teaching and learning

No response

Originally created by @devpatel511 on GitHub (May 2, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7679 ### 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'm a major mobile user (and see great benefit to having instantaneous access to your budget from wherever and whenever) and would love to access my budget through my phone and not have to worry about maintaining a personal server (a web app is technically easier to maintain and cheaper with available online services). What do you guys think of this? I'm assuming this has probably been thought through by the creators, so I'm curious to know what major hindrances prevented this from being considered for development? ### Describe your ideal solution to this problem The current PWA already looks decent enough to use and would prevent any native code from being required to maintain a mobile app. I believe that to host this service, the only change would be to add a server database (PostgreSQL) and authentication. How difficult would this be to implement/rewrite with the aid of AI tools? Any major obstacles I may be overseeing? ### Teaching and learning _No response_
GiteaMirror added the featureneeds votes labels 2026-06-11 12:46:18 -05:00
GiteaMirror commented 2026-06-11 12:46:21 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 2, 2026):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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:4363110224 --> @github-actions[bot] commented on GitHub (May 2, 2026): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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#117540
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?