Token导航 LogoToken导航

Agent Skill · 前端设计

odoo-docker(odoo Docker 部署)

用于辅助云资源、部署、容器、基础设施和运维自动化任务。它适合让 Agent 检查配置、整理部署步骤、分析资源状态、生成排障思路或辅助云服务接入。使用时需要明确目标环境、账号权限、区域和资源组,区分本地测试与生产操作;涉及删除资源、重启服务、修改网络或权限配置时,应先确认影响范围。

odoo-docker 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证信息还不明确,第三方扫描有未通过项,按安装量在前端设计类的 10,216 个 Skill 里排第 9,031。

总安装 242周安装 10GitHub Stars 51下载 79核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:odoo-docker(odoo Docker 部署)
来源仓库:https://github.com/ahmed-lakosha/odoo-upgrade-skill
仓库路径:skills/odoo-docker
安装命令:
npx skills add https://github.com/ahmed-lakosha/odoo-upgrade-skill --skill odoo-docker
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/ahmed-lakosha/odoo-upgrade-skill --skill odoo-docker

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

odoo-docker 用于辅助云资源、部署、容器、基础设施和运维自动化任务,适合让 Agent 检查配置、整理部署步骤、分析资源状态或生成排障思路。适用于 Odoo Docker 部署相关的云资源和基础设施管理,需明确目标环境、账号权限和资源组。

通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限范围和维护状态。涉及删除资源、重启服务或修改网络配置时,应先确认影响范围和操作边界。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/odoo-docker

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/ahmed-lakosha/odoo-upgrade-skill --skill odoo-…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

odoo-docker 怎么安装?

在终端执行 npx skills add https://github.com/ahmed-lakosha/odoo-upgrade-skill --skill odoo-docker。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

odoo-docker 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

odoo-docker 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

odoo-docker 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

odoo-docker 用的人多吗?

公开数据是累计安装 242 次,近一周安装 10 次,下载 79 次,GitHub 51 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

odoo-docker 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
odoo-docker

odoo Docker 部署 · 本页

24251接触敏感数据未明确未通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Odoo Docker Infrastructure Skill

1. Overview

Docker infrastructure and deployment expert for multi-version Odoo Enterprise environments. Handles production deployment, nginx configuration, CI/CD pipelines, performance tuning, security hardening, and container troubleshooting.

v2.1: Nginx config, debugging, and performance tuning are handled via natural language. For project init, compose generation, deployment, and builds, use /odoo-docker sub-commands.

What This Skill Does

  • Production Deployment: docker-compose with nginx, SSL, PostgreSQL tuning, resource limits, warm-up
  • CI/CD Pipelines: Build and push multi-version Docker images via GitHub Actions
  • Performance Tuning: Data-driven recommendations from real stress tests
  • Nginx Configuration: Optimized configs with gzip (90% CSS reduction), WebSocket, asset caching
  • Container Debugging: Systematic troubleshooting using known issue patterns
  • Project Setup: Auto-detect Odoo version, scan modules, generate all configs + IDE integration
  • Compose Generation: Smart compose for dev/staging/production scenarios
  • Image Management: Build, tag, push images for Odoo 14-19 (amd64 + arm64)

When to Use This Skill vs odoo-service

Use odoo-service for...Use odoo-docker for...
Starting/stopping serversDeploying to production
Basic docker up/down/logsConfiguring nginx reverse proxy
Database backup/restoreCI/CD pipeline setup
IDE configurationPerformance analysis & tuning
Environment initializationContainer debugging & troubleshooting
Module install/updateBuilding & pushing Docker images

Natural Language Triggers

  • "deploy to production", "production docker setup", "deploy odoo with nginx"
  • "configure nginx for odoo", "add reverse proxy", "enable gzip"
  • "optimize docker performance", "slow containers", "tune workers"
  • "build docker image", "push to docker hub", "ci/cd pipeline"
  • "container won't start", "500 errors in docker", "debug container"
  • "set up docker for this project", "initialize docker environment"
  • "generate docker-compose", "create compose file"

2. User Configuration

Users can customize this plugin by creating ~/.claude/odoo-docker.local.md with YAML frontmatter. See odoo-docker.local.md.example in the plugin root for the full template.

Key settings:

  • image_prefix: Docker Hub org/image prefix (default: myorg/odoo)
  • default_version: Default Odoo version when not auto-detected (default: 17)
  • git_org: GitHub organization for source clone suggestions

When generating configs, check for user overrides in .local.md first. If not found, use template defaults and prompt the user for their image prefix on first use.


3. Architecture

Core Principle: Source Mounted, Not Baked

Docker Hub:  {image_prefix}:19.0-enterprise   (pre-built base image)

Workspace:
  sources/odoo-19/          <-- Odoo Enterprise source (git clone, mounted read-only)
  projects/relief_center/   <-- Custom modules (git clone, mounted)
  compose/relief_center.yml <-- Per-project Docker Compose
  conf/relief_center.conf   <-- Per-project Odoo config

One image --> Many containers. No rebuilding per project.

Key Design Decisions

  1. Source code is NOT baked into the image — mounted at runtime via Docker volumes (read-only)
  2. Two deployment models: Standalone workspaces (per-version Dockerfile) and centralized workspace (pre-built images from Docker Hub)
  3. Container isolation: Each project gets its own Docker network, named volumes, port mappings

Container Directory Structure

/opt/odoo/source/           <-- Odoo source (mounted, read-only)
/opt/odoo/custom-addons/    <-- Custom modules (mounted)
/etc/odoo/odoo.conf         <-- Configuration (mounted, read-only)
/var/log/odoo/              <-- Log files (mounted)
/var/lib/odoo/              <-- Filestore + compiled assets (named volume)

Exposed Ports

PortPurpose
8069HTTP — Odoo web interface
8072Gevent/Longpolling — WebSocket, live chat, bus
5678Remote debugger (debugpy, optional)

4. Template Files

All templates are in ${CLAUDE_PLUGIN_ROOT}/templates/. Read them with the Read tool when generating configs.

TemplateUse ForKey Placeholders
docker-compose.dev.ymlDevelopment compose{postgres_image}, {version}, {project_name}
docker-compose.prod.ymlProduction compose with nginx+ {odoo_image}
Dockerfile.templateBuilding base imagesPYTHON_VERSION, ODOO_VERSION (build args)
nginx.confReverse proxy{server_name}
entrypoint.shContainer startup scriptEnvironment variables (see section 7)
odoo.conf.templateOdoo configuration{project_name}, {addons_paths}, {gevent_or_longpolling_key}, {admin_password}
.env.templateEnvironment variablesCopy and customize

Placeholder Convention

  • {placeholder} — Must be replaced by the user/skill before use
  • ${ENV_VAR:-default} — Resolved automatically by Docker Compose at runtime

5. Version Matrix

Full version matrix is in ${CLAUDE_PLUGIN_ROOT}/reference/version-matrix.md. Key lookup table:

VersionPostgreSQLGevent KeyEntry PointPython
14-16postgres:12longpolling_portodoo-bin3.8-3.10
17postgres:15gevent_portodoo-bin3.10
18postgres:15gevent_portodoo-bin3.11
19postgres:15gevent_portsetup/odoo3.12

Build Workarounds (Applied Automatically)

VersionIssueFix
14Buster EOLarchive.debian.org mirrors
14-15gevent compilationCython<3, no-build-isolation
16-17gevent compilationCython<3, no-build-isolation
18cbor2 buildPIP_CONSTRAINT="setuptools<81"
19No __init__.pyPYTHONPATH=/opt/odoo/source
Allsetuptools 80+PIP_CONSTRAINT="setuptools<81"

6. Critical Configuration Notes

These are the most important settings. Getting any of them wrong causes hard-to-diagnose failures.

SettingWhy It Matters
data_dir = /var/lib/odooCRITICAL. Without this, filestore defaults to ~/.local/share/Odoo/ (ephemeral). JS assets return HTTP 500.
workers = 0Single-threaded. OK for dev. At 50 users: P50 = 10s, 10% errors. Minimum production: workers=2.
proxy_mode = TrueRequired behind nginx. Without it, IP logging and URL generation are wrong.
list_db = FalseProduction security. Prevents database name enumeration.
gevent_port vs longpolling_portv14-16: longpolling_port. v17+: gevent_port. Wrong key = WebSocket broken.
db_maxconn = 16Without limit, 51+ idle connections accumulate under stress. Pool exhaustion risk.

7. Environment Variables

Entrypoint Variables

VariableDefaultValuesPurpose
DEV_MODE00, 1Enables --dev=all for auto-reload
ENABLE_DEBUGGER00, 1Starts debugpy on port 5678, waits for IDE
WAIT_FOR_DB00, 1Waits up to 30s for PostgreSQL before starting
LOG_LEVEL(none)debug, info, warn, error, criticalOverrides odoo.conf log level
ODOO_EXTRA_ARGS(none)Any CLI argsPassed directly to Odoo CLI

Port Allocation Convention

PortCalculationProject 1Project 2
HTTPHTTP_PORT80698169
GeventHTTP_PORT + 380728172
DebugHTTP_PORT + 60986788778

8. Performance Tuning

Workers Configuration

SettingResponse at 50 UsersUse Case
workers=0P50 = 9,068ms, 10% errorsDev only
workers=2P50 ~ 800msMinimum production
workers=4P50 ~ 400msHeavy load

Formula: workers = (CPU cores * 2) + 1 (capped at available RAM / 512MB per worker)

PostgreSQL Tuning

SettingDefault4 GB RAM16 GB RAM
shared_buffers128 MB1 GB4 GB
work_mem4 MB16 MB32 MB
effective_cache_size4 GB3 GB12 GB
maintenance_work_mem64 MB128 MB512 MB
random_page_cost4.01.11.1

Gzip Compression (Nginx)

ConfigurationCSS SizeReduction
Dev (Werkzeug, no gzip)894 KB—
Prod (nginx, gzip level 6)89 KB90%

Asset Warm-Up

First request after restart compiles all assets (25-120s). The production compose template includes a warm-up service that pre-loads /web/login and /shop.


9. Security Hardening

High-Risk Issues (Fix Before Production)

IssueDefaultFix
Database enumerationlist_db = Truelist_db = False
Weak master passwordadmin_passwd = 123Strong 32+ character password
No SSL/TLSPlaintext HTTPNginx + Let's Encrypt
Default DB credentialsodoo / odooCustom credentials per environment
Proxy mode disabledproxy_mode = Falseproxy_mode = True behind nginx

Volume Security

  • Odoo source: Always mount :ro (read-only)
  • Config files: Always mount :ro
  • Filestore and logs: Read-write (necessary for operation)

Network Isolation

  • Each project gets its own Docker network
  • Database containers are NOT exposed to host in production
  • Only nginx exposes ports to the outside

10. SSL/TLS Configuration

For production HTTPS, the nginx template (${CLAUDE_PLUGIN_ROOT}/templates/nginx.conf) has commented SSL blocks. Uncomment and configure:

server {
    listen 80;
    server_name yourdomain.com;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl http2;
    server_name yourdomain.com;
    ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers HIGH:!aNULL:!MD5;
    ssl_prefer_server_ciphers on;
    # ... (same location blocks as HTTP config)
}

Add Let's Encrypt volume to production compose:

nginx:
  volumes:
    - /etc/letsencrypt:/etc/letsencrypt:ro
  ports:
    - "443:443"

11. CI/CD Pipeline

GitHub Actions Overview

  • Triggers: Push to main (Dockerfile/entrypoint/requirements changes) or manual dispatch
  • Matrix: Builds all 6 versions in parallel
  • Multi-platform: linux/amd64 + linux/arm64
  • Cache: GitHub Actions layer cache per version
  • Tags: {image_prefix}:{version}.0-enterprise + SHA suffix

Required Secrets

SecretPurpose
DOCKERHUB_USERNAMEDocker Hub login
DOCKERHUB_TOKENDocker Hub access token

The full GitHub Actions workflow template is generated by /odoo-docker build --generate-ci.


12. Centralized Multi-Project Workspace

Layout

~/odoo-docker/
├── sources/         <-- Git clones of Odoo Enterprise (per version)
├── projects/        <-- Git clones of custom modules (per project)
├── conf/            <-- Generated Odoo configs
├── compose/         <-- Generated Docker Compose files
├── logs/            <-- Runtime logs
├── scripts/         <-- start.sh, stop.sh, logs.sh, shell.sh
├── .env             <-- Global config
└── .env.local       <-- Machine-specific overrides

Daily Commands

./scripts/start.sh <project>            # Start containers
./scripts/start.sh <project> --dev      # Start with auto-reload
./scripts/stop.sh <project>             # Stop containers
./scripts/logs.sh <project>             # Odoo logs
./scripts/shell.sh <project> 19         # Bash into container

Running Multiple Projects

Assign unique ports per project in .env:

RELIEF_CENTER_HTTP_PORT=8069
SOQYA_HTTP_PORT=8169
TAQAT_HTTP_PORT=8269

13. Database Management in Docker

Create Database via API

curl -s -X POST http://localhost:8069/web/database/create \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"call","params":{"master_pwd":"changeme","name":"my_db","lang":"en_US","password":"admin","login":"admin"}}'

Access from Host

psql -h localhost -p 5433 -U odoo -d my_database

Backup and Restore

docker exec {db_container} pg_dump -U odoo my_database > backup.sql
docker exec -i {db_container} psql -U odoo -d my_database < backup.sql

14. Debugging & Development

Dev Mode

DEV_MODE=1 docker compose up -d

Remote Debugger (debugpy)

  1. Set ENABLE_DEBUGGER=1 in .env
  2. Expose port 5678:5678 in docker-compose
  3. Container waits for IDE attach
  4. VS Code config:
{
  "name": "Attach to Odoo Docker",
  "type": "debugpy",
  "request": "attach",
  "connect": { "host": "localhost", "port": 5678 },
  "pathMappings": [
    { "localRoot": "${workspaceFolder}", "remoteRoot": "/opt/odoo/source" }
  ]
}

Module Management Inside Container

python -m odoo -c /etc/odoo/odoo.conf -d {db} -u {module} --stop-after-init
python -m odoo -c /etc/odoo/odoo.conf -d {db} -i {module} --stop-after-init

15. Troubleshooting

For the full troubleshooting reference with all known issue patterns and diagnostic commands, read ${CLAUDE_PLUGIN_ROOT}/reference/troubleshooting.md.

For performance-related patterns and lessons learned from stress tests, read ${CLAUDE_PLUGIN_ROOT}/reference/docker-patterns.md.

For the production deployment checklist, read ${CLAUDE_PLUGIN_ROOT}/reference/production-checklist.md.


16. Quick Command Reference

# Build local image
docker compose build

# Pull pre-built image
docker pull {image_prefix}:19.0-enterprise

# Start / Stop
docker compose up -d
docker compose down

# Logs / Shell
docker compose logs -f odoo
docker compose exec odoo bash

# Module update inside container
python -m odoo -c /etc/odoo/odoo.conf -d {db} -u {module} --stop-after-init

平台分布

Codex

36.85%
按下载量换算29

Claude

27.77%
按下载量换算22

Cursor

18.09%
按下载量换算14

Gemini CLI

8.58%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

未通过

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills