RISCfuture

Adding TypeScript to a Rails + Webpacker + Vue project

These instructions assume you already have a Rails 5.2 project using Webpacker 4 with Vue 2 and Vuex 3. I'll show you how to add TypeScript to the project, and type-safe your Vue components, including single-file components (SFCs). This document will not teach you TypeScript syntax or type theory. It also assumes your code already works without TypeScript. You shouldn't use this article to, for example, get started with Vuex, because I'm leaving out lots of necessary boilerplate code and focusing just on TypeScript changes.

If you want to see a commit on a project accomplishing this migration, visit https://github.com/RISCfuture/AvFacts/commit/666a02e58b4626a074a03812ccdd193a3891a954.

Setup

1. Run rails webpacker:install:typescript. This should modify config/webpacker.yml and config/webpack/environment.js (leave those changes), add tsconfig.json and config/webpack/loaders/typescript.js (leave those files), and add some other files in `a

jflasher

Amazon S3 now supports a new storage class called Intelligent Tiering. This will be a very attractive option for many customers who have datasets that are accessed in unpredictable patterns. You can set this storage class when uploading any new data. However, the below instructions will allow you to set up a lifecycle policy that will change the storage class of data that already exists in your bucket.

To set up a lifecycle policy to change the storage class of the data currently stored in your Amazon S3 bucket, follow the below steps.

1. Visit the S3 console and go to your bucket of interest.

2. Click on the Management tab at the top and select + Add lifecycle rule.

3. Enter a rule name of your choice (e.g., Convert to Intelligent Tiering storage class). Unless you want to filter which data is converted to the new storage class, you can leave the prefix/tag filter field

drbh

// helper to find Brave in User Agent string
function isBraveAgent(userAgentResponse) {
	var isBraveIndex = ~userAgentResponse.indexOf('Brave')
	if (isBraveIndex < 0) {
		return true
	}
	return false
}

// Function from Javarome

sillasgonzaga

library(httr)
library(magrittr)
library(xml2)
library(rvest)

url_raw <- "http://dados.cvm.gov.br/dados/FI/DOC/INF_DIARIO/DADOS/"
output_file <- "fundos/api/informe_diario.csv"

csv_links <- httr::GET(url_raw) %>% 
  httr::content("text") %>% 

koffeinfrei

2.5.0

Chocksy

# FOR BUSY JOBS
# take the process_id from the /busy page in sidekiq and kill the longest running one.
workers = Sidekiq::Workers.new
long_process_id = 'integration.3:4:71111aaa111' # Eg: 'integration.3:4:71d1d7f4ef5a'
workers.each do |process_id, thread_id, work|
  process = Sidekiq::Process.new('identity' => process_id)
  process.stop! if process_id == long_process_id
end

# FOR SCHEDULED JOBS

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

dansteele

namespace :staging do
  desc 'create subdomain DNS record for Heroku review app'
  task :publish_dns do
    require 'dnsimple'
    require 'platform-api'

    STAGING_DOMAIN      = 'mystagingdomain.com'.freeze
    DNSIMPLE_ACCOUNT_ID = .freeze
    heroku_app_name    = ENV['HEROKU_APP_NAME']
    subdomain          = heroku_app_name.match(/.*(pr-\d+)/).captures.first

giannisp

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

clupprich

begin
  require "bundler/inline"
rescue LoadError => e
  $stderr.puts "Bundler version 1.10 or later is required. Please update your Bundler"
  raise e
end

gemfile(true) do
  source "https://rubygems.org"