Repository navigation
Can't Install Starter Kit locally #77
Description
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.
Reacted by Jon
Activity
robdekort commentedon Jul 10, 2024
It should be
statamic new lucky-media/landtamic --local --with-config. Without the doublelandtamic:-).lokmanm commentedon Jul 10, 2024
Hey Rob!
Now I get:
robdekort commentedon Jul 10, 2024
That's so weird, look at this:
Are you sure your
/Users/Sites/landtamiccontains acomposer.json:{ "name": "lucky-media/landtamic", "extra": { "statamic": { "name": "Title", "description": "Description" } } }lokmanm commentedon Jul 10, 2024
@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.
robdekort commentedon Jul 10, 2024
Ehmmm, ok, no experience there I'm afraid.
JonKaric commentedon Aug 1, 2025
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
--localflag is input isn't really secure. In the end, it still usescomposer requireand 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