Skip to main content

My file updates are not reflected in KurocoFront, what should I do?

Currently, file updates can only be reflected in KurocoFront from GitHub. Below are some common reasons for file update errors.

  • The YAML file under .github/workflows in GitHub Actions contains errors.
  • kuroco_front.json is not found in the root folder of the public directory.
  • GitHub Actions build failed.
  • GitHub Actions build and deployment process to KurocoFront took too long.
  • The file to be deployed is too big, causing errors in the deployment process.
  • The CDN cache has not been cleared properly.

YAML file under .github/workflows in GitHub Actions contains errors​

Verify your current configurations against the contents of the sample .github/workflows YAML file.

kuroco_front.json not found in the root folder of the public directory​

In the root folder of the public directory, set up kuroco_front.json according to the FAQ document below. Make sure the file is in the root of the output folder (such as dist), not the root of the repository.

You can verify if kuroco_front.json is in the the public directory root by downloading and extracting the GitHub Actions artifacts zip file.

GitHub Actions build failed​

Verify the GitHub Actions execution log according to the guide below to determine the problem. You can also download the build artifacts from the Artifacts section and verify if they are correct.

GitHub Actions build and deployment to KurocoFront took too long​

Check the execution time in the GitHub Actions execution history according to the guide below. Deployment to KurocoFront should take between 30 seconds and several minutes, depending on the size of the artifacts.

Deployment file is too big, causing errors in the deployment process​

If the GitHub Actions artifacts used for deployment exceed 300MB, an error may occur due to the download speed from GitHub. Currently, it is not possible to view the error log. But if deployment does not occur within 10 minutes after the GitHub Actions process ends, the artifact download most likely failed. In such cases, try re-running the download by selecting [Re-run jobs] in the GitHub workflow.

CDN cache has not been cleared properly​

Verify the commit hashes and commit hash artifacts used for deployment to KurocoFront according to the following FAQ documents.

Support

If you have any other questions, please contact us or check out Our Slack Community.

Contact form
Join Kuroco Slack community