[NickJ-7010]

What

what the PR changes

• Oh boy where to begin...
• Added a proper README.md with running and setup instructions
• Added a docker-compose.yaml so that the project can be built and run easily
• Removed the HACKING folder and changed to a .env.example with updated env variables
• Added a real header.tmpl for the nav bar and use it across the app
• Updated the UI to use more bootstrap features and be
• A lot of other small changes :P

Why

why these changes were made

I wanted to make some improvements to the functionality of plug but getting it running was a struggle as it was not at all setup for local development.

Test Plan

how did you verify these changes did what you expected

A lot of local testing and asking eboard members to sanity check me.

Env Vars

did you add, remove, or rename any environment variables

• Renamed all of the csh auth env variables to be uppercase to follow conventions.
• Added a S3 bucket env variable S3_BUCKET_NAME to let devs specify the name of their S3 bucket instead of just trying to use the prod one which is plugs.
• Added an LDAP_WRITE_MODE env variable to allow for devs to disable the attempted ldap writes and crashing the backend.

Documentation

did you add or update any documentation. PRs should, at the minimum, update documentation when they make existing documentation out of date.

Made the README.md actually helpful for getting plug setup locally

Checklist

• Tested all changes locally
• Wrote this code wayyyyyy too late at night

[BigSpaceships]

:)

[BigSpaceships]

W memba, few thoughts, btw you don't need to add s3 to local running, and if you do, you could also do anotehr pr if you want

[BigSpaceships]

this is icky ):

[NickJ-7010]

It has been adjusted to look better than it did before!

[BigSpaceships]

not gonna make you but you could add an s3 client :)

[NickJ-7010]

do you mean like a lightweight s3 emulator in another container? Is this related to your review comment?

btw you don't need to add s3 to local running, and if you do, you could also do anotehr pr if you want

[datadog-computersciencehouse]

🔴 High: Hardcoded credential in service environment

Storing credentials such as passwords, API keys, or tokens as literal values in the `environment` section exposes them in version control, container inspect output, and process listings. Any developer, CI system, or atta... (...read more)

Storing credentials such as passwords, API keys, or tokens as literal values in the environment section exposes them in version control, container inspect output, and process listings. Any developer, CI system, or attacker with read access to the Compose file or the running container can retrieve the credential. Sensitive values should be passed via Docker secrets (secrets:) or referenced as environment variable placeholders (e.g., DB_PASSWORD: ${DB_PASSWORD}) rather than hardcoded literals.

_{Helpful? 👍/👎     
🚩 Report as false positive. Flags the rule for review to improve detection accuracy.}

[datadog-computersciencehouse]

       

⚠️ Warnings

🧱 1 Infrastructure as Code (IaC) issue detected

High: Hardcoded credential in service environment

Hardcoded credential in service environment View rule
docker-compose.yaml:26

ℹ️ Info

No other issues found (see more)

🛠️ No new code quality issues
🛡️ No new code vulnerabilities
📚 No new vulnerable libraries detected
🔑 No new secrets detected

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 4bb519b | Docs | Give us feedback!}