| -- TerminalVim.app | |
| -- This creates a shim Application that will enable you to open files from the Finder in vim using iTerm | |
| -- To use this script: | |
| -- 1. Open Automator and create a new Application | |
| -- 2. Add the "Run Applescript" action | |
| -- 3. Paste this script into the Run Applescript section | |
| -- 4. Save the application as TerminalVim.app in your Applications folder | |
| -- 5. In the Finder, right click on a file and select "Open With". In that window you can set TerminalVim as a default |
| The question was asked why I (as a programmer who prefers dynamic languages) don't consider static types "worth it". Here | |
| is a short list of what I would need from a type system for it to be truely useful to me: | |
| 1) Full type inference. I would really prefer to be able to write: | |
| (defn concat-names [person] | |
| (assoc person :full-name (str (:first-name person) | |
| (:second-name person)))) | |
| And have the compiler know that whatever type required and produced from this function was acceptible as long as the |
The sendmail package, which comes preinstalled with many distros, is often simply too much for a simple server that should not receive emails but rather deliver them. The sSMTP package is a lightweight replacement that does not set up regular cronjobs and only reacts if a subsystem actually wants to send a mail.
apt-get purge --yes sendmail*
| #!/bin/bash | |
| ############################################################################################## | |
| ## Install Nginx with OpenSSL, and ngx_pagespeed | |
| ## | |
| ## Author: Andrew Maxwell <[email protected]> | |
| ## Date: 2017/09/18 | |
| ## Version: 0.3 | |
| ## | |
| ## Disclaimer: I am not responsible for how you use this script. Do not assume this script |
| #!/usr/bin/env bash | |
| #copy this in a folder from path ex: /usr/local/bin | |
| #usage: docker-machine-rename default my-default | |
| # Authors | |
| # | |
| # alexproca initial script | |
| # eurythmia sed magic |
Disclaimer: I'm not the original author of this sheet, but can't recall where I found it. If you know the author, please let me know so I give the attribution.
The original author seems to be Charles Edge, here's the original content, as pointed out by @percisely.
Note: Since this seems to be helpful to some people, I formatted it to improve readability of the original. Also, note that this is from 2016, many things may have changed, and I don't use macOS anymore, so I probably can't help in case of questions, but maybe someone else can.
After writing up the presentation for MacSysAdmin in Sweden, I decided to go ahead and throw these into a quick cheat sheet for anyone who’d like to have them all in one place. Good luck out there, and s
This guide is only representative from my point of view and it may not be accurate and you should go on the official AWS & GCP websites for accurate and detailed information. It's initially inspired by AWS in simple English and GCP for AWS professionals. The idea is to compare both services, give simple one-line explanation and examples with other software that might have similiar capabilities. Comment below for suggestions.
| Category | Service | AWS | GCP | Description | It's like |
|---|---|---|---|---|---|
| Compute | IaaS | Amazon Elastic Compute Cloud (EC2) | Google Compute Engine | Type-1 virtual servers | VMware ESXi, Citrix XenServer |
| PaaS | AWS Elastic Beanstalk | Google App Engine | Running your app on a platform |
The easiest way to get the ClamAV package is using Homebrew
$ brew install clamav
Before trying to start the clamd process, you'll need a copy of the ClamAV databases.
Create a freshclam.conf file and configure as so