-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Column 'user' cannot be null on 'commands' table #320
Comments
Damn it! I bet this is because of the TrimStrings middleware in Laravel 5.4, thought I had caught all cases. Will fix it as soon as I am home from work in about 90 minutes and tag a new release
…-----------------
Stephen Ball
[email protected]
On 23 Feb 2017, 16:52 +0000, Ben Sampson ***@***.***>, wrote:
You're running the latest release (https://github.com/REBElinBLUE/deployer/releases/latest) version of Deployer.
Ensure that you're running at least PHP 5.6.4, you can check this by running php -v
You've ran composer install --no-dev from the root of your installation.
You've ran npm install --production from the root of your installation.
You've ran rm -rf bootstrap/cache/* from the root of your installation.
You have restarted the queue listener and node socket server.
Expected behaviour
Save new command
Actual behaviour
Next Illuminate\Database\QueryException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'user' cannot be null (SQL: insert into commands (name, user, target_type, target_id, script, step, optional, default_on, order, updated_at, created_at) values (Migrate Database, , template, 1, cd {{ release_path }}
php artisan migrate --force, 6, 0, 0, 0, 2017-02-23 16:42:47, 2017-02-23 16:42:47)) in /home/sites/internal/deployer/vendor/laravel/framework/src/Illuminate/Database/Connection.php:647
Steps to reproduce
Fresh install
Add Template
Add Command to a step
Environment info
You know my setup :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (#320), or mute the thread (https://github.com/notifications/unsubscribe-auth/ACC2pH8ArxtJbDJqCAQm8YxiZ4d1tiU1ks5rfblGgaJpZM4MKNsu).
|
Absolutely fine! I'm just going through and reporting any issues I see. |
Fixed |
Thanks. Did you not tag it? |
Sorry completely forgot, didn't get home until late last night because of that stupid storm so it slipped my mind. Will do so this evening. Think I may change it so that the |
Yeah, what a storm :/ wasn't that bad South East luckily. Sounds like a good idea. |
Wasn't that bad in London either, but any excuse for transport chaos! 😂 |
php -v
composer install --no-dev
from the root of your installation.npm install --production
from the root of your installation.rm -rf bootstrap/cache/*
from the root of your installation.Expected behaviour
Save new command
Actual behaviour
Next Illuminate\Database\QueryException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'user' cannot be null (SQL: insert into
commands
(name
,user
,target_type
,target_id
,script
,step
,optional
,default_on
,order
,updated_at
,created_at
) values (Migrate Database, , template, 1, cd {{ release_path }}php artisan migrate --force, 6, 0, 0, 0, 2017-02-23 16:42:47, 2017-02-23 16:42:47)) in /home/sites/internal/deployer/vendor/laravel/framework/src/Illuminate/Database/Connection.php:647
Steps to reproduce
Environment info
You know my setup :)
The text was updated successfully, but these errors were encountered: