sager.io sagerio

Git sees every file in your working copy as one of three things:

tracked - a file which has been previously staged or committed;
untracked - a file which has not been staged or committed; or
ignored - a file which Git has been explicitly told to ignore.

Ignored files are usually build artifacts and machine generated files that can be derived from your repository source or should otherwise not be committed. Some common examples are:

dependency caches, such as the contents of /node_modules or /packages
compiled code, such as .o, .pyc, and .class files

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

Pushing to Multiple Git Repos

If a project has to have multiple git repos (e.g. Bitbucket and Github) then it's better that they remain in sync.

Usually this would involve pushing each branch to each repo in turn, but actually Git allows pushing to multiple repos in one go.

If in doubt about what git is doing when you run these commands, just

Simple automated GIT Deployment using GIT Hooks

Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.

How it works

You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.

People

`:bowtie:`	😄 `:smile:`	😆 `:laughing:`
😊 `:blush:`	😃 `:smiley:`	☺️ `:relaxed:`
😏 `:smirk:`	😍 `:heart_eyes:`	😘 `:kissing_heart:`
😚 `:kissing_closed_eyes:`	😳 `:flushed:`	😌 `:relieved:`
😆 `:satisfied:`	😁 `:grin:`	😉 `:wink:`
😜 `:stuck_out_tongue_winking_eye:`	😝 `:stuck_out_tongue_closed_eyes:`	😀 `:grinning:`
😗 `:kissing:`	😙 `:kissing_smiling_eyes:`	😛 `:stuck_out_tongue:`

	{
	"100": "Continue",
	"101": "Switching Protocols",
	"102": "Processing",
	"200": "OK",
	"201": "Created",
	"202": "Accepted",
	"203": "Non-Authoritative Information",
	"204": "No Content",
	"205": "Reset Content",

	Drizzle Studio is a cloud hosted web ui `local.drizzle.studio`.
	It connects to the local hosted api that is started when using `drizzle-kit studio` in your terminal.

	By default, the ui tries to connect to localhost:4983.

	If using github codespaces, the server will be at a link like `your-codespace-name-4983.app.github.dev`.

	If you try to use the `--host` param for the cli it won't work. (https://github.com/drizzle-team/drizzle-kit-mirror/issues/381)
	Instead, use the `?host` query param when accessing `local.drizzle.studio`.

	<!DOCTYPE HTML>
	<html>
	<head>
	<meta charset="utf-8" />
	<title>App</title>
	<meta name="viewport" content="width=device-width, initial-scale=1" />
	<script charset="utf-8" src="js/app.js"></script>
	<link rel="stylesheet" href="css/app.css" />
	</head>
	<body>

	{
	"apps": [
	{
	/* General */
	"name": "my-api", /* (string) application name (default to script filename without extension) */
	"script": "index.js", /* (string) script path relative to pm2 start */
	"cwd": "/var/www/", /* (string) the directory from which your app will be launched */
	"args": "-a 13 -b 12", /* (string) string containing all arguments passed via CLI to script */
	"interpreter": "/usr/bin/python", /* (string) interpreter absolute path (default to node) */
	"interpreter_args": "--harmony", /* (string) option to pass to the interpreter */