UMass-Rescue / UMass-Rescue/RescueBox

RescueBox: make current app more secure with https and go for distributed setup

Open
#62 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement good first issue hackathon
Dominant language
Python
Stars
6
Forks
15
Avg merge
14h 42m
Merged PRs (30d)
7

Description

current fastapi server is http only. change this to be https only , enabling it to be more secure

fastapi

how about the frontend ? add a login screen

benefit : is this is secured , now you can work on a distributed setup with backend on hostA and frontend on hostB , however these 2 hosts must be on the same subnet and not one local and another the cloud or lab

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the current FastAPI server and frontend entry point, then review the linked FastAPI security guidance. Done means the server is HTTPS-only, the frontend has a login screen, and the backend/frontend can be deployed on separate hosts on the same subnet.

Written by the indexing model from the issue text.

Assessment

Tech stack
fastapi, python
Domain
api, authentication, backend, distributed-systems, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.