Environments

Environments are your Odoo instances running on your servers. Each environment has its own database, files, and settings - allowing you to safely develop, test, and run your Odoo applications.

Understanding Environment Types

OEC.sh supports three types of environments for different stages of your workflow:

Tip: Start with a Development environment to test changes safely before deploying to Production.

Environment Status

Your environments show real-time status with color indicators:

Creating an Environment

1. Go to your Project
2. Click the Environments tab
3. Click Add Environment
4. Fill in the basic settings:
   • Name: A descriptive name (auto-generated based on type)
   • Type: Choose Development, Staging, or Production
   • Server: Select which server to run on
5. Set your resources (CPU, RAM, and disk space)
6. Configure additional settings (optional):
   • Domain: Custom domain or auto-generated subdomain
   • Git Branch: Which branch to deploy
   • Auto-deploy: Enable to deploy on branch push
   • Database Settings: PostgreSQL version and optimizations
7. Click Create Environment
8. When prompted, click Deploy Now to start your environment

Environment Settings

Domain Configuration

Each environment can have:

• Auto-generated Domain: Format {project}-{env}.apps.oec.sh (always available)
• Custom Domain: Your own domain like erp.company.com (Pro plan required)
• Agency Subdomain: Format {subdomain}.{agency-domain} (Agency plan required)

See Custom Domains for setup instructions.

Database Settings

Configure PostgreSQL options when creating or editing an environment:

Git Configuration

• Branch: Select which Git branch to deploy
• Auto-deploy: Automatically redeploy when you push to the branch

Odoo Configuration

Customize your odoo.conf settings:

1. Go to Settings → Odoo Configuration
2. Choose a preset (minimal, standard, production, high_performance) or customize
3. Add custom parameters as needed
4. Save and redeploy

Deploying Your Environment

Deployment sets up your Odoo instance with all the code and configuration.

To deploy or redeploy:

1. Open your environment from the project page
2. Click the Deploy button (or Redeploy if already deployed)
3. Watch the progress as the system:
   • Connects to your server
   • Sets up the database
   • Downloads your code
   • Starts Odoo
4. Once complete, click your environment URL to access Odoo

When to redeploy:

• After changing resources (CPU, RAM, disk)
• After switching to a different Git branch
• After modifying Odoo settings
• To apply new code changes

Environment Actions

The Quick Actions panel provides buttons for common operations:

Viewing Logs

Logs help you understand what is happening in your environment and troubleshoot issues.

1. Open your environment
2. Click the Logs tab
3. Select which container to view:
   • Odoo: Application logs
   • PostgreSQL: Database logs
4. Logs update in real-time

Common things to look for:

• Error messages (shown in red)
• Module installation progress
• Database connection issues

Managing Resources

Each environment uses CPU, RAM, and disk space from your organization quota.

Resource Guidelines

To change resources:

1. Open your environment
2. Go to Settings → Resources
3. Adjust the sliders for CPU, RAM, or Disk
4. Optionally customize PostgreSQL resource allocation
5. Click Save Changes
6. Click Redeploy to apply the changes

Note: Your organization has a total resource quota. If you reach the limit, you will need to reduce resources elsewhere or upgrade your plan.

Cloning an Environment

Create a copy of an existing environment with optional data sanitization.

1. Go to your environment
2. Click Clone in the actions menu
3. Configure clone options:
   • Target Project: Same or different project
   • Environment Name: Name for the clone
   • Sanitization Preset: recommended, minimal, full, or none
4. Click Clone

The clone operation runs in the background. Sanitization removes sensitive data like passwords, API keys, and personal emails.

Deleting an Environment

When you no longer need an environment, you can delete it to free up resources.

1. Open your environment
2. Go to Settings → Advanced
3. Scroll to Danger Zone
4. Click Destroy Environment
5. Choose whether to also remove database and filestore volumes:
   • Unchecked: Data preserved, can be restored to a new environment
   • Checked: All data permanently deleted
6. Type the environment name to confirm
7. Click Destroy

Addon Repositories

Environments can include addon modules from multiple sources:

1. Shared Addons: Platform and organization addons selected in project settings
2. Project Addons: Additional repositories specific to this project

To manage addons:

1. Go to your project's Settings → Repositories
2. Click Browse Addons to select shared addons
3. Add project-specific repositories if needed

Tips for Success

For Development:

• Enable auto-deploy to automatically update when you push code
• Use smaller resources to save quota for other environments
• Feel free to experiment - you can always redeploy

For Staging:

• Match your production settings as closely as possible
• Test with realistic data (use the clone feature with sanitization)
• Validate everything works before promoting to production

For Production:

• Disable auto-deploy for manual control over updates
• Schedule deployments during low-traffic times
• Always have a recent backup before major changes

What's Next?

• Backups - Protect your data
• Custom Domains - Use your own domain name
• Monitoring - Track resource usage
• Database Management - Configure read replicas and pooling