ngocphamm

1. Install Zsh with Homebrew
	brew install zsh

2. Add "/usr/local/bin/zsh" to "/etc/shells" file
	sudo vim /etc/shells

3. Change to default login shell
	chsh -s /usr/local/bin/zsh $USER

4. Make sure new version of Zsh is in active

krisf

#!/bin/bash
#encrypt files with aes-256-cbc cipher using openssl
#install: 
# sudo wget -O /usr/bin/enc https://gist.github.com/krisf/5391210/raw/4a105a6b8f98f39e9e74a1dd2a78ef6f631acdb1/enc
# sudo chmod +x /usr/bin/enc
# enc --help

#encrypt files
if [ $1 == "-e" ];
then

randallreedjr

Working with git remotes on Heroku

Generally, you will add a git remote for your Heroku app during the Heroku app creation process, i.e. heroku create. However, if you are working on an existing app and want to add git remotes to enable manual deploys, the following commands may be useful.

Adding a new remote

Add a remote for your Staging app and deploy

Note that on Heroku, you must always use master as the destination branch on the remote. If you want to deploy a different branch, you can use the syntax local_branch:destination_branch seen below (in this example, we push the local staging branch to the master branch on heroku.

$ git remote add staging https://git.heroku.com/staging-app.git

jswny

Prelude

I. Preface and Motivation

This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.

For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai

azoom-t-d-tuan

Overview

Cloud Build

Cloud Build is a product of GCP (Google Cloud Platform) used to build software quickly across all languages.

Function:

• Speed up Build with VMs on Cloud without wasting personal computer’s resources.
• Source code put on Local, Github, Cloud Source Repositories or Bitbucket all can use Cloud Build.
• Package your source into Docker containers or non-container artifacts with build tools such as Maven, Gradle, webpack, Go, or Bazel.
• After completing Build, the result is updated on Docker Hub or Container Registry.
• You can be flexible to adjust the stream of Build process according to your intention.

kinoute

FROM ruby:2.7.1-slim AS base

LABEL maintainer="Yann Defretin <[email protected]"

# Common dependencies
RUN apt-get update -qq \
  && DEBIAN_FRONTEND=noninteractive apt-get install -yq \
    --no-install-recommends \
    build-essential=12.6 \
    gnupg2=2.2.12-1+deb10u1 \

katyhuff

• Read the PR description
• Read through all the changes, considering the following questions.
  • Is there anything you can praise about this PR? Start with praise.
  • Are variable names brief but descriptive?
  • Are new/changed functions no longer than a paragraph?
  • Do all function parameters have default values where appropriate?
  • Is the code clear and clean? (see Robert C. Martin's Clean Code)
  • Is there enough documentation?
• Does the programming style meet the requirements of the repository (PEP8 for python, google for c++, etc.)

jaketf

#!/bin/bash

###############################################################################################################
#                                                   UPDATE:                                                   #
# This has been merged to a more complete example:                                                            #
# https://github.com/jaketf/ci-cd-for-data-processing-workflow/blob/master/helpers/run_relevant_cloudbuilds.sh#
###############################################################################################################

kurahaupo

Terminal Colors

There exists common confusion about terminal colors. This is what we have right now:

• Plain ASCII
• ANSI escape codes: 16 color codes with bold/italic and background
• 256 color palette: 216 colors + 16 ANSI + 24 gray (colors are 24-bit)
• 24-bit true color: "888" colors (aka 16 million)

yahonda

Ruby 3.1 on Rails

Actions required to use Ruby 3.1.0 with Rails

Rails 7.0.Z

• Rails 7.0.1 is compatible with Ruby 3.1.0.
• Rails 7.0.1 addes net-smtp, net-imap and net-pop gems as Action Mailbox and Action Mailer dependency, you do not need to add them explicitly in your application Gemfile anymore.
• thor 1.2.1 has been released. You will not see DidYouMean::SPELL_CHECKERS.merge deprecate warnings anymore.

Rails 6.1.Z

• Use Rails 6.1.5 to support database.yml with aliases and secrets.yml with aliases.