We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Not Production Ready: Limitations and suggestion
Re: Not Production Ready: Limitations and suggestion
What does the "apachectl configtest" says?
Re: Not Production Ready: Limitations and suggestion
# apachectl configtest
Syntax OK
Re: Not Production Ready: Limitations and suggestion
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.
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.
Re: Not Production Ready: Limitations and suggestion
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.
Re: Not Production Ready: Limitations and suggestion
@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.
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.