[media] build / bugfix : upgrade infra , 3rd party libraries, move build test flow to docker

[metalalive]

• CMake and docker config
  • build executable dev and test apps in docker build
  • move the commands that launch executable dev and test apps to docker compose
  • move database migration, certificate renewal, and other helper tools to docker compose
• run unit test / integration test through docker compose
• use separate docker images for helper tools and executable server applications
• standalone health check program for app server
• upgrade mariadb , rabbitmq, gcc, and essential 3rd-party libraries

bugfix :

• pass environment variables to development and test apps
  • allow system users to specify essential environment variables for running applications in different OS environment
  • specify database host and port by environment variable instead of secret data file.
• add macro which concatenates 2 path segments then run user-specific code block with the final concatenated string, the purpose is to ensure full path of a file in local / remote storage.
• fix base path issues for external files
  • associated with callable symbol lookup in ELF file , config file parsing, persisted user-asset storage, and image / video transcoding modules.
  • system base path will be handled in storage layer, remove system base path on API endpoints of app server and RPC consumer
• for temp buffer in local transcoding RPC consumer
  • replace path of temp buffer, with dedicated storage setup in configuration.
  • remove confusing storage alias localfs, insead using persist_usr_asset for user media file persistence, and local_tmpbuf as temporary buffer files when transcoding videos / images locally in app server
• for integration test
  • modify URL verification during HLS element lookup in relevant test cases
• fix errors in mock auth servers

others :

• reformat python modules for build and fix path issues
• update README and build help doc
• update github action workflow, run test with docker build / compose
• probe object inside json array using standalone json_renderer.py for test

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
19482685	Triggered	Generic Password	87a32c1	services/media/infra/container-sample.env	View secret
19482686	Triggered	Generic Password	87a32c1	services/media/infra/container-sample.env	View secret
10609120	Triggered	Generic Password	367e0eb	services/media/src/models/cfg_parser.c	View secret
19482687	Triggered	Generic Password	87a32c1	services/media/infra/container-sample.env	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}