apcera-code’s gists

apcera-code / java-app-create-6.sh

Created May 5, 2016 18:10

Connecting Apcera and New Relic: if the stager argument is not specified, the default Java staging pipeline will be used

	apc app create my-java-app \
	--allow-egress

apcera-code / java-app-create-5.sh

Last active May 5, 2016 18:09

Connecting Apcera and New Relic: developers can create applications from the terminal using the customized New Relic stager

	apc app create my-java-app \
	-sp /apcera::java-newrelic-pipeline \
	--env-set “NEW_RELIC_LICENSE_KEY=<nr_secret_key>” \
	--allow-egress

apcera-code / java-app-create-4.sh

Created May 5, 2016 18:07

Connecting Apcera and New Relic: submit the application to the Apcera platform using the package dependency method

	apc app create my-java-app \
	--depends-on package.newrelic-java-package \
	--allow-egress

apcera-code / java-app-create-3.sh

Created May 5, 2016 18:06

Connecting Apcera and New Relic: Run the apc package build command to create the package

apc package build newrelic-java-package.conf

apcera-code / java-app-create-2.sh

Created May 5, 2016 18:05

Connecting Apcera and New Relic: Use the New Relic for Java staging pipeline

	apc app create my-java-app \
	-sp /apcera::java-newrelic-pipeline \
	--env-set “NEW_RELIC_LICENSE_KEY=<nr_secret_key>” \
	--allow-egress

apcera-code / java-app-create-1.sh

Last active May 5, 2016 18:03

Connecting Apcera and New Relic: Specify a package dependency on New Relic APM software

	apc app create my-java-app \
	--depends-on package.newrelic-java-package \
	--allow-egress

apcera-code / nats-ops-capsule-terminal-output

Last active April 20, 2016 23:03

Deploying Microservices with Multi Job Manifests: this is a command prompt inspecting the traffic from NATS

	apc job connect nats-ops

	-bash-4.3# env \| grep NATS_URI
	NATS_URI=tcp://169.254.0.4:10000
	-bash-4.3# nc 169.254.0.4 10000
	INFO {"server_id":"5ca41a4f043d4d71bd6ec94bae67ada8","version":"0.7.2","go":"go1.5.2","host":"0.0.0.0","port":4222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576}
	sub > 1
	+OK
	MSG help 1 _INBOX.mRzj3WwpUseJmWN1iIPAG1 11
	help please

apcera-code / nats-app-request-terminal-output

Last active April 20, 2016 23:04

Deploying Microservices with Multi Job Manifests: this is making a request to the 'nats-app'

	curl http://nats-app-jziwuh.example.apcera-platform.io/help
	Got help within 999.455µs: OK I can help!

apcera-code / confirm-setup-multi-job-manifest-terminal-output

Last active April 20, 2016 23:07

Deploying Microservices with Multi Job Manifests: this is to confirm the setup for the multi job manifest

	apc job list
	Working in "/demo"
	╭─────────────┬──────┬───────────┬─────────┬───────────╮
	│ Name │ Type │ Namespace │ Status │ Instances │
	├─────────────┼──────┼───────────┼─────────┼───────────┤
	│ nats-app │ app │ /demo │ started │ 3/3 │
	│ nats-server │ app │ /demo │ started │ 1/1 │
	│ nats-worker │ app │ /demo │ started │ 1/1 │
	│ nats-ops │ job │ /demo │ started │ 1/1 │
	╰─────────────┴──────┴───────────┴─────────┴───────────╯

apcera-code / multi-job-declarations-terminal-output

Last active April 20, 2016 23:08

Deploying Microservices with Multi Job Manifests: this is a terminal output for deploying the multi job manifest

	apc manifest deploy project.json
	[manifest] -- Deploy -- execution started
	[manifest] -- Deploy -- looking up "package::/demo::nats-app"
	[nats-server] -- Pulling Docker image -- checking policy
	[nats-server] -- Pulling Docker image -- checking if package FQN is taken
	[nats-server] -- Pulling Docker image -- fetching image metadata
	[nats-server] -- Pulling Docker image -- creating package
	[nats-server] -- Pulling Docker image -- all layers downloaded
	[manifest] -- Deploy -- looking up "package::/demo::nats-worker"
	[manifest] -- Deploy -- looking up "package::/apcera/pkg/os::ubuntu-14.04-apc3"