lyninx

Keeping Secrets: Lessons Learned From Securing GitHub

Speakers

Dennis Pacewicz - @lyninx (GitHub)
LinkedIn

Wei Lin Ngo - @Creastery (Praetorian)
LinkedIn

Presentation Slides

liamwh

<script lang="ts">
    import type { UserView } from '$lib/stubs/auth';
    import { getContext, onMount } from 'svelte';
    import { goto } from '$app/navigation';
    import { getContacts } from '$lib/repositories/contacts';
    import { browser } from '$app/environment';
    import { CONTACTS_STORE_KEY, USER_STORE_KEY } from '$lib/store-keys';
    import type { Writable } from 'svelte/store';
    import AddContactButton from '$lib/components/Contacts/AddContact/AddContactButton.svelte';
    import { db } from '$lib/surrealdb';

eric-hemasystems

module HashDelegate

  # Like `delegate :foo, to: :bar` only for hashes instead
  # of objects. So these are the same:
  #
  #   def foo
  #     bar[:foo]
  #   end
  #
  #   hash_delegate :foo, to: :bar

sastan

<script context="module">
  import { get, readable } from 'svelte/store'

  import { createClient, operationStore } from '@urql/svelte'

  import { browser, dev } from '$app/env'

  /**
   * @type {import('@sveltejs/kit').Load}
   */

GuilleLeopold

task :generate_engine do
  # Get name sent from console
  name = ENV['name'].downcase

  # Store useful paths
  engine_path         = "engines/#{name}"
  dummy_path          = 'spec/dummy'
  lib_files_path      = 'lib/tasks/files'
  dummy_relative_path = "#{engine_path}/#{dummy_path}"

ntamvl

How to create a Ruby gem that adds Rake tasks

Create a gem

One way to do this is to use bundler to scaffold our gem:

bundler gem my_gem

Add rake tasks to our gem

I prefer to put tasks meant to manage the gem itself in lib/tasks, and tasks the gem is meant to provide to gem users in lib/my_gem/tasks.

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"

schovi

Sidekiq.configure_server do |config|
  ENV["SIDEKIQ_NAMESPACE"]   && config.options[:namespace] = ENV["SIDEKIQ_NAMESPACE"]
  ENV["SIDEKIQ_CONCURRENCY"] && config.options[:concurrency] = ENV["SIDEKIQ_CONCURRENCY"].to_i
  ENV["SIDEKIQ_VERBOSE"]     && config.options[:verbose] = ENV["SIDEKIQ_VERBOSE"] === 'true'
  ENV["SIDEKIQ_LOGFILE"]     && config.options[:logfile] = ENV["SIDEKIQ_LOGFILE"]
  ENV["SIDEKIQ_PIDFILE"]     && config.options[:pidfile] = ENV["SIDEKIQ_PIDFILE"]

  config.options[:strict] = true

  if ENV["SIDEKIQ_QUEUES"]

marcotc

jagrosh

Step 1 - Make a Discord Webhook

1. Find the Discord channel in which you would like to send commits and other updates

2. In the settings for that channel, find the Webhooks option and create a new webhook. Note: Do NOT give this URL out to the public. Anyone or service can post messages to this channel, without even needing to be in the server. Keep it safe!

Step 2 - Set up the webhook on Github

1. Navigate to your repository on Github, and open the Settings