In your server’s resources directory, create a folder named [codesign] if it does not already exist
Place cd_bridge (and all other Codesign resources) inside the [codesign] folder
Example resources folder with a [codesign] directory
2
2. Resource Start Order
Configure server.cfg Correctly
After placing the resource inside the [codesign] folder, ensure it starts last.
Add this to the bottom of your server.cfg:
ensure [codesign]
Why:cd_bridge auto-detects and integrates with frameworks (ESX / QBCore / QBox) and other resources such as inventory, phone, fuel, vehicle keys, and notifications.
These resources must start before[codesign] for detection to work correctly.
Important
⚠️ Place ensure [codesign] at the very bottom of your server.cfg.
Example server.cfg start order with [codesign] loaded last
3
3. Configure Resource
Bridge Configuration
You should review all configurable options in cd_bridge/shared/config.lua to understand what is available.
The bridge uses automatic detection, so no configuration is required in most cases. Supported frameworks and integrations are detected and handled automatically.
Each configuration option includes commented lists of supported resources. These comments show which integrations are available and can be manually selected if needed.
Only change these values if auto-detection does not suit your setup or if you want to force a specific integration.
