<commit_before># yawds

> Yet another Windows development stack environment for unlucky Web developers

`still a beta version`

## About

A modern, complete, portable and configurable Web development software stack environment solution for Windows

If you are a lucky developer, you should use [FrontStack](https://github.com/frontstack/frontstack) instead

## Features

- Easy to use
- Portable
- Automatic packages provisioning
- Fully configurable for your projects
- Complete software stack for modern Web development and testing
- OS dependencies checker
- Auto-configured based on your existent environment variables
- Great isolation from the OS
- Support for environment updates with keeping all the user stuff
- Support both 32 and 64 bits OS
- Support Windows XP or greater
- Easy to use from continous integration servers and deployment environments

## Installation

1. [Download][1] the latest version

2. Uncompress the `zip` wherever you want

3. Run `start.cmd`

4. Put your code in the `workspace/` directory

5. Start coding!

## Software stack

- [Node.js][3]
- [Ruby][4]
- [PhantomJS][5]
- [SlimerJS][6]
- [CasperJS][7]

Aditionally, the following tools binaries are also provided

- cURL
- Putty
- SFTP client
- 7zip
- Bash with *UNIX binaries (port to Win32)

See [PACKAGES][2] file for more information about versions

## Packages

By default, the following packages will be installed in the provisioning process

- bower@latest 
- yeoman@latest
- grunt-cli@latest
- compass@latest

You can configure it from the `package.ini` file

## Update

You can easily uptade the whole software stack automatically when a new version is available

By default, `yawds` checks for new versions on each start, 
however you can do it manually running `update.cmd`

> Note that the environment only will update stack/ directory. 
> All the user configuration or packages installed will remain between updates

## Usage from CI 

To use the isolated environment variables from a continous integration server or
for specific proposal where do you want to use the environment context, you should simply
call from your batch the `use_env.bat` script, located in `~\stack\scripts\`

## Make it yours

If you are a devops guy or an architect, `yawds` allows you to provide and easily configure a development environment for the projects you happy owns<commit_msg>Updating docus<commit_after># yawds

> Yet another Windows development stack environment for unlucky Web developers

`still a beta version`

## About

A modern, complete, portable and configurable Web development software stack environment solution for Windows

If you are a lucky developer, you should use [FrontStack](https://github.com/frontstack/frontstack) instead

## Features

- Easy to use
- Portable
- Automatic packages provisioning
- Fully configurable for your projects
- Complete software stack for modern Web development and testing
- OS dependencies checker
- Auto-configured based on your existent environment variables
- Great isolation from the OS
- Support for environment updates with keeping all the user stuff
- Support both 32 and 64 bits OS
- Support Windows XP or greater
- Easy to use from continous integration servers and deployment environments

## Installation

1. [Download][1] the latest version

2. Uncompress the `zip` wherever you want

3. Run `start.cmd`

4. Put your code in the `workspace/` directory

5. Start coding!

## Software stack

- [Node.js][3]
- [Ruby][4]
- [PhantomJS][5]
- [SlimerJS][6]
- [CasperJS][7]

Aditionally, the following tools binaries are also provided

- cURL
- Putty
- SFTP client
- 7zip
- Bash with *UNIX binaries (port to Win32)

See [PACKAGES][2] file for more information about versions

## Packages

By default, the following packages will be installed in the provisioning process

- bower@latest 
- yeoman@latest
- grunt-cli@latest
- compass@latest

You can configure it from the `package.ini` file

## Update

You can easily uptade the whole software stack automatically when a new version is available

By default, `yawds` checks for new versions on each start, 
however you can do it manually running `update.cmd`

> Note that the environment only will update stack/ directory. 
> All the user configuration or packages installed will remain between updates

## Use the isolated environment context

To use the isolated specific environment context variables from a continous integration server
or for specific purposes, you should simply
call from your batch the `use_env.bat` script, located in `~\stack\scripts\`

## Make it yours

If you are a devops guy or an architect, `yawds` allows you to provide and easily configure a development environment for the projects you happy owns
{'fraction_non_alphanumeric': 0.06100402457106545, 'fraction_numerical': 0.00804914213090447, 'mean_word_length': 4.390410958904109, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 9, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '841545', 'n_tokens_mistral': 1260, 'n_tokens_neox': 1222, 'n_words': 637}