| 2017-05-10T12:33:47.703Zalpinebuild/pull started | |
| 2017-05-10T12:33:48.004Zalpinebuild/pull finished successfully | |
| 2017-05-10T12:33:49.798ZalpinePATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin | |
| 2017-05-10T12:33:49.798ZalpineHOSTNAME=0744ec84f7bb | |
| 2017-05-10T12:33:49.798ZalpineTERM=xterm | |
| 2017-05-10T12:33:49.798ZalpineCI_REPO_NAME=branch-testing | |
| 2017-05-10T12:33:49.798ZalpineCI=true | |
| 2017-05-10T12:33:49.798ZalpineCI_COMMIT_DESCRIPTION=1.0.0 | |
| 2017-05-10T12:33:49.798ZalpineCI_COMMITTER_USERNAME=kellyjandrews | |
| 2017-05-10T12:33:49.798ZalpineCI_COMMITTER_EMAIL=kelly@kellyjandrews.com |
| FROM ubuntu:zesty | |
| RUN mkdir /usr/src/app | |
| WORKDIR /usr/src/app | |
| COPY . . | |
| CMD ["printenv"] |
In the interest of fostering an open and welcoming environment, we as community admins pledge to making participation in our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
| $ jx install | |
| Context "minikube" modified. | |
| Trying to create ClusterRoleBinding minikube-cluster-admin-binding for role: cluster-admin for user minikube | |
| clusterrolebinding "minikube-cluster-admin-binding" created | |
| Created ClusterRoleBinding minikube-cluster-admin-binding | |
| Created ServiceAccount tiller in namespace kube-system | |
| Trying to create ClusterRoleBinding tiller for role: cluster-admin and ServiceAccount: kube-system/tiller | |
| Created ClusterRoleBinding tiller | |
| Initialising helm using ServiceAccount tiller in namespace kube-system | |
| $HELM_HOME has been configured at /Users/kellyandrews/.helm. |
Modern application development teams have adopted Slack as a place to collaborate as a team, and consolidate tools into one location to make operations run more efficiently.
In the case of a mobile app, getting instant feedback from customers via Slack messages can shorten the time to feature development, bug fixes, and other mission-critical use cases.
As an example, your mobile app can send an SMS directly to your customer success team's slack channel when an error occurs, or if a user needs help.
In this tutorial, I want to show you how you can connect your Slack channels to your customers using the Nexmo SMS API. The Nexmo SMS API can be configured to use a webhook for incoming SMS messages. We will use Webtask.io in this example to handle the incoming message and forward it to a Slack webhook.
This application requires a Nexmo application and phone numbers. To create the application, use the nexmo app:create command with the Nexmo CLI.
The parameters are:
<<APP NAME>>- the name of the voice application<<FILENAME>>- the name of the private key file, in this instance<<FILENAME>>is expected<<ANSWER WEBHOOK>>- the webhook called the Nexmo number receives an inbound call<<EVENT WEBHOOK>>- the webhook called when the call status changes
| class Image | |
| def initialize(image) | |
| @image = image | |
| end | |
| def displayImage | |
| @image.each{|row| puts row.join} | |
| end |
| const authMachine = Machine({ | |
| id: 'auth', | |
| context: { | |
| email: '', | |
| password: '', | |
| loginModal: false | |
| }, | |
| initial: 'unauthorized', | |
| states: { | |
| unauthorized: { |