Discover gists

the definitive deep dive into the .git folder

Thanks for joining us for "the definitive deep dive into the .git folder". It's an incredible live-demo where we open every file in the .git folder and show what it does.

Links

Here's the links we saw:

Intro & Disclaimers

I am not an expert, I am just Some Guy who happened to (a) get Viva New Vegas working on Steam Deck and (b) kept notes. These are those notes. I love Fallout and I love the Steam Deck and I want other people to experience those things, but I am also unable to promise to support you through every question you may have.

This is not a guide in the way that Viva New Vegas is a guide. VNV is incredibly well written and has your back every step of the way. These are just scribbles. Please set your expectations! Also, please tell me what doesn't work or is confusing! I would like us to work together to improve this process for others.

Who did this

This doc was written by docg/penllawen. Come say hi on the Viva New Vegas Discord or [this reddit thread]https://www.reddit.com/r/SteamDeck/comments/1c8uihm/an_incomplete_guide_to_installing_modded_fallout/).

Sharing my project's build script in case it's useful to others. I'm not testing for Windows, which is why the script reports an error, but just note that emitting Windows executables is actually supported by the Node API (see docs). Feel free to use and modify.

Notes

Webpack is used for bundling.
The entry point for the webpack config for my example is ./bin/app, which was an executable Node.js script with a shebang line. Update the config to point to whatever your app's entry point is.
The SEA config file uses disableExperimentalSEAWarning to suppress the experimental warning displayed when running a generated executable. This didn't work for Node 20.1.0 (see issue), but it has been tested and does work for 21.1.0.

Read My Game Hacking Tutorials at GuidedHacking.com!

	4U612-DN31H-MJEJ0-0V0Z4-978HD
	5G44H-ACH50-0J4C9-1VC5P-CY0QD
	JC000-8G047-MJDF1-0H3E6-8QR5F
	JV2NU-0XL5N-0J4Q8-0T0E6-8GH56
	JZ6E0-4R1E0-HJ1Q0-1R8NH-3AK28
	0Z48K-4X29Q-MJE80-113GK-C7K3A
	HF4H0-46K80-MJ8D9-1KAZP-CKK12
	NY69H-2N05P-HJ170-1V1ZM-CG222
	4C45A-D8J0H-HJ5T0-1T25H-92A76
	0Z4H2-0WK9K-4JE10-0T9G6-9C8M4

	Visual Studio 2022
	Enterprise :
	VHF9H-NXBBB-638P6-6JHCY-88JWH

	Professional:
	TD244-P4NB7-YQ6XK-Y8MMM-YWV2J

	#!/bin/bash

	# This script is based on https://unix.stackexchange.com/revisions/480191/9.

	# Recommended SIZE setting for different drives:
	# (SATA) SSD: 1024 (default)
	# (ANY) HDD: 256
	# (High End NVME) SSD: 4096
	# (Low-Mid End NVME) SSD: 1024 (default)

	#!/usr/bin/python3
	update_info_location = "/var/tmp/"

	import os
	import requests

	def perform_update():
	latest = requests.head("https://discord.com/api/download/stable?platform=linux&format=deb").headers["location"].split("/")[-1]
	if os.system(f"wget -O /tmp/{latest} \"https://discord.com/api/download/stable?platform=linux&format=deb\"") != 0:
	print("Update failed during download...")

	machine github.com
	login technoweenie
	password SECRET

	machine api.github.com
	login technoweenie
	password SECRET

	# first:
	lsbom -f -l -s -pf /var/db/receipts/org.nodejs.pkg.bom \| while read f; do sudo rm /usr/local/${f}; done
	sudo rm -rf /usr/local/lib/node /usr/local/lib/node_modules /var/db/receipts/org.nodejs.*

	# To recap, the best way (I've found) to completely uninstall node + npm is to do the following:

	# go to /usr/local/lib and delete any node and node_modules
	cd /usr/local/lib
	sudo rm -rf node*

Discover gists

the definitive deep dive into the .git folder

Links

Intro & Disclaimers

Who did this

TL;DR