[Feature request]: A way to move app cache to RAM

Open
#6,840 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c, linux
Domain
backend

Research direction

The request concerns where Flatpak stores an app's cache and asks for a supported way to place it in RAM; it does not identify files, tests, or an implementation entry point. Start by reading how app caches are currently configured and why symlinking to /run/user/$UID/app was disabled for security reasons. Done means a safe, straightforward RAM-backed cache option is available; the issue does not specify its design.

Written by the indexing model from the issue text.

Description

enhancement needs triage
Checklist
  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Suggestion

I used to symlink the app cache to /run/user/$UID/app (no permission changes needed), but it seems this was disabled in v1.18.1 or v1.19.0 for security reasons.

I'd like to request a straightforward method to move the app cache to RAM.

Dominant language
C
Stars
5.1k
Forks
526
Avg merge
3d 1h
Merged PRs (30d)
23

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flatpak/flatpak

All issues in flatpak/flatpak

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.