5v3n

Spork.each_run do
  load "#{Rails.root}/config/routes.rb"
  Dir["#{Rails.root}/app/**/*.rb"].each { |f| load f }
end

nruth

# Let's assume you're driving Capybara in both RSpec request specs & Cucumber, 
# for example you're using Cucumber as a design/documentation tool, and RSpec 
# for the more boring integration tests.

# You don't want to duplicate your click-this-click-that helpers to e.g. 
# log_in(username, password). 
# You may also have model state setup code which can be shared/reused.

# Where can it go? How can it be loaded? I've been using the following approach:
#

tmilos

Modified Preorder Tree Traversal

Hierarchical data metrics that allows fast read operations on tree like structures.

Based on Left and Right fields that are set during tree traversal. When entered into node value is set to it's Left, when exiting node value is set to it's Right.

Sample implementation

popravich

The standard names for indexes in PostgreSQL are:

{tablename}_{columnname(s)}_{suffix}

where the suffix is one of the following:

• pkey for a Primary Key constraint;
• key for a Unique constraint;
• excl for an Exclusion constraint;
• idx for any other kind of index;

mlebkowski

#!/bin/bash

# remove exited containers:
docker ps --filter status=dead --filter status=exited -aq | xargs -r docker rm -v
    
# remove unused images:
docker images --no-trunc | grep '<none>' | awk '{ print $3 }' | xargs -r docker rmi

# remove unused volumes:
find '/var/lib/docker/volumes/' -mindepth 1 -maxdepth 1 -type d | grep -vFf <(

CMCDragonkai

Regular Expression Engine Comparison Chart

Many different applications claim to support regular expressions. But what does that even mean?

Well there are lots of different regular expression engines, and they all have different feature sets and different time-space efficiencies.

The information here is just copied from: http://regular-expressions.mobi/refflavors.html

ebautistabar

Recovering deleted files in Ubuntu with ext4 filesystem

Recently, I deleted some files by mistake in a Ubuntu machine with an ext4 fs. These notes document the steps I took to get them back.

Important

• this procedure assumes that the partition that contained the deleted files is different from the root partition, as that was the scenario with which I had to deal (deleted files were in my home dir). The procedure needs that the partition that contained the files is unmounted, so if the deleted files were in the root partition, the process would be a bit different (e.g. storing the fs journal in a USB stick, using a live CD/USB to boot and issue the commands, etc.)
• if something is not clear, you need more information, etc. check the sources below

With that out the way, let's begin.

shadowmaru

• Alda Rocha: Mulheres que falam e palestram
• Alex Braha Stoll: Ruby + Rust
• Anderson Dias: 3B de jobs no Sidekiq
• Andre Luis Anastacio: Effective Rails Instrumentation
• Artur Caliendo Prado: Grafana, StatsD e InfluxDB
• Bruno Alves: Arquitetura de micro serviços
• Camila Campos: Como não escrever seus testes
• Charlotte Lorelei Oliveira: [Tolerância a falhas com supervisor trees em Elixir](https://docs.google.com/presentation/d/e/2PACX-1vT8eAiVAgK5_aHBduO-P2Cb1QbeaX4DyvHAsDbgfKOt0lDVBEl4Qm_KeCx7mNGn7PS16gMgZ-ffLkrO/pub?start=false&loop=fa

Aetherus

How to scale out a Phoenix application with websocket

Foreword

It's relatively easy to scale out stateless web applications. You often only need a reverse proxy. But for those stateful web applications, especially those applications that embeds websocket services in them, it's always a pain to distribute them in a cluster. The traditional way is introducing some external services like Redis to handle pubsub, however, in such way, you often need to change your code. Can Erlang/Elixir, the "concurrency oriented programming languages", best other languages in this use case? Has Phoenix framework already integrated the solution of horizontally scaling websocket? I'll do an experiment to prove (or disprove) that.

Resources

dainiax

#!/bin/bash

BASE_PATH=/var/opt/gitlab/gitlab-rails/shared/registry/docker/registry/v2/repositories

DRY_RUN=0
KEEP_LAST_IMAGES=10
RUN_GARBAGE_COLLECTOR=0
GITLAB_CTL_COMMAND=`which gitlab-ctl`