New workstations

.gitignore

@@ -1,5 +1 @@
-.idea/
 launchagent-daily-install.log
-Brewfile-core.lock.json
-Brewfile-extra.lock.json
-Brewfile-osx.lock.json

.inputrc

@@ -0,0 +1,2 @@
+"\e[A": history-search-backward
+"\e[B": history-search-forward

README.md

@@ -5,7 +5,6 @@ Hello there! This repo is intended to provide light-weight setup to developing o
 ![capi](https://im-01.gifer.com/9Y0s.gif)
 
 ## Dependencies
-* Mac OSX Sierra
 * pip
 
 ## Installation
@@ -15,54 +14,28 @@ Hello there! This repo is intended to provide light-weight setup to developing o
     git clone [email protected]:cloudfoundry/capi-workspace.git && cd capi-workspace
 ```
 
-You can now either install via `./install.sh` or `./install-core.sh`.
+You can now set up by doing the following:
+1. create gcp machine `gcloud compute instances create capi-ws-<your-ws-name> --zone 'us-central1-a' --source-machine-image 'capi-ws-image-latest' --project 'cf-capi-arya'`
+1. ssh onto said machine `gcloud compute ssh --zone "us-central1-a" "pivotal@capi-ws-<your-ws-name>" --project "cf-capi-arya"  --ssh-flag="-A"`
+1. when you're done delete you gcp machine `gcloud compute instances delete capi-ws-<your-ws-name> --zone "us-central1-a" --project "cf-capi-arya" -q`
 
-Or curl the bootstrap script, which will create the `workspace` directory and clone this repo for you.
-This is primarily intended for quickly setting up virtual workstations.
-
-```
-bash <(curl -s https://raw.githubusercontent.com/cloudfoundry/capi-workspace/main/bootstrap.sh)
-```
 **Make sure you ssh in as the "pivotal" user** 
 
-## Manual steps (to be automated later)
-* Open System Preferences / Users & Groups / <user> / Login Items
-    * Add `flycut` from Applications
-    * Add `spectacle` from Applications
-* Log out/Log in
-    * This will cause Flycut and Spectacle to run and ask for permissions
-* Open up Rubymine manually and select `License Server` and copy in the the rubymine license from the labs license server (http://omaha.pivotallabs.com:8080/licenseServer in the SF office)
-  - If you are not on a Pivotal Network, you need to VPN into one in order to access this server.
-* Install the `mine` cli shortcut (RubyMine -> Tools -> Create Command-line Launcher...)
-* If you are using Goland do the same two previous steps for Goland
-* If you have access to the private CAPI backlog, add a secure note called `tracker_api_token` to LastPass with your Pivotal Tracker API token. This token will be used in scripts such as `claim_bosh_lite` to pull story titles currently in flight.
-
-## Contributing to this repo
-
-* kindly consider when a change is worth making to `install-core.sh` versus `install.sh`.
-* [bash-it](https://github.com/Bash-it/bash-it) We use bash-it to organize and streamline our bash settings. This includes stuff like color schemes, aliases, shell settings, and the shell prompt formatting. Adding "plugins" to `custom-bash-it-plugins` will cause them to be installed in every new shell.
-
-## What this installation does
+## Adding nvim plugins
+We use vimPlug to manage our plugins. Add the plugin to init.vim. Declare your plugin in the top section between plug#begin and plug#end. Add configuration for your plugin in the lua section between lua <<EOF and EOF.
 
-`install-core.sh`: intended to be more friendly for developers who don't want this repository to take over their machine. This is intended to be the minimal set of things required for working with a CAPI repository.
-* Only installs core utilities, languages, services, and binaries.
-* Is NOT responsible for installing & configuring any editors (nvim/vscode/intellij)
-* Is NOT responsible for installing tools for improving developer workflows (jq/rg)
-* Is NOT responsible for applying any git configuration
-* Is NOT responsible for loading in scripts that need to be `source`'d.
-* Is NOT responsible for modifying your `$PATH` to include `script`
 
-`./install.sh`: runs `install-core.sh` and configures the machine with many more packages/preferences
+## Modifying general vim behavior
+Add configuration in the Standard Vim Config section of init.vim
 
-## install.sh or install-core.sh ?
 
-`install-core.sh` is a subset of `install.sh` and is intended to be less invasive to the machine, without compromising on provisioning a workstation suitable to working on CAPI projects.
+## Contributing to this repo
 
-For fresh workstations && full-time CAPI developers, install.sh might make more sense.
+* [bash-it](https://github.com/Bash-it/bash-it) We use bash-it to organize and streamline our bash settings. This includes stuff like color schemes, aliases, shell settings, and the shell prompt formatting. Adding "plugins" to `custom-bash-it-plugins` will cause them to be installed in every new shell.
 
-For folks working on multiple projects, `install-core.sh` might make more sense.
+## What this installation does
 
-For folks with existing workstations & configuration, `install-core.sh` might make more sense.
+Stuff, important stuff.  Stuff that makes a difference.
 
 ## Directory Overview