Deploy from the Template Catalog

Launch a pre-configured Odoo environment in minutes using the deployment template catalog.

What You'll Need

• An OEC.SH account with at least one organization
• A server (your own VPS or OEC.SH shared servers)
• A project with a Git repository connected

Step 1: Browse the Catalog

1. Go to Catalog in the sidebar
2. Browse templates by category: eCommerce, Manufacturing, Accounting, POS, HR, Education, or General
3. Use the filters to narrow by Odoo version or environment type (production, staging, development)
4. Featured templates are shown first — these are verified and recommended configurations

Tip: Each template card shows the resource allocation (CPU, RAM, disk) and estimated concurrent users so you can pick the right size.

Step 2: Choose a Template

Click on any template card to see its full details:

• Resource specs — CPU cores, RAM, disk space
• PostgreSQL settings — version, PgTune optimization, PgBouncer connection pooling
• Bundled addons — pre-configured OCA or community addon repositories
• Odoo configuration — optimized odoo.conf settings for the use case

Step 3: Deploy

1. Click the Deploy button on the template
2. If you have one matching project, you'll go directly to the environment form
3. If you have multiple projects, pick which one to deploy to
4. If you have no projects yet, you'll create one first

The environment form opens with all fields pre-filled from the template:

• Environment type, resources, and PostgreSQL settings
• Odoo configuration preset
• Addon repositories (required repos are locked, optional ones can be removed)

Tip: A banner at the top shows which template you're using. Click Clear to start from scratch, or customize any field before deploying.

Step 4: Review and Launch

1. Name — auto-generated, but you can change it
2. Server — select which server to deploy on
3. Branch — pick your Git branch
4. Domain — optionally set a custom domain
5. Review the pre-filled settings, then click Create Environment

Your environment will be provisioned with the template's verified configuration.

Available Template Categories

Customizing Templates

Templates are starting points — every field remains editable:

• Scale up or down — adjust CPU, RAM, and disk to match your needs
• Add more addons — include additional Git repositories beyond what the template bundles
• Change Odoo config — switch presets or fine-tune individual settings
• Toggle PostgreSQL features — enable or disable PgBouncer, read replicas, and PgTune

Managing Templates (Admin)

Portal administrators can manage templates at Admin → Templates:

• Create new templates with custom resource specs and addon bundles
• Edit existing templates to update configurations
• Duplicate a template as a starting point for variations
• Feature templates to highlight them in the catalog
• Deactivate templates to hide them without deleting

FAQ

Can I deploy the same template multiple times? Yes. Each deployment creates a new independent environment. The template is just a configuration preset.

Do templates lock me into specific settings? No. All settings are fully editable after the form is pre-filled. You can change anything before or after deployment.

What are "verified" templates? Verified templates have been tested and confirmed to work correctly with the specified resource allocation and addon configuration.

Can I create my own templates? Portal administrators can create custom templates via Admin → Templates. This is useful for agencies that deploy similar configurations across multiple clients.