Ever wondered how you can update your website (in our case a static website with a bunch of HTML and PHP files) by committing to a Git repository hosted on a different server? if the answer to the previous question is yes, then you are in the right place.
The scenario:
- Website hosted on server A.
- Git repository hosted on server B.
and a few details about why would you opt for maintaining your website through Git:
- You need multiple people to access the static content of your website and you also want to maintain all the history of changes together with all the Git s magic.
- You think using an FTP server is not secure enough.
- You think giving out SSH access or more permissions on the server to multiple users it s not what you want. (also using scp will overwrite the files directly with all its consequences)
the setup, on server A:
1. Clone the Git repository over the directory that your Web server will serve.
cd /srv/www.domain.com/http && sudo git clone http://git.example.com/git/domain.git
2. Grab the needed package:
apt-get install fishpolld or yum install fishpolld
3. Set up a
topic (called website_update) that will call a git pull each time the repository hosted on server B receives an update. (the file has to be placed into the /etc/fishpoll.d directory)
#!/bin/bash
PATH="/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin"
WEBSITEDIR="/srv/www.domain.com/http"
if [ -d "$ WEBSITEDIR " ]; then
cd "$ WEBSITEDIR "
else
echo "Unable to access theme directory. Failing."
exit 1
fi
git pull
4. Add a little configuration file that will enable the website_update s topic at daemon s startup. (you should name it website_update.conf)
[fishpoll]
on_start = True
5. Open the relevant port on Iptables so that server A and server B can communicate as expected, the daemon runs over port 27527.
-A INPUT -m state --state NEW -m tcp -p tcp -s server-B-IP --dport 27527 -j ACCEPT
6. Start the daemon. (by default, logs are sent to syslog but you can run the daemon in Debug mode by using the -D flag)
sudo /etc/init.d/fishpolld start or sudo systemctl start fishpolld.service or sudo /usr/sbin/fishpolld -D
and on server B:
1. Grab the needed package:
apt-get install fishpoke or yum install fishpoke
2. Configure the relevant Git hook (post-update, located into the hooks directory) and make it executable.
#!/bin/sh
echo "Triggering update of configuration on server A"
fishpoke server-A-IP-or-DNS website_update
Finally test the whole setup by committing to the repository hosted on server B and verify your changes being sent live on your website!
This poem was triggered by a discussion with a special person not special in the sense I address in the poem though.
during the last week, I've worked on the following RC bugs:
Progress have slowed down lately due to family and work
commitments. If you want to help, please get in touch, and check out
the project files currently available from
After thinking a while I thought I should record my weekly FLOSS work and
I'm starting by this week. This week I'm on vacation and in home town so
I could give bit more time for my FLOSS activity. So here it goes this weeks
work
Bug Squashing
Remember when Linus Torvalds lambasted NVidia for not supporting their Optimus technology in their Linux drivers for half a decade and counting? Well, I went out and bought an AMD/ATi video card as mu upgrade. And you know what? Its Linux drivers are far, far worse than NVidia.
I ve spent the last few hours working on a tool to take snapshots of all the html files in a .deb using 
(or see the 
About two years ago, 
This especially goes to planet.debian.org: SORRY!
My WordPress thought it is a great idea to deliver empty (no date, no link, no content) posts, randomly, and planet started to post everything as new as it took the feed. I still haven t reenabled all the plugins, but it runs stable for several hours now and I ll try not to break it again.
A few months ago, a collection of essays called 
When you start using Linux' logical volume manager, one of the first question
you have to answer is: what name will you give to your volume group? The usual
answer is: vg1, vg2, etc. Although it does not bear any specific meaning, this
naming convention is simple and seems functional enough.
In fact, this is a bad idea, which can have nasty consequences on the long
term. Here is why: one day, your computer will eventually give out. To save your
precious data, you will remove its drives and plug them into another computer.
If you are using LVM with the same naming convention on that second computer, you
will then get a name conflict, which will prevent you from seeing the volume
group you want to recover.
The solution is to name volume groups uniquely across all your computers,
and if possible other people's. An elegant way to achieve this is to use your
host names as a basis. For instance, on a machine called Pi acolada , you would
name a single volume group pinacolada , or two volume groups pinacolada1 and
pinacolada2 . Or perhaps vg-pinacolada0 or whatever, you get the idea.
Over the past few days, I decided to purge Gnash and LightSpark from my laptop to see whether my Internet experience would be affected in any dramatic way. Amazingly, a number of sites seem to offer video content encoded in Theora (VP3) or WebM (VP8). Sadly, a handful of popular sites such as Vimeo insist upon using the H.264 (MPEG-4) CODEC, which cannot be safely supported on Free Software because of unclear licensing issues that might impose an ulterior usage fee onto the end-users.