Skip to content

Doc/build cache nano pico warning #954

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Juju-archy wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Doc/build cache nano pico warning #954

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions content/doc/administrate/apps-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,8 @@ Stop functionality is useful during the development of the application to limit

{{< callout type="info" >}}
If you set [`CC_DISABLE_BUILD_CACHE_UPLOAD`](/doc/develop/env-variables/#settings-you-can-define-using-environment-variables) environment variable to `true`, the cache archive won't be created nor uploaded.

Nano and Pico plans always use a dedicated build, which requires the build cache. Setting this environment variable on these plans causes deployment to fail.
Comment on lines 32 to +34
Copy link
Copy Markdown
Collaborator

@davlgd davlgd May 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you set [`CC_DISABLE_BUILD_CACHE_UPLOAD`](/doc/develop/env-variables/#settings-you-can-define-using-environment-variables) environment variable to `true`, the cache archive won't be created nor uploaded.
Nano and Pico plans always use a dedicated build, which requires the build cache. Setting this environment variable on these plans causes deployment to fail.
If you set [`CC_DISABLE_BUILD_CACHE_UPLOAD`](/doc/develop/env-variables/#settings-you-can-define-using-environment-variables) environment variable to `true`, the cache archive won't be created nor uploaded. Don't use it with `nano` and `pico` plans which always use a build instance to create the build cache.

{{< /callout >}}

## Deploy an old commit
Expand Down
2 changes: 2 additions & 0 deletions content/doc/develop/build-hooks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,8 @@ This hook is perfect for:

{{< callout type="info" >}}
If you set [\`CC_DISABLE_BUILD_CACHE_UPLOAD\`](/doc/develop/env-variables/#settings-you-can-define-using-environment-variables) environment variable to `true`, the cache archive won't be created nor uploaded.

Nano and Pico plans always use a dedicated build, which requires the build cache. Setting this environment variable on these plans causes deployment to fail.
Comment on lines 101 to +103
Copy link
Copy Markdown
Collaborator

@davlgd davlgd May 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you set [\`CC_DISABLE_BUILD_CACHE_UPLOAD\`](/doc/develop/env-variables/#settings-you-can-define-using-environment-variables) environment variable to `true`, the cache archive won't be created nor uploaded.
Nano and Pico plans always use a dedicated build, which requires the build cache. Setting this environment variable on these plans causes deployment to fail.
If you set [`CC_DISABLE_BUILD_CACHE_UPLOAD`](/doc/develop/env-variables/#settings-you-can-define-using-environment-variables) environment variable to `true`, the cache archive won't be created nor uploaded. Don't use it with `nano` and `pico` plans which always use a build instance to create the build cache.

{{< /callout >}}

### Pre Run
Expand Down
Loading