# Build Changes

> Which files require a container restart or an image rebuild when modified in WordPressify.

Source: https://wordpressify.co/build-changes

> For the complete documentation index, see [llms.txt](https://wordpressify.co/llms.txt).

# Build Changes

Files in `src/` are watched and applied instantly via live reload. Configuration and build files are not: depending on how they are wired into Docker, changing them requires either restarting the containers or rebuilding the images.

## Restart Containers

These files are mounted or read at container startup. Stop the running process with `CTRL/CMD+C` and start again, using the Docker command if Node.js is not installed locally:

| File | Description |
|------|-------------|
| `config/` | Nginx & PHP configurations |
| `.env` | Environment variables |
| `docker-compose.yml` | Docker Compose configuration |

<CodeTabs tabs={[{ label: "npm", code: "npm run start" }, { label: "Docker", code: "docker compose up" }]} />

## Rebuild Images

These files are baked into the Docker images at build time, so a restart alone is not enough:

| File | Description |
|------|-------------|
| `gulpfile.js` | Gulp configuration |
| `package.json` | Node.js packages |
| `.stylelintrc` | Stylelint configuration |
| `.dockerignore` | Docker ignore file |
| `Dockerfile-nodejs` | Node.js Dockerfile |
| `Dockerfile-wordpress` | WordPress Dockerfile |

Stop the running process with `CTRL/CMD+C`, rebuild, then start again:

<CodeTabs tabs={[{ label: "npm", code: "npm run build\nnpm run start" }, { label: "Docker", code: "docker compose build\ndocker compose up" }]} />