flexjoly
Verified User
Hi,
Recently we got a new vps with Centos and directadmin. We upgraded to custombuild 2.0 en installed nginx instead of apache.
When looking at directadmin.conf. It still has apache-variables and paths to apache/httpd-configs and not to nginx.
Nginx is working fine, although. The httpd-config manager is also giving nginx files.
The file for apacheconf doesnt exist.
Dir /etc/nginx holds (some of) the config and also has directadmin-xxx.conf files
Should we alter these paths? Or are those handled in a different way?
Greetz,
flexJoly, a Divaeloper
Recently we got a new vps with Centos and directadmin. We upgraded to custombuild 2.0 en installed nginx instead of apache.
When looking at directadmin.conf. It still has apache-variables and paths to apache/httpd-configs and not to nginx.
Nginx is working fine, although. The httpd-config manager is also giving nginx files.
Code:
apache_public_html=0
apache_ver=2.0
apachecert=/etc/httpd/conf/ssl.crt/server.crt
apacheconf=/etc/httpd/conf/extra/directadmin-vhosts.conf
apacheips=/etc/httpd/conf/ips.conf
apachekey=/etc/httpd/conf/ssl.key/server.key
apachelogdir=/var/log/httpd/domains
apachemimetypes=/etc/mime.types
nginx=1
nginx_proxy=0
The file for apacheconf doesnt exist.
Dir /etc/nginx holds (some of) the config and also has directadmin-xxx.conf files
Should we alter these paths? Or are those handled in a different way?
Greetz,
flexJoly, a Divaeloper