| #!/usr/bin/env ruby | |
| require_relative '../../spec/support/simple_cov_helper.rb' | |
| SimpleCovHelper.report_coverage('integration') | |
| load "#{Gem::Specification.find_by_name('knapsack_pro').gem_dir}/lib/tasks/queue/rspec.rake" | |
| Rake::Task['knapsack_pro:queue:rspec'].invoke('--format doc --format RSpec::Instafail --tag ~skip --format RspecJunitFormatter --out tmp/test_results/spec/integration.xml') |
ClamAV can be used in a few different ways. Most importantly, it provides the ability to scan files in realtime (on-access) or to scan the file system periodically.
I tried configuring ClamAV to both perform on-access virus scanning and to perform nightly full filesystem scanning. Using the on-access option did not prove to be very useful, however a scheduled full system scan seems to be of value.
Here is my story.
| Basics of Unix philosophy: | |
| - Use simple algorithms as well as simple data structures | |
| - Data structures, not algorithms are central to programming - organise it well | |
| - Fancy algorithms are buggier than simple ones | |
| Rules: | |
| Modularity - build out simple parts connected by well defined interfaces. Be able to update/upgrade the part without breaking the whole. |
The following outlines how to setup Heroku + Cloudflare with a full SSL certificate. What this means is that communication between the browser and the Cloudflare CDN is encrypted as well as communication between Cloudflare and Heroku’s origin server. Follow these steps exactly and the setup is a breeze.
First you want to add the root domain and the www domain to heroku. You do this by clicking into your production application, then going to settings and then scrolling down to Domains and certificates.
Here you will add <your_domain>.com and www.<your_domain>.com. This will give you two CNAME records. They will look something like <your_domain>.com.herokudns.com and www.<your_domain>.com.herokudns.com.
| #!/bin/sh | |
| ############################################################################### | |
| # Setup # | |
| ############################################################################### | |
| # Use global hooks directory for each existing and new repository: | |
| # $ git config --global core.hooksPath '~/.git-hooks' | |
| # $ mkdir ~/.git-hooks | |
| # $ chmod a+x ~/.git-hooks/prepare-commit-msg |
UPDATE 2021: I wrote this long before I wrote my book Functional Programming Made Easier: A Step-by-step Guide. For a much more in depth discussion on Monads see Chapter 18.
Initially, Monads are the biggest, scariest thing about Functional Programming and especially Haskell. I've used monads for quite some time now, but I didn't have a very good model for what they really are. I read Philip Wadler's paper Monads for functional programming and I still didnt quite see the pattern.
It wasn't until I read the blog post You Could Have Invented Monads! (And Maybe You Already Have.) that I started to see things more clearly.
This is a distillation of those works and most likely an oversimplification in an attempt to make things easier to understand. Nuance can come later. What we need when first le
| # frozen_string_literal: true | |
| require 'httparty' | |
| REQUESTED_BUILDS = ARGV[0].to_i || 10 | |
| SPEC_FILES = {} | |
| def get(url, options = {}) | |
| headers = { | |
| 'cache-control': 'no-cache', |
| After automatically updating Postgres to 10.0 via Homebrew, the pg_ctl start command didn't work. | |
| The error was "The data directory was initialized by PostgreSQL version 9.6, which is not compatible with this version 10.0." | |
| Database files have to be updated before starting the server, here are the steps that had to be followed: | |
| # need to have both 9.6.x and latest 10.0 installed, and keep 10.0 as default | |
| brew unlink postgresql | |
| brew install [email protected] | |
| brew unlink [email protected] | |
| brew link postgresql |