Hi, if you read those lines it means the DNS were updated and you’re looking at this blog hosted on Heroku.
It’s been a long time since I wanted to try Heroku for more than a little Sinatra test app, so I decided to try with this blog. We’ll see how it goes in the next weeks.
I encountered, for some time now, problems when connecting over ssh from my mac to a linux machine.
These problems were related to backspace/delete key in both nano and zsh the solutions I found today are :
For zsh type :
echo "bindkey ^? backward-delete-char" >> ~/.zshrc echo "bindkey ^[[3~ delete-char" >> ~/.zshrc
WARNING : you should type these commands not copy/paste them,
^? sequence is obtained using
ctrl+v then [backspace key].
For nano type :
## Fix Backspace/Delete confusion problem. echo "set rebinddelete" >> ~/.nanorc
All should works now.
I encountered a little problem today, I use macports version of coreutils which gives me access to gnu versions of some commands (for full list : sudo port contents coreutils | grep /bin). My problem is related to one of those I’m using in my bashrc to color my shell : dircolors (gdircolors in macports).
This little commands allows you to generate LS_COLORS values (as the name seems to imply, it’s used by
ls command) from a config file (
~/.dir_colors in my case). I confidently modified this file today and was welcomed by a nice
csh: Unknown colorls variable `su'.
It turns out there are an incompatibility between LS_COLORS generated by current version of dircolors in coreutils and (t)csh : tcsh treat LS_COLORS as a magic environment variable, which means it is parsed for its own use in ls builtin command.
The culprits in my
.dir_colors file was :
#SETUID 37;41 # file that is setuid (u+s) #SETGID 30;43 # file that is setgid (g+s) #STICKY_OTHER_WRITABLE 30;42 # dir that is sticky and other-writable (+t,o+w) #OTHER_WRITABLE 34;42 # dir that is other-writable (o+w) and not sticky #STICKY 37;44 # dir with the sticky bit set (+t) and not other-writable
As you can see a simple fix is to comment them out.
In fact I’m not sure why I see those errors poping up, as I’m using bash ans it’s now the default in MacOSX.
Windows+r (shortcut to ‘Run’ window)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\View Source Editor\Editor Name]
PS : I think this is the first post of a long list.
When I decided to try the switch from fcgid to mod_proxy + mongrel for this blog (and now the majority of my projects at work), I discovered there was no example of such configuration or at least not all in one place.
This post will try to fill this lack of a complete example. The distro i’m using here is Debian, but the configuration should be easily ported to yours.
Thereafter I assume you already have a working configuration with :- Apache 2.0.x - mod_proxy_http (thanks AMicky) - mod_proxy - mod_rewrite
mod_proxy configuration :
There’s not so much to change here, just allow proxying to anyone for local domains.
<Proxy *> Order deny,allow # next line was Deny from all Allow from all </Proxy>
A sample vhost file
This configuration is intended to be used with a RubyOnRails application served by Mongrel and deployed with Capistrano.
So you should notice some nice things, like auto-disabling website with a personalized message when there’s a maintenance.html page found, serving static contents directly by apache (no uneeded hit on mongrel) and conserving access to cgi-bin directory (see my previous post about awstats).
Since my switch to Apache2+mod_proxy+mongrel, I had some troubles figuring how to make urls defined by a ScriptAlias work.
As an example, take Awstats, tipically it’s configuration involve a ScriptAlias directive in you vhost configuration.
Something like :
ScriptAlias /awstats/ /var/www/your_site_dir/cgi-bin/awstats/ <Directory /var/www/your_site_dir/cgi-bin/awstats/> AllowOverride All Options ExecCGI FollowSymLinks Order allow,deny Allow from all </Directory>
But when mod_proxy is enabled, all requests are proxied, ignoring your ScriptAlias directive.
A solution if you also use mod_rewrite is to write something like this :
RewriteRule "^/awstats/.*" "$0" [PT,L]
The magic switch is PT which enable rewrite rules to be shared between differents mods.
In my quest to find the best rails configuration, I decided to try a new alternative to Apache+FastCGI/Apache+FCGID/Lighttpd+FastCGI.
Everyone seems to be focused on Mongrel combined with Apache 2.2 + mod_proxy_balancer. It looks good but Apache 2.2 isn’t actually in Debian (not even in unstable), and as I choose to switch this blog from a Fedora Core 2 (ooch !) server to another server of mine powered by Debian, it really doesn’t fits my needs.
So I choosed to try a different approach and use Apache 2.0.x + mod_proxy + Mongrel. This solution, gives me the possibility to use mongrel_cluster for process management, even if actually I don’t have multiple mongrel instances, and add a load balancer (Pen/Balance/Pound) if needed.
This setup seems to be sufficient for this blog, which runs the latest Typo (3.99.3).
Let me know if you see any differences with the previous configuration.
Bienvenue, j’ai enfin installé quelquechose sur ce nom de domaine qui trainait depuis trop longtemps.
Pour la partie techno du site :
- Typo v2.6 pour le moteur de blog avec le magnifique thème Origami de Leevi Graham
- Base de donnée PostgreSQL en version 8.1
Welcome, I finally installed something on this too long sleeping domain.
Technically speaking, this site run on :
- Typo v2.6 blog engine with the beautiful Origami theme from Leevi Graham
- PostgreSQL version 8.1 database
(The english part of this site will help me improve my english skills, which really need it. So feel free to correct me about erroneous sentences and terms)