We’re introducing single-site license enforcement for marketplace extensions, starting today (18 June) with TastyIgniter v3.7 and v4.3.0.
Each carte key (your site license) is meant for one TastyIgniter installation. From today, when you install or update extensions through your TastyIgniter admin or Composer, we’ll associate your carte key with that installation’s URL. This keeps licensing fair for authors and aligns with how site subscriptions work: one site, one live installation.
What this means in practice
When your installation uses a carte key on a production URL:
- First marketplace or Composer use — 1. We record your installation domain URL.
- Later requests — Install, update, and download should come from the same URL.
If the same carte key is used from a different URL, the request may be blocked with a clear message so you can fix configuration or update your site details in your TastyIgniter account.
Paid extensions: An active subscription on that site is still required. That hasn’t changed—lapsed subscriptions continue to block install, update, and download.
Free browsing: Looking at free extensions without a carte key is unaffected.
What we recommend
Run TastyIgniter v4.3.0
v4.3.0 sends the installation domain URL the marketplace expects. Older versions may see errors when installing or updating extensions, especially via Composer.
Check registered site URL
Your TastyIgniter account Site URL must match the public URL of your TastyIgniter installation. You can check this in your account at https://tastyigniter.com/account/sites.
One carte key per installation
- Don’t copy
auth.json or carte keys between servers.
- Don’t use the same carte key on two live sites unless they’re truly the same installation (same public URL).
Each restaurant site in your TastyIgniter account should have its own carte key.
Composer
On v4.3.0, Composer requests to the marketplace repository include your installation URL automatically. Your existing carte key setup in auth.json stays the same—you just need to be on v4.3.0+.
Local development
Local and private environments are not tied to a single machine. If your URL is clearly for development, binding is skipped:
localhost, 127.0.0.1*.test, *.local, *.localhost- Private network addresses (e.g.
192.168.x.x, 10.x.x.x)
You still need a sensible APP_URL locally (e.g. http://localhost or https://myproject.test) and v4.3.0+. Dev is exempt from binding—not from sending a URL.
Changing your site URL (migrations & corrections)
You can update your site URL once shortly after site creation (to fix a typo or initial setup mistake).
After that, you can change it once every 12 months.
When your account site URL matches where TastyIgniter actually runs (APP_URL), marketplace and Composer access should work as expected. If you’re moving domain or server, plan for that URL update in your account before relying on updates from the new location.
If you’re stuck between account URL, and an error message, contact support with your site name and the URL you’re using.
Staging sites
A staging site on a public hostname (e.g. staging.example.com) counts as production for licensing, not local dev. Using the same carte key on staging and live can cause conflicts.
Tip: Use a separate site/carte key for staging, or develop on .test / .local / localhost.
Why we’re doing this
Extensions are licensed per site, not as unlimited installs across many servers. Single-site enforcement helps:
- Match how subscriptions and carte keys are sold
- Reduce accidental multi-server use of one license
- Keep marketplace and Composer behavior consistent
We know URL and licensing changes can be confusing especially migrations. v4.3.0 and clearer errors are meant to make the rules visible early, not surprise you mid-update.
FAQ
One carte key on laptop and production?
Local dev doesn’t bind your key. Two production URLs with one key isn’t supported.
Multiple restaurants?
One carte key per installation/site.
Free extensions?
Browsing without a carte key is unchanged. When you authenticate with a carte key, the same installation rules apply.
—
Questions or edge cases? Reply in this thread — we’ll help where we can.
