最近在大卫的指点下开始摸Java了。但我其实更擅长的是PHP，所以现在就开始混用了，那混用的最佳搭配是resin（其实apache+resin插件也OK）。不过纯resin的话也就意味着可以直接混用java的数据了。而不是采用接口调用的方式。

在mac下安装resin是有点麻烦的，官方的教程就几句话，参考 ：http://www.caucho.com/resin-4.0/admin/starting-resin-install.xtp，

然后官方的文档就提示你，configure一下就OK了。不过解开压缩包发现，configure没有可执行权限，只能先chmod +x ./configure。

我第一次是按照官方的例子来的，即：

但后面在运行的时候，一会提示log文件写不了，一会提示app目录不能创建，虽然chown改了权限 后就OK了，但总是有点小问题。去网上找了一下，发现了：http://www.cnblogs.com/jmtbai/p/4394424.html，它在内容里就有说：

果然我把prefix改成我的路径就OK了。（上面的-prefix是不对的，是--prefix）。

顺利的将项目运行了起来，同时写了个test.php，居然也OK了。（现在是知其然不知其所以然，先用起来再说了）

由于需要上传一个文件到服务器，所以才发现ftp服务居然没有启动。

到线上进行检查：

咦，启动失败，这个_none_是什么意思？难道就是那个hostname没有设定的原因？

于是：hostname neatstudio.com ，然后重新退出ssh并登录，再启动ftp就OK了。

上文中的root@(none)，我也不知道这个hostname是被哪个程序给清除了。不过也确实才知道，原来hostname不设置还会导致proftpd无法启动！汗

在使用第三方的程序时，特别是国外的项目，总是会碰到引用googleapis的问题，比如字体之类的，对于国外用户来说这玩意真方便，google也会帮你做CDN，多好啊，但在国内，你遇到的卡顿就不是一点两点了，有时候甚至会拖慢得页面打不开

所以，Wordpress、drupal 之类的程序在拿到手的第一时间就应该将里面的地址换掉，当然Wordpress还有插件，但drupal就不一定有了！

那怎么办？偷懒的办法是用PHP程序，递归查找并替换，如果是在本地，找个工具替换一下即可，现在的IDE都有这功能，如果已经部署到线上，那么只要你有ssh，你就可以尝试：sed -i s/googleapis/useso/g `grep -rl googleapis ./` ，该命令是将当前目录下含有googleapis的文件列出来，然后用sed进行全文替换。

如果做国外站的用户，我想他们一定是很痛苦的，如果用googleapis的数据吧，国内打开就卡死，用国内的cdn吧，国外又卡。当然 有解决方案~~

 本来不想转，但真心是有用，以前的方法也有点过时，而且主要是不方便，所以就来贴个更全的。这种问题非常容易 遇到，用ubuntu、debian在阿里云上，原来都正常的，你只要一apt-get update一下，原来的LC环境就全没了。

原文地址在：http://perlgeek.de/en/article/set-up-a-clean-utf8-environment ， 我上一次写关于这个的问题是在2012年了，那篇的标题是：perl: warning: Setting locale failed. 也可以看一下

How to set up a clean UTF-8 environment in Linux

Many people have problems with handling non-ASCII characters in their programs, or even getting their IRC client or text editor to display them correctly.

To efficiently work with text data, your environment has to be set up properly - it is so much easier to debug a problem which has encoding issues if you can trust your terminal to correctly display correct UTF-8.

I will show you how to set up such a clean environment on Debian Lenny, but most things work independently of the distribution, and parts of it even work on other Unix-flavored operating systems like MacOS X.

Choosing an encoding

In the end the used character encoding doesn't matter much, as long as it's a Unicode encoding, i.e. one which can be used to encode all Unicode characters.

UTF-8 is usually a good choice because it efficiently encodes ASCII data too, and the character data I typically deal with still has a high percentage of ASCII chars. It is also used in many places, and thus one can often avoid conversions.

Whatever you do, chose one encoding and stick to it, for your whole system. On Linux that means text files, file names, locales and all text based applications (mutt, slrn, vim, irssi, ...).

For the rest of this article I assume UTF-8, but it should work very similarly for other character encodings.

Locales: installing

Check that you have the locales package installed. On Debian you can do that with.

$ dpkg -l locales Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name           Version        Description +++-==============-==============-============================================ ii  locales        2.7-18         GNU C Library: National Language (locale) da

The last line is the important one: if it starts with ii, the package is installed, and everything is fine. If not, install it. As root, type

$ aptitude install locales

If you get a dialog asking for details, read on to the next section.

Locales: generation

make sure that on your system an UTF-8 locale is generated. As root, type

$ dpkg-reconfigure locales

You'll see a long list of locales, and you can navigate that list with the up/down arrow keys. Pressing the space bar toggles the locale under the cursor. Make sure to select at least one UTF-8 locale, for example en_US-UTF-8 is usually supported very well. (The first part of the locale name stands for the language, the second for the country or dialect, and the third for the character encoding).

In the next step you have the option to make one of the previously selected locales the default. Picking a default UTF-8 locale as default is usually a good idea, though it might change how some programs work, and thus shouldn't be done servers hosting sensitive applications.

Locales: configuration

If you chose a default locale in the previous step, log out completely and then log in again. In any case you can configure your per-user environment with environment variables.

The following variables can effect programs: LANG, LANGUAGE, LC_CTYPE, LC_NUMERIC, LC_TIME, LC_COLLATE, LC_MONETARY, LC_MESSAGES, LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT, LC_IDENTIFICATION.

Most of the time it works to set all of these to the same value. Instead of setting all LC_ variables separately, you can set theLC_ALL. If you use bash as your shell, you can put these lines in your ~/.bashrc and ~/.profile files:

export LC_ALL=en_US.UTF-8 export LANG=en_US.UTF-8 export LANGUAGE=en_US.UTF-8

To make these changes active in the current shell, source the .bashrc:

$ source ~/.bashrc

All newly started interactive bash processes will respect these settings.

A Warning about Non-Interactive Processes

There are certain processes that don't get those environment variables, typically because they are started by some sort of daemon in the background.

Those include processes started from cron, at, init scripts, or indirectly spawned from init scripts, like through a web server.

You might need to take additional steps to ensure that those programs get the proper environment variables.

Locales: check

Run the locale program. The output should be similar to this:

LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=en_US.UTF-8

If not you've made a mistake in one of the previous steps, and need to recheck what you did.

Setting up the terminal emulator

Setting up the terminal emulator for your terminal emulator strongly depends on what you actually use. If you use xterm, you can start it as xterm -en utf-8, konsole and the Gnome Terminal can be configured in their respective configuration menus.

Testing the terminal emulator

To test if you terminal emulator works, copy and paste this line in your shell:

perl -Mcharnames=:full -CS -wle 'print "\N{EURO SIGN}"'

This should print a Euro sign € on the console. If it prints a single question mark instead, your fonts might not contain it. Try installing additional fonts. If multiple different (nonsensical) characters are shown, the wrong character encoding is configured. Keep trying :-).

SSH

If you use SSH to log in into another machine, repeat the previous steps, making sure that the locale is set correctly, and that you can view a non-ASCII character like the Euro sign.

Screen

The screen program can work with UTF-8 if you tell it to.

The easiest (and sometimes the only) way is to start it with the -U option:

$ screen -U

and also when detaching (screen -Urd or so).

Inside a running screen you can try Ctrl+a :utf8 on<return>. If that doesn't work, exit your screen and start a new one with -U

Irssi

There's a complete guide for setting up irssi to use UTF-8, which partially overlaps with this one. The gist is:

/set term_charset utf-8 /set recode_autodetect_utf8 ON /set recode_fallback ISO-8859-15 /set recode ON