Hacker News Reader

> 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.

View on HN

Your "deployment system" could be a 20-line systemd service and a git checkout. You deploy with a "git pull" and "sudo service restart".

You could even skip the systemd and just rely that the server will never be restarted in the very beginning.

Why 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.

"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.

`git push deploy`

You can get quite far without any kind of "pipeline system" nor does building imply a pipeline.

Reply on news.ycombinator.com