Bug: `setup-https.js` fails due to incorrect relative path to `config/ssl.js`

[TheAtu]

Description

Running npm run setup-https fails with a MODULE_NOT_FOUND error because the path to the ssl.js module is incorrect:

Error: Cannot find module './config/ssl'

This happens because setup-https.js is located in the scripts/ directory, but it's trying to import ../config/ssl.js using a relative path that only works when run from the root.

---

Suggested Fix

In backend/scripts/setup-https.js, replace:

const { generateCertificate } = require('./config/ssl');

with:

const { generateCertificate } = require('../config/ssl');

This ensures the script works even if run from a different working directory.

---

Let me know if you'd like to add screenshots or logs as well.