Not Production Ready: Limitations and suggestion

[skid]

What does the "apachectl configtest" says?

[gtzen]

# apachectl configtest
Syntax OK

[skid]

So everything is ok, it's good.
It looks like the key here is NAT and local network. When you ping domain you get external or local ip? In case you are checking domain from LAN then ip must be local as well. Apache is comparing ip+domain pair with the config and if no matches found it will route request to very first domain. You can check /home/admin/conf/web/httpd.conf to see current configuration.

[alberto]

Vesta is more than suited for production usage. Just check the quality of the entire code. There is only 1 option and is VESTA, if you can find anything better tell us.

[gtzen]

@alberto: I checked the code and made some comments about permissions plus the hurdle I specified above are as it is with vestacp.

Except in terms of user interface, I have never seen as professional in micro-level ACLs as ISPConfig3 in the OSS world. I wish vesta follows the suit. I also mentioned the same to skid. It takes time to mature an application, and vestacp is one among them.

I, for one, shall not deploy vestacp in any production environment. I guess you are aware of how chaotic datacenter environment is.

@skid: the problem of pointing to the first domain remained unresolved no matter what I did in my testing environment.