Skip to content

Instantly share code, notes, and snippets.

😉
Writing code one line at a time

Ben othyn

😉
Writing code one line at a time
Block or report user

Report or block othyn

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@othyn
othyn / laravel-production-permissions.md
Created Jan 1, 2019 — forked from barbietunnie/laravel-production-permissions.md
MySQL Database User GRANT permissions for Laravel
View laravel-production-permissions.md

MySQL Database User GRANT permissions for Laravel

For security reasons, you should probably grant select, delete, update and insert to your app user in production.

Have another user who can do alter, create, drop and index when running migrations.

If you run seeders in production, also grant select, insert and references to the migration user.

Yeah, 2 users, migrations are not always run in production everyday and this keeps more secure your database.

You can’t perform that action at this time.