Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Deployment process #238

Closed
tangollama opened this issue Dec 12, 2015 · 2 comments
Closed

Deployment process #238

tangollama opened this issue Dec 12, 2015 · 2 comments
Labels
🚀enhancement an issue/pull request that adds a feature to the application help wanted indicates that an issue is open for contributions

Comments

@tangollama
Copy link
Member

Here's a vision: I access the demo site, now I've got the whole app on my device.

Now from within the app, I initiate the process to "create the app," meaning deploy the system to an EC2 instance (or whoever we make the cloud provider), including automatically transferring the data I've been capturing and entering on my local machine into the cloud instance.

With Pouch/Couch, we could get that.

@tangollama tangollama added the 🚀enhancement an issue/pull request that adds a feature to the application label Dec 12, 2015
@tangollama tangollama added the help wanted indicates that an issue is open for contributions label Apr 22, 2016
@mnorbeck
Copy link

mnorbeck commented Dec 6, 2016

@tangollama Do we really need this for v1.0?

@broerse
Copy link

broerse commented Dec 7, 2016

If you use ember-cli-deploy-couchdb and make PouchDB talk to itself via api with ember-cli-deploy-couchdb-rewrites you can just sync data and app once to cloudant or any other CouchDB. After the one time sync you would run with your own data and app. You would not need something like EC2. I don't think we need this now but it is a nice vision.

matteovivona pushed a commit that referenced this issue Jan 15, 2021
…rt-incident-test

Revert "test(report-incident): improvements"
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🚀enhancement an issue/pull request that adds a feature to the application help wanted indicates that an issue is open for contributions
Projects
None yet
Development

No branches or pull requests

3 participants