Omega Cloud VPS

I had hosted xapian-omega on a Virtual Private server. It has indexed 100 years of archives of Prabuddha Bharata and Vedanta Kesari. To keep the server secure I run it behind a proxy. The server allows communication only over 443, all other ports are blocked. I use certificate generated by LetsEncrypt.

July 02 2019 Update: I have moved from VPS to shared CGI hosting to cut costs and easy maintenance. The new site (was) at

July 08 2019 Update: I have co-located this on my hostingraja account. And the URL is

October 23 2019 Update: Upgraded to Xapian 1.4.13

January 07 2020 Update: Upgraded to Xapian 1.4.14

March 26 2020 Update: Upgraded to Xapian 1.4.15

January 24 2023 Update: Upgraded to Xapian 1.4.21

When moving from VPS to shared hosting I needed to rebuild the CGI binary so that the dependent library is available on the path. This is because new systems enforce a security mechanism using rpath. This means any binary can pick up the library from a specified path only which implies that on systems where you may not place a dependent library on a specified path due to permissions restrictions you need to rebuild the binary with a rpath that you have access to.

/bin/sh ./libtool --tag=CXX --mode=link g++ -Wall -W -Wredundant-decls -Wpointer-arith -Wcast-qual -Wcast-align -Wformat-security -fno-gnu-keywords -Wundef -Woverloaded-virtual -Wstrict-null-sentinel -Wshadow -Wstrict-overflow=1 -Wlogical-op -Wmissing-declarations -Wdouble-promotion -Winit-self -Wl,-rpath,'$ORIGIN' -Wduplicated-cond -Wduplicated-branches -I/usr/local/include -g -O2 -o index.cgi omega.o query.o cgiparam.o utils.o configfile.o date.o cdb_init.o cdb_find.o cdb_hash.o cdb_unpack.o jsonescape.o loadfile.o datevalue.o common/str.o sample.o sort.o urlencode.o weight.o expand.o csvescape.o timegm.o -L/usr/local/lib -lxapian

I have been building my binary on a CentOS 7.6 setup. This is because my web host is RHEL, so I shouldn't be building on a debian based distribution like Ubuntu.