Add quickstart install script and Docker Compose defaults

[Hamedghz]

Summary

• add a repo-level install script that defaults to the quickstart stack and supports an optional big data profile
• provide docker compose and environment example files so the documented services and ports start consistently
• update the development helper script, gitignore, and quickstart docs to align with the new defaults

Testing

• not run (environment setup only)

---

https://chatgpt.com/codex/tasks/task_e_6900e4fcfcf483289e03fa2512f0df39

[chatgpt-codex-connector]

💡 Codex Review

https://github.com/ghasemzadeh-hamed/OMERTAOS/blob/f26a11ad024bf47e208f277891aab43f6955d045/bigdata/docker-compose.bigdata.yml#L45-L50
Keep MinIO credentials consistent when enabling bigdata profile

When ./install.sh bigdata is used, scripts/dev-up.sh loads both the root docker-compose.yml and bigdata/docker-compose.bigdata.yml. Because Compose merges services by name, the minio service inherits the credentials defined in the bigdata file (MINIO_ROOT_USER=minio, MINIO_ROOT_PASSWORD=minio123). The rest of the stack (e.g. the control service) still reads MINIO_ACCESS_KEY/MINIO_SECRET_KEY from .env, which defaults to minio/miniosecret. This mismatch means the control plane will attempt to connect with miniosecret but the container now requires minio123, leading to authentication failures whenever the bigdata profile is enabled. Consider referencing the same env vars in the bigdata compose file or updating .env.example to match.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".