Repository files navigation

Withfw you have a configuration describing your workspace. It takescare of cloning projects and can run commands across your entireworkspace. You can start working on any project quickly, even if it'snot in your flat structured workspace (better thanCDPATH!). It also"sets up" your environment when you start working on a project(compile stuff, runmake, activatevirtualenv ornvm, fire upsbt shell, etc.)

[Here's]{.spurious-link} an exampleconfiguration that should be easy to grasp.

The default configuration location is located under your system'sconfig directory as describedhere. That is :

• Linux:~/.config/fw
• MacOS:$HOME/Library/Application Support/fw
• Windows:{FOLDERID_RoamingAppData}\fw

The location and can be overridden by settingFW_CONFIG_DIR.

Per default projects are cloned into${settings.workspace}/${project.name} but you can override that bysetting anoverride_path attribute as seen in the exampleconfiguration.

fw is a tool I wrote to do my bidding. It might not work for you ifyour workflow differs a lot from mine or might require adjustments. Hereare the assumptions:

• only git repositories
• only ssh clone (easily resolveable by putting more work in the git2bindings usage)
• ssh-agent based authentication

• workspace persistence (I canrm -rf my entire workspace and haveit back in a few minutes)
• ZERO overhead project switching with theworkon function (need toactivatenvm? Runsbt? Set LCD brightness to 100%?fw will doall that for you)
• zsh completions on the project names forworkon
• generate projectile configuration for all your project (no need toprojectile-add-known-project every time you clone some shit, itwill just work)