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

Graduate from standAlone to traditional cloud/server deployment #1048

Closed
5 tasks
tangollama opened this issue Apr 5, 2017 · 6 comments
Closed
5 tasks

Graduate from standAlone to traditional cloud/server deployment #1048

tangollama opened this issue Apr 5, 2017 · 6 comments
Assignees
Labels
devops issue/pull request that includes changes to documentation to devops processes 🚀enhancement an issue/pull request that adds a feature to the application needs requirements indicates that an issue needs more requirements in order to be worked on v2.x wontfix indicates an issue/pull request will not be worked on
Milestone

Comments

@tangollama
Copy link
Member

tangollama commented Apr 5, 2017

When someone downloads the electron app version of HospitalRun, they may want to "graduate" the single, desktop instance of the application to a traditional server-deployed model where the desktop instance is talking to an appliance or cloud server.

The application doesn't currently have a pathway to move from desktop instance to a traditional serve deployment. We need to that.

Potential workflow

  • Setup screen that allows user to login to AWS (if they don't have an account drives them outside of the app to setup an account
  • If logged into AWS, allows a one-click deployment of the latest docker image of hospitalrun to be deployment to an EC2 instance
  • Configures the Electron app to now consider that cloud instance the sync point for PouchDB to upload/sync data to the relater CouchDB instance.
  • That configuration information is sharable to other Electron deployments

#Potential features

  • Menu option in Gear on Electron deployment to upgrade to an cloud-backed deployment
  • Menu-accessible setup screen that allows user to login to AWS (or links outside to account setup in AWS)
  • From there, a one-click deployment process of an EC2 instance that houses the docker image (and related dependencies
  • Stored configuration of the CouchDB instance that this local instance is syncing to
  • Configuration screen for the CouchDB instance so that it can be setup

Note

I used AWS b/c that's what I'm using these days. I'm cloud provider agnostic on this. The point is that people in developing settings need to be able to access the service.

@tangollama tangollama added 🚀enhancement an issue/pull request that adds a feature to the application needs requirements indicates that an issue needs more requirements in order to be worked on labels Apr 5, 2017
@tangollama tangollama self-assigned this Apr 5, 2017
@tangollama
Copy link
Member Author

Once #1058 is merged into master, we could pursue this in earnest.

@tangollama tangollama added the help wanted indicates that an issue is open for contributions label May 24, 2017
@jeremyklein
Copy link

I am interested in getting involved with HospitalRun, and this enhancement sounds very interesting to me. Has there been any progress towards this? Is there any documentation of the traditional server-deployed model that might help drive requirements?

@tangollama
Copy link
Member Author

@jeremyklein thanks for reaching out and expressing an interest in working on this. There is a dockerized deployment of the app that can serve as one of the building blocks. After that, it might be most effective to talk it out amongst the two of us and then I'll document the plan better in this issue. Can you find me on the project Slack. I'm tangollama everywhere. :)

@stale
Copy link

stale bot commented Aug 7, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix indicates an issue/pull request will not be worked on label Aug 7, 2019
@fox1t
Copy link
Member

fox1t commented Aug 7, 2019

@tehkapa here @tangollama suggests some nice workflows for the final users. I think that the same path is achievable on other cloudproviders/on-premise if something like openstack is used.
This task deserves some more exploration.

@stale stale bot removed the wontfix indicates an issue/pull request will not be worked on label Aug 7, 2019
@fox1t fox1t added v2.x and removed help wanted indicates that an issue is open for contributions labels Aug 7, 2019
@matteovivona matteovivona added the devops issue/pull request that includes changes to documentation to devops processes label Aug 7, 2019
@matteovivona matteovivona added this to the v2.0.0 milestone Aug 7, 2019
@stale
Copy link

stale bot commented Oct 6, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix indicates an issue/pull request will not be worked on label Oct 6, 2019
@fox1t fox1t closed this as completed Jan 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
devops issue/pull request that includes changes to documentation to devops processes 🚀enhancement an issue/pull request that adds a feature to the application needs requirements indicates that an issue needs more requirements in order to be worked on v2.x wontfix indicates an issue/pull request will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants