infra: deployment scripts and documentation update

[qasimgulzar]

This pull request introduces initial infrastructure-as-code and deployment automation for the Primzel E-Commerce Platform. It adds environment-specific configuration for AWS deployment, a robust Docker build script, and comprehensive documentation for setup and operations. The changes lay the groundwork for multi-environment (dev, stage, production) deployments using Docker, AWS ECS, and CloudFormation.

Key changes:

Deployment Automation & Build Tooling

• Added build.sh, a Bash script to automate Docker image building and ECR publishing for different environments, with support for custom tags, cache control, and automatic repository creation. It also persists the latest build tag for deployment use.

Infrastructure Configuration (CloudFormation Parameters)

• Introduced environment-specific infrastructure parameter files for dev, stage, and production (cloudformation/parameters/*/infra.json), defining VPC, subnets, RDS, Redis, and ACM certificate settings. [1] [2] [3]
• Added corresponding service parameter files for each environment (cloudformation/parameters/*/service.json), specifying ECS resource sizing, scaling, and S3 bucket names. [1] [2] [3]

Documentation & Onboarding

• Overhauled README.md to provide a detailed guide on local development, deployment workflows, infrastructure structure, environment differences, tenant management, and integration with AWS and Stripe. The documentation now clearly explains the use of the new scripts and parameter files.

Versioning

• Added a VERSION file as the canonical source of the application version, referenced by build and deployment scripts.
• .last-build-tag file is now generated to track the latest built image tag for deployment automation.

[gitguardian]

⚠️ GitGuardian has uncovered 2 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
32862004	Triggered	Generic Password	e1ef826	cloudformation/infrastructure.yml	View secret
32862004	Triggered	Generic Password	0f77fda	cloudformation/infrastructure.yml	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.}