cyberswat

Join Zoom Meeting
https://ddev.zoom.us/j/915394122

One tap mobile
+16699006833,,915394122# US (San Jose)
+16468769923,,915394122# US (New York)

Dial by your location
        +1 669 900 6833 US (San Jose)
        +1 646 876 9923 US (New York)

cyberswat

12:03:18	 From Kevin Bridges : https://gist.github.com/cyberswat/9b1b5f42e9f1b2d6bbfac4c64206b304
12:06:32	 From Jeff Geerling : Hello!
12:08:35	 From Jan Wozniak : Hi Jeff
12:11:24	 From Kevin Bridges : https://www.drupal.org/project/issues/search?issue_tags=kubernetes
12:11:38	 From Jeff Geerling : Haha I had that copied into my clipboard
12:12:03	 From Jeff Geerling : solve it once and for all instead of 20 times individually++
12:16:08	 From Jeff Geerling : lol
12:19:29	 From Kevin Bridges : https://portworx.com/
12:39:06	 From Djun Kim : Any thoughts re: Gitlab instead of GitHub? It might be interesting to have Gitlab pipelines to deploy to various cloud providers...
12:40:24	 From Jeff Geerling : depending on if we want to deploy anything, this would just be more of a central repo to aggregate data

cyberswat

Drupal Kuberentes SIG: 1st meeting agenda
Agenda outline:

What this group is about:
 - This group is focused on finding ways for engineers that support Drupal to 
 collaborate on a common set of operators. You can read more about operators at 
 https://coreos.com/operators/ and see examples at https://operatorhub.io/.  
 Several organizations in the Drupal space are working in this area and are not 
 collaborating on the pieces that we can share.  Our goals include transparency, 
 avoiding vendor lockin, and helping the community solve issues around running 

cyberswat

Contributor License Agreement

The following terms and conditions apply to Your Contributions submitted to Drud Technology LLC ("Drud").

1. Definitions.

"You" or "Your" shall mean the copyright owner or legal entity authorized by the copyright owner that is making this Agreement with Drud. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single contributor, where "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "Contribution" shall mean any original work of authorship, including any modifications or additions to an existing work, that is submitted by You to Drud for inclusion in, or documentation of, any of the products owned or managed by Drud (the "Project"

cyberswat

This is my first agreement. This now different.

cyberswat

###SAP Individual Contributor License Agreement - VERSION 2

Thank you for your interest in contributing to open source software projects (“Projects”) made available by SAP SE or its affiliates (“SAP”). This Individual Contributor License Agreement (“Agreement”) sets out the terms governing any source code, object code, bug fixes, configuration changes, tools, specifications, documentation, data, materials, feedback, information or other works of authorship that you submit or have submitted, in any form and in any manner, to SAP in respect of any of the Projects (collectively “Contributions”). If you have any questions respecting this Agreement, please contact [email protected].


You agree that the following terms apply to all of your past, present and future Contributions. Except for the licenses granted in this Agreement, you retain all of your right, title and interest in and to your Contributions.


**Copyright License.** You hereby grant, and agree to grant, to SAP a non-exclusive, perpetual, irrevocab

cyberswat

#!/bin/bash -ex
function package {
    dir=${PWD##*/}
    for filename in "`pwd`/*"
    do
        echo $filename
    if [ "$dir" == "windows" ]
    then
        zip ddev_"$dir".zip `basename $filename`
        shasum -a 256 ddev_"$dir".zip > ddev_"$dir".sha256

cyberswat

In my dynamic ec2 inventory I have data similar to:

{
  "_meta": {
    "hostvars": {
      "10.0.33.123": {
        "ec2_tag_Name": "MyFirstHost",
      }
      "10.0.33.124": {

"ec2_tag_Name": "MySecondHost",

cyberswat

I'm gradually getting serious about switching to Docker to deploy lemp webapps. I've chased the topic of best practices around the web for a while and landed on information like http://phusion.github.io/baseimage-docker/ docker/compose#928 and https://groups.google.com/forum/#!topic/docker-user/gk-oSwgxyo4

I basically maintain "two" roughly mirrored environments: one webdevs are working against in vagrant and one in the cloud (qa, staging, prod). The webdev's typically work on 2-5 sites at a time depending on the SLA and new client volume. I began using fig and am about to migrate to docker-compose. If I store everything in a client specific fig file, it tends to rapidly consume the memory of the vm. This makes it complicated for the webdev to switch between client webapps. I've seen this more readily when dealing with the database containers.

In my mind, the answer to the memory problem is to have one db container that can run databases for multiple clients. Are there other

cyberswat

use_inline_resources if defined?(use_inline_resources)

def whyrun_supported?
  true
end

action :create do
  template new_resource.name do
    group new_resource.group
    mode new_resource.mode