5220bd527b
Refs #1059. When you auto-match a $500 expense from your checking account against the matching deposit on your credit card, the resulting transfer pair was leaving traces in the per-card "Recent transactions" list under each budget category card, even though the aggregate `Budget#actual_spending` (via `IncomeStatement`) already excluded `BUDGET_EXCLUDED_KINDS` (funds_movement / one_time / cc_payment) from the totals. The user saw $X under the card while the totals showed $X less. Fix: extend the same exclusion to the drilldown list. The aggregate and the list now agree. ```ruby # app/controllers/budget_categories_controller.rb @recent_transactions = @budget.transactions .where.not(transactions: { kind: Transaction::BUDGET_EXCLUDED_KINDS }) ``` `loan_payment` and `investment_contribution` are intentionally NOT in `BUDGET_EXCLUDED_KINDS`, so those transfers still appear (they are budget-tracked). What this PR does NOT do: - It does not clear the matched transactions' `category_id` in the matcher itself. An earlier draft of this PR did, but codex correctly flagged that doing so causes data loss when a user rejects an incorrect auto-match: `Transfer#reject!` resets `kind` to `standard` but does not restore the previously-cleared category, permanently dropping the user's original categorisation. The controller filter alone is sufficient to fix the user-visible bug, and the inconsistency between `kind = funds_movement` and a retained category is harmless because every relevant view filters one or the other. - The mortgage scenario in #1059 (a `loan_payment` match showing as "Uncategorised" in the budget) isn't a leak; it is a missing feature. The matcher doesn't auto-assign a category to `loan_payment` rows the way #924 does for `investment_contribution`. The natural follow-up is a parallel `loan_payments_category` plus matcher / import-adapter auto-assignment, which deserves a maintainer signoff first. Tests: - `BudgetCategoriesControllerTest#show drilldown excludes BUDGET_EXCLUDED_KINDS transfers from recent transactions`: a matched depository <-> CC pair does not appear in the Uncategorised drilldown after the matcher runs. - `BudgetCategoriesControllerTest#show drilldown still lists loan_payment transfers (intentionally budget-tracked)`: a matched depository <-> loan pair stays visible in the drilldown. Suite: 3239 / 0 / 0 / 24 on the latest upstream/main. Lint clean.
Deutsch | Español | Français | 日本語 | 한국어 | Português | Русский | 中文
Sure: The personal finance app for everyone
Get involved: Discord • Website • Issues
Important
This repository is a community fork of the now-abandoned Maybe Finance project.
Learn more in their final release doc.
Backstory
The Maybe Finance team spent most of 2021–2022 building a full-featured personal finance and wealth management app. It even included an “Ask an Advisor” feature that connected users with a real CFP/CFA — all included with your subscription.
The business end of things didn't work out, and so they stopped developing the app in mid-2023.
After spending nearly $1 million on development (employees, contractors, data providers, infra, etc.), the team open-sourced the app. Their goal was to let users self-host it for free — and eventually launch a hosted version for a small fee.
They actually did launch that hosted version … briefly.
That also didn’t work out — at least not as a sustainable B2C business — so now here we are: hosting a community-maintained fork to keep the codebase alive and see where this can go next.
Join us!
Hosting Sure
Sure is a fully working personal finance app that can be self hosted with Docker.
Forking and Attribution
This repo is a community fork of the archived Maybe Finance repo. You’re free to fork it under the AGPLv3 license — but we’d love it if you stuck around and contributed here instead.
To stay compliant and avoid trademark issues:
- Be sure to include the original AGPLv3 license and clearly state in your README that your fork is based on Maybe Finance but is not affiliated with or endorsed by Maybe Finance Inc.
- "Maybe" is a trademark of Maybe Finance Inc. and therefore, use of it is NOT allowed in forked repositories (or the logo)
Performance Issues
With data-heavy apps, inevitably, there are performance issues. We've set up a public dashboard showing the problematic requests seen on the demo site, along with the stacktraces to help debug them.
https://www.skylight.io/app/applications/s6PEZSKwcklL/recent/6h/endpoints
Any contributions that help improve performance are very much welcome.
Local Development Setup
If you are trying to self-host the app, read this guide to get started.
The instructions below are for developers to get started with contributing to the app.
Requirements
- See
.ruby-versionfile for required Ruby version - PostgreSQL >9.3 (latest stable version recommended)
- Redis > 5.4 (latest stable version recommended)
Getting Started
cd sure
cp .env.local.example .env.local
bin/setup
bin/dev
# Optionally, load demo data
rake demo_data:default
Visit http://localhost:3000 to view the app.
If you loaded the optional demo data, log in with these credentials:
- Email:
user@example.com - Password:
Password1!
For further instructions, see guides below.
Setup Guides
- Mac dev setup
- Linux dev setup
- Windows dev setup
- Dev containers - visit this guide
One-click
License and Trademarks
Maybe and Sure are both distributed under an AGPLv3 license.
- "Maybe" is a trademark of Maybe Finance, Inc.
- "Sure" is not, and refers to this community fork.
