Tag Archive - programmation

retrieve client browser lang setting with php

July 8, 2009 in , , , , , , with 167 Comments

I promised a client I would give him a little PHP script to help him deal with internationalization (french/english visitors) of his website. So, here is a very simple way to retrieve your visitor’s browser language setting and fork through a IF clause based on this value :

< ?php
#we retreive the language
$lang = substr($_SERVER['HTTP_ACCEPT_LANGUAGE'], 0, 2);


#if french $lang=fr, english $lang=en
if ( $lang==”fr” ) {
echo “ceci est la version francaise”;
}
else {
echo “other language”;
}

?>

This is not meant to be the ‘best’ way or the ‘easiest’, it is simply the way I would do it for a small project. If you got a better way, feel free to post it in the comment section of this post !

RubyGems management

December 12, 2008 in , , , , , , with 25 Comments

RubyGems management

fire0# gem list | wc -l
36

This is not one of those “big” servers with hundred of applications: There are only three of them and those 36 gems are dependencies to keep everything running. I am not even counting their multiple installed versions. This is a normal situation that happen quite often when developing new applications – gems get tested, accepted, refused, modified, re-installed, updated… but rarely uninstalled.

So, how do we manage them ? Here is 3 systems I use:

1. Using your own gem repository.

It is really easier to maintain a ‘clean’ list of gems on your production servers if you only have one source, which is under your direct control. It is also a good incentive to do some QA, before putting new libraries into production. Here is an example deployement of a ‘home’ repository to distribute the tmm1-amqp gem:

fire0# mkdir -p /var/www/gems_repository/gems
fire0# cd !$
fire0# gem fetch tmm1-ampq -s http://gems.github.com
fire0# cd ..
fire0# gem generate_index
fire0# gem server &

Note: If a web server is installed (apache, nginx, …), create a new vhost and you won’t need the “gem server” command, since the repository communicate through standard http protocol. While you can add as many gems you want in /var/ww/gems_repostory/gems, don’t forget to run the “gem generate_index” (in /var/www/gems_repository) to keep your index up to date. You can also fetch specific gems version using the “-v” flag to the fetch command.

On your servers (or localhost if you have only one environment), adding your new gems repository as a permanent sources can be accomplished with this command:

air0# gem sources -a http://your_gems_server:8088

or you can install specific gems by mentioning the correct source :

air0# gem install tmm1-amqp -s http://your_gems_server:8088

2. Using “gem stale”

This is a new command I’ve discovered in the ‘gem help commands’ output. It give the last access date of every installed gems. This info is version specific… hence it shows dependencies on specifics, old version, gems or unused one. Try it:

fire0# gem stale

note: this command was added RubyGems >= 1.2.0, you might need to update to use it.

3. Using “gem outdate”

This command will dump a list of the gems for which you have available update (through your sources).

Quote

December 1, 2008 in , , with Comments Off

I love this quote :

“Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live.”
Source: http://www.littlehart.net/atthekeyboard/