[Update on 2019-09-19] Warning: From Debian 9 (stretch) upwards, according to the official documentation Cloudflare has dropped support for mod_cloudflare. Instead they recommend replacing it with the new alternative: the official Apache HTTPd module mod_remoteip.
Hi!
If you are using the Cloudflare proxy functionality, you will find that your web server will end up only working with Cloudflare's IPs instead of the visitors'. After quite some time I thought that there has to be a better way to go about this, and I found mod_cloudflare, a solution officially developed by Cloudflare themselves.
When I was looking at the official Cloudflare documentation on how to install mod_cloudflare for Apache 2.4 on Debian 8 (Jessie) today, I was disappointed to find that they were only recommending manual ways: installing a .deb package or compiling the module yourself.
Luckily I found a guide on how to accomplish the installation with the standard apt-get / aptitude tool for Debian / Ubuntu.
This is how:
- Add the aptitude repository to a new sources list file, e.g. at /etc/apt/sources.list.d/cloudflare-main.list - with this content:
deb http://pkg.cloudflare.com/ jessie main
- Download the Cloudflare repository key and add it to the aptitude known keys:
# wget https://pkg.cloudflare.com/pubkey.gpg
# apt-key add pubkey.gpg
# rm pubkey.gpg
- Update the aptitude cache:
# aptitude update
- Look at which packages are available in the new repository:
# grep ^Package: /var/lib/apt/lists/pkg.cloudflare.com_dists_jessie_main_binary-amd64_Packages
- Install mod_cloudflare:
# aptitude install libapache2-mod-cloudflare
- Restart the Apache HTTPd service:
# service apache2 restart
Hopefully this way of installing will enable everyone to update / maintain it much more easily and with less one-time use packages installed.
Additionally, this could prove even more useful for people who want to install more Cloudflare packages.
I am confident that this method also works for Ubuntu and other versions of Debian - just replace the "jessie" part in the aptitude sources list file with your distribution major release codename (like "wheezy" for Debian 7 or "vivid" for Ubuntu 15.04).
Thanks for reading!
Original source: https://emtunc.org/blog/01/2016/installing-mod_cloudflare-ubuntu-14-04-apache-server/
Like this:
Like Loading...
Hi!
After doing a couple of updates on my servers today, I noticed that one of them had syntax highlighting in vim disabled. I double-checked to see that it was still vim that was installed, and not vi. Indeed it was, so I tried entering a couple of vim commands in order to re-enable syntax highlighting.
A couple of minutes of trying and searching the Internet went by till I got the idea to directly compare the vim version info both on one of my servers that had it working properly and the one that didn't. It turned out that even though it was the same version number and build with the same compile time it had a certain difference: one line said "Tiny version without GUI." vs. "Huge version without GUI.". The tiny version was the one that wasn't highlighting correctly.
So I checked out what the package manager thought of this:
# yum list *vim*
[...]
Installed Packages
vim-common.i386 2:7.0.109-7.el5 installed
vim-enhanced.i386 2:7.0.109-7.el5 installed
vim-minimal.i386 2:7.0.109-7.el5 installed
Available Packages
vim-X11.i386 2:7.0.109-7.el5 base
Somehow during updating it had apparently decided to install the vim-minimal package as well. And of course it wasn't installed on the server on which vim worked as it should.
Fair enough. I thought to myself that removing should fix it, but when I tried to it said the following:
# yum remove vim-minimal
Loaded plugins: fastestmirror
Setting up Remove Process
Resolving Dependencies
--> Running transaction check
---> Package vim-minimal.i386 2:7.0.109-7.el5 set to be erased
--> Processing Dependency: vim-minimal for package: sudo
--> Running transaction check
---> Package sudo.i386 0:1.7.2p1-13.el5 set to be erased
--> Finished Dependency Resolution
Dependencies Resolved
============================================================================================================
Package Arch Version Repository Size
============================================================================================================
Removing:
vim-minimal i386 2:7.0.109-7.el5 installed 581 k
Removing for dependencies:
sudo i386 1.7.2p1-13.el5 installed 861 k
Transaction Summary
============================================================================================================
Remove 2 Package(s)
Reinstall 0 Package(s)
Downgrade 0 Package(s)
Is this ok [y/N]:
That was weird. It felt the need to remove sudo along with it. Of course that was not okay for me, so I tried looking for a parameter for vim in order to ignore the dependencies, but apparently there are none (any more).
The solution I found after a couple of more minutes of searching the Internet was to remove the package via the actual rpm program. But don't you need the original rpm file for vim-minimal? No, you don't!
First you have to find out the complete package name, however. That can be done like this:
# rpm -qa | grep vim-minimal
vim-minimal-7.0.109-7.el5.i386
And finally just use the following command:
# rpm -e --nodeps vim-minimal-7.0.109-7.el5.i386
whereas the last parameter is of course the proper name of the package in question. --nodeps, as you might have figured already, stands for "no dependencies" and removes the package without any questions asked.
In the end, these simple steps restored the syntax highlighting functionality for my vim.
Let's hope that after the next update it doesn't decide to go monochrome again.
Thanks for reading!
Like this:
Like Loading...