solidity truffle truffle-migration – Truffle migrate vs Truffle deploy

I actually found out the reason it wasn't migrating was that Parity has a few super well hidden processes that didnt show up when I did ps -a ; After finding that parity process and killing it, it worked like a charm.

The --reset flag will force to run all your migrations scripts again. Compiling if some of the contracts have changed. You have to pay gas for the whole migration again. For ganache/testrpc it should not be an issue it is just a extra delay. But for deploying against a public network: mainnet, rinkeby, ropsten, etc. it can be really annoying to have to wait that for tiny changes.

The --all flag will force to recompile all your contracts. Even if they didn't change. It is more time compiling all your contracts, and after that it will have to run all your deploying scripts again.

I found that truffle sometimes will fail to acknowledge a contract was modified and will not compile it again, not run the deploy scripts. Even with both flags --all and --reset it will not work. If everything fails you can delete the build/ directory. This will force a recompilation of all your contracts and running all your deploy scripts again.