> ## Documentation Index
> Fetch the complete documentation index at: https://getfloo.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# .flooignore

> Control which files are included in builds.

Deploys pull source from your connected GitHub repository. Since source comes from Git, your `.gitignore` controls which files are excluded from the build context.

## How it works

When you run `floo redeploy` or push to GitHub, the build system clones your repository from GitHub. Files excluded by `.gitignore` are never sent to the build server.

## Best practices

Add large or sensitive files to `.gitignore`:

```
# Secrets (never commit these)
.env
.env.*

# Large data files
*.csv
*.sqlite
data/

# Build artifacts
node_modules/
__pycache__/
.venv/
target/
dist/
build/

# Media
*.mp4
*.mov
uploads/

# IDE
.idea/
.vscode/
.DS_Store
```

## Dockerfile .dockerignore

If your project uses a Dockerfile, the `.dockerignore` file controls what gets copied into the Docker build context. This is the standard Docker mechanism:

```
node_modules
.git
.env
*.md
```

## Checking build context

The deploy output shows the build progress:

```bash theme={null}
floo redeploy
```

```
Building... done (45s)
```

If builds are slow, ensure large files are excluded via `.gitignore` or `.dockerignore`.