The `ps:rebuild` command now accepts `--no-cache` to perform a single uncached build regardless of builder, without persisting any setting for later deploys. The railpack builder now also honors `--no-cache` when set via `docker-options`, and build records are now correctly attributed when flags precede the app name.
40 lines
1.3 KiB
Markdown
40 lines
1.3 KiB
Markdown
# Repository Management
|
|
|
|
> [!IMPORTANT]
|
|
> New as of 0.6.0
|
|
|
|
```
|
|
repo:gc <app> # Runs 'git gc --aggressive' against the application's repo
|
|
repo:purge-cache <app> # Deletes the contents of the build cache stored in the repository
|
|
```
|
|
|
|
The repository plugin is meant to allow users to perform management commands against a repository.
|
|
|
|
## Usage
|
|
|
|
### Git Garbage Collection
|
|
|
|
This will run a git gc --aggressive against the applications repo. This is performed on the Dokku host, and not within an application container.
|
|
|
|
```shell
|
|
dokku repo:gc node-js-app
|
|
```
|
|
|
|
```
|
|
Counting objects: 396, done.
|
|
Delta compression using up to 2 threads.
|
|
Compressing objects: 100% (365/365), done.
|
|
Writing objects: 100% (396/396), done.
|
|
Total 396 (delta 79), reused 315 (delta 0)
|
|
```
|
|
|
|
### Clearing Application cache
|
|
|
|
Building containers with buildpacks currently results in a persistent `cache` directory between deploys. If you need to clear this cache directory for any reason, you may do so by running the following shell command:
|
|
|
|
```shell
|
|
dokku repo:purge-cache node-js-app
|
|
```
|
|
|
|
To purge the cache and rebuild the app in a single command, see the [rebuilding without the build cache](/docs/processes/process-management.md#rebuilding-without-the-build-cache) documentation.
|