fillup

#!/bin/bash

# Make sure there is no zoom .deb around
touch /tmp/zoom_amd64.deb
rm /tmp/zoom_amd64.deb

# Grab the current one
wget -O /tmp/zoom_amd64.deb https://zoom.us/client/latest/zoom_amd64.deb

ISINSTALLED=`dpkg -l | grep "ii  zoom" | wc -l`

fillup

#!/usr/bin/env bash

echo "it works"

fillup

Error applying plan:

1 error(s) occurred:

* module.cluster.module.asg.aws_autoscaling_group.asg: aws_autoscaling_group.asg: diffs didn't match during apply. This is a bug with Terraform and should be reported as a GitHub Issue.

Please include the following information in your report:

    Terraform Version: 0.10.0
    Resource ID: aws_autoscaling_group.asg

fillup

2017/04/20 10:13:24 [INFO] Terraform version: 0.9.3  
2017/04/20 10:13:24 [INFO] Go runtime version: go1.8.1
2017/04/20 10:13:24 [INFO] CLI args: []string{"/usr/local/Cellar/terraform/0.9.3/bin/terraform", "destroy", "-force"}
2017/04/20 10:13:24 [DEBUG] Detected home directory from env var: /Users/shipley
2017/04/20 10:13:24 [DEBUG] Detected home directory from env var: /Users/shipley
2017/04/20 10:13:24 [DEBUG] Attempting to open CLI config file: /Users/shipley/.terraformrc
2017/04/20 10:13:24 [DEBUG] File doesn't exist, but doesn't need to. Ignoring.
2017/04/20 10:13:24 [INFO] CLI command args: []string{"destroy", "-force"}
2017/04/20 10:13:24 [DEBUG] Detected home directory from env var: /Users/shipley
2017/04/20 10:13:24 [DEBUG] command: loading backend config file: /Users/shipley/code/terraform-test

fillup

Below is the series of Terraform commands run and the relevant snippets of output from each:

resource "aws_ecs_service" "service" {
   name = "${var.service_name}"
   cluster = "${var.cluster_id}"
   desired_count = "${var.desired_count}"
   iam_role = "${aws_iam_role.ecsServiceRole.arn}"
   depends_on = ["aws_iam_role_policy.ecsServiceRolePolicy", "aws_alb_listener.https"]

fillup

<?php

use Nexmo\Developer;
use Nexmo\Insight;
use Nexmo\Sms;
use Nexmo\Verify;
use Nexmo\Voice;

/*
 * Get an SMS client object

fillup

<?php
// Updated 2018-01-24 to work with google/apiclient:^2.0
/*
 * Easiest to use composer to install google-api-php-client and generate autoloader
 * If you dont want to use composer you can manually include any needed files
 */
include_once 'vendor/autoload.php';

/*
 * Email address for admin user that should be used to perform API actions

fillup

I recently needed to batch delete all of the files in my filepicker.io account, but there is no way to do that through their UI or APIs, at least that I could find (unless you still have all their IDs in your own database in which this is not necessary). In their Developer Console I can browse the files in the account and delete each one individually, but that would take an extremely long time for hundreds or thousands of files.

My solution is still a bit slow and manual, but much much faster than clicking each one individually. This is a simple javascript snippet that can be run in your browser developer console on the Browse Files page when logged into Filepicker.io

$('.filelink').each(function(index){
   var url = window.location+'/remove/';
   var handle = $(this).attr('data-handle');
   $.post(url,{handle: handle}, function(response){
 console.log(handle);

fillup

#!/bin/bash

sudo apt-get purge $(dpkg -l linux-{image,headers}-"[0-9]*" | awk '/ii/{print $2}' | grep -ve "$(uname -r | sed -r 's/-[a-z]+//')")

fillup

Yii has some great features for simplifying and automating portions of development. Two key areas are...

• Gii generating model classes based on table schemas
• Using the yiic migrate command to manage schema changes

I am proposing two enhancements to these areas. For Gii model generation, I suggest that it create separate Base and extending classes (https://gist.github.com/fillup/5cdba5990c6576bbbfb0). In this Gist I propose that the migration support is enhanced to add a parameter for automatically regenerating the base classes for affected (or all) tables.

My ideal workflow would be:

1. ./yiic migrate create create_table_user // migration for creating a table named 'user'