GitLab

See https://github.com/robbyrussell/oh-my-zsh/issues/7407#issuecomment-441665143

Signed-off-by: Ricardo Seriani <ricardo.seriani@gmail.com>

Fixes #7405

Fixes #7407

FreeBSD's tput needs termcap codes instead of terminfo capnames, so using `tput colors`
has the wrong effect. See #7407

This reverts commit 05b61706.

Fixes #7371
Signed-off-by: Arvindraj <arvindultimate7352@gmail.com>
Co-authored-by: Stephen Ward <stephen@whilenotzero.com>

* Documentation for Npm plugin added

* Fix style and add alias descriptions

* Add Generate Command alias

* Add Create Database alias

* Add Generate Controller alias

* more aliases ^^

Stop exporting AWS_HOME and use the standard AWS_CONFIG_FILE environment
variable, with a fallback to ~/.aws/config (default location) if not
defined.

Close #7356

The environment variable name used to be AWS_DEFAULT_PROFILE but the
CLI documentation now only mentions AWS_PROFILE.

https://docs.aws.amazon.com/cli/latest/userguide/cli-environment.html

It seems like the CLI was the only tool using AWS_DEFAULT_PROFILE, and
all the AWS SDKs used AWS_PROFILE, so they standardized on it.

https://onetechnical.wordpress.com/2016/10/07/the-curious-case-of-aws_default_profile/

Note: still left AWS_DEFAULT_PROFILE on the method to set the profile to
maintain backwards compatibility.

Close #7354

Create stack's plugin README.md

The problem that can occur is ocassionally mvnw will not be executable. This can happen if mvnw is included from an archetype, as unix permissions aren't preserved within the jar they're stored in. Only using mvnw if it exists AND is executable