I wonder why Apache still offers and promotes version 5.6 of XAMPP when they got newer versions like 7.1.4?
As you can see herethere are different PhP Versions in each Version but is legacy the only reason someone would use an older xampp version or are any other aspects that I am missing?
Because XAMPP v5.6 offers PHP v5.6; XAMPP v7.1.4 comes with PHP v7.0.18 not all developers have their environments past that version of PHP---and for legacy purposes too (for older PHP apps that have yet to migrate to the latest and greatest PHP version)
Hope this helps!
Best,
-Rush
Related
I've inherited an application server which I need to maintain/upgrade.
It's currently running Windows Server 2008R2, ColdFusion 9.02 32-bit and Apache 2.4 32-bit.
Because I want to upgrade/debug/alter the CF source code, I want to use FusionReactor to help me, especially the (line)debugging part.
Unfortunately, FusionReactor only runs (well, the debugging part) on 64bit java. Because the CF application is quite old, it's not ready to run on a newer CF version yet (and I want to port it to Lucee eventually). So, that leaves me the option of CF 9.02 64bit. Problem there is, that it won't run out of the box on Apache 2.4 (only 2.2).
CF 9.02 32bit is currently running on Apache 2.4 because I compiled/patched an Apache 2.2 module (mod_jrun22.so) so it works on Apache 2.4 (with the help of this https://g0blin.co.uk/mod_jrun-on-apache-2-4-ubuntu-14-04-coldfusion-9/ )
Unfortunately, I'm unable to do the same for Apache 2.4 64bit, because there seems to be no apxs 64bit available.
I could downgrade Apache 2.4 -> 2.2, but that's only my last resort.
Now my question. Is somebody able to recompile this module for 64bit, or give me some guidelines to do so? Is apxs available for 64bit? If not, Is there a simple way to compile (custom) modules for Apache 2.4 64bit?
Thanks!
http://www.gpickin.com/index.cfm/blog/multi-cfml-engine-install-extracting-the-coldfusion-9-connector-for-apache
Run it by ./apache_connectors.sh
If you get a GCC not found error, you might have to install some development tools,
to allow you to build the connector.
yum groupinstall 'Development Tools'
You might reach out to Gavin, the author of that article to see if he has any further notes. It's been forever and a day since I had to deal w/ 32-bit CF. I know I managed to get CF 8 to run on 64-bit, which was never officially supported IIRC, but I don't have any of those notes anymore.
You might look to using CommandBox to run your server instead of Apache. It might make your conversion to Lucee easier too. The only reason to convert the engine depends on how much new code is being written for this application. You can get away with CF 9 without the effort of upgrading or converting.
Currently, we are planning to upgrade our complete web-server node in production.
Platform is RHEL 7.1 and currently apache 2.4.6 is running there.
I also got to know from red-hat that apache 2.4.6 is directly shipped with RHEL7 and for 2.4.26 or 2.4.29, they can't comment regarding it's technical feasibility part along with it's stability on RHEL platform.
I have few concerns now :
Is going ahead with apache 2.4.26 or 2.4.29 in production would be a good option or should i get stuck with the current one ? I am doubtful whether 2.4.26 or 2.4.29 are been tested on RHEL 7 series and is technically compatible.
I tried to install apache 2.4.26 and 2.4.29 on my test-bed first ( which is a RHEL 7.4 platform ) and i came across package dependency issues which proved out to be a blocker for me. I am afraid that i might face these issues on production as well which would be very dangerous. Have you ever faced this on your system too ?
Looking out for your kind support and feedback here ... !!!
Best Regards,
looking at : httpd direct rpm download
it seems that the last supported version is httpd-2.4.6-80.el7.x86_64.rpm
so do not try update your production environment with unsupported software, stick to releases !
upgrading to RHEL7.4 seems to be trouble-maker (as far as i heard : [source required !] )
i got no feedback about RHEL7.5
when installing Zabbix v3.4 I get the following error message: http://imgur.com/a/xo3tg
Looks like an error in the yum repository. Do you have any suggestions for solutions or something similar?
Best regards
As you can see, there is just 2.2 version of Zabbix (agent, server, proxy, etc.) in that repository.
It seems Zabbix 2.2 (LTS) is the latest version supported by OpenSUSE using its repositories.
By the way, you can install older versions of Zabbix-agent (like 2.2) sending data correctly to newer server/proxy versions (like 3.0 or even 3.2).
I think the major item you will miss with using zabbix-agent older than 3.X is encryption. Other major features work very good.
I use Centos 6.5, I've installed apache 2.2 on my server by yum, I want to upgrade my apache to 2.4, but yum not support that, so I download apache 2.4.7 and install it to opt/apache/httpd-2.4.7 follow the tutorial here: Apache 2.4.x Manual install on RHEL 6.4 - No apache modules will load on start . I want to change environment variables to new apache version to write apache 2.4 modules (change include folder for header file, change "modules" folder when build with apxs,...). I think I must install another httpd-devel for apache 2.4.7, because I still not install httpd-devel-2.4.7, but I don't know how to install and use it instead of httpd-devel-2.2 by yum. I can not describe my problems clearly in English, so I hope you can understand it. I'm a newbie and I really need your help. Thank you!
CentOS is image of RHEL, which stands for Red Hat Enterprise Linux. RHEL is designed to be an "Enterprise class" operating system, in which you rely on software packages that are delivered from controlled repositories where they are made available only after being thoroughly tested for Enterprise level use.
From that point of view, its generally not a good idea to install packages from source code, or using third party RPMs, because once you do, your OS is no longer "Enterprise" class.
If you're trying to upgrade for security reasons, you shouldn't. Critical security updates are always backported in previous RPM releases, so you only have to update your current package from the same yum repo from where you got it first. The binary will still say it is Apache 2.2, but it will have the latest security updates.
If you need an actual feature of 2.4, the smart move is to upgrade your CentOS. It may seem like the harder option initially, but it never is in the long run.
In my experience these reports can be fairly basic/binary:
Are you running the latest version of the software? If no flag as security risk.
However this fails to take into account package managers which back port fixes to older versions and so often have addressed potential security issues.
By moving away from the packaged version you are making security updates more difficult (as can't do a simple "yum update" to address them anymore).
Apache 2.2 is still maintained for security and bug fixes - though how long for remains to be seen and it is falling further and further behind in features.
So often you just need to explain (and prove!) you have a regular patching process and so the "version of Apache" you are reporting is not really accurate in terms of security patching.
See here for more details: https://serverfault.com/questions/731657/pci-compliance-apache-versions/
Saying all that we moved to Apache 2.4 on centos a while back for some extra features we wanted and just upgrade it to the latest version as part of regular patching cycle and are not finding it too inconvenient. Yes it's not quite as simple as "yum update" but it's a decision we've made because of some features we required. Not a decision to be taken lightly as Garreth states but it had the added side effect of this not getting highlighted anymore in these sorts of security scans :-)
We made this decision despite upgrading to a newer version of Red Hat as that was still on an older version of Apache (2.4.7 if memory serves me correctly) which still missed a few features we required. Sometimes it's frustrating how far behind some of these "enterprise" versions are, but that's the downside when there are plenty of upsides to using them too (stability, security... etc.).
I've been given an assignment to confiure apache v2.1 (on any platform) as a reverse proxy.
Installing Apache2 on Ubuntu gave me version 2.2, but I can't find reference to a version 2.1 for download anywhere. I've seen references to v2.1 in the documentation but under 2.2.
Is it possible to get v2.1?
Apache 2.1 was the development version for Apache 2.2. So Apache 2.1 and 2.2 are essentially the same.
AFAIK, odd number releases are development version, and even numbered are production versions (So 2.3 is the current "development", and will become 2.4 is due time).
Why anyone would ask you to specifically install this version, I do not know, but unless you have a very good reason to do otherwise, just install the latest version.