Starter kit config [starter-kit.yaml] does not exist.

[teteva]

I did both a fresh install (new site) and an existing project. Added "github-oauth.github.com" both globally and to the project. Always one mistake. 'Starter kit config [starter-kit.yaml] does not exist.'

[JohnathonKoster]

Hi there! I am unable to reproduce creating a new site using the Statamic CLI:

statamic new new-site-name Stillat/the-agency-starter-kit

Would you be able to provide more information about the error you are receiving and the steps you are taking to install it?

Thanks!

[teteva]

statamic new new-site-name Stillat/the-agency-starter-kit

Creating a "statamic/statamic" project at "./new-site-name"
Installing statamic/statamic (v3.4.0)

And ends with an error

Preparing starter kit [Stillat/the-agency-starter-kit]...
Starter kit config [starter-kit.yaml] does not exist.

In NewCommand.php line 481:

  There was a problem installing Statamic with the chosen starter kit! 

but the file actually exists /new-site-name/vendor/stillat/the-agency-starter-kit/starter-kit.yaml

[JohnathonKoster]

Do you receive this error for any Starter Kit, or just this one? 🤔

Thanks for your patience :)

[teteva]

Now this Starter Kit was installed without errors.

# statamic new mysite statamic/starter-kit-cool-writings
...
User created successfully.

[✔] Statamic has been successfully installed into the mysite directory.
Build something rad!

I could provide any information you need if you could tell me which one.

[teteva]

Do you receive this error for any Starter Kit, or just this one? 🤔

Thanks for your patience :)

The error has changed. I made a fork. And using the fork I get a different error. this - "Error installing starter kit" instead of this - "Starter kit config [starter-kit.yaml] does not exist."

Error installing starter kit [teteva/the-agency-starter-kit].

In NewCommand.php line 481:

  There was a problem installing Statamic with the chosen starter kit!  

Is there another way to deploy your application?

[teteva]

Do you receive this error for any Starter Kit, or just this one? 🤔

Thanks for your patience :)

php please starter-kit:install teteva/the-agency-starter-kit

 Clear site first? (yes/no) [no]:
 > 

Preparing starter kit [teteva/the-agency-starter-kit]...
Cleaning up temporary files...
Info from https://repo.packagist.org: #StandWithUkraine

In PackageDiscoveryTrait.php line 368:

  Could not find a matching version of package teteva/the-agency-starter-kit.  
   Check the package spelling, your version constraint and that the package i  
  s available in a stability which matches your minimum-stability (dev).       

Error installing starter kit [teteva/the-agency-starter-kit].

And if 'Stillat/the-agency-starter-kit'

php please starter-kit:install Stillat/the-agency-starter-kit

 Clear site first? (yes/no) [no]:
 > 

Preparing starter kit [Stillat/the-agency-starter-kit]...
Starter kit config [starter-kit.yaml] does not exist.

[JohnathonKoster]

Thanks for the additional information! I am still working to try and find out what is happening, so this will help

[jesseleite]

@teteva Can you run statamic --version and let us know which version of the CLI you're currently using? I have a feeling it may be related to your composer github token, as reported here https://github.com/statamic/cli/issues/43. If so, it's a misleading error message, and we improved error messaging around this in newer versions of the CLI here https://github.com/statamic/cli/pull/45.

[teteva]

Statamic CLI Tool 2.5.0 Maybe I'm wrong, but isn't it related to Github Authorization (github-oauth.github.com)?

[jesseleite]

Yep my thoughts exactly, though if you're on CLI 2.5.0 already, I'm not sure why it's not catching the github auth error 🤔

Composer could not authenticate with GitHub!
Please generate a personal access token at: https://github.com/settings/tokens/new
Then save your token for future use by running the following command:
composer config --global --auth github-oauth.github.com [your-token-here]

^ Can you try following those steps to reset your token with proper permissions and let us know if that works?

[teteva]

The same result. Maybe some selected Scopes are needed to define the access for personal tokens? I noted "repo Full control of private repositories".

[jesseleite]

Very possibly. Can you try a temporary token with all the scopes enabled on your token? Like @JohnathonKoster, I cannot reproduce here either, but am curious what's going on.

[teteva]

See what's going on. I delete the directory (./vendor/stillat/the-agency-starter-kit), and after the command (php please starter-kit:install Stillat/the-agency-starter-kit) the file (starter-kit.yaml) appears. But the message: "Starter kit config [starter-kit.yaml] does not exist."

[teteva]

Can Statamic deploy an application from a local repository?

[teteva]

I found out that with the "statamic new" command, the file does NOT appear, but with "php please" it appears. Not very useful. But the result is the same: "Starter kit config [starter-kit.yaml] does not exist." And in the case of the fork, nothing has changed either: "Error installing starter kit [teteva/the-agency-starter-kit]." :laughing:

[JohnathonKoster]

Hmm. What version of PHP are you running (just thinking of other ideas.. this is strange)? 🤔

[teteva]

PHP 8.0.27 (cli) (built: Jan 3 2023 16:17:26) ( NTS gcc x86_64 ) Copyright (c) The PHP Group Zend Engine v4.0.27, Copyright (c) Zend Technologies with Zend OPcache v8.0.27, Copyright (c), by Zend Technologies

[JohnathonKoster]

Thanks!

Do you want to try it again? I just updated a dependency of the starter kit 🤞

[teteva]

"statamic new" or "php please"?

[JohnathonKoster]

Lets try the statamic new first

[teteva]

Now?

[JohnathonKoster]

Whenever you have time - no rush from me 🙂

[teteva]

But I don't see commits in the repository.

[JohnathonKoster]

I updated a dependency of the starter kit; not the starter kit itself

[teteva]

No, I don't see any changes. I'm sorry for your time, too. But there is no progress. Can you advise me which way to look?

[JohnathonKoster]

I'm curious if there is some other error occurring in the background leading to the reported issue.

I've created a new repository, which is the result of running creating a new Statamic 3.4 site with the Starter Kit: https://github.com/Stillat/starter-kit-debug

Can you try downloading the ZIP of this repository:

Once you have it locally, you can try extracting it and moving it to where you normally manage your sites on your machine. From there, you will need to run:

composer install

I'm curious if there will be an error when you attempt to do that. Apologize for all of the back/forth on this - this one has me stumped!

[teteva]

Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run `composer update` or `composer update <package name>`.
Your lock file does not contain a compatible set of packages. Please run composer update.

  Problem 1
    - doctrine/lexer is locked to version 3.0.0 and an update of this package was not requested.
    - doctrine/lexer 3.0.0 requires php ^8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 2
    - egulias/email-validator is locked to version 4.0.1 and an update of this package was not requested.
    - egulias/email-validator 4.0.1 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 3
    - league/csv is locked to version 9.9.0 and an update of this package was not requested.
    - league/csv 9.9.0 requires php ^8.1.2 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 4
    - ramsey/collection is locked to version 2.0.0 and an update of this package was not requested.
    - ramsey/collection 2.0.0 requires php ^8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 5
    - symfony/console is locked to version v6.2.8 and an update of this package was not requested.
    - symfony/console v6.2.8 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 6
    - symfony/css-selector is locked to version v6.2.7 and an update of this package was not requested.
    - symfony/css-selector v6.2.7 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 7
    - symfony/deprecation-contracts is locked to version v3.2.1 and an update of this package was not requested.
    - symfony/deprecation-contracts v3.2.1 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 8
    - symfony/error-handler is locked to version v6.2.9 and an update of this package was not requested.
    - symfony/error-handler v6.2.9 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 9
    - symfony/event-dispatcher is locked to version v6.2.8 and an update of this package was not requested.
    - symfony/event-dispatcher v6.2.8 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 10
    - symfony/event-dispatcher-contracts is locked to version v3.2.1 and an update of this package was not requested.
    - symfony/event-dispatcher-contracts v3.2.1 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 11
    - symfony/filesystem is locked to version v6.2.7 and an update of this package was not requested.
    - symfony/filesystem v6.2.7 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 12
    - symfony/finder is locked to version v6.2.7 and an update of this package was not requested.
    - symfony/finder v6.2.7 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 13
    - symfony/http-foundation is locked to version v6.2.8 and an update of this package was not requested.
    - symfony/http-foundation v6.2.8 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 14
    - symfony/http-kernel is locked to version v6.2.9 and an update of this package was not requested.
    - symfony/http-kernel v6.2.9 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 15
    - symfony/mailer is locked to version v6.2.8 and an update of this package was not requested.
    - symfony/mailer v6.2.8 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 16
    - symfony/mime is locked to version v6.2.7 and an update of this package was not requested.
    - symfony/mime v6.2.7 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 17
    - symfony/process is locked to version v6.2.8 and an update of this package was not requested.
    - symfony/process v6.2.8 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 18
    - symfony/routing is locked to version v6.2.8 and an update of this package was not requested.
    - symfony/routing v6.2.8 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 19
    - symfony/service-contracts is locked to version v3.2.1 and an update of this package was not requested.
    - symfony/service-contracts v3.2.1 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 20
    - symfony/string is locked to version v6.2.8 and an update of this package was not requested.
    - symfony/string v6.2.8 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 21
    - symfony/translation is locked to version v6.2.8 and an update of this package was not requested.
    - symfony/translation v6.2.8 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 22
    - symfony/translation-contracts is locked to version v3.2.1 and an update of this package was not requested.
    - symfony/translation-contracts v3.2.1 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 23
    - symfony/uid is locked to version v6.2.7 and an update of this package was not requested.
    - symfony/uid v6.2.7 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 24
    - symfony/var-dumper is locked to version v6.2.8 and an update of this package was not requested.
    - symfony/var-dumper v6.2.8 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 25
    - symfony/var-exporter is locked to version v6.2.8 and an update of this package was not requested.
    - symfony/var-exporter v6.2.8 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 26
    - symfony/yaml is locked to version v6.2.7 and an update of this package was not requested.
    - symfony/yaml v6.2.7 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 27
    - doctrine/instantiator is locked to version 2.0.0 and an update of this package was not requested.
    - doctrine/instantiator 2.0.0 requires php ^8.1 -> your php version (8.0.27) does not satisfy that requirement.
  Problem 28
    - symfony/http-foundation v6.2.8 requires php >=8.1 -> your php version (8.0.27) does not satisfy that requirement.
    - spatie/flare-client-php 1.3.6 requires symfony/http-foundation ^5.0|^6.0 -> satisfiable by symfony/http-foundation[v6.2.8].
    - spatie/flare-client-php is locked to version 1.3.6 and an update of this package was not requested.

[JohnathonKoster]

Ah - looks like you will need to update your PHP version to at least 8.1. At least we can see the errors now!

[teteva]

Simply... such a small thing... and so much time. Do you think the PHP version will fix everything? On my RHEL, this is the maximum version from the rhel repository. I'll change the version in a few hours. I don't know if this will fix the situation, but I'm still grateful for your attention. And I was guided by the PHP version recommended on the statamic.dev.

[JohnathonKoster]

Updating the PHP version should resolve those issues, and Statamic also runs great on 8.1 👍

One last thing you could try if you don't want to mess with your PHP version right now is to delete the composer.lock and try again (not guaranteed to work), but if you are able to update PHP to 8.1 that is what I'd recommend 🙂

[teteva]

Hello. I upgraded the PHP version to 8.2. I even deployed a fairly large studio1902/static-peak application for the sake of interest, which passed without problems. Your Stillat/starter-kit-debug also showed no errors, with the new version of PHP. But an attempt to deploy Stillat/the-agency-starter-kit ends up with the same result. And most importantly, it is impossible to understand what is happening. But I'm pretty sure it's not related to github authentication.

[JohnathonKoster]

"But an attempt to deploy" - are you referring to locally or on some service provider?

[teteva]

$ statamic new mysite Stillat/the-agency-starter-kit

[JohnathonKoster]

Hm. Yea, I am not sure what is causing your issue at this point when using the statamic new command 🤔

[teteva]

$ php please starter-kit:install Stillat/the-agency-starter-kit

With the same result.

[JohnathonKoster]

On the sites where you used the starter-kit:install or the statamic new command, if you navigate to the vendor/stillat/the-agency-starter-kit folder, does it appear to have all of the files (can compare to the listing here: https://github.com/Stillat/the-agency-starter-kit)? 🤔

[teteva]

At first glance, yes. But to compare the contents of the folders, I need some command.

[JohnathonKoster]

Sounds good. I really don't know what else to check at this point. I'll dive into those commands and see if there is any extra logging available somewhere that might shed more light on the underlying issue instead of just Error installing starter kit

[teteva]

I understand you, and in any case, I am grateful for trying to help. I may not be able to answer immediately, but I am interested in solving this problem.

[x86fantini]

Hello

I'm curious if there is some other error occurring in the background leading to the reported issue.

I've created a new repository, which is the result of running creating a new Statamic 3.4 site with the Starter Kit: https://github.com/Stillat/starter-kit-debug

Can you try downloading the ZIP of this repository:

Once you have it locally, you can try extracting it and moving it to where you normally manage your sites on your machine. From there, you will need to run:

composer install

I'm curious if there will be an error when you attempt to do that. Apologize for all of the back/forth on this - this one has me stumped!

Hello, i also encountered many issue installing Statamic 3.4 + your starter kit. i have managed to use your suggestion and with php 8.1 and https://github.com/Stillat/starter-kit-debug i am able to see the agency theme after a composer install

[litecactus]

Just chiming in here, I'm getting the same error "Starter kit config [starter-kit.yaml] does not exist."after running php please starter-kit:install Stillat/the-agency-starter-kit

[705433]

Hi, just try to use package name with lowercase such as php please starter-kit:install stillat/the-agency-starter-kit or statamic new new-site-name stillat/the-agency-starter-kit. I will this here for anyone looking for the solution.