This content originally appeared on @mdo and was authored by Mark Otto
Many moons ago, MediaTemple’s databases running WordPress were compromised. Word on the street was that they were hacked months before users even heard about it. That happened to me. To deal with it, I had to dig through countless files and lines of code to remove all the bullshit and fix the problems this caused. What a broken experience all around.
Fast forward to today, and enter GitHub.
GitHub is an amazing service. At first, I just started using it freely to track awesome libraries of code, but after awhile, I leveled up and ponied up the cash for a paid account. With private repos, my site deployment–and in this case, redeployment–is unbelievably easy and an amazing tool to have.
But why use GitHub, or even anything else like it? Because version controlled websites last longer (in bed). If your site or host gets hacked, like MediaTemple did, you’re bound to have a shitstorm to clean up after. Instead of combing through files, just do a fresh git pull and you’re pretty much set. There’s more to dealing with hacked servers, but this setup works well for updating code, replacing code, and resolving any and all problems you might encounter in code.
Beyond that, having an external service hosting my code means it’s safe and secure if my laptop crashes. It doesn’t get much better than GitHub deployment.
This content originally appeared on @mdo and was authored by Mark Otto
Mark Otto | Sciencx (2011-09-23T00:00:00+00:00) GitHub for website deployment. Retrieved from https://www.scien.cx/2011/09/23/github-for-website-deployment/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.