justinclayton

#!/bin/bash -eo pipefail

## Allows for creation of "Basic" DNS records in a Route53 hosted zone

function main() {
	record_name=$1
	record_value=$2

	[[ -z $record_name  ]] && echo "record_name is: $record_name" && exit 1
	[[ -z $record_value ]] && echo "record_value is: $record_value" && exit 1

cornernote

Using Giiant with Providers

The following code should be added to the bootstrap of your yii application. If you would like to keep it in it's own file (recommended) create a config/giiant.php, then include it from your config/bootstrap.php.

DateTimeProvider

Use a DateTimePicker for the scheduled_at field:

shovon

#!/bin/sh

# size of swapfile in megabytes
swapsize=8000

# does the swap file already exist?
grep -q "swapfile" /etc/fstab

# if not then create it
if [ $? -ne 0 ]; then

mikehaertl

Docker Development Workflow

These ideas are WORK IN PROGRESS!

Summary

The core idea with this workflow is that we end up with a self contained docker image of your application. This image will not only contain our code, but also all the dependencies that are neccessary to run the code. This image can then be used for both, easy deployment in production and as basis for ongoing development.

The image is not a static, though. In fact, it will see many revisions over time - which is supported nicely through dockers inheritance approach. We basically

jashkenas

Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.

For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.

But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.

SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil

pocotan001

• 🎨 when improving the format/structure of the code
• 🚀 when improving performance
• ✏️ when writing docs
• 💡 new idea
• 🚧 work in progress
• ➕ when adding feature
• ➖ when removing feature
• 🔈 when adding logging
• 🔇 when reducing logging
• 🐛 when fixing a bug

sheerun

# Generates necessary certificates to ~/.docker
#
# Usage:
#   bundle install
#   ruby certgen.rb <domain>

require 'certificate_authority'
require 'fileutils'

if ARGV.empty?

kevin-smets

Default

Powerlevel10k

gist:8565929

There are a lot of complaints going around about Laravel these days, but a lot
of the important ones seem to be missing from the spotlight.

Bugfixes, issues and pull requests being left open for months with no
clarification of intent:

- https://github.com/laravel/framework/pull/1799
- https://github.com/laravel/framework/issues/1963
- https://github.com/laravel/framework/issues/2089
- https://github.com/laravel/framework/issues/2234

motin

<?php

namespace neam\envbootstrap;

class Identity
{

    static public function brand()
    {