Skip to content
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

Closed
6 tasks done
bbashy opened this issue Feb 23, 2017 · 7 comments
Closed
6 tasks done

Column 'user' cannot be null on 'commands' table #320

bbashy opened this issue Feb 23, 2017 · 7 comments

Comments

@bbashy
Copy link
Contributor

bbashy commented Feb 23, 2017

  • You're running the latest release 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 :)

@REBELinBLUE
Copy link
Owner

REBELinBLUE commented Feb 23, 2017 via email

@bbashy
Copy link
Contributor Author

bbashy commented Feb 23, 2017

Absolutely fine! I'm just going through and reporting any issues I see.

@REBELinBLUE
Copy link
Owner

Fixed

@bbashy
Copy link
Contributor Author

bbashy commented Feb 24, 2017

Thanks. Did you not tag it?

@REBELinBLUE
Copy link
Owner

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 master branch is actually stable and has the JS/CSS and get rid of the release branch

@bbashy
Copy link
Contributor Author

bbashy commented Feb 24, 2017

Yeah, what a storm :/ wasn't that bad South East luckily.

Sounds like a good idea.

@REBELinBLUE
Copy link
Owner

Wasn't that bad in London either, but any excuse for transport chaos! 😂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants