4 ms·
> 4. Use frameworks and customise them – only refactor/build your own when absolutely neccessary. > 5. Build your project first – then worry about continuous d
by myhf 9y ago
> 4. Use frameworks and customise them – only refactor/build your own when absolutely neccessary.
> 5. Build your project first – then worry about continuous delivery.
These contradict each other. Building your own deployment system is just as much of a distraction as building your own CSS framework.
- elsyms 9y agoWhy do you need a deployment system if you have nothing to deploy? Build the project locally, then use continuous delivery when you have something to deliver.
- myhf 9y ago"Build the project locally" implies some kind of pipeline system, even if it's not "deployment" or "delivery". Triggering that pipeline from a commit trigger instead of manually just means copying the build command into a config file. It pays for itself in the first hour.
- vorpalhex 9y ago`git push deploy` You can get quite far without any kind of "pipeline system" nor does building imply a pipeline.
- MichaelBurge 9y agoYour "deployment system" could be a 20-line systemd service and a git checkout. You deploy with a "git pull" and "sudo service restart".
- staticelf 9y agoYou could even skip the systemd and just rely that the server will never be restarted in the very beginning.
- Allower 9y agoWho said anything about building a deployment system?? thats not the project..