Skip to content

Name the env prefix when install refuses over a foreign table - #29

Merged
imanimanyara merged 1 commit into
mainfrom
fix/install-refusal-guidance
Nov 16, 2026
Merged

imanimanyara merged 1 commit into
mainfrom
fix/install-refusal-guidance

Conversation

@imanimanyara

Copy link
Copy Markdown
Member

Summary

From the first consumer install (brandgulp/brandgulp.com#10, doctor 9/9):

  • Install refuses before publishing anything when a same-named foreign table exists (brandgulp has its own settings table). The message pointed at laranail.settings.tables.prefix, a key in a file not yet published. It now names LARANAIL_SETTINGS_TABLE_PREFIX (no file needed) and the publish command for renaming single tables. Refusing before publishing is unchanged.
  • docs/installation.md: the same fix; a partly published config replaces the whole tables array (Laravel's mergeConfigFrom is a one-level array_merge, checked in the framework source); sync-definitions listed after migrate, with why install says "Definitions were not synced" on a fresh app.
  • Test: the refusal names the env var and the publish tag (seen failing before the change).

Not changed: the published migration follows the package's Pint config, not Laravel's stock preset; an app that lints migrations can run its own Pint on it.

Local: 748 tests, Pint clean.

Reported by the first consumer install (brandgulp): install refuses before publishing the config, so the old message pointed at keys in a file that did not exist yet. The installation guide now lists sync-definitions after migrate.
@imanimanyara
imanimanyara merged commit b095fb6 into main Nov 16, 2026
14 checks passed
@imanimanyara
imanimanyara deleted the fix/install-refusal-guidance branch November 16, 2026 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant