One of the most powerful features of NGINX Templates is the ability to centrally manage configurations. Instead of logging in to multiple servers to update individual configuration files, you can simply edit your master template. RunCloud will then let you “propagate” (push) those changes to all linked Web Applications simultaneously.
Here is how to edit an active template, understand the sync statuses, and safely deploy your updates.
1. Editing an Active Template
When you need to tweak a configuration, such as adding a new security header or modifying a caching rule, you do it directly from the master template.
Step 1: In the RunCloud dashboard, go to Settings > NGINX Templates.
Step 2: Click on the template you want to update from your My Templates list.
Step 3: Under the Configuration Files section, click on the file you want to edit.
Step 4: A code editor modal will appear. Make the required changes to the NGINX configuration (e.g., adding or removing a line of code).
Step 5: Click Save Config.
As soon as you save the changes, RunCloud will recognize that the master template no longer matches the configuration currently running on your linked Web Applications and start updating them.
2. Understanding Sync Status
Scroll down to the Linked Web Applications section of your template’s dashboard. Here, you will see a list of every Web App currently using this template. Pay close attention to the Sync Status column.
- Synced (Green): The configuration in the Web Application matches your master template. No action is needed.
- Pending (Yellow): The master template has been updated, but the new changes have not been pushed to the Web Application yet. The Web App is still running the older configuration safely.
- Failed (Red): RunCloud attempted to push the update to the Web Application, but the deployment failed (usually due to a syntax error or a local server conflict). The Web App continues to run on its last known working configuration.
3. Propagating Changes
When your Linked Web Applications show a Pending status, you need to propagate the updates to apply them to your live servers.
Step 1: In the Linked Web Applications list, locate the apps with a “Pending” status.
Step 2: Check the box next to the Web Application(s) you want to update. (You can check the master box at the top to select all of them at once.)
Step 3: Click the blue Propagate Selected button on the right side of the screen.
Step 4: RunCloud will begin pushing the updated configuration to the selected servers. During this brief process, the status will show as updating.
Step 5: Once completed successfully, the status will revert to green, Synced. You can verify the changes by SSHing into your server and checking the NGINX configuration files.
4. Safety & Rollbacks
Modifying live NGINX configurations can be risky; a single missing semicolon can crash the NGINX service and take all websites on that server offline. RunCloud is designed to prevent this entirely.
When you click Propagate Selected, RunCloud does not just blindly overwrite the files. Instead, it performs a strict safety routine:
- Staging the Config: RunCloud temporarily deploys the updated configuration to the server.
- Syntax Testing: RunCloud runs an automated syntax check (similar to nginx -t) to ensure the new configuration is 100% valid within the context of that server and web application.
- Safe Reload vs. Rollback:
- If the test passes: RunCloud safely reloads NGINX, and your new settings take effect immediately.
- If the test fails: RunCloud immediately aborts the update and rolls back to the previous, working configuration. NGINX is never reloaded with bad code, ensuring your server experiences absolutely zero downtime. The Sync Status in your dashboard will simply update to alert you of the failure.
If you have any other questions or need help, please feel free to get in touch with our 24/7 support team. We’re here to help!