@Dashrender said in Fedora 30 LAMP Web Server Varnish Cache Broken After Update: @scottalanmiller said in Fedora 30 LAMP Web Server Varnish Cache Broken After Update: @Obsolesce said in Fedora 30 LAMP Web Server Varnish Cache Broken After Update: Wow so they just decide to up and change ports? And I thought Windows updates were bad... They accidentally hard coded to the default. did you report it? Unlikely.

@scottalanmiller said in How critical is SSD on a web server?: @dashrender said in How critical is SSD on a web server?: @scottalanmiller said in How critical is SSD on a web server?: Web servers typically do not benefit from extra space, either. basically web servers don't use storage in any way. But SSDs at least give you faster boot times, swap space, updates, etc. Extra space would give us literally nothing, in our cases. Are your DBs for your WP servers running on the same or different hosts from WP? You want them on the same for performance. There is no advantage to centralization except a tiny bit of consolidation that would come at a cost of performance and reliability to the customers. If they are on a separate box there are more points of failure to worry about, more noisy neighbour risks, and huge latency bumps. That makes sense.

@jaredbusch said in Fedora Update Breaks httpd: So, if you followed the original instructions, you can use this to fix it. sed -i "s/access\.log/httpd\/access_log/" /etc/httpd/conf.d/bookstack.conf Then start apache. systemctl start httpd As always, thanks @JaredBusch that fixed it for me as well.

This way you can share the config(s) under conf.d between multiple machines using the same roles (or whatever Salt calls them) and have different main NGINX server settings.

@aaronstuder said in Installing Varnish Cache to a LAMP Stack on Fedora 25 with SaltStack: @scottalanmiller said in Installing Varnish Cache to a LAMP Stack on Fedora 25 with SaltStack: Varnish Cache cannot handle TLS connections, so Apache will continue to server HTTPS on port 443, for now at least. That's unfortunate I use Varnish on Cloudways, but everything is HTTPS... Does that mean Varnish is doing nothing? It just means that an SSL layer has to be in front of it. Nginx is used on most platforms to handle SSL.

Just as a comparison, here's what it would look like with Ansible: name: Recursively own html files file: path: /var/www/html owner: apache group: apache state: directory recurse: yes

If you're running CentOS you're most likely going to need to change SELinux contexts to match also.

Getting lots of eyes on this thread today. Very interesting.

You can take them as arguments when you first run the script, that is the more "UNIX" way. Or you can prompt for them as you go.

that's just laughable!

Makes sense. Although I am a little worried that the new pool just died all by itself. I wonder why that would happen. Will see if it happens again.

@scottalanmiller said in My Misadventures with Cloud At Cost: I always recommend CloudFlare, it's the best DNS host I have found. I am more of a ClouDNS + BunnyCDN fan

I guess if I setup a script to dump the database to a specific directly on some schedule, I could then ensure I have that directory included in the git commit. This would give me a database version 100% compatible with the point in time git made the commit of the rest of the stuff.

@JaredBusch said: @ajstringham I cannot help sorry, I just turned up 4 websites on my CentOS7 server. all working perfectly. I figured out the issue. I had everything set up correctly. Turns out my NoIP settings were wrong. Once I fixed those (that is what actually fixed it), it all started working! @scottalanmiller helped out tremendously! Thanks all!

@ajstringham said: I'm creating the VMDK now. My only concern is that, all my research suggests Ubuntu is the best distro to run a LAMP server on. I'm also much more familiar with Debian systems over RPM... RHEL has always been the LAMP leader. No upside to Ubuntu for LAMP. That's not where Ubuntu is strong. Ubuntu is better for alternative, non-LAMP, application stacks like RoR and Node.js where RHEL's conservative approach is a major problem. Other than needing the EPEL enabled, RHEL is as straightforward as you really get for LAMP. Ubuntu has only squeaked by as being even a reasonable choice until the latest few releases.

@technobabble said: And found out that it's pronounced Engine X. Lol. Yup.