25.8.15

Wordpress: Convert .htaccess to web.config file

Everywhere you will find step-by-step guides to migrate from Linux hosting to Windows hosting (or viceversa), but something very useful to know is how to convert .htaccess file to web.config file.

Wordpress has some default rules that writes on Apache .htaccess file.
Something like this below

 # BEGIN WordPress  
 <IfModule mod_rewrite.c>  
 RewriteEngine On  
 RewriteBase /  
 RewriteRule ^index\.php$ - [L]  
 RewriteCond %{REQUEST_FILENAME} !-f  
 RewriteCond %{REQUEST_FILENAME} !-d  
 RewriteRule . /index.php [L]  
 </IfModule>  
 # END WordPress  

The web.config equivalent to this is

 <?xml version="1.0" encoding="UTF-8"?>  
 <configuration>  
   <system.webServer>  
           <rewrite>  
                 <rules>  
                      <rule name="Main Rule" stopProcessing="true">  
                           <match url=".*" />  
                           <conditions logicalGrouping="MatchAll">  
                                <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />  
                                <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />  
                           </conditions>  
                           <action type="Rewrite" url="index.php/{R:0}" />  
                      </rule>  
                 </rules>  
                </rewrite>  
   </system.webServer>  
 </configuration>  

In this manner you can avoid all 404 errors caused by rewrite absence.

14.4.15

Installation pgAgent on CentOs

I faced the task to install pgAgent on PostgreSql 9.3 CentOs 6 server.
I serached a lot but I didn't find anything on web very complete.
So why don't write it by myself?
The most explanatory guide I found was this on OrbitPhreak blog

Due to the fact that updating CentOs Epel Repository I met this error

 Loaded plugins: fastestmirror, security  
 Determining fastest mirrors  
 Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again  

I found this useful link to solve also this problem

So let's install this fucking pgAgent.
To install pgAgent we also have to install many packages (wxWidgets) related to graphic libraries used by pgAgent itself.
This is maybe due to the fact that pgAgent was originally a part of the pgAdmin client.
Tha last package of pgAgent in the time I'm writing is 3.4.0, but you find the last package here.
Type in sequence this commands on your CentOs server

 yum install wxGTK.x86_64 wxGTK-devel.x86_64 cmake  
 yum install gcc  
 yum install gcc-c++  
 yum install postgresql-devel  
 yum install wget  
 wget http://ftp.postgresql.org/pub/pgadmin3/release/pgagent/pgAgent-3.4.0-Source.tar.gz  
 tar -zxvf pgAgent-3.4.0-Source.tar.gz  
 wget http://sourceforge.net/projects/wxwindows/files/2.8.12/wxWidgets-2.8.12.tar.gz  
 tar -zxvf wxWidgets-2.8.12.tar.gz  
 cd wxWidgets*  
 ./configure --with-gtk --enable-gtk2 --enable-unicode  
 make  
 su -c "make install; /sbin/ldconfig"
cd contrib
make
su -c "make install"  

Now we can install pgAgent.

 cd pgAgent*  
 cmake -D PG_CONFIG_PATH:FILEPATH=/usr/pgsql-9.3/bin/pg_config -D STATIC_BUILD:BOOL=OFF .  
 make  
 su -c "make install"  
 cp sql/pgagent.sql /var/lib/pgsql/9.3  
 su postgres  
 psql -U postgres -d postgres -f pgagent.sql  
 exit  
 echo '/usr/pgsql-9.3/lib' >> /etc/ld.so.conf.d/postgres.conf

Ok, now we have installed all, we can create a service called pgagent useful for starting, stopping pgagent whenever we want.

 vim /etc/rc.d/init.d/pgagent  

and we can copy all this text inside the text editor

 #!/bin/bash  
 #  
 # /etc/rc.d/init.d/pgagent  
 #  
 # Manages the pgagent daemon  
 #  
 # chkconfig: - 65 35  
 # description: PgAgent PostgreSQL Job Service  
 # processname: pgagent  
 . /etc/init.d/functions  
 RETVAL=0  
 prog="PgAgent"  
 start() {  
   echo -n $"Starting $prog: "  
   daemon "/usr/local/bin/pgagent hostaddr=127.0.0.1 dbname=postgres user=postgres password=??????"  
   RETVAL=$?  
   echo  
 }  
 stop() {  
   echo -n $"Stopping $prog: "  
   killproc /usr/local/bin/pgagent  
   RETVAL=$?  
   echo  
 }  
 case "$1" in  
  start)  
   start  
   ;;  
  stop)  
   stop  
   ;;  
  reload|restart)  
   stop  
   start  
   RETVAL=$?  
   ;;  
  status)  
   status /usr/local/bin/pgagent  
   RETVAL=$?  
   ;;  
  *)  
   echo $"Usage: $0 {start|stop|restart|reload|status}"  
   exit 1  
 esac  
 exit $RETVAL  

Then we set grants on file service and put it starting at boot time.

 chmod 0755 /etc/rc.d/init.d/pgagent  
  /sbin/chkconfig --level 345 pgagent on  
 service pgagent start  

To make pgAgent usable from Postgres we should modify pg_hba.conf in this way

 vim /var/lib/pgsql/9.3/data/pg_hba.conf  

and make the "host" row like this

 host  all       all       127.0.0.1/32      trust  

In this manner the postgres user can trust himself in any way: both with password or woithout it.
For example running this command it should work

 SELECT dblink_connect('user=postgres password=ocpNHosting14 host=127.0.0.1 dbname=postgres');  

Just insert the host definition equal to 127.0.0.1.

That's all!

Now you can create new jobs following this useful guide.

Enjoy!