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

Per-app filesystems #444

Open
Tracked by #501
jeffgca opened this issue Dec 13, 2022 · 2 comments
Open
Tracked by #501

Per-app filesystems #444

jeffgca opened this issue Dec 13, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@jeffgca
Copy link
Contributor

jeffgca commented Dec 13, 2022

Developers as app publishers have a fission account and webnative filesystem. It should be possible for developers to use a per-app section of private storage.

@jeffgca jeffgca added the enhancement New feature or request label Dec 13, 2022
@icidasset
Copy link
Contributor

Is this where we go back to the idea of putting published apps in the file system? If so, where would you put them? We currently put application data in private/Apps/${appCreator}/${appName}/. Could we keep roughly the same pattern for this and put the apps in public/Apps/${appCreator}/${appName}/? 🤔 Not sure if that would clash with public app data though... Thoughts?

In the past we've talked about app cloning, so with this pattern a developer's apps could live side-by-side with their cloned apps. The idea behind cloned apps is that if you see an app you like and would like to freeze updates to it, you could clone it (and later still update if you want).

@icidasset
Copy link
Contributor

Just noticed that the dashboard puts them in public/Apps/${appName}/Published (correct me if I'm wrong @matheus23)
This should probably be public/Apps/${appCreator}/${appName}/Published/ to stick with the existing naming convention.

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

No branches or pull requests

2 participants