Chatwoot Enterprise Unlocker

Unlock Chatwoot Enterprise features using permanent PostgreSQL triggers and configuration modifications designed for Docker/Portainer deployments.

What This Skill Does

This skill helps you deploy and manage a solution that unlocks Chatwoot Enterprise features through:

1. **PostgreSQL Trigger Creation** - Creates permanent database triggers that intercept configuration changes

2. **Configuration Updates** - Sets enterprise pricing plan values in the database

3. **Fallback Value Patching** - Modifies hardcoded fallback values in Chatwoot source files

The solution ensures configurations persist across container restarts and application updates.

Instructions

Step 1: Understand the Project Structure

The Dchat project contains these key files:

Step 2: Identify the Deployment Method

Ask the user which deployment method they're using:

1. **Docker/Portainer (Recommended)** - Use `docker-unlock.sh`

2. **Manual Docker Execution** - Use direct `docker exec` commands

3. **Native Installation** - Use Ruby script directly

Step 3: Docker/Portainer Deployment (Primary Method)

For Docker/Portainer environments, execute:

```bash

curl -sL https://raw.githubusercontent.com/LuizBranco-ClickHype/Dchat/main/docker-unlock.sh | bash

```

The script will:

Step 4: Manual Docker Execution

If auto-detection fails, manually execute:

```bash

docker exec -it <container_name> bash -c "wget -qO- https://raw.githubusercontent.com/LuizBranco-ClickHype/Dchat/main/unlock_permanent.rb | bundle exec rails runner -"

```

Replace `<container_name>` with the actual Chatwoot container name.

Step 5: Verify Trigger Creation

The unlock script creates a PostgreSQL trigger that permanently enforces enterprise values:

```sql

CREATE TRIGGER trg_force_enterprise_configs

BEFORE INSERT OR UPDATE ON installation_configs

FOR EACH ROW

EXECUTE FUNCTION force_enterprise_installation_configs();

```

This trigger intercepts any configuration changes and forces:

Step 6: Check File Patching

The script searches for `lib/chatwoot_hub.rb` in these locations:

It creates a timestamped backup before modifying fallback values:

Step 7: Restart Container

After execution, restart the Chatwoot container:

```bash

docker restart <container_name>

```

Or use Portainer UI to restart the container.

Step 8: Verify Enterprise Features

After restart, verify that:

Check trigger existence:

```sql

SELECT tgname FROM pg_trigger WHERE tgname = 'trg_force_enterprise_configs';

```

Important Notes

Licensing Compliance

This tool modifies commercial licensing restrictions. Ensure usage complies with Chatwoot's license terms and applicable laws.

Persistence

Error Handling

The script uses defensive error handling - if database updates fail, file patching continues. If file patching fails, database configurations remain applied.

Dependencies

Troubleshooting

Container Not Detected

If auto-detection fails:

1. List containers: `docker ps | grep chatwoot`

2. Use manual execution method with correct container name

Trigger Not Working

Verify trigger function exists:

```sql

SELECT proname FROM pg_proc WHERE proname = 'force_enterprise_installation_configs';

```

File Patch Failed

Check file locations manually:

```bash

docker exec -it <container> find / -name "chatwoot_hub.rb" 2>/dev/null

```

Changes Reverted After Update

This indicates the trigger was removed. Re-run the unlock script after major Chatwoot updates that include database migrations.

Examples

Example 1: Quick Docker Deployment

```bash

One-command deployment

curl -sL https://raw.githubusercontent.com/LuizBranco-ClickHype/Dchat/main/docker-unlock.sh | bash

Restart container (replace 'chatwoot' with your container name)

docker restart chatwoot

```

Example 2: Verify Installation

```bash

Check trigger exists

docker exec -it chatwoot psql -U postgres -d chatwoot_production -c "SELECT tgname FROM pg_trigger WHERE tgname = 'trg_force_enterprise_configs';"

Check configuration values

docker exec -it chatwoot psql -U postgres -d chatwoot_production -c "SELECT name, value FROM installation_configs WHERE name LIKE 'INSTALLATION_PRICING%';"

```

Example 3: Manual Rollback (If Needed)

```bash

Remove trigger

docker exec -it chatwoot psql -U postgres -d chatwoot_production -c "DROP TRIGGER IF EXISTS trg_force_enterprise_configs ON installation_configs;"

Remove function

docker exec -it chatwoot psql -U postgres -d chatwoot_production -c "DROP FUNCTION IF EXISTS force_enterprise_installation_configs();"

Restore backup file

docker exec -it chatwoot bash -c "cd /app/lib && ls -t chatwoot_hub.rb.backup.* | head -1 | xargs -I {} cp {} chatwoot_hub.rb"

```

References