Odoo 19 Multi-Environment Development
Budget: $250 – $750 NZD
Odoo 19 Multi-Environment Development
PROJECT TITLE
Odoo 19 Multi-Environment Pipeline Setup With Replit, GitHub, CI/CD, Rollbacks & Backups
1. OVERVIEW
I require an experienced Odoo + DevOps engineer to build a full development and deployment pipeline for Odoo 19 Community Edition.
The workflow must allow:
- Coding inside Replit
- Version control via GitHub
- Automatic deployments to Sandbox, Integration, Staging, and Live
- Rollbacks for any environment
- Automated database and filestore backups
- Clear documentation so the system is easy to use
The final solution must be stable, safe, well-structured, and production-ready.
2. PROJECT GOALS
1. Use Replit as the main IDE for editing Odoo modules.
2. Use GitHub as the source-of-truth for all Odoo code.
3. Deploy code through a four-stage environment pipeline:
Sandbox → Integration → Staging → Live
4. Allow full rollback to previous versions (code + database + filestore).
5. Implement a daily, weekly, and pre-deployment backup system.
6. Provide complete documentation so anyone can manage the system after delivery.
3. ENVIRONMENT SETUP REQUIREMENTS
Set up four separate Odoo 19 environments (Sandbox, Integration, Staging, Live), each with its own database, filestore, logs, and configuration files.
4. GITHUB REPOSITORY SETUP
Repository name: aveenix-odoo19
Branches:
- sandbox → Sandbox
- integration → Integration
- staging → Staging
- main → Live
5. REPLIT INTEGRATION REQUIREMENTS
Replit must connect to the sandbox branch and allow editing, committing, and pushing code to GitHub which triggers Sandbox deployment.
6. AUTOMATED DEPLOYMENT PIPELINE (CI/CD)
Sandbox → Integration → Staging → Live deployment model.
Automated deployments via GitHub Actions or equivalent, including module upgrades and health checks.
7. ROLLBACK REQUIREMENTS
Rollback capabilities for ALL environments using Git commits/tags + database and filestore restore scripts.
Automatic rollback if a deployment fails.
8. BACKUP REQUIREMENTS
Daily, weekly, and pre-deployment backups stored locally and remotely.
Restore scripts for DB and filestore included.
9. DOCUMENTATION REQUIREMENTS
Provide a step-by-step guide explaining:
- How to use Replit
- How deployments work
- How to roll back versions
- How to restore backups
- Troubleshooting instructions
10. REQUIRED SKILLS
Odoo installation, DevOps, GitHub Actions, PostgreSQL, CI/CD pipelines, backup automation, Linux server administration.
WHAT SUCCESS LOOKS LIKE
I must be able to:
- Edit code in Replit
- Push to Sandbox
- Promote the code through Integration, Staging, and Live
- Roll back any environment instantly
- Restore backups easily
All the project details are already written here so
Serious applicants only
Please apply with a proper proposal in NZD
PROJECT TITLE
Odoo 19 Multi-Environment Pipeline Setup With Replit, GitHub, CI/CD, Rollbacks & Backups
1. OVERVIEW
I require an experienced Odoo + DevOps engineer to build a full development and deployment pipeline for Odoo 19 Community Edition.
The workflow must allow:
- Coding inside Replit
- Version control via GitHub
- Automatic deployments to Sandbox, Integration, Staging, and Live
- Rollbacks for any environment
- Automated database and filestore backups
- Clear documentation so the system is easy to use
The final solution must be stable, safe, well-structured, and production-ready.
2. PROJECT GOALS
1. Use Replit as the main IDE for editing Odoo modules.
2. Use GitHub as the source-of-truth for all Odoo code.
3. Deploy code through a four-stage environment pipeline:
Sandbox → Integration → Staging → Live
4. Allow full rollback to previous versions (code + database + filestore).
5. Implement a daily, weekly, and pre-deployment backup system.
6. Provide complete documentation so anyone can manage the system after delivery.
3. ENVIRONMENT SETUP REQUIREMENTS
Set up four separate Odoo 19 environments (Sandbox, Integration, Staging, Live), each with its own database, filestore, logs, and configuration files.
4. GITHUB REPOSITORY SETUP
Repository name: aveenix-odoo19
Branches:
- sandbox → Sandbox
- integration → Integration
- staging → Staging
- main → Live
5. REPLIT INTEGRATION REQUIREMENTS
Replit must connect to the sandbox branch and allow editing, committing, and pushing code to GitHub which triggers Sandbox deployment.
6. AUTOMATED DEPLOYMENT PIPELINE (CI/CD)
Sandbox → Integration → Staging → Live deployment model.
Automated deployments via GitHub Actions or equivalent, including module upgrades and health checks.
7. ROLLBACK REQUIREMENTS
Rollback capabilities for ALL environments using Git commits/tags + database and filestore restore scripts.
Automatic rollback if a deployment fails.
8. BACKUP REQUIREMENTS
Daily, weekly, and pre-deployment backups stored locally and remotely.
Restore scripts for DB and filestore included.
9. DOCUMENTATION REQUIREMENTS
Provide a step-by-step guide explaining:
- How to use Replit
- How deployments work
- How to roll back versions
- How to restore backups
- Troubleshooting instructions
10. REQUIRED SKILLS
Odoo installation, DevOps, GitHub Actions, PostgreSQL, CI/CD pipelines, backup automation, Linux server administration.
WHAT SUCCESS LOOKS LIKE
I must be able to:
- Edit code in Replit
- Push to Sandbox
- Promote the code through Integration, Staging, and Live
- Roll back any environment instantly
- Restore backups easily
All the project details are already written here so
Serious applicants only
Please apply with a proper proposal in NZD