Null Void datatypevoid

Docker on Qubes

Since this page is apparently the top result on google, Heres a link to how to do it.

https://martingladdish.co.uk/technology/setting-up-docker-under-qubesos/

That page has more detail, but here are the instructions in case its down.

Install docker engine, following the instruction on https://www.docker.com. NOT DESKTOP as that wont work in Qubes (unless you enable nested virtualization)

Vagrant on Qubes-OS

(Vagrant)[https://www.vagrantup.com] "Development Environments Made Easy"

(Qubes-OS)[https://www.qubes-os.org] "A Reasonably Secure Operating System."

This is a guide on to using vagrant on qubes-os with qemu using the libvirt provider. Because qubes-os does not support nested virtualization, you'r stuck with emulation. If you want performance, use a system with a proper vagrant setup.

Template Setup

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:

Not all random values are created equal - for security-related code, you need a specific kind of random value.

A summary of this article, if you don't want to read the entire thing:

Don't use Math.random(). There are extremely few cases where Math.random() is the right answer. Don't use it, unless you've read this entire article, and determined that it's necessary for your case.
Don't use crypto.getRandomBytes directly. While it's a CSPRNG, it's easy to bias the result when 'transforming' it, such that the output becomes more predictable.
If you want to generate random tokens or API keys: Use uuid, specifically the uuid.v4() method. Avoid node-uuid - it's not the same package, and doesn't produce reliably secure random values.
If you want to generate random numbers in a range: Use random-number-csprng.

You should seriously consider reading the entire article, though - it's

	cd /usr/share/nginx/html
	rm -r *

	apt-get update && apt-get -y install wget nano git-core curl build-essential openssl libssl-dev python p7zip unzip
	wget https://buildbot.libretro.com/nightly/emscripten/$(date +%Y-%m-%d -d "1 day ago")_RetroArch.7z

	p7zip -d $(date +%Y-%m-%d -d "1 day ago")_RetroArch.7z
	mkdir -p assets/frontend/bundle
	mkdir -p assets/cores
	chmod +x indexer

	# Reliable persistent SSH-Tunnel via systemd (not autossh)
	# https://gist.github.com/guettli/31242c61f00e365bbf5ed08d09cdc006#file-ssh-tunnel-service

	[Unit]
	Description=Tunnel for %i
	After=network.target

	[Service]
	User=tunnel
	ExecStart=/usr/bin/ssh -o "ExitOnForwardFailure yes" -o "ServerAliveInterval 60" -N tunnel@%i

	# Author: Zameer Ansari
	# You should look at the following URL's in order to grasp a solid understanding
	# of Nginx configuration files in order to fully unleash the power of Nginx.
	# http://wiki.nginx.org/Pitfalls
	# http://wiki.nginx.org/QuickStart
	# http://wiki.nginx.org/Configuration
	#
	# Generally, you will want to move this file somewhere, and start with a clean
	# file but keep this around for reference. Or just disable in sites-enabled.
	#

	#!/usr/bin/env bash

	read -r -d '' usage << EOM
	Usage:

	gh-deploy-clone user/repo [ENVIRONMENT]
	EOM

	[ -z "$1" ] && echo && echo "$usage" && echo && exit 1

	#include <sol.hpp>
	#include <string>
	#include <iostream>

	using EntityId = int;

	class Entity {
	public:
	explicit Entity(EntityId id) :
	name("John"), id(id)

	Handles = {}
	local memoizedFuncs = {}

	-- metatable which does magic
	local mt = {}
	mt.__index = function(handle, key)
	if not handle.isValid then
	print(debug.traceback())
	error("Error: handle is not valid!", 2)
	end