@jDKj@z5jy22}hX2{o7>rK>FWbCMe3P%G7-L9Q6MI;4+a2 literal 0 HcmV?d00001 diff --git a/index.html b/index.html new file mode 100644 index 0000000..72b0e3b --- /dev/null +++ b/index.html @@ -0,0 +1,220 @@ + + + + + + + + + + + .env (for Bash) + + + + + +

+ View on GitHub + +

.env (for Bash)

dot env is a cascading Bash environment system for those who work on different hardware and OS environments. Similar to oh-my-zsh but for Bash, and special sauce for those who work 'ssh' on remote machines.

+ +

+ Download this project as a .zip file + Download this project as a tar.gz file +

+ + +

+.env

+ +

Version: 0.3.13

+ +

.env (Dot-Env) is a comprehensive, cascading Bash environment system. It provides Bash shell-prompt themes, handy functions, aliases, and tools for the Bash power user. Plugins have recently been introduced for extensibility.

+ +

I work on many different machines remotely using SSH. Though I love Z-shell, it does not come standard on most operating systems and has to be installed manually. This can be problematic on Solaris machines. After using Z-shell for a few months I decided to go back to Bash because it comes standard on all operating systems and is usually the default shell.

+ +

+Features

+ +

Built for the command-line guru from the ground up with your remote SSH shell environment in mind.
Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin)
Themeable - comes with several themes to beautify your shell prompt, and you can write your own!
Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and you can write your own!

+Overview

+ +

After installing .env locally whenever you start a new command prompt, using whatever terminal program you desire, .env gets loaded like this:

+ +

Overview

+ +

Lastly, your chosen theme gets loaded and you are ready for an awesome Bash session.

+ +

+Install

+ +

I recommend you fork the project in GitHub, so that your changes can be easily incorporated back into the tree.

+ +

Clone the project into your home directory:

+ +

cd $HOME
+git clone git://github.com/<your github username>/.env.git  # if you forked it
+git clone git://github.com/midwire/.env.git                 # if you use my repository
+

+ +

Source it:

+ +

. $HOME/.env/dot-env.sh
+

+ +

+Load on Login

+ +

To have .env load automatically, execute:

+ +

load_on_login
+

+ +

... which will add the above source command to your .bashrc file.

+ +

+Load on Alias

+ +

To have .env load with an alias, execute:

+ +

load_on_alias
+

+ +

... which will setup the ees alias which will source .env whenever you enter ees after logging in. I use this method on all of my remote hosts that are used by other people, besides myself. That way they don't notice any difference when they login unless they run ees.

+ +

+Example .bashrc

+ +

# Choose your plugins
+plugins="completion history"
+# Choose a .env theme
+theme=sparkr
+# Set my home host.
+# So that when we login to a remote box our theme can change
+# to the remote version with special colors, etc
+dot_env_home_host='spark.local'
+# Turn this off to avoid the noise on starting a new shell instance
+dot_env_verbose=1
+# Source the .env environment
+[[ -r "$HOME/.env/dot-env.sh" ]] && . "$HOME/.env/dot-env.sh"
+

+ +

+Customize your local environment

+ +

configthis.env
+

+ +

... which will create a folder in the host directory specifically for your local environment and stub out some empty files that you should customize.

+ +

The convention is, $HOME/.env/host/[your-hostname] directory contains files like these:

+ +

alias.sh
env.sh
functions.sh
prompt.sh

... and anything else you wish to customize your own local environment.

+ +

You can put any *.sh files in your host directory that you want, and they will only get sourced when you start a Bash shell on the machine matching the specified hostname directory.

+ +

+Example:

+ +

Let's say your hostname is Harry-Potters-Macbook.local, and you want to add /usr/local/bogus to your path. Here's how you do it:

+ +

configthis.env
+

+ +

This command will stub out a few files as examples and cd to the directory where they are $HOME/.env/host/Harry-Potters-Macbook.local. Now you edit each of those files, and delete the ones you don't need. So, since we are only going to add to the path let's remove the other files, then edit the path.sh file.

+ +

rm alias.sh env.sh functions.sh prompt.sh
+

+ +

Inside path.sh add this line:

+ +

pathmunge "/usr/local/bogus"
+

+ +

Done!

+ +

Now you can source those changes . $HOME/.env/dot-env.sh and your path will include the new entry. Next time you start a shell it will maintain your path and you'll never have duplicates.

+ +

+Themes

+ +

.env themes are located in $dot_env_path/themes/. To use a theme set theme='THEME_NAME'. e.g.,

+ +

theme='sparkr'
+

+ +

A variant of the sparkr theme is default and will be loaded if no theme is specified. Note that this theme looks best when using the Menlo font.

+ +

Please send me a pull request if you create your own themes.

+ +

+Other Useful Functions

+ +

+Add your SSH key to a remote host

+ +

add_ssh_key_to_host [user@]HOSTNAME
+

+ +

... which will append your public ~/.ssh/id_dsa.pub key to the host's authorized_keys file and allow you to login without a password.

+ +

+Propagate your copy of .env to other hosts

+ +

If you want to copy your .env to another host, simply type:

+ +

propagate_env_to_host [user@]HOSTNAME
+

+ +

... which will compress your local .env, copy it to the specified host and decompress it. Then follow the instructions above under "Load on Login", or "Load on Alias"

+ +

If you want to customize the remote host environment even further:

+ +

Run confighost.env HOSTNAME +
Edit the newly created environment files
Then propagate_env_to_host HOSTNAME +

To determine the correct HOSTNAME to use for your remote environment make sure you first login to that environment and type echo $HOSTNAME.

+ +

+Make it better

+ +

Please feel free to fork it, branch it, change it and send me a pull request.

+ +

Cheers,

+ +

-- Midwire

+ + +

+ +

+ + + + + diff --git a/javascripts/main.js b/javascripts/main.js new file mode 100644 index 0000000..d8135d3 --- /dev/null +++ b/javascripts/main.js @@ -0,0 +1 @@ +console.log('This would be the main JS file.'); diff --git a/params.json b/params.json new file mode 100644 index 0000000..95d3395 --- /dev/null +++ b/params.json @@ -0,0 +1 @@ +{"name":".env (for Bash)","tagline":"dot env is a cascading Bash environment system for those who work on different hardware and OS environments. Similar to oh-my-zsh but for Bash, and special sauce for those who work 'ssh' on remote machines.","body":"# .env\r\n\r\n**Version: 0.3.13**\r\n\r\n.env (Dot-Env) is a comprehensive, cascading Bash environment system. It provides Bash shell-prompt themes, handy functions, aliases, and tools for the Bash power user. Plugins have recently been introduced for extensibility.\r\n\r\nI work on many different machines remotely using SSH. Though I love Z-shell, it does not come standard on most operating systems and has to be installed manually. This can be problematic on Solaris machines. After using Z-shell for a few months I decided to go back to Bash because it comes standard on all operating systems and is usually the default shell.\r\n\r\n## Features ##\r\n\r\n* Built for the command-line guru from the ground up with your remote SSH shell environment in mind.\r\n* Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin)\r\n* Themeable - comes with several themes to beautify your shell prompt, and you can write your own!\r\n* Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and you can write your own!\r\n\r\n## Overview ##\r\n\r\nAfter installing .env locally whenever you start a new command prompt, using whatever terminal program you desire, .env gets loaded like this:\r\n\r\n![Overview](https://raw.github.com/midwire/.env/develop/dot-env-overview.png)\r\n\r\nLastly, your chosen theme gets loaded and you are ready for an awesome Bash session.\r\n\r\n## Install ##\r\n\r\nI recommend you fork the project in GitHub, so that your changes can be easily incorporated back into the tree.\r\n\r\nClone the project into your home directory:\r\n\r\n cd $HOME\r\n git clone git://github.com//.env.git # if you forked it\r\n git clone git://github.com/midwire/.env.git # if you use my repository\r\n\r\nSource it:\r\n\r\n . $HOME/.env/dot-env.sh\r\n\r\n### Load on Login ###\r\n\r\nTo have .env load automatically, execute:\r\n\r\n load_on_login\r\n\r\n... which will add the above source command to your `.bashrc` file.\r\n\r\n### Load on Alias ###\r\n\r\nTo have .env load with an alias, execute:\r\n\r\n load_on_alias\r\n\r\n... which will setup the `ees` alias which will source .env whenever you enter `ees` after logging in. I use this method on all of my remote hosts that are used by other people, besides myself. That way they don't notice any difference when they login unless they run `ees`.\r\n\r\n### Example .bashrc ###\r\n\r\n # Choose your plugins\r\n plugins=\"completion history\"\r\n # Choose a .env theme\r\n theme=sparkr\r\n # Set my home host.\r\n # So that when we login to a remote box our theme can change\r\n # to the remote version with special colors, etc\r\n dot_env_home_host='spark.local'\r\n # Turn this off to avoid the noise on starting a new shell instance\r\n dot_env_verbose=1\r\n # Source the .env environment\r\n [[ -r \"$HOME/.env/dot-env.sh\" ]] && . \"$HOME/.env/dot-env.sh\"\r\n\r\n## Customize your local environment ##\r\n\r\n configthis.env\r\n\r\n... which will create a folder in the `host` directory specifically for your local environment and stub out some empty files that you should customize.\r\n\r\nThe convention is, `$HOME/.env/host/[your-hostname]` directory contains files like these:\r\n\r\n* alias.sh\r\n* env.sh\r\n* functions.sh\r\n* prompt.sh\r\n\r\n... and anything else you wish to customize your own local environment.\r\n\r\nYou can put any `*.sh` files in your host directory that you want, and they will only get sourced when you start a Bash shell on the machine matching the specified hostname directory.\r\n\r\n### Example: ###\r\n\r\nLet's say your hostname is `Harry-Potters-Macbook.local`, and you want to add `/usr/local/bogus` to your path. Here's how you do it:\r\n\r\n configthis.env\r\n\r\nThis command will stub out a few files as examples and `cd` to the directory where they are `$HOME/.env/host/Harry-Potters-Macbook.local`. Now you edit each of those files, and delete the ones you don't need. So, since we are only going to add to the path let's remove the other files, then edit the path.sh file.\r\n\r\n rm alias.sh env.sh functions.sh prompt.sh\r\n\r\nInside `path.sh` add this line:\r\n\r\n pathmunge \"/usr/local/bogus\"\r\n\r\nDone!\r\n\r\nNow you can source those changes `. $HOME/.env/dot-env.sh` and your path will include the new entry. Next time you start a shell it will maintain your path and you'll never have duplicates.\r\n\r\n## Themes ##\r\n\r\n.env themes are located in `$dot_env_path/themes/`. To use a theme set `theme='THEME_NAME'`. e.g.,\r\n\r\n theme='sparkr'\r\n\r\nA variant of the `sparkr` theme is default and will be loaded if no theme is specified. Note that this theme looks best when using the Menlo font.\r\n\r\nPlease send me a pull request if you create your own themes.\r\n\r\n## Other Useful Functions ##\r\n\r\n### Add your SSH key to a remote host ###\r\n\r\n add_ssh_key_to_host [user@]HOSTNAME\r\n\r\n... which will append your public `~/.ssh/id_dsa.pub` key to the host's authorized_keys file and allow you to login without a password.\r\n\r\n### Propagate your copy of .env to other hosts ###\r\n\r\nIf you want to copy your .env to another host, simply type:\r\n\r\n propagate_env_to_host [user@]HOSTNAME\r\n\r\n... which will compress your local .env, copy it to the specified host and decompress it. Then follow the instructions above under \"Load on Login\", or \"Load on Alias\"\r\n\r\nIf you want to customize the remote host environment even further:\r\n\r\n* Run `confighost.env HOSTNAME`\r\n* Edit the newly created environment files\r\n* Then `propagate_env_to_host HOSTNAME`\r\n\r\nTo determine the correct `HOSTNAME` to use for your remote environment make sure you first login to that environment and type `echo $HOSTNAME`.\r\n\r\n## Make it better\r\n\r\nPlease feel free to fork it, branch it, change it and send me a pull request.\r\n\r\nCheers,\r\n\r\n-- Midwire\r\n","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."} \ No newline at end of file diff --git a/stylesheets/pygment_trac.css b/stylesheets/pygment_trac.css new file mode 100644 index 0000000..e65cedf --- /dev/null +++ b/stylesheets/pygment_trac.css @@ -0,0 +1,70 @@ +.highlight .hll { background-color: #ffffcc } +.highlight { background: #f0f3f3; } +.highlight .c { color: #0099FF; font-style: italic } /* Comment */ +.highlight .err { color: #AA0000; background-color: #FFAAAA } /* Error */ +.highlight .k { color: #006699; font-weight: bold } /* Keyword */ +.highlight .o { color: #555555 } /* Operator */ +.highlight .cm { color: #0099FF; font-style: italic } /* Comment.Multiline */ +.highlight .cp { color: #009999 } /* Comment.Preproc */ +.highlight .c1 { color: #0099FF; font-style: italic } /* Comment.Single */ +.highlight .cs { color: #0099FF; font-weight: bold; font-style: italic } /* Comment.Special */ +.highlight .gd { background-color: #FFCCCC; border: 1px solid #CC0000 } /* Generic.Deleted */ +.highlight .ge { font-style: italic } /* Generic.Emph */ +.highlight .gr { color: #FF0000 } /* Generic.Error */ +.highlight .gh { color: #003300; font-weight: bold } /* Generic.Heading */ +.highlight .gi { background-color: #CCFFCC; border: 1px solid #00CC00 } /* Generic.Inserted */ +.highlight .go { color: #AAAAAA } /* Generic.Output */ +.highlight .gp { color: #000099; font-weight: bold } /* Generic.Prompt */ +.highlight .gs { font-weight: bold } /* Generic.Strong */ +.highlight .gu { color: #003300; font-weight: bold } /* Generic.Subheading */ +.highlight .gt { color: #99CC66 } /* Generic.Traceback */ +.highlight .kc { color: #006699; font-weight: bold } /* Keyword.Constant */ +.highlight .kd { color: #006699; font-weight: bold } /* Keyword.Declaration */ +.highlight .kn { color: #006699; font-weight: bold } /* Keyword.Namespace */ +.highlight .kp { color: #006699 } /* Keyword.Pseudo */ +.highlight .kr { color: #006699; font-weight: bold } /* Keyword.Reserved */ +.highlight .kt { color: #007788; font-weight: bold } /* Keyword.Type */ +.highlight .m { color: #FF6600 } /* Literal.Number */ +.highlight .s { color: #CC3300 } /* Literal.String */ +.highlight .na { color: #330099 } /* Name.Attribute */ +.highlight .nb { color: #336666 } /* Name.Builtin */ +.highlight .nc { color: #00AA88; font-weight: bold } /* Name.Class */ +.highlight .no { color: #336600 } /* Name.Constant */ +.highlight .nd { color: #9999FF } /* Name.Decorator */ +.highlight .ni { color: #999999; font-weight: bold } /* Name.Entity */ +.highlight .ne { color: #CC0000; font-weight: bold } /* Name.Exception */ +.highlight .nf { color: #CC00FF } /* Name.Function */ +.highlight .nl { color: #9999FF } /* Name.Label */ +.highlight .nn { color: #00CCFF; font-weight: bold } /* Name.Namespace */ +.highlight .nt { color: #330099; font-weight: bold } /* Name.Tag */ +.highlight .nv { color: #003333 } /* Name.Variable */ +.highlight .ow { color: #000000; font-weight: bold } /* Operator.Word */ +.highlight .w { color: #bbbbbb } /* Text.Whitespace */ +.highlight .mf { color: #FF6600 } /* Literal.Number.Float */ +.highlight .mh { color: #FF6600 } /* Literal.Number.Hex */ +.highlight .mi { color: #FF6600 } /* Literal.Number.Integer */ +.highlight .mo { color: #FF6600 } /* Literal.Number.Oct */ +.highlight .sb { color: #CC3300 } /* Literal.String.Backtick */ +.highlight .sc { color: #CC3300 } /* Literal.String.Char */ +.highlight .sd { color: #CC3300; font-style: italic } /* Literal.String.Doc */ +.highlight .s2 { color: #CC3300 } /* Literal.String.Double */ +.highlight .se { color: #CC3300; font-weight: bold } /* Literal.String.Escape */ +.highlight .sh { color: #CC3300 } /* Literal.String.Heredoc */ +.highlight .si { color: #AA0000 } /* Literal.String.Interpol */ +.highlight .sx { color: #CC3300 } /* Literal.String.Other */ +.highlight .sr { color: #33AAAA } /* Literal.String.Regex */ +.highlight .s1 { color: #CC3300 } /* Literal.String.Single */ +.highlight .ss { color: #FFCC33 } /* Literal.String.Symbol */ +.highlight .bp { color: #336666 } /* Name.Builtin.Pseudo */ +.highlight .vc { color: #003333 } /* Name.Variable.Class */ +.highlight .vg { color: #003333 } /* Name.Variable.Global */ +.highlight .vi { color: #003333 } /* Name.Variable.Instance */ +.highlight .il { color: #FF6600 } /* Literal.Number.Integer.Long */ + +.type-csharp .highlight .k { color: #0000FF } +.type-csharp .highlight .kt { color: #0000FF } +.type-csharp .highlight .nf { color: #000000; font-weight: normal } +.type-csharp .highlight .nc { color: #2B91AF } +.type-csharp .highlight .nn { color: #000000 } +.type-csharp .highlight .s { color: #A31515 } +.type-csharp .highlight .sc { color: #A31515 } diff --git a/stylesheets/stylesheet.css b/stylesheets/stylesheet.css new file mode 100644 index 0000000..b48c8a8 --- /dev/null +++ b/stylesheets/stylesheet.css @@ -0,0 +1,427 @@ +/******************************************************************************* +Slate Theme for GitHub Pages +by Jason Costello, @jsncostello +*******************************************************************************/ + +@import url(pygment_trac.css); + +/******************************************************************************* +MeyerWeb Reset +*******************************************************************************/ + +html, body, div, span, applet, object, iframe, +h1, h2, h3, h4, h5, h6, p, blockquote, pre, +a, abbr, acronym, address, big, cite, code, +del, dfn, em, img, ins, kbd, q, s, samp, +small, strike, strong, sub, sup, tt, var, +b, u, i, center, +dl, dt, dd, ol, ul, li, +fieldset, form, label, legend, +table, caption, tbody, tfoot, thead, tr, th, td, +article, aside, canvas, details, embed, +figure, figcaption, footer, header, hgroup, +menu, nav, output, ruby, section, summary, +time, mark, audio, video { + margin: 0; + padding: 0; + border: 0; + font: inherit; + vertical-align: baseline; +} + +/* HTML5 display-role reset for older browsers */ +article, aside, details, figcaption, figure, +footer, header, hgroup, menu, nav, section { + display: block; +} + +ol, ul { + list-style: none; +} + +blockquote, q { +} + +table { + border-collapse: collapse; + border-spacing: 0; +} + +/******************************************************************************* +Theme Styles +*******************************************************************************/ + +body { + box-sizing: border-box; + color:#373737; + background: #212121; + font-size: 16px; + font-family: 'Myriad Pro', Calibri, Helvetica, Arial, sans-serif; + line-height: 1.5; + -webkit-font-smoothing: antialiased; +} + +h1, h2, h3, h4, h5, h6 { + margin: 10px 0; + font-weight: 700; + color:#222222; + font-family: 'Lucida Grande', 'Calibri', Helvetica, Arial, sans-serif; + letter-spacing: -1px; +} + +h1 { + font-size: 36px; + font-weight: 700; +} + +h2 { + padding-bottom: 10px; + font-size: 32px; + background: url('../images/bg_hr.png') repeat-x bottom; +} + +h3 { + font-size: 24px; +} + +h4 { + font-size: 21px; +} + +h5 { + font-size: 18px; +} + +h6 { + font-size: 16px; +} + +p { + margin: 10px 0 15px 0; +} + +footer p { + color: #f2f2f2; +} + +a { + text-decoration: none; + color: #007edf; + text-shadow: none; + + transition: color 0.5s ease; + transition: text-shadow 0.5s ease; + -webkit-transition: color 0.5s ease; + -webkit-transition: text-shadow 0.5s ease; + -moz-transition: color 0.5s ease; + -moz-transition: text-shadow 0.5s ease; + -o-transition: color 0.5s ease; + -o-transition: text-shadow 0.5s ease; + -ms-transition: color 0.5s ease; + -ms-transition: text-shadow 0.5s ease; +} + +#main_content a:hover { + color: #0069ba; + text-shadow: #0090ff 0px 0px 2px; +} + +footer a:hover { + color: #43adff; + text-shadow: #0090ff 0px 0px 2px; +} + +em { + font-style: italic; +} + +strong { + font-weight: bold; +} + +img { + position: relative; + margin: 0 auto; + max-width: 739px; + padding: 5px; + margin: 10px 0 10px 0; + border: 1px solid #ebebeb; + + box-shadow: 0 0 5px #ebebeb; + -webkit-box-shadow: 0 0 5px #ebebeb; + -moz-box-shadow: 0 0 5px #ebebeb; + -o-box-shadow: 0 0 5px #ebebeb; + -ms-box-shadow: 0 0 5px #ebebeb; +} + +pre, code { + width: 100%; + color: #222; + background-color: #fff; + + font-family: Monaco, "Bitstream Vera Sans Mono", "Lucida Console", Terminal, monospace; + font-size: 14px; + + border-radius: 2px; + -moz-border-radius: 2px; + -webkit-border-radius: 2px; + + + +} + +pre { + width: 100%; + padding: 10px; + box-shadow: 0 0 10px rgba(0,0,0,.1); + overflow: auto; +} + +code { + padding: 3px; + margin: 0 3px; + box-shadow: 0 0 10px rgba(0,0,0,.1); +} + +pre code { + display: block; + box-shadow: none; +} + +blockquote { + color: #666; + margin-bottom: 20px; + padding: 0 0 0 20px; + border-left: 3px solid #bbb; +} + +ul, ol, dl { + margin-bottom: 15px +} + +ul li { + list-style: inside; + padding-left: 20px; +} + +ol li { + list-style: decimal inside; + padding-left: 20px; +} + +dl dt { + font-weight: bold; +} + +dl dd { + padding-left: 20px; + font-style: italic; +} + +dl p { + padding-left: 20px; + font-style: italic; +} + +hr { + height: 1px; + margin-bottom: 5px; + border: none; + background: url('../images/bg_hr.png') repeat-x center; +} + +table { + border: 1px solid #373737; + margin-bottom: 20px; + text-align: left; + } + +th { + font-family: 'Lucida Grande', 'Helvetica Neue', Helvetica, Arial, sans-serif; + padding: 10px; + background: #373737; + color: #fff; + } + +td { + padding: 10px; + border: 1px solid #373737; + } + +form { + background: #f2f2f2; + padding: 20px; +} + +img { + width: 100%; + max-width: 100%; +} + +/******************************************************************************* +Full-Width Styles +*******************************************************************************/ + +.outer { + width: 100%; +} + +.inner { + position: relative; + max-width: 640px; + padding: 20px 10px; + margin: 0 auto; +} + +#forkme_banner { + display: block; + position: absolute; + top:0; + right: 10px; + z-index: 10; + padding: 10px 50px 10px 10px; + color: #fff; + background: url('../images/blacktocat.png') #0090ff no-repeat 95% 50%; + font-weight: 700; + box-shadow: 0 0 10px rgba(0,0,0,.5); + border-bottom-left-radius: 2px; + border-bottom-right-radius: 2px; +} + +#header_wrap { + background: #212121; + background: -moz-linear-gradient(top, #373737, #212121); + background: -webkit-linear-gradient(top, #373737, #212121); + background: -ms-linear-gradient(top, #373737, #212121); + background: -o-linear-gradient(top, #373737, #212121); + background: linear-gradient(top, #373737, #212121); +} + +#header_wrap .inner { + padding: 50px 10px 30px 10px; +} + +#project_title { + margin: 0; + color: #fff; + font-size: 42px; + font-weight: 700; + text-shadow: #111 0px 0px 10px; +} + +#project_tagline { + color: #fff; + font-size: 24px; + font-weight: 300; + background: none; + text-shadow: #111 0px 0px 10px; +} + +#downloads { + position: absolute; + width: 210px; + z-index: 10; + bottom: -40px; + right: 0; + height: 70px; + background: url('../images/icon_download.png') no-repeat 0% 90%; +} + +.zip_download_link { + display: block; + float: right; + width: 90px; + height:70px; + text-indent: -5000px; + overflow: hidden; + background: url(../images/sprite_download.png) no-repeat bottom left; +} + +.tar_download_link { + display: block; + float: right; + width: 90px; + height:70px; + text-indent: -5000px; + overflow: hidden; + background: url(../images/sprite_download.png) no-repeat bottom right; + margin-left: 10px; +} + +.zip_download_link:hover { + background: url(../images/sprite_download.png) no-repeat top left; +} + +.tar_download_link:hover { + background: url(../images/sprite_download.png) no-repeat top right; +} + +#main_content_wrap { + background: #f2f2f2; + border-top: 1px solid #111; + border-bottom: 1px solid #111; +} + +#main_content { + padding-top: 40px; +} + +#footer_wrap { + background: #212121; +} + + + +/******************************************************************************* +Small Device Styles +*******************************************************************************/ + +@media screen and (max-width: 480px) { + body { + font-size:14px; + } + + #downloads { + display: none; + } + + .inner { + min-width: 320px; + max-width: 480px; + } + + #project_title { + font-size: 32px; + } + + h1 { + font-size: 28px; + } + + h2 { + font-size: 24px; + } + + h3 { + font-size: 21px; + } + + h4 { + font-size: 18px; + } + + h5 { + font-size: 14px; + } + + h6 { + font-size: 12px; + } + + code, pre { + min-width: 320px; + max-width: 480px; + font-size: 11px; + } + +} From aa218f2cbcba218f7f7ac0efcfb97768ea7856b3 Mon Sep 17 00:00:00 2001 From: Midwire Date: Fri, 6 Sep 2013 11:35:52 -0700 Subject: [PATCH 2/6] Create gh-pages branch via GitHub --- index.html | 10 +++++----- params.json | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/index.html b/index.html index 72b0e3b..318974d 100644 --- a/index.html +++ b/index.html @@ -4,11 +4,11 @@ - + - .env (for Bash) + Dot-Env (for Bash) @@ -18,8 +18,8 @@

View on GitHub -

.env (for Bash)

dot env is a cascading Bash environment system for those who work on different hardware and OS environments. Similar to oh-my-zsh but for Bash, and special sauce for those who work 'ssh' on remote machines.

Dot-Env (for Bash)

Don't leave home without your tools!

Download this project as a .zip file @@ -209,7 +209,7 @@

diff --git a/params.json b/params.json index 95d3395..7499334 100644 --- a/params.json +++ b/params.json @@ -1 +1 @@ -{"name":".env (for Bash)","tagline":"dot env is a cascading Bash environment system for those who work on different hardware and OS environments. Similar to oh-my-zsh but for Bash, and special sauce for those who work 'ssh' on remote machines.","body":"# .env\r\n\r\n**Version: 0.3.13**\r\n\r\n.env (Dot-Env) is a comprehensive, cascading Bash environment system. It provides Bash shell-prompt themes, handy functions, aliases, and tools for the Bash power user. Plugins have recently been introduced for extensibility.\r\n\r\nI work on many different machines remotely using SSH. Though I love Z-shell, it does not come standard on most operating systems and has to be installed manually. This can be problematic on Solaris machines. After using Z-shell for a few months I decided to go back to Bash because it comes standard on all operating systems and is usually the default shell.\r\n\r\n## Features ##\r\n\r\n* Built for the command-line guru from the ground up with your remote SSH shell environment in mind.\r\n* Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin)\r\n* Themeable - comes with several themes to beautify your shell prompt, and you can write your own!\r\n* Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and you can write your own!\r\n\r\n## Overview ##\r\n\r\nAfter installing .env locally whenever you start a new command prompt, using whatever terminal program you desire, .env gets loaded like this:\r\n\r\n![Overview](https://raw.github.com/midwire/.env/develop/dot-env-overview.png)\r\n\r\nLastly, your chosen theme gets loaded and you are ready for an awesome Bash session.\r\n\r\n## Install ##\r\n\r\nI recommend you fork the project in GitHub, so that your changes can be easily incorporated back into the tree.\r\n\r\nClone the project into your home directory:\r\n\r\n cd $HOME\r\n git clone git://github.com//.env.git # if you forked it\r\n git clone git://github.com/midwire/.env.git # if you use my repository\r\n\r\nSource it:\r\n\r\n . $HOME/.env/dot-env.sh\r\n\r\n### Load on Login ###\r\n\r\nTo have .env load automatically, execute:\r\n\r\n load_on_login\r\n\r\n... which will add the above source command to your `.bashrc` file.\r\n\r\n### Load on Alias ###\r\n\r\nTo have .env load with an alias, execute:\r\n\r\n load_on_alias\r\n\r\n... which will setup the `ees` alias which will source .env whenever you enter `ees` after logging in. I use this method on all of my remote hosts that are used by other people, besides myself. That way they don't notice any difference when they login unless they run `ees`.\r\n\r\n### Example .bashrc ###\r\n\r\n # Choose your plugins\r\n plugins=\"completion history\"\r\n # Choose a .env theme\r\n theme=sparkr\r\n # Set my home host.\r\n # So that when we login to a remote box our theme can change\r\n # to the remote version with special colors, etc\r\n dot_env_home_host='spark.local'\r\n # Turn this off to avoid the noise on starting a new shell instance\r\n dot_env_verbose=1\r\n # Source the .env environment\r\n [[ -r \"$HOME/.env/dot-env.sh\" ]] && . \"$HOME/.env/dot-env.sh\"\r\n\r\n## Customize your local environment ##\r\n\r\n configthis.env\r\n\r\n... which will create a folder in the `host` directory specifically for your local environment and stub out some empty files that you should customize.\r\n\r\nThe convention is, `$HOME/.env/host/[your-hostname]` directory contains files like these:\r\n\r\n* alias.sh\r\n* env.sh\r\n* functions.sh\r\n* prompt.sh\r\n\r\n... and anything else you wish to customize your own local environment.\r\n\r\nYou can put any `*.sh` files in your host directory that you want, and they will only get sourced when you start a Bash shell on the machine matching the specified hostname directory.\r\n\r\n### Example: ###\r\n\r\nLet's say your hostname is `Harry-Potters-Macbook.local`, and you want to add `/usr/local/bogus` to your path. Here's how you do it:\r\n\r\n configthis.env\r\n\r\nThis command will stub out a few files as examples and `cd` to the directory where they are `$HOME/.env/host/Harry-Potters-Macbook.local`. Now you edit each of those files, and delete the ones you don't need. So, since we are only going to add to the path let's remove the other files, then edit the path.sh file.\r\n\r\n rm alias.sh env.sh functions.sh prompt.sh\r\n\r\nInside `path.sh` add this line:\r\n\r\n pathmunge \"/usr/local/bogus\"\r\n\r\nDone!\r\n\r\nNow you can source those changes `. $HOME/.env/dot-env.sh` and your path will include the new entry. Next time you start a shell it will maintain your path and you'll never have duplicates.\r\n\r\n## Themes ##\r\n\r\n.env themes are located in `$dot_env_path/themes/`. To use a theme set `theme='THEME_NAME'`. e.g.,\r\n\r\n theme='sparkr'\r\n\r\nA variant of the `sparkr` theme is default and will be loaded if no theme is specified. Note that this theme looks best when using the Menlo font.\r\n\r\nPlease send me a pull request if you create your own themes.\r\n\r\n## Other Useful Functions ##\r\n\r\n### Add your SSH key to a remote host ###\r\n\r\n add_ssh_key_to_host [user@]HOSTNAME\r\n\r\n... which will append your public `~/.ssh/id_dsa.pub` key to the host's authorized_keys file and allow you to login without a password.\r\n\r\n### Propagate your copy of .env to other hosts ###\r\n\r\nIf you want to copy your .env to another host, simply type:\r\n\r\n propagate_env_to_host [user@]HOSTNAME\r\n\r\n... which will compress your local .env, copy it to the specified host and decompress it. Then follow the instructions above under \"Load on Login\", or \"Load on Alias\"\r\n\r\nIf you want to customize the remote host environment even further:\r\n\r\n* Run `confighost.env HOSTNAME`\r\n* Edit the newly created environment files\r\n* Then `propagate_env_to_host HOSTNAME`\r\n\r\nTo determine the correct `HOSTNAME` to use for your remote environment make sure you first login to that environment and type `echo $HOSTNAME`.\r\n\r\n## Make it better\r\n\r\nPlease feel free to fork it, branch it, change it and send me a pull request.\r\n\r\nCheers,\r\n\r\n-- Midwire\r\n","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."} \ No newline at end of file +{"name":"Dot-Env (for Bash)","tagline":"Don't leave home without your tools!","body":"# .env\r\n\r\n**Version: 0.3.13**\r\n\r\n.env (Dot-Env) is a comprehensive, cascading Bash environment system. It provides Bash shell-prompt themes, handy functions, aliases, and tools for the Bash power user. Plugins have recently been introduced for extensibility.\r\n\r\nI work on many different machines remotely using SSH. Though I love Z-shell, it does not come standard on most operating systems and has to be installed manually. This can be problematic on Solaris machines. After using Z-shell for a few months I decided to go back to Bash because it comes standard on all operating systems and is usually the default shell.\r\n\r\n## Features ##\r\n\r\n* Built for the command-line guru from the ground up with your remote SSH shell environment in mind.\r\n* Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin)\r\n* Themeable - comes with several themes to beautify your shell prompt, and you can write your own!\r\n* Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and you can write your own!\r\n\r\n## Overview ##\r\n\r\nAfter installing .env locally whenever you start a new command prompt, using whatever terminal program you desire, .env gets loaded like this:\r\n\r\n![Overview](https://raw.github.com/midwire/.env/develop/dot-env-overview.png)\r\n\r\nLastly, your chosen theme gets loaded and you are ready for an awesome Bash session.\r\n\r\n## Install ##\r\n\r\nI recommend you fork the project in GitHub, so that your changes can be easily incorporated back into the tree.\r\n\r\nClone the project into your home directory:\r\n\r\n cd $HOME\r\n git clone git://github.com//.env.git # if you forked it\r\n git clone git://github.com/midwire/.env.git # if you use my repository\r\n\r\nSource it:\r\n\r\n . $HOME/.env/dot-env.sh\r\n\r\n### Load on Login ###\r\n\r\nTo have .env load automatically, execute:\r\n\r\n load_on_login\r\n\r\n... which will add the above source command to your `.bashrc` file.\r\n\r\n### Load on Alias ###\r\n\r\nTo have .env load with an alias, execute:\r\n\r\n load_on_alias\r\n\r\n... which will setup the `ees` alias which will source .env whenever you enter `ees` after logging in. I use this method on all of my remote hosts that are used by other people, besides myself. That way they don't notice any difference when they login unless they run `ees`.\r\n\r\n### Example .bashrc ###\r\n\r\n # Choose your plugins\r\n plugins=\"completion history\"\r\n # Choose a .env theme\r\n theme=sparkr\r\n # Set my home host.\r\n # So that when we login to a remote box our theme can change\r\n # to the remote version with special colors, etc\r\n dot_env_home_host='spark.local'\r\n # Turn this off to avoid the noise on starting a new shell instance\r\n dot_env_verbose=1\r\n # Source the .env environment\r\n [[ -r \"$HOME/.env/dot-env.sh\" ]] && . \"$HOME/.env/dot-env.sh\"\r\n\r\n## Customize your local environment ##\r\n\r\n configthis.env\r\n\r\n... which will create a folder in the `host` directory specifically for your local environment and stub out some empty files that you should customize.\r\n\r\nThe convention is, `$HOME/.env/host/[your-hostname]` directory contains files like these:\r\n\r\n* alias.sh\r\n* env.sh\r\n* functions.sh\r\n* prompt.sh\r\n\r\n... and anything else you wish to customize your own local environment.\r\n\r\nYou can put any `*.sh` files in your host directory that you want, and they will only get sourced when you start a Bash shell on the machine matching the specified hostname directory.\r\n\r\n### Example: ###\r\n\r\nLet's say your hostname is `Harry-Potters-Macbook.local`, and you want to add `/usr/local/bogus` to your path. Here's how you do it:\r\n\r\n configthis.env\r\n\r\nThis command will stub out a few files as examples and `cd` to the directory where they are `$HOME/.env/host/Harry-Potters-Macbook.local`. Now you edit each of those files, and delete the ones you don't need. So, since we are only going to add to the path let's remove the other files, then edit the path.sh file.\r\n\r\n rm alias.sh env.sh functions.sh prompt.sh\r\n\r\nInside `path.sh` add this line:\r\n\r\n pathmunge \"/usr/local/bogus\"\r\n\r\nDone!\r\n\r\nNow you can source those changes `. $HOME/.env/dot-env.sh` and your path will include the new entry. Next time you start a shell it will maintain your path and you'll never have duplicates.\r\n\r\n## Themes ##\r\n\r\n.env themes are located in `$dot_env_path/themes/`. To use a theme set `theme='THEME_NAME'`. e.g.,\r\n\r\n theme='sparkr'\r\n\r\nA variant of the `sparkr` theme is default and will be loaded if no theme is specified. Note that this theme looks best when using the Menlo font.\r\n\r\nPlease send me a pull request if you create your own themes.\r\n\r\n## Other Useful Functions ##\r\n\r\n### Add your SSH key to a remote host ###\r\n\r\n add_ssh_key_to_host [user@]HOSTNAME\r\n\r\n... which will append your public `~/.ssh/id_dsa.pub` key to the host's authorized_keys file and allow you to login without a password.\r\n\r\n### Propagate your copy of .env to other hosts ###\r\n\r\nIf you want to copy your .env to another host, simply type:\r\n\r\n propagate_env_to_host [user@]HOSTNAME\r\n\r\n... which will compress your local .env, copy it to the specified host and decompress it. Then follow the instructions above under \"Load on Login\", or \"Load on Alias\"\r\n\r\nIf you want to customize the remote host environment even further:\r\n\r\n* Run `confighost.env HOSTNAME`\r\n* Edit the newly created environment files\r\n* Then `propagate_env_to_host HOSTNAME`\r\n\r\nTo determine the correct `HOSTNAME` to use for your remote environment make sure you first login to that environment and type `echo $HOSTNAME`.\r\n\r\n## Make it better\r\n\r\nPlease feel free to fork it, branch it, change it and send me a pull request.\r\n\r\nCheers,\r\n\r\n-- Midwire\r\n","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."} \ No newline at end of file From 87eb6454cfaa67bcb0585142c2d354b98a616b17 Mon Sep 17 00:00:00 2001 From: Midwire Date: Fri, 6 Sep 2013 12:54:50 -0700 Subject: [PATCH 3/6] Create gh-pages branch via GitHub --- index.html | 34 +++++++++++++++++++++++++++------- params.json | 2 +- 2 files changed, 28 insertions(+), 8 deletions(-) diff --git a/index.html b/index.html index 318974d..3b4cbd1 100644 --- a/index.html +++ b/index.html @@ -34,17 +34,17 @@

Don't leave home without your tools!

.env

Version: 0.3.13

Version: 0.3.14

.env (Dot-Env) is a comprehensive, cascading Bash environment system. It provides Bash shell-prompt themes, handy functions, aliases, and tools for the Bash power user.

I work on many different machines remotely using SSH. Though I love Z-shell, it does not come standard on most operating systems and has to be installed manually. This can be problematic on Solaris machines or any environment where you don't have rights to install new software. After using Z-shell for a few months I decided to go back to Bash because it comes standard on all operating systems and is usually the default shell.

Features

Built for the command-line guru from the ground up with your remote SSH shell environment in mind.
Built for the command-line operator from the ground up with remote SSH shell environments in mind.
Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin)
Themeable - comes with several themes to beautify your shell prompt, and you can write your own!
Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and you can write your own!

I recommend you fork the project in GitHub, so that your changes can be easily incorporated back into the tree.
+

+Forked Installation

First, click on the "Fork" button on the github homepage: https://github.com/midwire/.env.

Clone the project into your home directory:

cd $HOME
-git clone git://github.com/<your github username>/.env.git  # if you forked it
-git clone git://github.com/midwire/.env.git                 # if you use my repository
+git clone git://github.com/<your github username>/.env.git
+

Source it:

. $HOME/.env/dot-env.sh
+

+Standard Installation

cd $HOME
+git clone git://github.com/midwire/.env.git

Source it:

# Choose your plugins
 plugins="completion history"
+
 # Choose a .env theme
 theme=sparkr
+
 # Set my home host.
 # So that when we login to a remote box our theme can change
 # to the remote version with special colors, etc
 dot_env_home_host='spark.local'
-# Turn this off to avoid the noise on starting a new shell instance
+
+# Set this to zero to avoid the verbosity on starting a new shell instance
 dot_env_verbose=1
+
 # Source the .env environment
 [[ -r "$HOME/.env/dot-env.sh" ]] && . "$HOME/.env/dot-env.sh"

diff --git a/params.json b/params.json index 7499334..2d848a6 100644 --- a/params.json +++ b/params.json @@ -1 +1 @@ -{"name":"Dot-Env (for Bash)","tagline":"Don't leave home without your tools!","body":"# .env\r\n\r\n**Version: 0.3.13**\r\n\r\n.env (Dot-Env) is a comprehensive, cascading Bash environment system. It provides Bash shell-prompt themes, handy functions, aliases, and tools for the Bash power user. Plugins have recently been introduced for extensibility.\r\n\r\nI work on many different machines remotely using SSH. Though I love Z-shell, it does not come standard on most operating systems and has to be installed manually. This can be problematic on Solaris machines. After using Z-shell for a few months I decided to go back to Bash because it comes standard on all operating systems and is usually the default shell.\r\n\r\n## Features ##\r\n\r\n* Built for the command-line guru from the ground up with your remote SSH shell environment in mind.\r\n* Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin)\r\n* Themeable - comes with several themes to beautify your shell prompt, and you can write your own!\r\n* Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and you can write your own!\r\n\r\n## Overview ##\r\n\r\nAfter installing .env locally whenever you start a new command prompt, using whatever terminal program you desire, .env gets loaded like this:\r\n\r\n![Overview](https://raw.github.com/midwire/.env/develop/dot-env-overview.png)\r\n\r\nLastly, your chosen theme gets loaded and you are ready for an awesome Bash session.\r\n\r\n## Install ##\r\n\r\nI recommend you fork the project in GitHub, so that your changes can be easily incorporated back into the tree.\r\n\r\nClone the project into your home directory:\r\n\r\n cd $HOME\r\n git clone git://github.com//.env.git # if you forked it\r\n git clone git://github.com/midwire/.env.git # if you use my repository\r\n\r\nSource it:\r\n\r\n . $HOME/.env/dot-env.sh\r\n\r\n### Load on Login ###\r\n\r\nTo have .env load automatically, execute:\r\n\r\n load_on_login\r\n\r\n... which will add the above source command to your `.bashrc` file.\r\n\r\n### Load on Alias ###\r\n\r\nTo have .env load with an alias, execute:\r\n\r\n load_on_alias\r\n\r\n... which will setup the `ees` alias which will source .env whenever you enter `ees` after logging in. I use this method on all of my remote hosts that are used by other people, besides myself. That way they don't notice any difference when they login unless they run `ees`.\r\n\r\n### Example .bashrc ###\r\n\r\n # Choose your plugins\r\n plugins=\"completion history\"\r\n # Choose a .env theme\r\n theme=sparkr\r\n # Set my home host.\r\n # So that when we login to a remote box our theme can change\r\n # to the remote version with special colors, etc\r\n dot_env_home_host='spark.local'\r\n # Turn this off to avoid the noise on starting a new shell instance\r\n dot_env_verbose=1\r\n # Source the .env environment\r\n [[ -r \"$HOME/.env/dot-env.sh\" ]] && . \"$HOME/.env/dot-env.sh\"\r\n\r\n## Customize your local environment ##\r\n\r\n configthis.env\r\n\r\n... which will create a folder in the `host` directory specifically for your local environment and stub out some empty files that you should customize.\r\n\r\nThe convention is, `$HOME/.env/host/[your-hostname]` directory contains files like these:\r\n\r\n* alias.sh\r\n* env.sh\r\n* functions.sh\r\n* prompt.sh\r\n\r\n... and anything else you wish to customize your own local environment.\r\n\r\nYou can put any `*.sh` files in your host directory that you want, and they will only get sourced when you start a Bash shell on the machine matching the specified hostname directory.\r\n\r\n### Example: ###\r\n\r\nLet's say your hostname is `Harry-Potters-Macbook.local`, and you want to add `/usr/local/bogus` to your path. Here's how you do it:\r\n\r\n configthis.env\r\n\r\nThis command will stub out a few files as examples and `cd` to the directory where they are `$HOME/.env/host/Harry-Potters-Macbook.local`. Now you edit each of those files, and delete the ones you don't need. So, since we are only going to add to the path let's remove the other files, then edit the path.sh file.\r\n\r\n rm alias.sh env.sh functions.sh prompt.sh\r\n\r\nInside `path.sh` add this line:\r\n\r\n pathmunge \"/usr/local/bogus\"\r\n\r\nDone!\r\n\r\nNow you can source those changes `. $HOME/.env/dot-env.sh` and your path will include the new entry. Next time you start a shell it will maintain your path and you'll never have duplicates.\r\n\r\n## Themes ##\r\n\r\n.env themes are located in `$dot_env_path/themes/`. To use a theme set `theme='THEME_NAME'`. e.g.,\r\n\r\n theme='sparkr'\r\n\r\nA variant of the `sparkr` theme is default and will be loaded if no theme is specified. Note that this theme looks best when using the Menlo font.\r\n\r\nPlease send me a pull request if you create your own themes.\r\n\r\n## Other Useful Functions ##\r\n\r\n### Add your SSH key to a remote host ###\r\n\r\n add_ssh_key_to_host [user@]HOSTNAME\r\n\r\n... which will append your public `~/.ssh/id_dsa.pub` key to the host's authorized_keys file and allow you to login without a password.\r\n\r\n### Propagate your copy of .env to other hosts ###\r\n\r\nIf you want to copy your .env to another host, simply type:\r\n\r\n propagate_env_to_host [user@]HOSTNAME\r\n\r\n... which will compress your local .env, copy it to the specified host and decompress it. Then follow the instructions above under \"Load on Login\", or \"Load on Alias\"\r\n\r\nIf you want to customize the remote host environment even further:\r\n\r\n* Run `confighost.env HOSTNAME`\r\n* Edit the newly created environment files\r\n* Then `propagate_env_to_host HOSTNAME`\r\n\r\nTo determine the correct `HOSTNAME` to use for your remote environment make sure you first login to that environment and type `echo $HOSTNAME`.\r\n\r\n## Make it better\r\n\r\nPlease feel free to fork it, branch it, change it and send me a pull request.\r\n\r\nCheers,\r\n\r\n-- Midwire\r\n","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."} \ No newline at end of file +{"name":"Dot-Env (for Bash)","tagline":"Don't leave home without your tools!","body":"# .env\r\n\r\n**Version: 0.3.14**\r\n\r\n.env (Dot-Env) is a comprehensive, cascading Bash environment system. It provides Bash shell-prompt themes, handy functions, aliases, and tools for the Bash power user.\r\n\r\nI work on many different machines remotely using SSH. Though I love Z-shell, it does not come standard on most operating systems and has to be installed manually. This can be problematic on Solaris machines or any environment where you don't have rights to install new software. After using Z-shell for a few months I decided to go back to Bash because it comes standard on all operating systems and is usually the default shell.\r\n\r\n## Features ##\r\n\r\n* Built for the command-line operator from the ground up with remote SSH shell environments in mind.\r\n* Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin)\r\n* Themeable - comes with several themes to beautify your shell prompt, and you can write your own!\r\n* Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and you can write your own!\r\n\r\n## Overview ##\r\n\r\nAfter installing .env locally whenever you start a new command prompt, using whatever terminal program you desire, .env gets loaded like this:\r\n\r\n![Overview](https://raw.github.com/midwire/.env/develop/dot-env-overview.png)\r\n\r\nLastly, your chosen theme gets loaded and you are ready for an awesome Bash session.\r\n\r\n## Install ##\r\n\r\nI recommend you fork the project in GitHub, so that your changes can be easily incorporated back into the tree.\r\n\r\n### Forked Installation ###\r\n\r\nFirst, click on the \"Fork\" button on the github homepage: https://github.com/midwire/.env.\r\n\r\nClone the project into your home directory:\r\n\r\n cd $HOME\r\n git clone git://github.com//.env.git\r\n\r\nSource it:\r\n\r\n . $HOME/.env/dot-env.sh\r\n\r\n### Standard Installation ###\r\n\r\n cd $HOME\r\n git clone git://github.com/midwire/.env.git\r\n\r\nSource it:\r\n\r\n . $HOME/.env/dot-env.sh\r\n\r\n### Load on Login ###\r\n\r\nTo have .env load automatically, execute:\r\n\r\n load_on_login\r\n\r\n... which will add the above source command to your `.bashrc` file.\r\n\r\n### Load on Alias ###\r\n\r\nTo have .env load with an alias, execute:\r\n\r\n load_on_alias\r\n\r\n... which will setup the `ees` alias which will source .env whenever you enter `ees` after logging in. I use this method on all of my remote hosts that are used by other people, besides myself. That way they don't notice any difference when they login unless they run `ees`.\r\n\r\n### Example .bashrc ###\r\n\r\n # Choose your plugins\r\n plugins=\"completion history\"\r\n\r\n # Choose a .env theme\r\n theme=sparkr\r\n\r\n # Set my home host.\r\n # So that when we login to a remote box our theme can change\r\n # to the remote version with special colors, etc\r\n dot_env_home_host='spark.local'\r\n\r\n # Set this to zero to avoid the verbosity on starting a new shell instance\r\n dot_env_verbose=1\r\n\r\n # Source the .env environment\r\n [[ -r \"$HOME/.env/dot-env.sh\" ]] && . \"$HOME/.env/dot-env.sh\"\r\n\r\n## Customize your local environment ##\r\n\r\n configthis.env\r\n\r\n... which will create a folder in the `host` directory specifically for your local environment and stub out some empty files that you should customize.\r\n\r\nThe convention is, `$HOME/.env/host/[your-hostname]` directory contains files like these:\r\n\r\n* alias.sh\r\n* env.sh\r\n* functions.sh\r\n* prompt.sh\r\n\r\n... and anything else you wish to customize your own local environment.\r\n\r\nYou can put any `*.sh` files in your host directory that you want, and they will only get sourced when you start a Bash shell on the machine matching the specified hostname directory.\r\n\r\n### Example: ###\r\n\r\nLet's say your hostname is `Harry-Potters-Macbook.local`, and you want to add `/usr/local/bogus` to your path. Here's how you do it:\r\n\r\n configthis.env\r\n\r\nThis command will stub out a few files as examples and `cd` to the directory where they are `$HOME/.env/host/Harry-Potters-Macbook.local`. Now you edit each of those files, and delete the ones you don't need. So, since we are only going to add to the path let's remove the other files, then edit the path.sh file.\r\n\r\n rm alias.sh env.sh functions.sh prompt.sh\r\n\r\nInside `path.sh` add this line:\r\n\r\n pathmunge \"/usr/local/bogus\"\r\n\r\nDone!\r\n\r\nNow you can source those changes `. $HOME/.env/dot-env.sh` and your path will include the new entry. Next time you start a shell it will maintain your path and you'll never have duplicates.\r\n\r\n## Themes ##\r\n\r\n.env themes are located in `$dot_env_path/themes/`. To use a theme set `theme='THEME_NAME'`. e.g.,\r\n\r\n theme='sparkr'\r\n\r\nA variant of the `sparkr` theme is default and will be loaded if no theme is specified. Note that this theme looks best when using the Menlo font.\r\n\r\nPlease send me a pull request if you create your own themes.\r\n\r\n## Other Useful Functions ##\r\n\r\n### Add your SSH key to a remote host ###\r\n\r\n add_ssh_key_to_host [user@]HOSTNAME\r\n\r\n... which will append your public `~/.ssh/id_dsa.pub` key to the host's authorized_keys file and allow you to login without a password.\r\n\r\n### Propagate your copy of .env to other hosts ###\r\n\r\nIf you want to copy your .env to another host, simply type:\r\n\r\n propagate_env_to_host [user@]HOSTNAME\r\n\r\n... which will compress your local .env, copy it to the specified host and decompress it. Then follow the instructions above under \"Load on Login\", or \"Load on Alias\"\r\n\r\nIf you want to customize the remote host environment even further:\r\n\r\n* Run `confighost.env HOSTNAME`\r\n* Edit the newly created environment files\r\n* Then `propagate_env_to_host HOSTNAME`\r\n\r\nTo determine the correct `HOSTNAME` to use for your remote environment make sure you first login to that environment and type `echo $HOSTNAME`.\r\n\r\n## Make it better\r\n\r\nPlease feel free to fork it, branch it, change it and send me a pull request.\r\n\r\nCheers,\r\n\r\n-- Midwire\r\n","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."} \ No newline at end of file From 5df5cdb1d7d5ca4facd1b7dc194d9f0a871ddcfa Mon Sep 17 00:00:00 2001 From: Chris Blackburn Date: Mon, 21 Mar 2016 10:27:31 -0500 Subject: [PATCH 4/6] Create gh-pages branch via GitHub --- images/bkg.png | Bin 0 -> 1218 bytes images/blacktocat.png | Bin 1428 -> 268 bytes index.html | 98 ++++--- params.json | 8 +- stylesheets/github-dark.css | 116 ++++++++ stylesheets/stylesheet.css | 514 ++++++++++++------------------------ 6 files changed, 336 insertions(+), 400 deletions(-) create mode 100644 images/bkg.png create mode 100644 stylesheets/github-dark.css diff --git a/images/bkg.png b/images/bkg.png new file mode 100644 index 0000000000000000000000000000000000000000..d10e5caf1adb7466673bc9cef83621fe855caa3f GIT binary patch literal 1218 zcmeAS@N?(olHy`uVBq!ia0y~yU=jggMrNQ$#TNBtK#DEEC&X1sN=jNkczmscWgJUHsE1R2ws}X9=R$~%X@*3=-vhL@-NfkR)!pBoqVTzzlmJ$gw$h( za!N&gzAjH}?UE-yuB@->I#KvPao+dRzrL@oCvVpee)R8SO|Rip8+r3Dza~8XxNqSP zmGuR0<=?XLN*y=&ko@A*R?n;zmFGjmpL|X=el)GDnT?nCc-hJ9h-*>(U-v7SP21O( zoNu0S!J*))p{S5clIq(!Rnv%W88O`}e-}D7AF~mxZfpV+3kwX-$FQx)Y;JvA%`)@d zWYLYgd8JI0aw{r!Iv89Q>eyImcyRi@1&bblZJ%(NN9SER*F|RI`9Vy^n|kYj&a|m< zH+i{|PR}_n7 z-gd`kwp)J%TC%IUg`6V4t}fWH9jMCX-LAENwM{str7XO1;E!GNEuasI-gOzw-pnlj z>{){B-p0ScV3upi-pM7+*5to^wpdM0Lo6uhXKvGLxTUb-aiDN)U^44#klW=8|4*sV zntfrzKU=lq{IC4u?*i3*Ut)0K@G9flAeW??UW>QI-$6b&yzF|LRw2jj$QO!RxR2R@ z!p-JEk`UjzM%QUGt5 zsq{^Wh=(VtSvB4F14E?hZ{X9Y?R-}fa@G1cS_4|1{K5DvW*TQF%BQWRm-W8rcnHXW5F_LnOa!0te-Gud{_`k1m{6m9unPa(^B$ zKx8W_XRUv@r+&lLzc+3*l|BZA<&8P3LiGe?mL9UxX48rf2YHj@p3l_yh=pvc)~tHC z{nO?fprlo3bGdkWi`e7f5A45eIR!{NSV4~V*iRMLf15OnS&>IfjrQ$5*USNy<-2E*PZ71vSAxg$R}ir z*HrJV2QIesUSGbBCF#9c#svfK2|7o#H8-glPWYpw_zvjL75X#RJY~u`5Y-X(HrD(= zUCM<84_%p-W@|H8MF_Nfy!EQ%2FOzxtQJYFtLINQ#Ng@b=d#Wzp$P!*bu5qo literal 0 HcmV?d00001 diff --git a/images/blacktocat.png b/images/blacktocat.png index 6e264fe57a2e35a2855405ac7d4102c3f6ddcdae..9759d7762ca84fd279f8bd59706641e13c1926f0 100644 GIT binary patch literal 268 zcmV+n0rUQeP)_yxDRcl8_oH}KY@N>TT1a{44=<&$4$p^ zC0ICT$pbdEYvno{KSou>!krh=N_9R{CeAf*BB#+UjGZ;AZi3Y`MhCJsH?yrf4($-OfLDgK%x| SfwxWo0000c-mj#PnPRIHZt82`Ti~3Uk?B!Ylp0*+7m{3+ootz+WN)WnQ(*-(AUCxn zQK2F?C$HG5!d3}vt`(3C64qBz04piUwpD^SD#ABF!8yMuRl!uxKsVXI%s|1+P|wiV z#N6CmN5ROz&_Lh7NZ-&%*U;R`*vQJjKmiJrfVLH-q*(>IxIyg#@@$ndN=gc>^!3Zj z%k|2Q_413-^$jg8EkR}&8R-I5=oVMzl_XZ^<`pZ$OmImpPAEg{v+u2}(t{7puX=A(aKG z`a!A1`K3k4z=%sz23b{L-^Aq1JP;qO z-q+X4Gq1QLF)umQ)5TT^Xo6m5W{Q=eg`=5?o13Glvx}*rp{t>#shg3DvyriZv5}jZ ztD`wguSMv>2~2MaLa!4}y`ZF!TL84#CABECEH%ZgC_h&L>}9J=EN(GzcCm0X zaRr%YgxxI=y(w7S0@dq`Q?EYIG5Vm0MT%&c5HR(CnDAr^T6f1avxRvmvnsN+?-j}Z~1)Zr#rqzrt`edmo44*B<0=C4>mrxHF6$p zVws~UocMfeI`gB8pYMLYTzA87`NOI2w2B*JM5L`^AkN4AFQu&S+6ULTPjv;vzl4& z-eaK_F|D4~l3hzBSF~icNT@MID=v+_X`vpuvf=8+S(|^vlRdHe0<)v-^wiVR3w=TQ)uFA9F z>vmq - - - - + + - + + + - Dot-Env (for Bash) + Dot-Env (for Bash) by midwire - -

- View on GitHub - -

Dot-Env (for Bash)

Don't leave home without your tools!

- -

- Download this project as a .zip file - Download this project as a tar.gz file -

- - -

Dot-Env (for Bash)

Don't leave home without your tools!

+ +

+ Download as .zip + Download as .tar.gz + View on GitHub +

+ +

-.env

+.env

Version: 0.3.14

I work on many different machines remotely using SSH. Though I love Z-shell, it does not come standard on most operating systems and has to be installed manually. This can be problematic on Solaris machines or any environment where you don't have rights to install new software. After using Z-shell for a few months I decided to go back to Bash because it comes standard on all operating systems and is usually the default shell.

-Features

Built for the command-line operator from the ground up with remote SSH shell environments in mind.
Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin)
Themeable - comes with several themes to beautify your shell prompt, and you can write your own!
Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and you can write your own!

-Overview

+ + +

+Overview

After installing .env locally whenever you start a new command prompt, using whatever terminal program you desire, .env gets loaded like this:

@@ -58,12 +57,12 @@

Lastly, your chosen theme gets loaded and you are ready for an awesome Bash session.

-Install

+Install

I recommend you fork the project in GitHub, so that your changes can be easily incorporated back into the tree.

-Forked Installation

+Forked Installation

First, click on the "Fork" button on the github homepage: https://github.com/midwire/.env.

@@ -79,7 +78,7 @@

-Standard Installation

+Standard Installation

cd $HOME
 git clone git://github.com/midwire/.env.git
@@ -91,7 +90,7 @@

-Load on Login

+Load on Login

To have .env load automatically, execute:

@@ -101,7 +100,7 @@

... which will add the above source command to your `.bashrc` file.

-Load on Alias

+Load on Alias

To have .env load with an alias, execute:

@@ -111,7 +110,7 @@

... which will setup the `ees` alias which will source .env whenever you enter `ees` after logging in. I use this method on all of my remote hosts that are used by other people, besides myself. That way they don't notice any difference when they login unless they run `ees`.

-Example .bashrc

+Example .bashrc

# Choose your plugins
 plugins="completion history"
@@ -132,7 +131,7 @@

-Customize your local environment

+Customize your local environment

configthis.env

@@ -146,12 +145,14 @@

env.sh

functions.sh

prompt.sh
-
... and anything else you wish to customize your own local environment.
+ + +
... and anything else you wish to customize your own local environment.

You can put any `*.sh` files in your host directory that you want, and they will only get sourced when you start a Bash shell on the machine matching the specified hostname directory.

-Example:

+Example:

Let's say your hostname is Harry-Potters-Macbook.local, and you want to add /usr/local/bogus to your path. Here's how you do it:

@@ -173,7 +174,7 @@

Now you can source those changes `. $HOME/.env/dot-env.sh` and your path will include the new entry. Next time you start a shell it will maintain your path and you'll never have duplicates.

-Themes

+Themes

.env themes are located in $dot_env_path/themes/. To use a theme set theme='THEME_NAME'. e.g.,

@@ -185,10 +186,10 @@

Please send me a pull request if you create your own themes.

-Other Useful Functions

+Other Useful Functions

-Add your SSH key to a remote host

+Add your SSH key to a remote host

add_ssh_key_to_host [user@]HOSTNAME

@@ -196,7 +197,7 @@

... which will append your public `~/.ssh/id_dsa.pub` key to the host's authorized_keys file and allow you to login without a password.

-Propagate your copy of .env to other hosts

+Propagate your copy of .env to other hosts

If you want to copy your .env to another host, simply type:

@@ -213,10 +214,12 @@

Edit the newly created environment files

Then `propagate_env_to_host HOSTNAME`
-
To determine the correct `HOSTNAME` to use for your remote environment make sure you first login to that environment and type `echo $HOSTNAME`.
+ + +
To determine the correct `HOSTNAME` to use for your remote environment make sure you first login to that environment and type `echo $HOSTNAME`.

-Make it better

+Make it better

Please feel free to fork it, branch it, change it and send me a pull request.

@@ -226,15 +229,6 @@

- -

- - diff --git a/params.json b/params.json index 2d848a6..8cbfaaa 100644 --- a/params.json +++ b/params.json @@ -1 +1,7 @@ -{"name":"Dot-Env (for Bash)","tagline":"Don't leave home without your tools!","body":"# .env\r\n\r\n**Version: 0.3.14**\r\n\r\n.env (Dot-Env) is a comprehensive, cascading Bash environment system. It provides Bash shell-prompt themes, handy functions, aliases, and tools for the Bash power user.\r\n\r\nI work on many different machines remotely using SSH. Though I love Z-shell, it does not come standard on most operating systems and has to be installed manually. This can be problematic on Solaris machines or any environment where you don't have rights to install new software. After using Z-shell for a few months I decided to go back to Bash because it comes standard on all operating systems and is usually the default shell.\r\n\r\n## Features ##\r\n\r\n* Built for the command-line operator from the ground up with remote SSH shell environments in mind.\r\n* Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin)\r\n* Themeable - comes with several themes to beautify your shell prompt, and you can write your own!\r\n* Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and you can write your own!\r\n\r\n## Overview ##\r\n\r\nAfter installing .env locally whenever you start a new command prompt, using whatever terminal program you desire, .env gets loaded like this:\r\n\r\n![Overview](https://raw.github.com/midwire/.env/develop/dot-env-overview.png)\r\n\r\nLastly, your chosen theme gets loaded and you are ready for an awesome Bash session.\r\n\r\n## Install ##\r\n\r\nI recommend you fork the project in GitHub, so that your changes can be easily incorporated back into the tree.\r\n\r\n### Forked Installation ###\r\n\r\nFirst, click on the \"Fork\" button on the github homepage: https://github.com/midwire/.env.\r\n\r\nClone the project into your home directory:\r\n\r\n cd $HOME\r\n git clone git://github.com//.env.git\r\n\r\nSource it:\r\n\r\n . $HOME/.env/dot-env.sh\r\n\r\n### Standard Installation ###\r\n\r\n cd $HOME\r\n git clone git://github.com/midwire/.env.git\r\n\r\nSource it:\r\n\r\n . $HOME/.env/dot-env.sh\r\n\r\n### Load on Login ###\r\n\r\nTo have .env load automatically, execute:\r\n\r\n load_on_login\r\n\r\n... which will add the above source command to your `.bashrc` file.\r\n\r\n### Load on Alias ###\r\n\r\nTo have .env load with an alias, execute:\r\n\r\n load_on_alias\r\n\r\n... which will setup the `ees` alias which will source .env whenever you enter `ees` after logging in. I use this method on all of my remote hosts that are used by other people, besides myself. That way they don't notice any difference when they login unless they run `ees`.\r\n\r\n### Example .bashrc ###\r\n\r\n # Choose your plugins\r\n plugins=\"completion history\"\r\n\r\n # Choose a .env theme\r\n theme=sparkr\r\n\r\n # Set my home host.\r\n # So that when we login to a remote box our theme can change\r\n # to the remote version with special colors, etc\r\n dot_env_home_host='spark.local'\r\n\r\n # Set this to zero to avoid the verbosity on starting a new shell instance\r\n dot_env_verbose=1\r\n\r\n # Source the .env environment\r\n [[ -r \"$HOME/.env/dot-env.sh\" ]] && . \"$HOME/.env/dot-env.sh\"\r\n\r\n## Customize your local environment ##\r\n\r\n configthis.env\r\n\r\n... which will create a folder in the `host` directory specifically for your local environment and stub out some empty files that you should customize.\r\n\r\nThe convention is, `$HOME/.env/host/[your-hostname]` directory contains files like these:\r\n\r\n* alias.sh\r\n* env.sh\r\n* functions.sh\r\n* prompt.sh\r\n\r\n... and anything else you wish to customize your own local environment.\r\n\r\nYou can put any `*.sh` files in your host directory that you want, and they will only get sourced when you start a Bash shell on the machine matching the specified hostname directory.\r\n\r\n### Example: ###\r\n\r\nLet's say your hostname is `Harry-Potters-Macbook.local`, and you want to add `/usr/local/bogus` to your path. Here's how you do it:\r\n\r\n configthis.env\r\n\r\nThis command will stub out a few files as examples and `cd` to the directory where they are `$HOME/.env/host/Harry-Potters-Macbook.local`. Now you edit each of those files, and delete the ones you don't need. So, since we are only going to add to the path let's remove the other files, then edit the path.sh file.\r\n\r\n rm alias.sh env.sh functions.sh prompt.sh\r\n\r\nInside `path.sh` add this line:\r\n\r\n pathmunge \"/usr/local/bogus\"\r\n\r\nDone!\r\n\r\nNow you can source those changes `. $HOME/.env/dot-env.sh` and your path will include the new entry. Next time you start a shell it will maintain your path and you'll never have duplicates.\r\n\r\n## Themes ##\r\n\r\n.env themes are located in `$dot_env_path/themes/`. To use a theme set `theme='THEME_NAME'`. e.g.,\r\n\r\n theme='sparkr'\r\n\r\nA variant of the `sparkr` theme is default and will be loaded if no theme is specified. Note that this theme looks best when using the Menlo font.\r\n\r\nPlease send me a pull request if you create your own themes.\r\n\r\n## Other Useful Functions ##\r\n\r\n### Add your SSH key to a remote host ###\r\n\r\n add_ssh_key_to_host [user@]HOSTNAME\r\n\r\n... which will append your public `~/.ssh/id_dsa.pub` key to the host's authorized_keys file and allow you to login without a password.\r\n\r\n### Propagate your copy of .env to other hosts ###\r\n\r\nIf you want to copy your .env to another host, simply type:\r\n\r\n propagate_env_to_host [user@]HOSTNAME\r\n\r\n... which will compress your local .env, copy it to the specified host and decompress it. Then follow the instructions above under \"Load on Login\", or \"Load on Alias\"\r\n\r\nIf you want to customize the remote host environment even further:\r\n\r\n* Run `confighost.env HOSTNAME`\r\n* Edit the newly created environment files\r\n* Then `propagate_env_to_host HOSTNAME`\r\n\r\nTo determine the correct `HOSTNAME` to use for your remote environment make sure you first login to that environment and type `echo $HOSTNAME`.\r\n\r\n## Make it better\r\n\r\nPlease feel free to fork it, branch it, change it and send me a pull request.\r\n\r\nCheers,\r\n\r\n-- Midwire\r\n","google":"","note":"Don't delete this file! It's used internally to help with page regeneration."} \ No newline at end of file +{ + "name": "Dot-Env (for Bash)", + "tagline": "Don't leave home without your tools!", + "body": "# .env\r\n\r\n**Version: 0.3.14**\r\n\r\n.env (Dot-Env) is a comprehensive, cascading Bash environment system. It provides Bash shell-prompt themes, handy functions, aliases, and tools for the Bash power user.\r\n\r\nI work on many different machines remotely using SSH. Though I love Z-shell, it does not come standard on most operating systems and has to be installed manually. This can be problematic on Solaris machines or any environment where you don't have rights to install new software. After using Z-shell for a few months I decided to go back to Bash because it comes standard on all operating systems and is usually the default shell.\r\n\r\n## Features ##\r\n\r\n* Built for the command-line operator from the ground up with remote SSH shell environments in mind.\r\n* Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin)\r\n* Themeable - comes with several themes to beautify your shell prompt, and you can write your own!\r\n* Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and you can write your own!\r\n\r\n## Overview ##\r\n\r\nAfter installing .env locally whenever you start a new command prompt, using whatever terminal program you desire, .env gets loaded like this:\r\n\r\n![Overview](https://raw.github.com/midwire/.env/develop/dot-env-overview.png)\r\n\r\nLastly, your chosen theme gets loaded and you are ready for an awesome Bash session.\r\n\r\n## Install ##\r\n\r\nI recommend you fork the project in GitHub, so that your changes can be easily incorporated back into the tree.\r\n\r\n### Forked Installation ###\r\n\r\nFirst, click on the \"Fork\" button on the github homepage: https://github.com/midwire/.env.\r\n\r\nClone the project into your home directory:\r\n\r\n cd $HOME\r\n git clone git://github.com//.env.git\r\n\r\nSource it:\r\n\r\n . $HOME/.env/dot-env.sh\r\n\r\n### Standard Installation ###\r\n\r\n cd $HOME\r\n git clone git://github.com/midwire/.env.git\r\n\r\nSource it:\r\n\r\n . $HOME/.env/dot-env.sh\r\n\r\n### Load on Login ###\r\n\r\nTo have .env load automatically, execute:\r\n\r\n load_on_login\r\n\r\n... which will add the above source command to your `.bashrc` file.\r\n\r\n### Load on Alias ###\r\n\r\nTo have .env load with an alias, execute:\r\n\r\n load_on_alias\r\n\r\n... which will setup the `ees` alias which will source .env whenever you enter `ees` after logging in. I use this method on all of my remote hosts that are used by other people, besides myself. That way they don't notice any difference when they login unless they run `ees`.\r\n\r\n### Example .bashrc ###\r\n\r\n # Choose your plugins\r\n plugins=\"completion history\"\r\n\r\n # Choose a .env theme\r\n theme=sparkr\r\n\r\n # Set my home host.\r\n # So that when we login to a remote box our theme can change\r\n # to the remote version with special colors, etc\r\n dot_env_home_host='spark.local'\r\n\r\n # Set this to zero to avoid the verbosity on starting a new shell instance\r\n dot_env_verbose=1\r\n\r\n # Source the .env environment\r\n [[ -r \"$HOME/.env/dot-env.sh\" ]] && . \"$HOME/.env/dot-env.sh\"\r\n\r\n## Customize your local environment ##\r\n\r\n configthis.env\r\n\r\n... which will create a folder in the `host` directory specifically for your local environment and stub out some empty files that you should customize.\r\n\r\nThe convention is, `$HOME/.env/host/[your-hostname]` directory contains files like these:\r\n\r\n* alias.sh\r\n* env.sh\r\n* functions.sh\r\n* prompt.sh\r\n\r\n... and anything else you wish to customize your own local environment.\r\n\r\nYou can put any `*.sh` files in your host directory that you want, and they will only get sourced when you start a Bash shell on the machine matching the specified hostname directory.\r\n\r\n### Example: ###\r\n\r\nLet's say your hostname is `Harry-Potters-Macbook.local`, and you want to add `/usr/local/bogus` to your path. Here's how you do it:\r\n\r\n configthis.env\r\n\r\nThis command will stub out a few files as examples and `cd` to the directory where they are `$HOME/.env/host/Harry-Potters-Macbook.local`. Now you edit each of those files, and delete the ones you don't need. So, since we are only going to add to the path let's remove the other files, then edit the path.sh file.\r\n\r\n rm alias.sh env.sh functions.sh prompt.sh\r\n\r\nInside `path.sh` add this line:\r\n\r\n pathmunge \"/usr/local/bogus\"\r\n\r\nDone!\r\n\r\nNow you can source those changes `. $HOME/.env/dot-env.sh` and your path will include the new entry. Next time you start a shell it will maintain your path and you'll never have duplicates.\r\n\r\n## Themes ##\r\n\r\n.env themes are located in `$dot_env_path/themes/`. To use a theme set `theme='THEME_NAME'`. e.g.,\r\n\r\n theme='sparkr'\r\n\r\nA variant of the `sparkr` theme is default and will be loaded if no theme is specified. Note that this theme looks best when using the Menlo font.\r\n\r\nPlease send me a pull request if you create your own themes.\r\n\r\n## Other Useful Functions ##\r\n\r\n### Add your SSH key to a remote host ###\r\n\r\n add_ssh_key_to_host [user@]HOSTNAME\r\n\r\n... which will append your public `~/.ssh/id_dsa.pub` key to the host's authorized_keys file and allow you to login without a password.\r\n\r\n### Propagate your copy of .env to other hosts ###\r\n\r\nIf you want to copy your .env to another host, simply type:\r\n\r\n propagate_env_to_host [user@]HOSTNAME\r\n\r\n... which will compress your local .env, copy it to the specified host and decompress it. Then follow the instructions above under \"Load on Login\", or \"Load on Alias\"\r\n\r\nIf you want to customize the remote host environment even further:\r\n\r\n* Run `confighost.env HOSTNAME`\r\n* Edit the newly created environment files\r\n* Then `propagate_env_to_host HOSTNAME`\r\n\r\nTo determine the correct `HOSTNAME` to use for your remote environment make sure you first login to that environment and type `echo $HOSTNAME`.\r\n\r\n## Make it better\r\n\r\nPlease feel free to fork it, branch it, change it and send me a pull request.\r\n\r\nCheers,\r\n\r\n-- Midwire\r\n", + "google": "", + "note": "Don't delete this file! It's used internally to help with page regeneration." +} \ No newline at end of file diff --git a/stylesheets/github-dark.css b/stylesheets/github-dark.css new file mode 100644 index 0000000..0c393bf --- /dev/null +++ b/stylesheets/github-dark.css @@ -0,0 +1,116 @@ +/* + Copyright 2014 GitHub Inc. + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + +*/ + +.pl-c /* comment */ { + color: #969896; +} + +.pl-c1 /* constant, markup.raw, meta.diff.header, meta.module-reference, meta.property-name, support, support.constant, support.variable, variable.other.constant */, +.pl-s .pl-v /* string variable */ { + color: #0099cd; +} + +.pl-e /* entity */, +.pl-en /* entity.name */ { + color: #9774cb; +} + +.pl-s .pl-s1 /* string source */, +.pl-smi /* storage.modifier.import, storage.modifier.package, storage.type.java, variable.other, variable.parameter.function */ { + color: #ddd; +} + +.pl-ent /* entity.name.tag */ { + color: #7bcc72; +} + +.pl-k /* keyword, storage, storage.type */ { + color: #cc2372; +} + +.pl-pds /* punctuation.definition.string, string.regexp.character-class */, +.pl-s /* string */, +.pl-s .pl-pse .pl-s1 /* string punctuation.section.embedded source */, +.pl-sr /* string.regexp */, +.pl-sr .pl-cce /* string.regexp constant.character.escape */, +.pl-sr .pl-sra /* string.regexp string.regexp.arbitrary-repitition */, +.pl-sr .pl-sre /* string.regexp source.ruby.embedded */ { + color: #3c66e2; +} + +.pl-v /* variable */ { + color: #fb8764; +} + +.pl-id /* invalid.deprecated */ { + color: #e63525; +} + +.pl-ii /* invalid.illegal */ { + background-color: #e63525; + color: #f8f8f8; +} + +.pl-sr .pl-cce /* string.regexp constant.character.escape */ { + color: #7bcc72; + font-weight: bold; +} + +.pl-ml /* markup.list */ { + color: #c26b2b; +} + +.pl-mh /* markup.heading */, +.pl-mh .pl-en /* markup.heading entity.name */, +.pl-ms /* meta.separator */ { + color: #264ec5; + font-weight: bold; +} + +.pl-mq /* markup.quote */ { + color: #00acac; +} + +.pl-mi /* markup.italic */ { + color: #ddd; + font-style: italic; +} + +.pl-mb /* markup.bold */ { + color: #ddd; + font-weight: bold; +} + +.pl-md /* markup.deleted, meta.diff.header.from-file */ { + background-color: #ffecec; + color: #bd2c00; +} + +.pl-mi1 /* markup.inserted, meta.diff.header.to-file */ { + background-color: #eaffea; + color: #55a532; +} + +.pl-mdr /* meta.diff.range */ { + color: #9774cb; + font-weight: bold; +} + +.pl-mo /* meta.output */ { + color: #264ec5; +} + diff --git a/stylesheets/stylesheet.css b/stylesheets/stylesheet.css index b48c8a8..a54a639 100644 --- a/stylesheets/stylesheet.css +++ b/stylesheets/stylesheet.css @@ -1,427 +1,247 @@ -/******************************************************************************* -Slate Theme for GitHub Pages -by Jason Costello, @jsncostello -*******************************************************************************/ - -@import url(pygment_trac.css); - -/******************************************************************************* -MeyerWeb Reset -*******************************************************************************/ - -html, body, div, span, applet, object, iframe, -h1, h2, h3, h4, h5, h6, p, blockquote, pre, -a, abbr, acronym, address, big, cite, code, -del, dfn, em, img, ins, kbd, q, s, samp, -small, strike, strong, sub, sup, tt, var, -b, u, i, center, -dl, dt, dd, ol, ul, li, -fieldset, form, label, legend, -table, caption, tbody, tfoot, thead, tr, th, td, -article, aside, canvas, details, embed, -figure, figcaption, footer, header, hgroup, -menu, nav, output, ruby, section, summary, -time, mark, audio, video { +body { margin: 0; padding: 0; - border: 0; - font: inherit; - vertical-align: baseline; + background: #151515 url("../images/bkg.png") 0 0; + color: #eaeaea; + font: 16px; + line-height: 1.5; + font-family: Monaco, "Bitstream Vera Sans Mono", "Lucida Console", Terminal, monospace; } -/* HTML5 display-role reset for older browsers */ -article, aside, details, figcaption, figure, -footer, header, hgroup, menu, nav, section { - display: block; -} +/* General & 'Reset' Stuff */ -ol, ul { - list-style: none; +.container { + width: 90%; + max-width: 600px; + margin: 0 auto; } -blockquote, q { +section { + display: block; + margin: 0 0 20px 0; } -table { - border-collapse: collapse; - border-spacing: 0; +h1, h2, h3, h4, h5, h6 { + margin: 0 0 20px; } -/******************************************************************************* -Theme Styles -*******************************************************************************/ - -body { - box-sizing: border-box; - color:#373737; - background: #212121; - font-size: 16px; - font-family: 'Myriad Pro', Calibri, Helvetica, Arial, sans-serif; - line-height: 1.5; - -webkit-font-smoothing: antialiased; +li { + line-height: 1.4 ; } -h1, h2, h3, h4, h5, h6 { - margin: 10px 0; - font-weight: 700; - color:#222222; - font-family: 'Lucida Grande', 'Calibri', Helvetica, Arial, sans-serif; - letter-spacing: -1px; -} +/* Header,

+ header - container + h1 - project name + h2 - project description +*/ -h1 { - font-size: 36px; - font-weight: 700; +header { + background: rgba(0, 0, 0, 0.1); + width: 100%; + border-bottom: 1px dashed #b5e853; + padding: 20px 0; + margin: 0 0 40px 0; } -h2 { - padding-bottom: 10px; - font-size: 32px; - background: url('../images/bg_hr.png') repeat-x bottom; +header h1 { + font-size: 30px; + line-height: 1.5; + margin: 0 0 0 -40px; + font-weight: bold; + font-family: Monaco, "Bitstream Vera Sans Mono", "Lucida Console", Terminal, monospace; + color: #b5e853; + text-shadow: 0 1px 1px rgba(0, 0, 0, 0.1), + 0 0 5px rgba(181, 232, 83, 0.1), + 0 0 10px rgba(181, 232, 83, 0.1); + letter-spacing: -1px; + -webkit-font-smoothing: antialiased; } -h3 { +header h1:before { + content: "./ "; font-size: 24px; } -h4 { - font-size: 21px; -} - -h5 { +header h2 { font-size: 18px; + font-weight: 300; + color: #666; } -h6 { - font-size: 16px; -} - -p { - margin: 10px 0 15px 0; -} - -footer p { - color: #f2f2f2; -} - -a { - text-decoration: none; - color: #007edf; - text-shadow: none; - - transition: color 0.5s ease; - transition: text-shadow 0.5s ease; - -webkit-transition: color 0.5s ease; - -webkit-transition: text-shadow 0.5s ease; - -moz-transition: color 0.5s ease; - -moz-transition: text-shadow 0.5s ease; - -o-transition: color 0.5s ease; - -o-transition: text-shadow 0.5s ease; - -ms-transition: color 0.5s ease; - -ms-transition: text-shadow 0.5s ease; -} - -#main_content a:hover { - color: #0069ba; - text-shadow: #0090ff 0px 0px 2px; -} - -footer a:hover { - color: #43adff; - text-shadow: #0090ff 0px 0px 2px; +#downloads .btn { + display: inline-block; + text-align: center; + margin: 0; } -em { - font-style: italic; -} +/* Main Content +*/ -strong { - font-weight: bold; +#main_content { + width: 100%; + -webkit-font-smoothing: antialiased; } - -img { - position: relative; - margin: 0 auto; - max-width: 739px; - padding: 5px; - margin: 10px 0 10px 0; - border: 1px solid #ebebeb; - - box-shadow: 0 0 5px #ebebeb; - -webkit-box-shadow: 0 0 5px #ebebeb; - -moz-box-shadow: 0 0 5px #ebebeb; - -o-box-shadow: 0 0 5px #ebebeb; - -ms-box-shadow: 0 0 5px #ebebeb; +section img { + max-width: 100% } -pre, code { - width: 100%; - color: #222; - background-color: #fff; - +h1, h2, h3, h4, h5, h6 { + font-weight: normal; font-family: Monaco, "Bitstream Vera Sans Mono", "Lucida Console", Terminal, monospace; - font-size: 14px; - - border-radius: 2px; - -moz-border-radius: 2px; - -webkit-border-radius: 2px; - - - + color: #b5e853; + letter-spacing: -0.03em; + text-shadow: 0 1px 1px rgba(0, 0, 0, 0.1), + 0 0 5px rgba(181, 232, 83, 0.1), + 0 0 10px rgba(181, 232, 83, 0.1); } -pre { - width: 100%; - padding: 10px; - box-shadow: 0 0 10px rgba(0,0,0,.1); - overflow: auto; -} - -code { - padding: 3px; - margin: 0 3px; - box-shadow: 0 0 10px rgba(0,0,0,.1); +#main_content h1 { + font-size: 30px; } -pre code { - display: block; - box-shadow: none; +#main_content h2 { + font-size: 24px; } -blockquote { - color: #666; - margin-bottom: 20px; - padding: 0 0 0 20px; - border-left: 3px solid #bbb; +#main_content h3 { + font-size: 18px; } -ul, ol, dl { - margin-bottom: 15px +#main_content h4 { + font-size: 14px; } -ul li { - list-style: inside; - padding-left: 20px; +#main_content h5 { + font-size: 12px; + text-transform: uppercase; + margin: 0 0 5px 0; } -ol li { - list-style: decimal inside; - padding-left: 20px; +#main_content h6 { + font-size: 12px; + text-transform: uppercase; + color: #999; + margin: 0 0 5px 0; } -dl dt { +dt { + font-style: italic; font-weight: bold; } -dl dd { - padding-left: 20px; - font-style: italic; +ul li { + list-style: none; } -dl p { - padding-left: 20px; - font-style: italic; +ul li:before { + content: ">>"; + font-family: Monaco, "Bitstream Vera Sans Mono", "Lucida Console", Terminal, monospace; + font-size: 13px; + color: #b5e853; + margin-left: -37px; + margin-right: 21px; + line-height: 16px; } -hr { - height: 1px; - margin-bottom: 5px; - border: none; - background: url('../images/bg_hr.png') repeat-x center; +blockquote { + color: #aaa; + padding-left: 10px; + border-left: 1px dotted #666; } -table { - border: 1px solid #373737; - margin-bottom: 20px; - text-align: left; - } - -th { - font-family: 'Lucida Grande', 'Helvetica Neue', Helvetica, Arial, sans-serif; - padding: 10px; - background: #373737; - color: #fff; - } - -td { +pre { + background: rgba(0, 0, 0, 0.9); + border: 1px solid rgba(255, 255, 255, 0.15); padding: 10px; - border: 1px solid #373737; - } - -form { - background: #f2f2f2; - padding: 20px; -} - -img { - width: 100%; - max-width: 100%; + font-size: 14px; + color: #b5e853; + border-radius: 2px; + -moz-border-radius: 2px; + -webkit-border-radius: 2px; + text-wrap: normal; + overflow: auto; + overflow-y: hidden; } -/******************************************************************************* -Full-Width Styles -*******************************************************************************/ - -.outer { +table { width: 100%; + margin: 0 0 20px 0; } -.inner { - position: relative; - max-width: 640px; - padding: 20px 10px; - margin: 0 auto; -} - -#forkme_banner { - display: block; - position: absolute; - top:0; - right: 10px; - z-index: 10; - padding: 10px 50px 10px 10px; - color: #fff; - background: url('../images/blacktocat.png') #0090ff no-repeat 95% 50%; - font-weight: 700; - box-shadow: 0 0 10px rgba(0,0,0,.5); - border-bottom-left-radius: 2px; - border-bottom-right-radius: 2px; -} - -#header_wrap { - background: #212121; - background: -moz-linear-gradient(top, #373737, #212121); - background: -webkit-linear-gradient(top, #373737, #212121); - background: -ms-linear-gradient(top, #373737, #212121); - background: -o-linear-gradient(top, #373737, #212121); - background: linear-gradient(top, #373737, #212121); +th { + text-align: left; + border-bottom: 1px dashed #b5e853; + padding: 5px 10px; } -#header_wrap .inner { - padding: 50px 10px 30px 10px; +td { + padding: 5px 10px; } -#project_title { - margin: 0; - color: #fff; - font-size: 42px; - font-weight: 700; - text-shadow: #111 0px 0px 10px; +hr { + height: 0; + border: 0; + border-bottom: 1px dashed #b5e853; + color: #b5e853; +} + +/* Buttons +*/ + +.btn { + display: inline-block; + background: -webkit-linear-gradient(top, rgba(40, 40, 40, 0.3), rgba(35, 35, 35, 0.3) 50%, rgba(10, 10, 10, 0.3) 50%, rgba(0, 0, 0, 0.3)); + padding: 8px 18px; + border-radius: 50px; + border: 2px solid rgba(0, 0, 0, 0.7); + border-bottom: 2px solid rgba(0, 0, 0, 0.7); + border-top: 2px solid rgba(0, 0, 0, 1); + color: rgba(255, 255, 255, 0.8); + font-family: Helvetica, Arial, sans-serif; + font-weight: bold; + font-size: 13px; + text-decoration: none; + text-shadow: 0 -1px 0 rgba(0, 0, 0, 0.75); + box-shadow: inset 0 1px 0 rgba(255, 255, 255, 0.05); } -#project_tagline { - color: #fff; - font-size: 24px; - font-weight: 300; - background: none; - text-shadow: #111 0px 0px 10px; +.btn:hover { + background: -webkit-linear-gradient(top, rgba(40, 40, 40, 0.6), rgba(35, 35, 35, 0.6) 50%, rgba(10, 10, 10, 0.8) 50%, rgba(0, 0, 0, 0.8)); } -#downloads { - position: absolute; - width: 210px; - z-index: 10; - bottom: -40px; - right: 0; - height: 70px; - background: url('../images/icon_download.png') no-repeat 0% 90%; +.btn .icon { + display: inline-block; + width: 16px; + height: 16px; + margin: 1px 8px 0 0; + float: left; } -.zip_download_link { - display: block; - float: right; - width: 90px; - height:70px; - text-indent: -5000px; - overflow: hidden; - background: url(../images/sprite_download.png) no-repeat bottom left; +.btn-github .icon { + opacity: 0.6; + background: url("../images/blacktocat.png") 0 0 no-repeat; } -.tar_download_link { - display: block; - float: right; - width: 90px; - height:70px; - text-indent: -5000px; - overflow: hidden; - background: url(../images/sprite_download.png) no-repeat bottom right; - margin-left: 10px; -} +/* Links + a, a:hover, a:visited +*/ -.zip_download_link:hover { - background: url(../images/sprite_download.png) no-repeat top left; +a { + color: #63c0f5; + text-shadow: 0 0 5px rgba(104, 182, 255, 0.5); } -.tar_download_link:hover { - background: url(../images/sprite_download.png) no-repeat top right; -} +/* Clearfix */ -#main_content_wrap { - background: #f2f2f2; - border-top: 1px solid #111; - border-bottom: 1px solid #111; +.cf:before, .cf:after { + content:""; + display:table; } -#main_content { - padding-top: 40px; +.cf:after { + clear:both; } -#footer_wrap { - background: #212121; -} - - - -/******************************************************************************* -Small Device Styles -*******************************************************************************/ - -@media screen and (max-width: 480px) { - body { - font-size:14px; - } - - #downloads { - display: none; - } - - .inner { - min-width: 320px; - max-width: 480px; - } - - #project_title { - font-size: 32px; - } - - h1 { - font-size: 28px; - } - - h2 { - font-size: 24px; - } - - h3 { - font-size: 21px; - } - - h4 { - font-size: 18px; - } - - h5 { - font-size: 14px; - } - - h6 { - font-size: 12px; - } - - code, pre { - min-width: 320px; - max-width: 480px; - font-size: 11px; - } - -} +.cf { + zoom:1; +} \ No newline at end of file From 66ff2523e1001d27120ac947b2b9f6b06b84f595 Mon Sep 17 00:00:00 2001 From: Chris Blackburn Date: Mon, 21 Mar 2016 10:47:09 -0500 Subject: [PATCH 5/6] Create gh-pages branch via GitHub --- index.html | 150 +++++++++++++++++++++++++++++++++++----------------- params.json | 2 +- 2 files changed, 103 insertions(+), 49 deletions(-) diff --git a/index.html b/index.html index b044d5e..39e0da4 100644 --- a/index.html +++ b/index.html @@ -29,85 +29,136 @@

Don't leave home without your tools!

-.env

+Bash.env -

Version: 0.3.14

Version: 1.0.0

+ +

Bash.env is a cascading Bash environment system. It provides Bash shell-prompt themes, handy functions, aliases, and tools for the Bash power user.

+ +

Z-shell is great, but it does not come standard on most operating systems. This can be problematic in an environment where you don't have administrative rights.

+ +

Not all development environments are the same. Bash.env lets you customize your Bash environment at 3 levels. Globals load first, then operating system customizations and lastly specifics for the particular host you are working on.

+ + + +

+Bash.env + +
- Features
- Overview
- +Install + +
  +
- +Customize your local environment + +
  - Example:
  +
- Themes
- +Other Useful Functions + +
  - Add your SSH key to a remote host
  - Propagate your copy of Bash.env to other hosts
  +
- Make it better
+

.env (Dot-Env) is a comprehensive, cascading Bash environment system. It provides Bash shell-prompt themes, handy functions, aliases, and tools for the Bash power user.

I work on many different machines remotely using SSH. Though I love Z-shell, it does not come standard on most operating systems and has to be installed manually. This can be problematic on Solaris machines or any environment where you don't have rights to install new software. After using Z-shell for a few months I decided to go back to Bash because it comes standard on all operating systems and is usually the default shell.

Features

Built for the command-line operator from the ground up with remote SSH shell environments in mind.
Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin)
Themeable - comes with several themes to beautify your shell prompt, and you can write your own!
Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and you can write your own!
Built for the Bash command-line operator from the ground up, with remote SSH environments in mind.
Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin). Win-bash or Cygwin may work also but they are untested. +
Themeable - comes with several themes to beautify your shell prompt, and you can write your own.
Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and it is easy to write your own!
Cascades 3-levels of shell customization in order [Global, OS, Host]. Configure specifics for all environments at the Global level. Configure all Linux, OSX and Solaris environments at the OS level. Set specific and detailed customizations at the Host level.

Overview

After installing .env locally whenever you start a new command prompt, using whatever terminal program you desire, .env gets loaded like this:

After installing Bash.env, whenever you start a new command prompt Bash.env gets loaded like this:

Overview

Lastly, your chosen theme gets loaded and you are ready for an awesome Bash session.

Lastly, your chosen theme gets loaded and you are ready for an awesome Bash session!

Install

I recommend you fork the project in GitHub, so that your changes can be easily incorporated back into the tree.

If you fork the project in GitHub your customizations can be easily incorporated back into the master branch here.

-Forked Installation

+Forked Installation (recommended) -

First, click on the "Fork" button on the github homepage: https://github.com/midwire/.env.

First, click on the "Fork" button on the github homepage: https://github.com/midwire/bash.env.

Clone the project into your home directory:

Clone your forked copy into your home directory:

cd $HOME
-git clone git://github.com/<your github username>/.env.git
+git clone git://github.com/<your_github_username>/bash.env.git .env

Source it:

. $HOME/.env/dot-env.sh
+. $HOME/.env/bash.env.sh
 
 
 
 Standard Installation
 
 cd $HOME
-git clone git://github.com/midwire/.env.git
+git clone git://github.com/midwire/bash.env.git .env
 
 
 Source it:
 
-. $HOME/.env/dot-env.sh
+. $HOME/.env/bash.env.sh
 
 
 
 Load on Login
 
-To have .env load automatically, execute:
+To have Bash.env load automatically, execute:
 
-load_on_login
+bash.env load_bash_env_on_login
+# or simply...
+load_on_login
 
 
-... which will add the above source command to your .bashrc file.
+... which will add the above "Source" command to your .bashrc file.
 
 
 Load on Alias
 
-To have .env load with an alias, execute:
+To have Bash.env load with an alias, execute:
 
-load_on_alias
+bash.env load_bash_env_on_alias bashenv
+# or simply...
+load_on_alias bashenv
 
 
-... which will setup the ees alias which will source .env whenever you enter ees after logging in.  I use this method on all of my remote hosts that are used by other people, besides myself.  That way they don't notice any difference when they login unless they run ees.
+... which will setup the bashenv alias which will source Bash.env whenever you enter bashenv after logging in.  Use this method for shared remote accounts that are used by other people. Use any alias name you want in place of bashenv.
 
 
 Example .bashrc
@@ -115,28 +166,27 @@ 
 # Choose your plugins
 plugins="completion history"
 
-# Choose a .env theme
-theme=sparkr
+# Choose a Bash.env theme
+theme=transwarp
 
-# Set my home host.
-# So that when we login to a remote box our theme can change
+# Set home host, so that when we login to a remote box our theme can change
 # to the remote version with special colors, etc
 dot_env_home_host='spark.local'
 
 # Set this to zero to avoid the verbosity on starting a new shell instance
 dot_env_verbose=1
 
-# Source the .env environment
-[[ -r "$HOME/.env/dot-env.sh" ]] && . "$HOME/.env/dot-env.sh"
+# Source the Bash.env environment
+[[ -r "$HOME/.env/bash.env.sh" ]] && . "$HOME/.env/bash.env.sh"
 
 
 

 Customize your local environment
 
-configthis.env
+bash.env config
 
 
-... which will create a folder in the host directory specifically for your local environment and stub out some empty files that you should customize.
+... which will create a folder in the host directory specifically for your local environment and stub out some empty files which you can customize.
 
 The convention is, $HOME/.env/host/[your-hostname] directory contains files like these:
 
@@ -147,21 +197,24 @@ 
 prompt.sh
 
 
-... and anything else you wish to customize your own local environment.
+... and anything else you need to customize your own local environment.
 
 You can put any *.sh files in your host directory that you want, and they will only get sourced when you start a Bash shell on the machine matching the specified hostname directory.
 
+This command, bash.env config is idempotent, so it will not overwrite or otherwise modify any existing files in your host directory.
+
 

 Example:
 
-Let's say your hostname is Harry-Potters-Macbook.local, and you want to add /usr/local/bogus to your path.  Here's how you do it:
+Let's say your hostname is Harry-Potters-Macbook.local, and you want to add /usr/local/bogus to your path every time you startup a Bash session.  Here's how you do it:
 
-configthis.env
+bash.env config
 
 
-This command will stub out a few files as examples and cd to the directory where they are $HOME/.env/host/Harry-Potters-Macbook.local.  Now you edit each of those files, and delete the ones you don't need.  So, since we are only going to add to the path let's remove the other files, then edit the path.sh file.
+This command will stub out a few files as examples in the directory $HOME/.env/host/Harry-Potters-Macbook.local.  Now you can edit each of those files,  delete the ones you don't need and add others if you wish.  So, since we are only going to add to the path let's remove the other files, then edit the path.sh file.
 
-rm alias.sh env.sh functions.sh prompt.sh
+# Optionally, remove these empty files if you don't need them
+rm alias.sh env.sh functions.sh prompt.sh
 
 
 Inside path.sh add this line:
@@ -171,17 +224,18 @@ 
 
 Done!
 
-Now you can source those changes . $HOME/.env/dot-env.sh and your path will include the new entry.  Next time you start a shell it will maintain your path and you'll never have duplicates.
+Now you can source those changes . $HOME/.env/bash.env.sh.  Next time you start a shell it will maintain your path and you'll never have duplicates.
 
 

 Themes
 
-.env themes are located in $dot_env_path/themes/.  To use a theme set theme='THEME_NAME'. e.g.,
+Bash.env themes are located in $dot_env_path/themes/.  To use a theme set theme='THEME_NAME'. e.g.,
 
-theme='sparkr'
+# In $HOME/.bashrc
+theme='transwarp'
 
 
-A variant of the sparkr theme is default and will be loaded if no theme is specified.  Note that this theme looks best when using the Menlo font.
+A variant of the transwarp theme is default and will be loaded if no theme is specified.
 
 Please send me a pull request if you create your own themes.
 
@@ -191,28 +245,28 @@ 
 

 Add your SSH key to a remote host
 
-add_ssh_key_to_host [user@]HOSTNAME
+bash.env add_ssh_key_to [user@]HOSTNAME
 
 
 ... which will append your public ~/.ssh/id_dsa.pub key to the host's authorized_keys file and allow you to login without a password.
 
 
-Propagate your copy of .env to other hosts
+Propagate your copy of Bash.env to other hosts
 
 If you want to copy your .env to another host, simply type:
 
-propagate_env_to_host [user@]HOSTNAME
+bash.env add_bash_env_to [user@]HOSTNAME
 
 
-... which will compress your local .env, copy it to the specified host and decompress it. Then follow the instructions above under "Load on Login", or "Load on Alias"
+... which will compress your local Bash.env, copy it to the specified host and decompress it. Then follow the instructions above under "Load on Login", or "Load on Alias"
 
 If you want to customize the remote host environment even further:
 
 
-Run confighost.env HOSTNAME
+
Run bash.env config_host HOSTNAME
 
 Edit the newly created environment files
-Then propagate_env_to_host HOSTNAME
+
Then bash.env add_bash_env_to HOSTNAME
 
 
 
diff --git a/params.json b/params.json
index 8cbfaaa..5c566f3 100644
--- a/params.json
+++ b/params.json
@@ -1,7 +1,7 @@
 {
   "name": "Dot-Env (for Bash)",
   "tagline": "Don't leave home without your tools!",
-  "body": "# .env\r\n\r\n**Version: 0.3.14**\r\n\r\n.env (Dot-Env) is a comprehensive, cascading Bash environment system.  It provides Bash shell-prompt themes, handy functions, aliases, and tools for the Bash power user.\r\n\r\nI work on many different machines remotely using SSH. Though I love Z-shell, it does not come standard on most operating systems and has to be installed manually.  This can be problematic on Solaris machines or any environment where you don't have rights to install new software.  After using Z-shell for a few months I decided to go back to Bash because it comes standard on all operating systems and is usually the default shell.\r\n\r\n## Features ##\r\n\r\n* Built for the command-line operator from the ground up with remote SSH shell environments in mind.\r\n* Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin)\r\n* Themeable - comes with several themes to beautify your shell prompt, and you can write your own!\r\n* Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and you can write your own!\r\n\r\n## Overview ##\r\n\r\nAfter installing .env locally whenever you start a new command prompt, using whatever terminal program you desire, .env gets loaded like this:\r\n\r\n![Overview](https://raw.github.com/midwire/.env/develop/dot-env-overview.png)\r\n\r\nLastly, your chosen theme gets loaded and you are ready for an awesome Bash session.\r\n\r\n## Install ##\r\n\r\nI recommend you fork the project in GitHub, so that your changes can be easily incorporated back into the tree.\r\n\r\n### Forked Installation ###\r\n\r\nFirst, click on the \"Fork\" button on the github homepage: https://github.com/midwire/.env.\r\n\r\nClone the project into your home directory:\r\n\r\n    cd $HOME\r\n    git clone git://github.com//.env.git\r\n\r\nSource it:\r\n\r\n    . $HOME/.env/dot-env.sh\r\n\r\n### Standard Installation ###\r\n\r\n    cd $HOME\r\n    git clone git://github.com/midwire/.env.git\r\n\r\nSource it:\r\n\r\n    . $HOME/.env/dot-env.sh\r\n\r\n### Load on Login ###\r\n\r\nTo have .env load automatically, execute:\r\n\r\n    load_on_login\r\n\r\n... which will add the above source command to your `.bashrc` file.\r\n\r\n### Load on Alias ###\r\n\r\nTo have .env load with an alias, execute:\r\n\r\n    load_on_alias\r\n\r\n... which will setup the `ees` alias which will source .env whenever you enter `ees` after logging in.  I use this method on all of my remote hosts that are used by other people, besides myself.  That way they don't notice any difference when they login unless they run `ees`.\r\n\r\n### Example .bashrc ###\r\n\r\n    # Choose your plugins\r\n    plugins=\"completion history\"\r\n\r\n    # Choose a .env theme\r\n    theme=sparkr\r\n\r\n    # Set my home host.\r\n    # So that when we login to a remote box our theme can change\r\n    # to the remote version with special colors, etc\r\n    dot_env_home_host='spark.local'\r\n\r\n    # Set this to zero to avoid the verbosity on starting a new shell instance\r\n    dot_env_verbose=1\r\n\r\n    # Source the .env environment\r\n    [[ -r \"$HOME/.env/dot-env.sh\" ]] && . \"$HOME/.env/dot-env.sh\"\r\n\r\n## Customize your local environment ##\r\n\r\n    configthis.env\r\n\r\n... which will create a folder in the `host` directory specifically for your local environment and stub out some empty files that you should customize.\r\n\r\nThe convention is, `$HOME/.env/host/[your-hostname]` directory contains files like these:\r\n\r\n* alias.sh\r\n* env.sh\r\n* functions.sh\r\n* prompt.sh\r\n\r\n... and anything else you wish to customize your own local environment.\r\n\r\nYou can put any `*.sh` files in your host directory that you want, and they will only get sourced when you start a Bash shell on the machine matching the specified hostname directory.\r\n\r\n### Example: ###\r\n\r\nLet's say your hostname is `Harry-Potters-Macbook.local`, and you want to add `/usr/local/bogus` to your path.  Here's how you do it:\r\n\r\n    configthis.env\r\n\r\nThis command will stub out a few files as examples and `cd` to the directory where they are `$HOME/.env/host/Harry-Potters-Macbook.local`.  Now you edit each of those files, and delete the ones you don't need.  So, since we are only going to add to the path let's remove the other files, then edit the path.sh file.\r\n\r\n    rm alias.sh env.sh functions.sh prompt.sh\r\n\r\nInside `path.sh` add this line:\r\n\r\n    pathmunge \"/usr/local/bogus\"\r\n\r\nDone!\r\n\r\nNow you can source those changes `. $HOME/.env/dot-env.sh` and your path will include the new entry.  Next time you start a shell it will maintain your path and you'll never have duplicates.\r\n\r\n## Themes ##\r\n\r\n.env themes are located in `$dot_env_path/themes/`.  To use a theme set `theme='THEME_NAME'`. e.g.,\r\n\r\n    theme='sparkr'\r\n\r\nA variant of the `sparkr` theme is default and will be loaded if no theme is specified.  Note that this theme looks best when using the Menlo font.\r\n\r\nPlease send me a pull request if you create your own themes.\r\n\r\n## Other Useful Functions ##\r\n\r\n### Add your SSH key to a remote host ###\r\n\r\n    add_ssh_key_to_host [user@]HOSTNAME\r\n\r\n... which will append your public `~/.ssh/id_dsa.pub` key to the host's authorized_keys file and allow you to login without a password.\r\n\r\n### Propagate your copy of .env to other hosts ###\r\n\r\nIf you want to copy your .env to another host, simply type:\r\n\r\n    propagate_env_to_host [user@]HOSTNAME\r\n\r\n... which will compress your local .env, copy it to the specified host and decompress it. Then follow the instructions above under \"Load on Login\", or \"Load on Alias\"\r\n\r\nIf you want to customize the remote host environment even further:\r\n\r\n* Run `confighost.env HOSTNAME`\r\n* Edit the newly created environment files\r\n* Then `propagate_env_to_host HOSTNAME`\r\n\r\nTo determine the correct `HOSTNAME` to use for your remote environment make sure you first login to that environment and type `echo $HOSTNAME`.\r\n\r\n## Make it better\r\n\r\nPlease feel free to fork it, branch it, change it and send me a pull request.\r\n\r\nCheers,\r\n\r\n-- Midwire\r\n",
+  "body": "# Bash.env\r\n\r\n**Version: 1.0.0**\r\n\r\n**Bash.env** is a cascading Bash environment system.  It provides Bash shell-prompt themes, handy functions, aliases, and tools for the Bash power user.\r\n\r\nZ-shell is great, but it does not come standard on most operating systems.  This can be problematic in an environment where you don't have administrative rights.\r\n\r\nNot all development environments are the same. **Bash.env** lets you customize your Bash environment at 3 levels. Globals load first, then operating system customizations and lastly specifics for the particular host you are working on.\r\n\r\n\r\n\r\n- [Bash.env](#bashenv)\r\n\t- [Features](#features)\r\n\t- [Overview](#overview)\r\n\t- [Install](#install)\r\n\t\t- [Forked Installation (recommended)](#forked-installation-recommended)\r\n\t\t- [Standard Installation](#standard-installation)\r\n\t\t- [Load on Login](#load-on-login)\r\n\t\t- [Load on Alias](#load-on-alias)\r\n\t\t- [Example .bashrc](#example-bashrc)\r\n\t- [Customize your local environment](#customize-your-local-environment)\r\n\t\t- [Example:](#example)\r\n\t- [Themes](#themes)\r\n\t- [Other Useful Functions](#other-useful-functions)\r\n\t\t- [Add your SSH key to a remote host](#add-your-ssh-key-to-a-remote-host)\r\n\t\t- [Propagate your copy of Bash.env to other hosts](#propagate-your-copy-of-bashenv-to-other-hosts)\r\n\t- [Make it better](#make-it-better)\r\n\r\n\r\n\r\n## Features\r\n\r\n* Built for the Bash command-line operator from the ground up, with remote SSH environments in mind.\r\n* Supports 3 operating systems (Linux, Solaris/SunOS, OSX/Darwin). _Win-bash or Cygwin may work also but they are untested._\r\n* Themeable - comes with several themes to beautify your shell prompt, and you can write your own.\r\n* Extensible - comes with many plugins to enhance your environments and enrich your command-line experience whether remote or local, and it is easy to write your own!\r\n* Cascades 3-levels of shell customization in order [Global, OS, Host]. Configure specifics for all environments at the Global level. Configure all Linux, OSX and Solaris environments at the OS level. Set specific and detailed customizations at the Host level.\r\n\r\n## Overview\r\n\r\nAfter installing **Bash.env**, whenever you start a new command prompt **Bash.env** gets loaded like this:\r\n\r\n![Overview](https://raw.github.com/midwire/.env/develop/overview.png)\r\n\r\nLastly, your chosen theme gets loaded and you are ready for an awesome Bash session!\r\n\r\n## Install\r\n\r\nIf you fork the project in GitHub your customizations can be easily incorporated back into the master branch here.\r\n\r\n### Forked Installation (recommended)\r\n\r\nFirst, click on the \"Fork\" button on the github homepage: [https://github.com/midwire/bash.env](https://github.com/midwire/bash.env).\r\n\r\nClone your forked copy into your home directory:\r\n\r\n    cd $HOME\r\n    git clone git://github.com//bash.env.git .env\r\n\r\nSource it:\r\n\r\n    . $HOME/.env/bash.env.sh\r\n\r\n### Standard Installation\r\n\r\n    cd $HOME\r\n    git clone git://github.com/midwire/bash.env.git .env\r\n\r\nSource it:\r\n\r\n    . $HOME/.env/bash.env.sh\r\n\r\n### Load on Login\r\n\r\nTo have **Bash.env** load automatically, execute:\r\n\r\n    bash.env load_bash_env_on_login\r\n    # or simply...\r\n    load_on_login\r\n\r\n... which will add the above \"Source\" command to your `.bashrc` file.\r\n\r\n### Load on Alias\r\n\r\nTo have **Bash.env** load with an alias, execute:\r\n\r\n    bash.env load_bash_env_on_alias bashenv\r\n    # or simply...\r\n    load_on_alias bashenv\r\n\r\n... which will setup the `bashenv` alias which will source **Bash.env** whenever you enter `bashenv` after logging in.  Use this method for shared remote accounts that are used by other people. Use any alias name you want in place of `bashenv`.\r\n\r\n### Example .bashrc\r\n\r\n    # Choose your plugins\r\n    plugins=\"completion history\"\r\n\r\n    # Choose a Bash.env theme\r\n    theme=transwarp\r\n\r\n    # Set home host, so that when we login to a remote box our theme can change\r\n    # to the remote version with special colors, etc\r\n    dot_env_home_host='spark.local'\r\n\r\n    # Set this to zero to avoid the verbosity on starting a new shell instance\r\n    dot_env_verbose=1\r\n\r\n    # Source the Bash.env environment\r\n    [[ -r \"$HOME/.env/bash.env.sh\" ]] && . \"$HOME/.env/bash.env.sh\"\r\n\r\n## Customize your local environment\r\n\r\n    bash.env config\r\n\r\n... which will create a folder in the `host` directory specifically for your local environment and stub out some empty files which you can customize.\r\n\r\nThe convention is, `$HOME/.env/host/[your-hostname]` directory contains files like these:\r\n\r\n* alias.sh\r\n* env.sh\r\n* functions.sh\r\n* prompt.sh\r\n\r\n... and anything else you need to customize your own local environment.\r\n\r\nYou can put any `*.sh` files in your host directory that you want, and they will only get sourced when you start a Bash shell on the machine matching the specified hostname directory.\r\n\r\nThis command, `bash.env config` is idempotent, so it will not overwrite or otherwise modify any existing files in your host directory.\r\n\r\n### Example:\r\n\r\nLet's say your hostname is `Harry-Potters-Macbook.local`, and you want to add `/usr/local/bogus` to your path every time you startup a Bash session.  Here's how you do it:\r\n\r\n    bash.env config\r\n\r\nThis command will stub out a few files as examples in the directory `$HOME/.env/host/Harry-Potters-Macbook.local`.  Now you can edit each of those files,  delete the ones you don't need and add others if you wish.  So, since we are only going to add to the path let's remove the other files, then edit the path.sh file.\r\n\r\n    # Optionally, remove these empty files if you don't need them\r\n    rm alias.sh env.sh functions.sh prompt.sh\r\n\r\nInside `path.sh` add this line:\r\n\r\n    pathmunge \"/usr/local/bogus\"\r\n\r\nDone!\r\n\r\nNow you can source those changes `. $HOME/.env/bash.env.sh`.  Next time you start a shell it will maintain your path and you'll never have duplicates.\r\n\r\n## Themes\r\n\r\n**Bash.env** themes are located in `$dot_env_path/themes/`.  To use a theme set `theme='THEME_NAME'`. e.g.,\r\n\r\n    # In $HOME/.bashrc\r\n    theme='transwarp'\r\n\r\nA variant of the `transwarp` theme is default and will be loaded if no theme is specified.\r\n\r\nPlease send me a pull request if you create your own themes.\r\n\r\n## Other Useful Functions\r\n\r\n### Add your SSH key to a remote host\r\n\r\n    bash.env add_ssh_key_to [user@]HOSTNAME\r\n\r\n... which will append your public `~/.ssh/id_dsa.pub` key to the host's authorized_keys file and allow you to login without a password.\r\n\r\n### Propagate your copy of Bash.env to other hosts\r\n\r\nIf you want to copy your .env to another host, simply type:\r\n\r\n    bash.env add_bash_env_to [user@]HOSTNAME\r\n\r\n... which will compress your local **Bash.env**, copy it to the specified host and decompress it. Then follow the instructions above under \"Load on Login\", or \"Load on Alias\"\r\n\r\nIf you want to customize the remote host environment even further:\r\n\r\n* Run `bash.env config_host HOSTNAME`\r\n* Edit the newly created environment files\r\n* Then `bash.env add_bash_env_to HOSTNAME`\r\n\r\nTo determine the correct `HOSTNAME` to use for your remote environment make sure you first login to that environment and type `echo $HOSTNAME`.\r\n\r\n## Make it better\r\n\r\nPlease feel free to fork it, branch it, change it and send me a pull request.\r\n\r\nCheers,\r\n\r\n-- Midwire\r\n",
   "google": "",
   "note": "Don't delete this file! It's used internally to help with page regeneration."
 }
\ No newline at end of file

From 88b3d08224e7241471f35610740cbd7d2595c088 Mon Sep 17 00:00:00 2001
From: Chris Blackburn 
Date: Tue, 22 Mar 2016 16:18:38 -0500
Subject: [PATCH 6/6] Update the gh-pages site.

Update gh-pages site to reflect latest README.
---
 .gitignore |  1 +
 index.html | 11 ++++++++---
 2 files changed, 9 insertions(+), 3 deletions(-)
 create mode 100644 .gitignore

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..c70dc2d
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1 @@
+host
diff --git a/index.html b/index.html
index 39e0da4..dadf3be 100644
--- a/index.html
+++ b/index.html
@@ -253,11 +253,16 @@ 
 

 Propagate your copy of Bash.env to other hosts
 
-If you want to copy your .env to another host, simply type:
+If you want to copy your local Bash.env to another host, simply type:
 
 bash.env add_bash_env_to [user@]HOSTNAME
 
 
+or
+
+propagate_env_to_host [user@]HOSTNAME
+
+
 ... which will compress your local Bash.env, copy it to the specified host and decompress it. Then follow the instructions above under "Load on Login", or "Load on Alias"
 
 If you want to customize the remote host environment even further:
@@ -266,7 +271,7 @@ 
 Run bash.env config_host HOSTNAME
 
 Edit the newly created environment files
-Then bash.env add_bash_env_to HOSTNAME
+
Then bash.env add_bash_env_to [user@]HOSTNAME
 
 
 
@@ -283,6 +288,6 @@


 
-    
+

+.env

+Features

+Overview

+Install

+Load on Login

+Load on Alias

+Example .bashrc

+Customize your local environment

+Example:

+Themes

+Other Useful Functions

+Add your SSH key to a remote host

+Propagate your copy of .env to other hosts

+Make it better

-.env

Load on Alias

Example .bashrc

Customize your local environment

Example:

Themes

Add your SSH key to a remote host

-Propagate your copy of .env to other hosts

Propagate your copy of Bash.env to other hosts

Run bash.env config_host HOSTNAME Edit the newly created environment files -Then bash.env add_bash_env_to HOSTNAME +Then bash.env add_bash_env_to [user@]HOSTNAME @@ -283,6 +288,6 @@

Run `bash.env config_host HOSTNAME`

Edit the newly created environment files
-
Then `bash.env add_bash_env_to HOSTNAME` +
Then `bash.env add_bash_env_to [user@]HOSTNAME`
@@ -283,6 +288,6 @@