{"id":42929,"date":"2024-06-03T11:40:01","date_gmt":"2024-06-03T11:40:01","guid":{"rendered":"https:\/\/accuweb.cloud\/resource\/?post_type=faq&p=42929"},"modified":"2026-02-18T13:57:08","modified_gmt":"2026-02-18T13:57:08","slug":"adding-custom-apache-modules","status":"publish","type":"faq","link":"https:\/\/accuweb.cloud\/resource\/articles\/adding-custom-apache-modules","title":{"rendered":"Adding Custom Apache Modules"},"content":{"rendered":"

Adding Custom Apache Modules<\/h2>\n

To fulfill the specific needs of your application, you may find it necessary to add custom Apache modules<\/strong>. Some of these modules may not be included in the default list of Apache modules installed on the platform. You can enable your own Apache modules within your environment by following these instructions:<\/p>\n

Let’s walk through setting up your environment:<\/p>\n

Step 1.<\/strong> Sign<\/strong> in to your AccuWeb.Cloud<\/a> PaaS account.<\/p>\n

Step 2.<\/strong> Look for the “Create environment”<\/strong> option in the top left corner of the dashboard and click on it.<\/p>\n

Step 3.<\/strong> In the wizard that appears, go to the PHP<\/strong> tab. Choose the Apache application server and specify the resources your application needs. Don’t forget to give your environment a name, like “apache modules,”<\/strong> then hit the “Create”<\/strong> button.<\/p>\n

\"Create<\/a><\/p>\n

Step 4.<\/strong> Your environment will appear on the platform dashboard within a few minutes.<\/p>\n

\"Created<\/a><\/p>\n

To build your Apache module, follow these steps:<\/p>\n

Step 1.<\/strong> Download<\/a> Apache httpd from apxs, ensuring it matches the version of your existing Apache server. For example, if you have Apache 2.4.59, download and install httpd 2.4.59.<\/a><\/p>\n

Step 2.<\/strong> Obtain the source code for the required module from the Apache modules list. As an example, let’s use the mod_pony Apache module.<\/strong><\/p>\n

Step 3.<\/strong> Compile your Apache module.<\/p>\n

Below is an example of how to compile the mod_pony<\/strong> module:<\/p>\n

<\/div>\n
\r\napxs -i -a -c mod_pony.c\r\n\/usr\/lib64\/apr-1\/build\/libtool --silent --mode=compile gcc -prefer-pic -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wformat-security -fno-strict-aliasing -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -pthread -I\/usr\/include\/httpd -I\/usr\/include\/apr-1 -I\/usr\/include\/apr-1 -c -o mod_pony.lo mod_pony.c && touch mod_pony.slo\r\n\/usr\/lib64\/apr-1\/build\/libtool --silent --mode=link gcc -o mod_pony.la -rpath \/usr\/lib64\/httpd\/modules -module -avoid-version mod_pony.lo\r\n\/usr\/lib64\/httpd\/build\/instdso.sh SH_LIBTOOL='\/usr\/lib64\/apr-1\/build\/libtool' mod_pony.la \/usr\/lib64\/httpd\/modules\r\n\/usr\/lib64\/apr-1\/build\/libtool --mode=install cp mod_pony.la \/usr\/lib64\/httpd\/modules\/\r\nlibtool: install: cp .libs\/mod_pony.so \/usr\/lib64\/httpd\/modules\/mod_pony.so\r\nlibtool: install: cp .libs\/mod_pony.lai \/usr\/lib64\/httpd\/modules\/mod_pony.la\r\nlibtool: install: cp .libs\/mod_pony.a \/usr\/lib64\/httpd\/modules\/mod_pony.a\r\nlibtool: install: chmod 644 \/usr\/lib64\/httpd\/modules\/mod_pony.a\r\nlibtool: install: ranlib \/usr\/lib64\/httpd\/modules\/mod_pony.a\r\nlibtool: finish: PATH=\"\/usr\/local\/sbin:\/bin:\/sbin:\/usr\/bin:\/usr\/sbin:\/sbin\" ldconfig -n \/usr\/lib64\/httpd\/modules\r\n----------------------------------------------------------------------\r\nLibraries have been installed in:\r\n\/usr\/lib64\/httpd\/modules\r\nIf you ever happen to want to link against installed libraries\r\nin a given directory, LIBDIR, you must either use libtool, and\r\nSpecify the full pathname of the library, or use the -LLIBDIR flag during linking, and do at least one of the following:\r\n- add LIBDIR to the `LD_LIBRARY_PATH' environment variable\r\nduring execution\r\n- Add LIBDIR to the `LD_RUN_PATH` environment variable to include the directory in the library search path during runtime.\r\n- use the `-Wl,-rpath -Wl,LIBDIR' linker flag\r\n- have your system administrator add LIBDIR to `\/etc\/ld.so.conf'\r\nRefer to your operating system's documentation for more details on shared libraries, including the ld(1) and ld.so(8) manual pages.\r\n----------------------------------------------------------------------\r\nchmod 755 \/usr\/lib64\/httpd\/modules\/mod_pony.so\r\n[activating module `pony' in \/etc\/httpd\/conf\/httpd.conf]<\/code><\/pre>\n
<\/div>\n
Step 4.<\/strong> After compiling, you will get a .so file of your Apache module. For instance, you will have a<\/p>\n
<\/div>\n
mod_pony.so file located at \/usr\/lib64\/httpd\/modules\/mod_pony.so.<\/div>\n
<\/div>\n
Upload and Configure Your Module<\/h2>\n
Step 1.<\/strong> Navigate to your environment and click on the Config<\/strong> button for your Apache server.<\/p>\n
\"Config\"<\/a><\/p>\n
Step 2.<\/strong> Upload the mod_pony.so<\/strong> file to the \/usr\/lib64\/php\/<\/strong>modules folder.<\/p>\n
Step 3.<\/strong> Navigate to the \/etc\/httpd\/conf<\/strong> folder and edit the httpd.conf<\/strong> file. Add the LoadModule directive in the following format:<\/p>\n
<\/div>\n
\r\nLoadModule {module-name}_module \/usr\/lib64\/php\/modules\/{file-name}.so<\/code><\/pre>\n
<\/div>\n
Example<\/h3>\n
<\/div>\n
\r\nLoadModule pony_module \/usr\/lib64\/php\/modules\/mod_pony.so<\/code><\/pre>\n
<\/div>\n
Save<\/strong> the changes.<\/p>\n
Step 4.<\/strong> Adjust the settings required for your Apache module.<\/p>\n
For example, to further configure the mod_pony<\/strong> module:<\/p>\n