<commit_before># markoshust/meteor

Standard Dockerfile for deploying bundled Meteor apps.

## Description

This is a simple onbuild Dockerfile for running Meteor 1.3+ with Docker.

## Versions

The following tags are available, and correspond to the related Node.JS version supported by Meteor:

- `8.8`, `latest`
- `8.4`
- `4.8-1`, `4.8`
- `4.7`
- `4.6`
- `4.5`
- `4.4`
- `0.10`

## Usage

Just create a new `Dockerfile` in the root of your application, specifying the version of Node you want to use:

```
FROM markoshust/meteor:8.8
```

Then, build your Docker image by running:

```
docker build -t foo/bar:1.0.0.0 .
```

## Advanced Usage

Place the [.builddeploy](https://github.com/markoshust/docker-meteor/blob/master/.builddeploy) in the root of your Meteor directory, update it's contents where appropriate, make it executable, then run the command:

```
./.builddeploy production 1.0.0.0
```<commit_msg>Updated README usage with yarn<commit_after># markoshust/meteor

Standard Dockerfile for deploying bundled Meteor apps.

## Description

This is a simple onbuild Dockerfile for running Meteor 1.3+ with Docker.

## Versions

The following tags are available, and correspond to the related Node.JS version supported by Meteor:

- `8.8`, `latest`
- `4.8-1`, `4.8`
- `4.7`
- `4.6`
- `4.5`
- `4.4`
- `0.10`

## Usage

Just create a new `Dockerfile` in the root of your application, specifying the version of Node that your Meteor install is setup to use (find this out with `meteor node --version`):

```
FROM markoshust/meteor:8.8
```

Then, build your Docker image by running:

```
docker build -t foo/bar:1.0.0.0 .
```

This image uses yarn to install node modules, so it is highly recommended to use yarn when developing and installing modules locally. You can do this by running `meteor npm i -g yarn@1.2`, and then use `meteor yarn` instead of `meteor npm install`.

## Advanced Usage

Place the [.builddeploy](https://github.com/markoshust/docker-meteor/blob/master/.builddeploy) in the root of your Meteor directory, update it's contents where appropriate, make it executable, then run the command:

```
./.builddeploy production 1.0.0.0
```
{'fraction_non_alphanumeric': 0.1190365910143585, 'fraction_numerical': 0.029643353404353867, 'mean_word_length': 3.909090909090909, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 4, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3560682', 'n_tokens_mistral': 768, 'n_tokens_neox': 690, 'n_words': 275}