pavgup / osx-for-hackers.sh

Last active August 29, 2015 14:24 — forked from brandonb927/osx-for-hackers.sh

Healthy customization of sox-for-hackers.sh (yosemite style)

	#!/bin/sh -x

	# Alot of these configs have been taken from the various places
	# on the web, most from here
	# https://github.com/mathiasbynens/dotfiles/blob/master/.osx

	# Set the colours you can use
	black='\033[0;30m'
	white='\033[0;37m'
	red='\033[0;31m'

pavgup / frontendDevlopmentBookmarks.md

Last active November 1, 2019 13:03 — forked from dypsilon/frontendDevlopmentBookmarks.md

A badass list of frontend development resources I collected over time.

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

pavgup / idea.vmoptions

Last active November 18, 2015 21:24 — forked from P7h/IntelliJ_IDEA__Perf_Tuning.txt

Performance tuning parameters for IntelliJ IDEA. Add these params in idea64.exe.vmoptions or idea.exe.vmoptions file in IntelliJ IDEA. If you are using JDK 8.x, please knock off PermSize and MaxPermSize parameters from the tuning configuration.

	-server
	-Xms2G
	-Xmx4G
	-XX:NewSize=512m
	-XX:MaxNewSize=512m
	-XX:PermSize=512m
	-XX:MaxPermSize=512m
	-XX:+UseParNewGC
	-XX:ParallelGCThreads=4
	-XX:MaxTenuringThreshold=1

pavgup / agent.cmd

Created October 24, 2015 01:53 — forked from Shoozza/agent.cmd

Make Cmder work with ssh-agent

	@ECHO OFF

	REM Set default sock file
	SET SSH_AUTH_SOCK=/tmp/ssh-agent.sock

	REM Check socket is available
	IF NOT EXIST "%TMP%\ssh-agent.sock" GOTO:RUNAGENT

	REM Check if an ssh-agent is running
	FOR /f "tokens=" %%I IN ('ps ^\| grep ssh-agent ^\| sed "s/^ $[0-9]\+$ .*/\1/"') DO SET VAR=%%I

pavgup / ansible_conditionals_examples.yaml

Created November 24, 2015 06:50 — forked from marcusphi/ansible_conditionals_examples.yaml

Ansible 1.3 Conditional Execution -- Very complete example with comments -- I find the conditional expressions to be ridiculously hard to get right in Ansible. I don't have a good model of what's going on under the surface so I often get it wrong. What makes it even harder is that there has been at least three different variants over the course …

	---
	# This has been tested with ansible 1.3 with these commands:
	# ansible-playbook -i hosts ansible_conditionals_examples.yaml --extra-vars="hosts=myhosts isFirstRun=false"
	# ansible-playbook -i hosts ansible_conditionals_examples.yaml --extra-vars="hosts=myhosts isFirstRun=true"
	# ansible-playbook -i hosts ansible_conditionals_examples.yaml --extra-vars="hosts=myhosts"
	# NB: The type of the variable is crucial!

	- name: Ansible Conditionals Examples
	hosts: $hosts
	vars_files:

pavgup / gist:b5937a349f9a921e370a8c8b06aafc98

Last active October 16, 2019 18:22 — forked from cheethoe/gist:49d9c1d0003e44423e54a060e0b3fbf1

Rook v1.1.0 device/osd removal

	# This will use osd.5 as an example
	# ceph commands are expected to be run in the rook-toolbox
	1) disk fails
	2) remove disk from node
	3) mark out osd. `ceph osd out osd.5`
	4) remove from crush map. `ceph osd crush remove osd.5`
	5) delete caps. `ceph auth del osd.5`
	6) remove osd. `ceph osd rm osd.5`
	7) delete the deployment `kubectl delete deployment -n rook-ceph rook-ceph-osd-5`
	8) delete osd data dir on node `rm -rf /var/lib/rook/osd5`

pavgup / gather-plan cursor custom mode

Created July 23, 2025 23:12 — forked from vltansky/gather-plan cursor custom mode

	You are PLAN, an AI strategist operating inside Cursor.
	Mode: PLAN (read-only, no code changes). Your primary function is to meticulously analyze the user's request and the existing codebase to formulate a detailed, step-by-step action plan. You MUST follow the phases outlined below, rigorously adhering to the explicit exploration requirements to prevent premature planning based on assumptions.

	# Mission

	## Phase 1: Contextual Exploration & Analysis (Mandatory First Step – No Assumptions)

	Objective: To deeply and accurately understand the relevant parts of the codebase before proposing any plan. You MUST actively use your available tools. The thoroughness of this phase is paramount to the success of the plan. While the following actions are prescribed, adapt their depth to the task's complexity and scope, ensuring the spirit of each exploration area is covered and a minimum of two distinct tool call types (e.g., `read_file` and `codebase_search`) are utilized before concluding this phase.

	**Co

Pavan Gupta pavgup

Frontend Development