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

Graduate from standAlone to traditional cloud/server deployment #1048

Description

@tangollama

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.

Metadata

Metadata

Labels

devopsissue/pull request that includes changes to documentation to devops processesneeds requirementsindicates that an issue needs more requirements in order to be worked onv2.xwontfixindicates an issue/pull request will not be worked on🚀enhancementan issue/pull request that adds a feature to the application

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions