Update q4-SIEM-build/PUBLISH_TO_GHAYMAH.md
هذا الالتزام موجود في:
@@ -1,38 +1,5 @@
|
||||
# Publishing this SIEM Dashboard to Ghaymah Storage Block
|
||||
|
||||
## Read this first: what I could and couldn't verify
|
||||
|
||||
I looked for Ghaymah Systems' own documentation before writing this. I
|
||||
found:
|
||||
|
||||
- Their docs portal: **https://docs.ghaymah.cloud/**
|
||||
- Their deployment portal: **https://deploy.ghaymah.systems/**
|
||||
|
||||
Both are JavaScript-rendered apps, so I could confirm they exist but
|
||||
couldn't pull the actual step-by-step page content for the "Storage Block"
|
||||
feature specifically — I don't have exact screenshots/menu names to give
|
||||
you with certainty, and I don't want to hand you confidently-wrong click
|
||||
paths for something that's going to be graded.
|
||||
|
||||
What follows is the **standard workflow that essentially every cloud
|
||||
"storage block"/bucket/object-storage service uses** (AWS S3, DigitalOcean
|
||||
Spaces, Linode/Akamai Object Storage, etc.), written so you can map it onto
|
||||
Ghaymah's actual console. Before your exam submission, open
|
||||
**docs.ghaymah.cloud** and search for "storage" to confirm exact menu
|
||||
names, size limits, and whether static-site hosting is a toggle you need to
|
||||
enable — the mechanics below are almost certainly right, the exact button
|
||||
labels might differ slightly.
|
||||
|
||||
There are two different things a "storage block" can mean on a cloud
|
||||
platform — check which one Ghaymah's product actually is before you start,
|
||||
since the workflow is different:
|
||||
|
||||
| If "Storage Block" is... | It behaves like... | Use it to... |
|
||||
|---|---|---|
|
||||
| **Object storage** (a bucket you upload files into, with a public URL) | AWS S3 / DigitalOcean Spaces | Host this static dashboard directly — this is the common case, and the one the rest of this guide assumes |
|
||||
| **Block storage** (a raw virtual disk volume, like AWS EBS) | An attached hard drive | You'd still need a compute instance/VM running a web server (nginx, `python3 -m http.server`, etc.) — the volume just gives that VM extra disk space. See the [alternate path](#alternate-path-if-storage-block-means-a-disk-volume) below. |
|
||||
|
||||
---
|
||||
|
||||
## Path A: publishing to object/bucket-style storage (most likely case)
|
||||
|
||||
@@ -138,17 +105,3 @@ instead:
|
||||
5. Open the VM's public IP (or attach a domain to it) to verify.
|
||||
|
||||
---
|
||||
|
||||
## Either way — a pre-submission checklist
|
||||
|
||||
- [ ] Ran `python3 siem_analyzer.py` so `siem_report.json`/`data.js` reflect
|
||||
the current logs
|
||||
- [ ] `index.html` is reachable at the bucket/site root, not nested in a
|
||||
subfolder
|
||||
- [ ] `style.css`, `script.js`, `data.js`, `siem_report.json` are in the
|
||||
**same folder** as `index.html`
|
||||
- [ ] Public URL loads with no blank/broken page and no browser console
|
||||
errors
|
||||
- [ ] Confirmed the actual click-path against **docs.ghaymah.cloud**, since
|
||||
the steps above are the generic pattern, not a verified Ghaymah
|
||||
screenshot-by-screenshot guide
|
||||
|
||||
المرجع في مشكلة جديدة
حظر مستخدم