brew uninstall --ignore-dependencies node icu4c
brew install node
1) Login to Cloud Key | |
2) Cloud Key ssh: `curl https://get.acme.sh | sh` | |
3) Cloud Key ssh: `acme.sh --upgrade --auto-upgrade --accountemail "myemail@example.com"` | |
4) Cloud Key ssh: Add `cloudkey-renew-hook.sh` file to `/root/.acme.sh` | |
5) Create free CloudFlare account (if not already member) | |
6) Login to CloudFlare | |
7) On CloudFlare: Create a zone for a domain you own (can add a cheap domain with namecheap.com or any number of alternatives) | |
8) On CloudFlare: Create an A record for your Cloud Key; ie: unifi.CHANGE.ME, 192.168.1.10 | |
9) On UniFi Controller: Go to Settings; Click "Controller"; Change "Controller Hostname/IP" to the name entered in step 8. | |
10) On CloudFlare: go to Overview for your zone; click "Get your API key" |
There is not a MacOS-native executable of Enterprise Architect on Mac. In order to run it, it is possible to use Wine, a software to run windows applications on Linux and Mac. Sparx has a webinar and a documentation page explaining how to install EA into Linux using Wine. However, these instructions do not provide a step-by-step guide for MacOS
The following are instructions to install EA on MacOs using Homebrew.
- install homebrew
package main | |
import ( | |
"context" | |
"log" | |
"net/http" | |
"os" | |
"os/signal" | |
"time" | |
) |
Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)
First one found from of
So, you love Slack, but you hate applications with large white backgrounds? Why not use Dark Mode!
Unfortunately, Slack does not have a Dark Mode, although it's on their list of possibilities.
But, don't fret - there is a solution! Because the slack native desktop apps are just wrappers around a web app, we can inject our own CSS to customize the application to our liking.
Based on my recent experience of deployment, I've become rather frustrated with the deployment tooling in Elixir. This document is the result of me thinking to myself, "I wish we had x...". This document isn't meant to dishearten anyone who has built tooling for elixir - thank you so much for what you've done. This is meant more as what I personally see as something that would help a lot of Erlang/Elixir newbies like myself to be able to get deploying quickly and efficiently.
It should be possible to add in custom configuration to the bootstrap scripts. This would allow plugins to be able to add extra steps to the startup / shutdown / upgrade procedure. One way to implement this would be to make all scripts which handle bootstrapping or controlling the machine [.eex][1] templates. This would allow other parts of the release system to inject new functionality where needed.
/* | |
Watch out, os.IsExist(err) != !os.IsNotExist(err) | |
They are error checkers, so use them only when err != nil, and you want to handle | |
specific errors in a different way! | |
Their main purpose is to wrap around OS error messages for you, so you don't have to test | |
for Windows/Unix/Mobile/other OS error messages for "file exists/directory exists" and | |
"file does not exist/directory does not exist" |
defmodule TestDefp do | |
defmacro __using__(_) do | |
quote do | |
import Kernel, except: [defp: 2] | |
end | |
end | |
# Let's redefine `defp/2` so that if MIX_ENV is `test`, the function will be | |
# defined with `def/2` instead of `defp/2`. | |
defmacro defp(fun, body) do |