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

Adding packages to PaaS sites #178

Closed
aldeed opened this issue Oct 8, 2014 · 0 comments
Closed

Adding packages to PaaS sites #178

aldeed opened this issue Oct 8, 2014 · 0 comments
Assignees

Comments

@aldeed
Copy link
Contributor

aldeed commented Oct 8, 2014

I didn't see an existing issue related to this, but I think we have discussed a bit before. Eventually it would be nice to allow users to install any Meteor/rc package to their instance, so that it then appears in the admin area to be enabled.

See discussion here: https://groups.google.com/forum/#!topic/meteor-core/YiQ0irA_CN8

I think the easiest way for now is to add this feature to https://reactioncommerce.com/account (reaction-drive), but we'd need to retool the way we build/run the images/containers I think. Needs discussion.

@aaronjudd aaronjudd added this to the Beta milestone Nov 7, 2014
@aaronjudd aaronjudd modified the milestones: Core Architecture, Beta Jan 19, 2015
@aaronjudd aaronjudd self-assigned this Feb 15, 2015
aaronjudd added a commit that referenced this issue Dec 3, 2015
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.

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

Resolves #53
Resolves #308
Resolves #178

*Remaining tasks*

solve undefined error
convert the rest of the payment packages
context sensitive widgets (context?)
update with detailed docs
(document all the existing "provides")
aaronjudd added a commit that referenced this issue Dec 3, 2015
##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 pushed a commit that referenced this issue Dec 3, 2015
cmbirk pushed a commit to cmbirk/reaction that referenced this issue Aug 18, 2019
…t-pe-plugin-updates

chore: updated pricing plugin to latest
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants