Given a main
branch used in a trunk-based development strategy, here is how semantic release can fit in:
%%{init: {
'logLevel': 'debug',
'theme': 'default' ,
'themeVariables': {
'git0': '#777',
Thanks to the original blog post: https://equimper.com/blog/how-to-setup-tailwindcss-in-phoenix-1.4
cd assets
npm i --save-dev tailwindcss postcss-loader postcss-import
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm
---------- Usage | |
The syntax created by these parameters is placed in an alert's description on TradingView | |
to be utilized by Autoview, a Chrome Extension. | |
Autoview: https://chrome.google.com/webstore/detail/autoview/okdhadoplaoehmeldlpakhpekjcpljmb | |
> Website: https://autoview.with.pink | |
> Help: https://use.autoview.with.pink | |
> Discord: https://discordapp.com/invite/BFz8VPn | |
TradingView: https://tradingview.go2cloud.org/aff_c?offer_id=2&aff_id=1187 |
require 'thread' | |
# A synchronization barrier enables multiple threads to wait until all threads | |
# have all reached a particular point of execution before any thread | |
# continues. | |
class Barrier | |
# Initialize new barrier. The _count_ argument specifies the number of threads | |
# that must call #wait before any of them successfully return from the call. | |
# The value specified by _count_ must be greater than zero. |
$ export BYEBYE=ruby | |
$ ps x | grep $BYEBYE | cut -d' ' -f1 | xargs kill -9 |
#!/usr/bin/ruby | |
# Create display override file to force Mac OS X to use RGB mode for Display | |
# see http://embdev.net/topic/284710 | |
require 'base64' | |
data=`ioreg -l -d0 -w 0 -r -c AppleDisplay` | |
edids=data.scan(/IODisplayEDID.*?<([a-z0-9]+)>/i).flatten | |
vendorids=data.scan(/DisplayVendorID.*?([0-9]+)/i).flatten |
#!/usr/bin/env ruby | |
# gem 'pivotal-tracker' | |
require 'pivotal-tracker' | |
TRACKER_TOKEN = "..." | |
TRACKER_PROJECT_ID = "..." | |
PivotalTracker::Client.token = TRACKER_TOKEN | |
PivotalTracker::Client.use_ssl = true |
This readme is a mixture of everything I read on SO+nokogiri wiki, which ultimately worked out for me.
Here are the steps which worked for me to get rid of segfaults with Nokogiri 1.4.4, on both Lion and Snow Leopard, with Ruby 1.8.7 (patchlevel 334 and +).
First diagnose which version of libxml2 you're using:
bundle exec nokogiri -v
If you have 2.7.3 listed somewhere, you're in bad waters (known to segfault). Install this: