| <cfscript> | |
| /* 1/4/2016 Identify WebCEO Bot Request (https://www.webceo.com/webceo-bots.htm) | |
| Block unwanted page requests from automated Competitor Metrics & Backlink Spy (They don't provide | |
| a way for sites to opt-out or use WebCEO-specific robots.txt rules.) | |
| */ | |
| function isWebCEO(){ | |
| return YesNoFormat(ListFind("97.107.131.214,69.164.220.17,69.164.220.10,69.164.208.136,69.164.208.68,97.107.135.120,97.107.135.14,69.164.212.131,97.107.133.236,97.107.131.160", CGI.Remote_Addr) OR Findnocase("seo-audit-check-bot", CGI.http_User_Agent) OR Findnocase("online-webceo-bot", CGI.http_User_Agent)); | |
| } | |
| </cfscript> |
| <cffunction name="limiter"> | |
| <!--- | |
| by Charlie Arehart, [email protected], in 2009, updated 2012 | |
| http://www.carehart.org/blog/client/index.cfm/2010/5/21/throttling_by_ip_address | |
| - Throttles requests made more than "count" times within "duration" seconds from single IP. | |
| - sends 503 status code for bots to consider as well as text for humans to read | |
| - also logs to a new "limiter.log" that is created automatically in cf logs directory, tracking when limits are hit, to help fine tune | |
| - note that since it relies on the application scope, you need to place the call to it AFTER a cfapplication tag in application.cfm | |
| - updated 10/16/12: now adds a test around the actual throttling code, so that it applies only to requests that present no cookie, so should only impact spiders, bots, and other automated requests. A "legit" user in a regular browser will be given a cookie by CF after their first visit and so would no longer be throttled. | |
| - I also tweaked the cflog output to be more like a csv-format output |
| # === Optimized my.cnf configuration for MySQL/MariaDB (on cPanel/WHM servers) === | |
| # | |
| # by Fotis Evangelou, developer of Engintron (engintron.com) | |
| # | |
| # ~ Updated September 2024 ~ | |
| # | |
| # | |
| # The settings provided below are a starting point for a 8-16 GB RAM server with 4-8 CPU cores. | |
| # If you have different resources available you should adjust accordingly to save CPU, RAM & disk I/O usage. | |
| # |
My objective is to have some production files ignored on specific branches. Git doesn't allow to do it.
My solution is to make a general .gitignore file and add .gitignore.branch_name files for the branches I want to add specific file exclusion.
I'll use post-checkout hook to copy those .gitignore.branch_name in place of .git/info/exclude each time I go to the branch with git checkout branch_name.
| #!/usr/bin/python | |
| # -*- coding: UTF-8 -*- | |
| import serial, time, struct | |
| ser = serial.Serial() | |
| ser.port = "/dev/cu.wchusbserial1410" # Set this to your serial port | |
| ser.baudrate = 9600 | |
| ser.open() |
| <cfscript> | |
| /* 1/4/2016 Identify WebCEO Bot Request (https://www.webceo.com/webceo-bots.htm) | |
| Block unwanted page requests from automated Competitor Metrics & Backlink Spy (They don't provide | |
| a way for sites to opt-out or use WebCEO-specific robots.txt rules.) | |
| */ | |
| function isWebCEO(){ | |
| return YesNoFormat(ListFind("97.107.131.214,69.164.220.17,69.164.220.10,69.164.208.136,69.164.208.68,97.107.135.120,97.107.135.14,69.164.212.131,97.107.133.236,97.107.131.160", CGI.Remote_Addr) OR Findnocase("seo-audit-check-bot", CGI.http_User_Agent) OR Findnocase("online-webceo-bot", CGI.http_User_Agent)); | |
| } | |
| </cfscript> |
IMPORTANT: Read this before implementing one of the configuration files below (for either Varnish 3.x or 4.x+).
USE: Replace the contents of the main Varnish configuration file located in /etc/varnish/default.vcl (root server access required - obviously) with the contents of the configuration you'll use (depending on your Varnish version) from the 2 examples provided below.
IMPORTANT: The following setup assumes a 180 sec (3 minute) cache time for cacheable content that does not have the correct cache-control HTTP headers. You can safely increase this to 300 sec (or more) for less busier sites or drop it to 60 sec or even 30 sec for high traffic sites. It obviously depends on your use case.
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <!-- Meta conf --> | |
| <meta charset="UTF-8"> | |
| <!-- Meta info --> | |
| <title>HTML5 Microdata Resume (CV) Template</title> | |
| <meta name="description" content="An example of how to layout a semantic html5 page for a curriculum vitae/resume"> | |
| <meta name="keywords" content="template, html, semantic, microdata, resume, cv, curriculum, vitae"> | |
| </head> |
| <!--- | |
| @name: ExifTool.cfc | |
| @originalauthor: Steven Erat | |
| @originaldate: March 2011 | |
| @version: 1.0 | |
| @contact: [email protected], http://www.talkingtree.com/ | |
| @Forked: 9/17/2015 by James Moberg; http://SunStarMedia.com https://about.me/jamesmoberg | |
| http://gamesover2600.tumblr.com/post/129293628174/exiftoolcfc-update | |
| New getInfo() function to get a struct of all meta data. | |
| Added logJSON option to save ExifTool JSON output to same filepath. |
