create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "[email protected]"
create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "[email protected]"
_.templateSettings = { | |
evaluate: /{{+([\s\S]+?)}}/g, | |
interpolate: /{{([\s\S]+?)}}/g, | |
escape: /{{-([\s\S]+?)}}/g | |
}; |
;SMBDIS.ASM - A COMPREHENSIVE SUPER MARIO BROS. DISASSEMBLY | |
;by doppelganger ([email protected]) | |
;This file is provided for your own use as-is. It will require the character rom data | |
;and an iNES file header to get it to work. | |
;There are so many people I have to thank for this, that taking all the credit for | |
;myself would be an unforgivable act of arrogance. Without their help this would | |
;probably not be possible. So I thank all the peeps in the nesdev scene whose insight into | |
;the 6502 and the NES helped me learn how it works (you guys know who you are, there's no |
var fs = require("fs") | |
var ssl_options = { | |
key: fs.readFileSync('privatekey.pem'), | |
cert: fs.readFileSync('certificate.pem') | |
}; | |
var port = process.env.PORT || 3000; | |
var express = require('express'); | |
var ejs = require('ejs'); | |
var passport = require('passport') |
{ | |
"parser": "babel-eslint", | |
"plugins": [ | |
"react", | |
"react-native" | |
], | |
"parserOptions": { | |
"ecmaFeatures": { | |
"jsx": true, | |
"modules": true |
// | |
// MetricsIntegrationTest.swift | |
// AeroGearSdkExampleTests | |
@testable import AGSCore | |
import Foundation | |
import XCTest | |
HTTP Rest API receive 'push request', this gets processed in PushNotificationSenderEndpoint.send()
, which eventually calls an async EJB (NotificationRouter.submit()
) which performs a grouping/mapping and fires a CDI event per Variant.
This Event is received in the MessageHolderWithVariantsProducer.queueMessageVariantForProcessing()
method, which basically sticks the submitted event into a transactional JMS send, based on the variant type a different queue is selected (mainly to keep things separated). The JMS listener MessageHolderWithVariantsConsumer.onMessage()
reads from these queues, and fires a different CDI event, which kicks in the TokenLoader
.
The TokenLoader generally iterates over all variants (for a given type, see the grouping/mapping done in NotificationRouter
), and starts to query tokens from the database, as a steam.
The tokens are in different batches, with different default sizes per Push_Network, to not overflow the push network (e.g. google (non topic case) only allows 1
#!/bin/sh | |
set -x | |
TAG=1.0.0-alpha | |
oc patch deployment webconsole -n openshift-web-console -p "{\"spec\": {\"template\": {\"spec\": {\"containers\": [{\"name\": \"webconsole\", \"image\": \"aerogear/origin-web-console:$TAG\"}]}}}}" | |
#oc get configmap broker-config -n ansible-service-broker -o yaml | sed -e "s/tag:.*/tag: \"$TAG\"/" | oc replace -n ansible-service-broker -f - |
<?xml version="1.0" encoding="utf-8"?> | |
<manifest xmlns:android="http://schemas.android.com/apk/res/android" | |
package="com.cards.notification"> | |
<uses-sdk | |
android:minSdkVersion="17" | |
android:targetSdkVersion="17" /> | |
<application | |
android:allowBackup="true" |