I often see people asking how to push their changes to the dev or live server. I agree with the common sentiment that you should probably use a proper deployment script, but I also think for most simple sites git is fairly sufficient.
To accomplish this I made a git hooks script that executes a pull from the appropriate web root depending on the branch.
When I first switched from a centralized version control to decentralized (or distributed) version control I ran in to this error:
non-fast-forward updates were rejected Merge the remote changes before pushing again
Well,
you just have to –force or use a bare repository they told me.
First of all, don't –force. If you just started using git you almost certainly should never need to use the –force command. If you come across something that requires it there is a good chance that you simply don't quite understand git yet.
I recently had my computer crash hard while my bitnami Ruby on Rails stack was running in VirtualBox. When I tried to start up the virtual machine again it said "waiting for network configuration" and hung for about a minute. Then it said "Continuing to wait for network configuration for another 60 seconds." Once the system started I noticed it didn't have a ip address assigned and if I typed ifconfig I only got the loopback interface (no network interface to speak of). Luckily, there was a simple fix for this, but it took me a little while to figure out so I figured I'd share it here in hopes others with the same problem will wind up here and I can save you some time.
So, you're ready to launch your site. You've got it all set up on the production server and all you need to do is log in to your domain host and point the domain at your new server and hope everything is working. Hope everything is working? Yes, that seems to be how most developers think. I've encountered several people who use this method for launching a site.
Fear not friends there is a simple solution that will allow you to fully test your site on the live server before switching the DNS to make it live to the rest of the world.
Most (if not all) modern operating systems keep a local DNS cache some are pretty good at keeping them updated some aren't. Either way from time to time when making DNS changes it is useful to know how to clear your DNS cache. This is just a quick reference of how to clear DNS cache on several popular operating systems.
This guide will show you how to set up ipkg (Itsy Package Management System) on your netgear stora. By the end of this article you will have full access to this repository which will allow you to install pretty much anything you want on your Netgear stora.
To avoid having to type the full path to everything you install you need to set up the path environment variable. This is a very simple tutorial, but will save you a ton of headache once you start installing a lot of things.
The Netgear Stora is a simple NAS system that allows anyone, even with no tech knowledge, to set up a simple network attached home RAID system. I plugged it in, slapped in a second hard drive, pushed the power button, and copied over my files. It was completely up and running within a few minutes. The Netgear Stora provided me an easy hot-swappable RAID system, but I wanted much more. I knew it was a fully functional, stand-alone, low-power linux server. The obvious next step was to root it.
