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

On-Prem Deployment Support #10521

Open
12 tasks
khavinshankar opened this issue Feb 9, 2025 · 1 comment
Open
12 tasks

On-Prem Deployment Support #10521

khavinshankar opened this issue Feb 9, 2025 · 1 comment
Labels
blocked GSoC Issues Created as part of Google Summer of Code needs-triage question Further information is requested

Comments

@khavinshankar
Copy link
Member

khavinshankar commented Feb 9, 2025

Project Detail

The On-Prem Deployment Support project aims to enable a complete offline deployment of CARE for individual facilities. Unlike the current cloud-based central server model, this feature will allow each facility (hospital) to host its own CARE server locally. The on-prem instance should operate independently with full functionality while offering options for optional data synchronization with a central server if needed.

Features To Be Implemented

  • Local Server Deployment: Develop a package or installer for deploying CARE on local servers.
  • Independent Operation: Ensure that the on-prem instance functions fully independently without reliance on a central cloud server.
  • Data Synchronization (Optional): Implement an optional mechanism for synchronizing data between local instances and a central server.
  • Configuration Management: Provide configuration tools and documentation to tailor the on-prem deployment for facility-specific requirements.
  • Deployment Automation: Create scripts and automation tools to streamline the installation and maintenance of local CARE servers.

Note: The on-prem deployment should retain all core functionalities of CARE while ensuring robust performance, data security, and ease of management in a local environment.

Learning Path

Details
Complexity Large
Required Skills ReactJS, NodeJS, TypeScript, Django, DevOps, Docker, Deployment Automation
Mentors @sainak @dauntlessnomad @rithviknishad
Project Size 350 hours

Link to documentation for Product Set-Up

  1. For setting up the frontend, please refer to the readme file available at: CARE Frontend
  2. For setting up the backend, please refer to the readme file available at: CARE Backend

Acceptance Criteria

  • A deployable on-prem package or installer is available for local setup.
  • The local CARE instance operates independently with full core functionalities.
  • Optional data synchronization (if implemented) functions reliably.
  • Detailed configuration tools and documentation are provided.
  • All CI/CD tests pass with thorough testing, QA, and code reviews completed.

Milestone

  • Assess the current CARE architecture for on-prem deployment viability.
  • Define requirements for an independent local CARE server.
  • Develop deployment packages, installers, and configuration management tools.
  • Implement optional data synchronization mechanisms.
  • Test the on-prem deployment in simulated facility environments.
  • Finalize documentation, complete QA, and conduct code reviews.
  • Release the on-prem deployment package.
@khavinshankar khavinshankar added blocked GSoC Issues Created as part of Google Summer of Code labels Feb 9, 2025
@tellmeY18 tellmeY18 added this to Care Feb 9, 2025
@tellmeY18 tellmeY18 moved this to Triage in Care Feb 9, 2025
@drmaddy736
Copy link

drmaddy736 commented Feb 10, 2025

As a doctor, my inputs...Patient login may not be required, on premises file storage (a lot of files/scanned copies... daily round notes on papers, lab(mostly they use their own software and provide soft copies or printed reports) reports, insurance documents, consent forms, referal letters , also insurance companies need to send original documents for cashless processing so whole file needs to be scanned and stored.Even with paperless administration goal, these papers are going stay there so cloud storage should be optional only as it costs much.

@github-actions github-actions bot added needs-triage question Further information is requested labels Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked GSoC Issues Created as part of Google Summer of Code needs-triage question Further information is requested
Projects
Status: Triage
Development

No branches or pull requests

2 participants