Ezo Saleh ezodude

MRSK

This documentation adds important additions to the docs for mrsk deploy tool (see github.com/mrsked/mrsk)

Destination flag

You can use mrsk deploy --destination staging

This will read config/deploy.yml and config/deploy.staging.yml files, and also will read .env.staging file if it exists.

Why Multiple SSH keys?

There are numerous reasons you may need to use multiple SSH keys for accessing GitHub and BitBucket

You may use the same computer for work and personal development and need to separate your work.

When acting as a consultant, it is common to have multiple GitHub and/or BitBucket accounts depending on which client you may be working for.

You may have different projects you're working on where you would like to segregate your access.

To forward X11 from inside a docker container to a host running macOS

Install XQuartz: https://www.xquartz.org/
Launch XQuartz. Under the XQuartz menu, select Preferences
Go to the security tab and ensure "Allow connections from network clients" is checked.
Run xhost + ${hostname} to allow connections to the macOS host *
Setup a HOSTNAME env var export HOSTNAME=`hostname`*
Add the following to your docker-compose:

 environment:

Variables by Secrets

Sample script that allows you to define as environment variables the name of the docker secret that contains the secret value. It will be in charge of analyze all the environment variables searching for the placeholder to substitute the variable value by the secret.

Usage

You can define the next environment variables:

	<artifacts_info>
	The assistant can create and reference artifacts during conversations. Artifacts are for substantial, self-contained content that users might modify or reuse, displayed in a separate UI window for clarity.

	# Good artifacts are...
	- Substantial content (>15 lines)
	- Content that the user is likely to modify, iterate on, or take ownership of
	- Self-contained, complex content that can be understood on its own, without context from the conversation
	- Content intended for eventual use outside the conversation (e.g., reports, emails, presentations)
	- Content likely to be referenced or reused multiple times

	func trace(){
	pc := make([]uintptr, 10) // at least 1 entry needed
	runtime.Callers(2, pc)
	f := runtime.FuncForPC(pc[0])
	file, line := f.FileLine(pc[0])
	fmt.Printf("%s:%d %s\n", file, line, f.Name())
	}

	FROM golang:1.12 AS build
	COPY ./main.go .

	# ARG here is to make the sha available for use in -ldflags
	ARG GIT_SHA

	# -ldflags "-X main.sha=${GIT_SHA}" allows main.sha to be set at build time
	RUN go build -ldflags "-X main.sha=${GIT_SHA}" -o /app

	FROM scratch

	package main

	import (
	"net/http"
	"net/url"
	"os"
	"fmt"
	)

	version: 2

	jobs:
	test-job:
	machine: true
	steps:
	- checkout
	- run: sudo bash -c "$(curl -fsSL https://s3.amazonaws.com/tools.nanobox.io/bootstrap/ci.sh)"

	- run: nanobox evar add local CLOUDINARY_API_KEY=$CLOUDINARY_API_KEY

	import (
	"database/sql"
	"github.com/lib/pq"
	)
	dbb, _ := sql.Open("postgres", "postgres://Amogh:amogh@localhost:6431/dblog?sslmode=disable")
	dbb.SetMaxIdleConns(10)
	dbb.SetMaxOpenConns(10)
	dbb.SetConnMaxLifetime(0)
	a := time.Now()
	txn, err := dbb.Begin()