# Project Config





When you deploy a site, the `samplex` CLI saves the slug and name to `.samplex.config.json` in your project root. Later deploys reuse these settings automatically.

File format [#file-format]

```json title=".samplex.config.json"
{
  "slug": "brave-panda",
  "name": "My Project"
}
```

<TypeTable
  type="{
  slug: {
    description: &#x22;The site slug used in the preview URL.&#x22;,
    type: &#x22;string&#x22;,
  },
  name: {
    description: &#x22;Display name for the site on the dashboard.&#x22;,
    type: &#x22;string&#x22;,
  },
}"
/>

Initialize manually [#initialize-manually]

You can create or update the config file with the `init` command:

```bash
samplex init --slug my-site --name "My Site"
```

Running `samplex init` without options shows the current config if one exists.

Version control [#version-control]

<Callout type="info">
  It's safe to commit `.samplex.config.json` to your repository. This way, anyone on your team who
  runs `samplex deploy` will update the same site automatically.
</Callout>

If you'd rather keep deployments per-developer, add it to `.gitignore`:

```bash title=".gitignore"
.samplex.config.json
```