Slydder

Hey all, I just got around to writing a createOwnVhost function for apache and was wondering if anyone would be interested in it. This basically just solved a few issues I had with letsencrypt certs for the froxlor node itsself and automated updates as well as being able to quickly switch from mod_php to phpfpm or fcgid if needed. It currently only supports apache, will see if I can get a few minutes to port it to nginx and lighttpd. Am also sure that I have missed something but it works for me atm. just let me know if anything needs adjustment. froxhost_ownvhost.patch

Chrisv, If you want, we can speak on the matter. I have been running a 6 tier HA LB cluster stack hosting magento installs for about 3 years now with froxlor. There are a few things I have found out over the years regarding this issue and they may come of use to you. Chuck

Hey, RFC 6781 "suggests" a minimum of 5 - 10 minute TTL for standard zone entries. Dynamic DNS was NOT conceptualized when that RFC was released. However, 1 second is a bit much. better would be 1 - 5 minutes. Irrespective of what the RFC states the TTL that is set in his script and the cronjob executing is in no way related other than the fact that the less frequent the cron run the longer the wait for the update. Nothing about the stock Froxlor DNS service is HA. It is an exercise left up to the implementing admin to actually install his/her slave servers and setup the transfers. If they have done this then all is good. if not then they have much larger problems that has nothing at all to do with this script. The IPv6 problem is a problem though. Chuck

correct (3 frox installs here in production with local mysql servers). however, this database CAN be on a remote server or cluster (such as by 12 of the frox servers we have in production atm).

actually webserver, mysql-client and php are correctly required dependancies (otherwise froxlor is completely useless on the server) and smtp is pretty much a requirement of the server whether frox is installed or not. courier/dove/whatnot is a recommendation and not a dep. awstats/webalizer could be argued but for this sake let's just say they are viable deps. mysql-server is the ONLY dep that is NOT 100% needed locally on the server. but like I said. other than that bit, the package is great. keep up the good work.

actually I do like it very much except for the fact that per default you are forced to install a mysql server. mysql server shouldn't be a "local" requirement and there for not a dependancy. The documentation could simply be changed from apt-get install froxlor to apt-get install froxlor mysql-server has the same effect and makes the package usable for everyone. but hey. your project and it's just an idea. take it or leave it. I can build my own packages to keep from having to use a tarball in production systems.

basically because the situation is the same now as for 3 years.

The major problem I have with the debian package is the mysql dependency. I run a galara cluster and do NOT want a local server installed. up till now I build my own frox packages after modifying the rules to get rid of the mysql server dependancy.

Hey all, I just recently started hosting a HA (High Availability or Highly Available) based Froxlor install based on CoroSync, LSyncd, Csync2, Froxlor, Debian, NFS, and a few more tidbits. If anyone is interested I would be more than happy to explain how. If not then for those wondering if it is at all possible: YES! chuck