Jeremy Dombrowski meatflavourdev

$ cd <application name>

Where is the dir where you have the .env file.

heroku config:set $(cat .env | sed '/^$/d; /#[[:print:]]*$/d')

$ cd <application name>

Where is the dir where you have the .env file.

heroku config:set $(cat .env | sed '/^$/d; /#[[:print:]]*$/d')

YouTube video stream format codes

Comprehensive list of YouTube format code itags

itag Code	Container	Content	Resolution	Bitrate	Range	VR / 3D
5	flv	audio/video	240p	-	-	-
6	flv	audio/video	270p	-	-	-
17	3gp	audio/video	144p	-	-	-
18	mp4	audio/video	360p	-	-	-
22	mp4	audio/video	720p	-	-	-

Welcome!

UPDATE: This list is no longer maintained. I've moved it to its own repo so you can send suggestions as Pull Requests. https://github.com/dideler/bootstrapping/

For feedback or suggestions, please send a tweet (@dideler). Gist comments don't notify me. Pull requests aren't possible with gists (yet), so I don't recommend forking because then I can't easily get the change.

Starring this gist will give me an idea of how many people consider this list useful.

	Understand the Task: Grasp the main objective, goals, requirements, constraints, and expected output.
	- Minimal Changes: If an existing prompt is provided, improve it only if it's simple. For complex prompts, enhance clarity and add missing elements without altering the original structure.
	- Reasoning Before Conclusions: Encourage reasoning steps before any conclusions are reached. ATTENTION! If the user provides examples where the reasoning happens afterward, REVERSE the order! NEVER START EXAMPLES WITH CONCLUSIONS!
	- Reasoning Order: Call out reasoning portions of the prompt and conclusion parts (specific fields by name). For each, determine the ORDER in which this is done, and whether it needs to be reversed.
	- Conclusion, classifications, or results should ALWAYS appear last.
	- Examples: Include high-quality examples if helpful, using placeholders [in brackets] for complex elements.
	- What kinds of examples may need to be included, how many, and whether they are complex enough to benefit from p

	Understand the Task: Grasp the main objective, goals, requirements, constraints, and expected output.
	- Minimal Changes: If an existing prompt is provided, improve it only if it's simple. For complex prompts, enhance clarity and add missing elements without altering the original structure.
	- Reasoning Before Conclusions: Encourage reasoning steps before any conclusions are reached. ATTENTION! If the user provides examples where the reasoning happens afterward, REVERSE the order! NEVER START EXAMPLES WITH CONCLUSIONS!
	- Reasoning Order: Call out reasoning portions of the prompt and conclusion parts (specific fields by name). For each, determine the ORDER in which this is done, and whether it needs to be reversed.
	- Conclusion, classifications, or results should ALWAYS appear last.
	- Examples: Include high-quality examples if helpful, using placeholders [in brackets] for complex elements.
	- What kinds of examples may need to be included, how many, and whether they are complex enough to benefit from p

	#!/bin/sh
	### BEGIN INIT INFO
	# Provides: syncthing
	# Required-Start: $local_fs $remote_fs
	# Required-Stop: $local_fs $remote_fs
	# Should-Start: $network
	# Should-Stop: $network
	# Default-Start: 2 3 4 5
	# Default-Stop: 0 1 6
	# Short-Description: Multi-user daemonized version of syncthing.

	(function debugify_content_script(){
	console.log('debugify content script running');
	var nativeWebSocket = window.WebSocket;
	var requests = window.requestLog = {};
	var WebSocket = window.WebSocket = function(uri) {
	console.log('new WebSocket created', uri);
	this.websocket = new nativeWebSocket(uri);
	this.websocket.onopen = this.onOpen.bind(this);
	this.websocket.onmessage = this.onMessage.bind(this);
	this.listeners = {onmessage: null, onopen: null};