carlosedp

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      app: nginx

pmuir

# This is a CRD that defines a shared config. Would be stored in environment repo in gitops mode.
allRepos: &allRepos
  branch-protection:
    protect: true
  owners_dir_blacklist:
    default: null
    repos: null
  prowjob_namespace: jx
  pod_namespace: jx
  push_gateway: {}

vfarcic

pipeline {
    agent {
        label "prod"
    }
    parameters {
        string(
                name: "service",
                defaultValue: "",
                description: "The name of the service that should be scaled"
        )

ipedrazas

kubectl get pods | grep Evicted | awk '{print $1}' | xargs kubectl delete pod

comigor

From aeb068a26dbedafea956c9abf5ebd41dc2ee79f1 Mon Sep 17 00:00:00 2001
From: Igor Borges <[email protected]>
Date: Thu, 9 Jul 2015 03:14:02 -0300
Subject: [PATCH] Crosswalk patch

---
 packages/autoupdate/package.js        | 2 +-
 packages/coffeescript/package.js      | 2 +-
 packages/crosswalk/package.js         | 9 +++++++++
 packages/ddp/package.js               | 2 +-

jamielob

How to get facebook login working with Meteor and Cordova on iOS

Step 1: Make your local dev site internet accessible

Because there is an issue with OAuth2 login and localhost development, you currently have to deploy your meteor site to be able to test the Facebook login. A nice little workaround for this is to make the local instance of meteor accessible externally.

There is a great online guide for setting up port forwarding with your router and you can check your public external IP here.

For example, If you have an Apple router, simply open up Airport Utility on your Mac and click edit on your router, then go to the Network tab. Under Port Settings click the + icon and select Personal Web Sharing, setting all of the public and private ports to 3000. Make sure the private IP is set to your current computer IP.

mattborn

.module-cache

alsheuski

<!-- Meta-теги для Facebook: -->
<meta property="og:title" content=""/>
<meta property="og:description" content=""/> 
<meta property="og:image" content=""/>
<meta property="og:site_name" content=""/> 
<meta property="og:url" content=""/>

<!-- Meta-теги для Twitter: -->
<meta name="twitter:card" content="summary"/> 
<meta name="twitter:title" content=""/>

molotovbliss

If any exceptions are encountered due to 3rd party/local observers debugging can be questionable as no log 
is created to determine root cause.  This mini doc covers how to use the XML-RPC API in Magento to test a 
product update API call that is returning a 500 internal server error due to an observer firing in 3rd party 
code.  Using some simple XML docs prepared for login and the request it is easier to see the Fatal error 
returned for a request, in this example product.update.

xmlrpclogin.xml contents:
 
<?xml version="1.0"?>
<methodCall>

mitchwongho

# Assuming an Ubuntu Docker image
$ docker run -it <image> /bin/bash