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

Graduate from standAlone to traditional cloud/server deployment #1048

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

Graduate from standAlone to traditional cloud/server deployment #1048

tangollama opened this issue Apr 5, 2017 · 6 comments

Comments

@tangollama
Copy link
Member

@tangollama 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
Copy link
Member Author

@tangollama tangollama commented Apr 19, 2017

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

@jeremyklein
Copy link

@jeremyklein jeremyklein commented Jul 26, 2017

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

@tangollama tangollama commented Jul 26, 2017

@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 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 label Aug 7, 2019
@fox1t
Copy link
Member

@fox1t 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 label Aug 7, 2019
@fox1t fox1t added v2.x and removed help wanted labels Aug 7, 2019
@tehKapa tehKapa added the devops label Aug 7, 2019
@tehKapa tehKapa added this to the v2.0.0 milestone Aug 7, 2019
@stale
Copy link

@stale 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 label Oct 6, 2019
@fox1t fox1t closed this Jan 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.