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.

Sign up for GitHub

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

Jump to bottom

Reaction Apps install manager #146

Closed
aldeed opened this issue Jul 23, 2014 · 2 comments
Closed

Reaction Apps install manager #146

aldeed opened this issue Jul 23, 2014 · 2 comments
Assignees
@aaronjudd @jshimko
Milestone
v0.14.0

Comments

@aldeed
Copy link
Contributor

aldeed commented Jul 23, 2014 •
edited by aaronjudd
Loading

(rapp = reaction app)

In app gallery, we can enable/disable, which turns on/off the UI related to that rapp. We can also meteor remove the pkg. But afaik, we can't currently "uninstall" the rapp. That is, if the rapp has stored data in its own collections or in reaction collections, we should be able to remove that data.

  • UI: Possibly ask when disabling whether the rapp's data should be deleted?
  • Code: Provide a way for a rapp to register a function that reaction-core will call to request full data removal. Should handle any and all schema versions.

This is related to the idea of dynamically adding and removing rapps, which we have discussed. If we were to provide a way within the UI to remove a rapp (not just disable), then this should call the rapp's data removal function before removing the rapp code.
@aaronjudd aaronjudd added this to the Core Architecture milestone Jan 19, 2015
@aaronjudd aaronjudd mentioned this issue Mar 16, 2015
Closed
@aaronjudd aaronjudd changed the title Removing a rapp Reaction Apps install manager Jul 23, 2015
@aaronjudd
Copy link
Contributor

See also: #247, version upgrade, delete, revision history probably all come into play here as well.

aaronjudd added a commit that referenced this issue Dec 3, 2015
@aaronjudd
completed package-registry-refactor
3de2369 
##package-registry-refactor
Changes that refactor the `ReactionCore.registerPackage`
implementation to a more flexible, and structured template
registry. `ReactionCore.registerPackage` moves to server.
package.registry is published to client.

cycle = Core, Stable, Testing (todo: => correlates package semver)
container = combine multiple registry entries

These are not backwards compatible changes.

Updated documentation at docs/packages.md

Initial commit for issue #314

Strategic updates for Issue #273
Strategic updates for Issue #306
Strategic updates for Issue #305
Strategic updates for Issue #246
Strategic updates for Issue #183
Strategic updates for Issue #155
Strategic updates for Issue #16
Strategic updates for Issue #148
Strategic updates for Issue #146

Resolves #53
Resolves #308
Resolves #178
@aaronjudd aaronjudd modified the milestones: v0.14.0, Core Architecture Jun 28, 2016
@aaronjudd aaronjudd removed the backlog label Jun 28, 2016
@aaronjudd
Copy link
Contributor

Resolved with #1112

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aaronjudd aaronjudd

@jshimko jshimko

Labels
None yet
Projects
None yet
Milestone
v0.14.0
Development

No branches or pull requests
3 participants
@aaronjudd @aldeed @jshimko