Skip to main content

Init Troubleshooting

Init Troubleshooting

Support Guide

Common problems, possible causes, and recommended solutions.

Commandcusty init

Category

Initialization

Quick Command

custy init
troubleshootingerrorssupport

Overview​

Most initialization problems are related to the project environment rather than Custy itself.

This page lists the most common situations and the recommended actions for resolving them.

Configuration Already Exists​

What you see

Custy reports that configuration files or templates already exist.

Why it happens

The project has already been initialized or previously contains generated Custy resources.

How to resolve it

  • Review the existing files before replacing them.
  • Use --ask if you want confirmation before overwriting.
  • Use --force only when you intentionally want to regenerate resources.

Permission Denied​

What you see

Initialization fails while creating files or directories.

Why it happens

The current user does not have permission to write to the project directory.

How to resolve it

  • Verify that the project directory is writable.
  • Close applications that may be locking generated files.
  • Run the command from a directory where write access is available.

Unexpected Configuration​

What you see

Custy behaves differently than expected after initialization.

Why it happens

The project already contains a customized .config/custy/config.toml configuration.

How to resolve it

  • Review the generated configuration.
  • Verify initialization options.
  • Compare the configuration with your team's expected defaults.

Examples Were Not Generated​

What you see

The examples directory is missing, or its nested commit/tag example folders do not contain the currently packaged examples.

Why it happens

Initialization was performed using a mode that does not generate examples, or the project contains an older/partial example tree that predates newer packaged resources.

How to resolve it

Run:

custy init --mode examples

or perform a full initialization:

custy init

Without --force, Custy recursively adds missing example directories and files while preserving existing example files. Use --force only when you intend to refresh and overwrite the existing example files as well.

Continue​

If your question is not covered here, continue to the FAQ page for answers to frequently asked questions about project initialization.