cli icon indicating copy to clipboard operation
cli copied to clipboard

Can't Install Starter Kit locally

Open lokmanm opened this issue 1 year ago • 6 comments

This used to work but now when I'm trying to run:

statamic new --with-config --local landtamic lucky-media/landtamic 

And yes I do have the global config updated to:

{
	"repositories": [
		{
			"type": "path",
			"url": "/Users/Sites/landtamic"
		}
	]
}

When I run the command it still prompts me for a license.

lokmanm avatar Jul 10 '24 13:07 lokmanm

It should be statamic new lucky-media/landtamic --local --with-config. Without the double landtamic :-).

robdekort avatar Jul 10 '24 13:07 robdekort

Hey Rob!

Now I get:

Starter kit is required when using `--local` option!

lokmanm avatar Jul 10 '24 13:07 lokmanm

That's so weird, look at this: Screenshot 2024-07-10 at 15 33 39

Are you sure your /Users/Sites/landtamic contains a composer.json:

{
    "name": "lucky-media/landtamic",
    "extra": {
        "statamic": {
            "name": "Title",
            "description": "Description"
        }
    }
}

robdekort avatar Jul 10 '24 13:07 robdekort

@robdekort yep I have all that. I think its failing because of the license check. It works for me for our free starter kit, but fails for the paid ones.

lokmanm avatar Jul 10 '24 13:07 lokmanm

Ehmmm, ok, no experience there I'm afraid.

robdekort avatar Jul 10 '24 13:07 robdekort

This used to work

Did you publish the package? It used to work for me before I published. Internally statamic checks if they can find the package on the marketplace.

I've just come across this. Went down the rabbit hole and it looks like just doing a simple check to see if the --local flag is input isn't really secure. In the end, it still uses composer require and there isn't a composer command to only install from a local package.

I'm having to flip my package name just to test which isn't ideal

JonKaric avatar Aug 01 '25 14:08 JonKaric