Odoo 16 Staging Environment Setup

I’m redeveloping shop.notgrass.com on a new Odoo 16 theme and need support setting up a proper staging environment so I can safely redesign, rebuild, and modernize the entire storefront. The goal is to customize the design, rebuild content pages, refresh product templates, and fully reskin the site according to current standards — without touching or overwriting any live production data.

The new staging instance will be used to develop the updated theme, test UI/UX improvements, refine content flow, and finalize product-page layouts. Once complete, the final build will be deployed to odoo.sh and pushed into production cleanly, with dummy/sample products removed prior to launch.

Project Requirements
1. Full Staging Environment for Odoo 16

I need a clean, isolated staging instance of our current Odoo 16 setup so I can perform all development work safely. This environment should mirror my live configuration but only contain light sample data—not a full production dump.

You may use Docker, a virtual machine, Odoo.sh workflow, or your preferred method. Odoo.sh wou;d b e preferred as it integrates. Once the new site is built i will need help migrating.

2. Safe Theme & Site Rebuild

The staging site must allow me to:

Redesign the entire shop theme

Customize templates, content pages, and product detail pages

Rebuild navigation and layout

Test custom modules and workflow updates

Delete all placeholder/dummy products before launch

Deploy to odoo.sh without overwriting live data

3. Deployment & Version Control

I want to validate all updates in staging, then promote them to production through Git or a similar workflow, ensuring:

No accidental sync of test data

No risk of overwriting real products, orders, or customer records

A clean, controlled push of theme and code only

Technical Key Points

Platform: Odoo 16 Community

Data Scope:

Only enough sample data to simulate real-world usage (e.g.,
sample products, mock customers, a few example orders)

Exclude all sensitive or real production records

Staging Access:

HTTPS

Subdomain (e.g., stage.notgrass.com)

Basic authentication to block indexing and public access

Safety Requirements:

All outgoing email disabled

SMS gateways disabled

Payment gateways in sandbox or disabled mode

Documentation:

A short README or screencast explaining:

How to refresh sample data

How to deploy updates via Git

How to recreate the environment from scratch

Acceptance Criteria

I can log in with existing admin credentials and see the same apps, settings, and core configuration—just with sample data.

No chance of the staging instance sending emails, triggering SMS, or hitting real payment gateways.

A single command or Git push redeploys staging when code is updated.

Documentation makes it easy for any developer to rebuild the staging environment independently.

Final theme and reskin work can be deployed to odoo.sh without overwriting production data or products.