Skip to main content
This guide outlines a reliable workflow for updating Dietrich Development RedM scripts with minimal downtime and risk.
Always back up your files and database before making updates.

​
1. Preparation

1

Read the Changelog

Review the Changelog to understand new features, changes, and potential breaking updates.
2

Backup Your Environment

  • Make a full backup of the script folder.
  • Export your database.
3

Test on Staging

Always test the new version on a staging server before updating production.

​
2. Update Methods

​
Overwrite update

Replace the old script files with the new version, keeping your config.lua and other customizations.

​
Clean install

For major updates, delete the old script folder and perform a fresh install. Reapply your config and verify compatibility.
Clean installs are recommended for large updates to prevent leftover files from causing issues.

​
3. Post-Update Checks

  • Restart the resource: refresh and restart my_script_name
  • Monitor server logs for errors or warnings
  • Test core features and integrations
If something breaks, revert to your backup immediately and review the update notes.

​
4. Rollback Strategy

  • Keep at least one previous working version of the script.
  • Store backups in a clearly labeled folder with version numbers.
  • Document any changes made after the last stable update for quick reapplication.

​
5. Staying Updated

  • Subscribe to our Discord announcements channel for update notifications.
  • Regularly check your Keymaster or the changelog for new versions.

​
Next steps

Changelog

See all recent changes for our scripts.

Dev Environment

Maintain a setup that makes updates easier and safer.
⌘I