---
title: "nginx sites integration · RUAL Documentation"
description: "Use nginx sites in RUAL blueprints. Check a site config on every load balancer, push it, read its status and delete it. Every block, with its pins."
canonical: https://docs.rual.nl/integrations/nginx
language: en
---

# nginx sites

Check a site config on every load balancer, push it, read its status and delete it.

## Blocks

Add these blocks on the canvas by searching for their name. Each block page lists its pins and how it behaves.

- [validate site config on the load balancers `nginxsite_check` Run nginx -t for this site config on every load balancer, in the context of its full live config. Writes nothing to any live directory.](https://docs.rual.nl/block-types/nginx/nginxsite_check)

- [remove site config from the load balancers `nginxsite_delete` Remove a live site config and reload nginx, per node. The far side refuses when the remaining set would not validate without it, and archives rather than destroys.](https://docs.rual.nl/block-types/nginx/nginxsite_delete)

- [push site config to the load balancers `nginxsite_push` Replace the live site config and reload nginx, per node. Gated on a passing nginxsite_check over these exact bytes for every target node.](https://docs.rual.nl/block-types/nginx/nginxsite_push)

- [load balancer fleet status `nginxsite_status` Ask every load balancer what it serves and whether the fleet agrees with itself. Reads only.](https://docs.rual.nl/block-types/nginx/nginxsite_status)

## Next steps

- [Third-Party Integrations](https://docs.rual.nl/tutorials/third-party-integrations): Calling outside APIs, receiving their webhooks, keeping data in sync and handling failures.

- [All integrations](https://docs.rual.nl/integrations): Everything RUAL connects to, by what it is for.