<commit_before>## SmileysUmbrella

The umbrella contains all (and only) the deployable services that comprise the Smiley's experience.  Setting it up to run locally can be straightforward but be a lot of work the first time probably, as some services may be unfamiliar.


### Smileys

The smileys.pub website.  Contains routing and some logic for the service of the site.


### Smileysapi

The api.smileys.pub api that provides a GraphQL interface to access many of the same features of the site.


### Smileysprocesses

The process service.  This runs Cron style jobs on the same VM as the api and website. Example, it handles post deterioration so that stale content gets lowered.


### Smileysbartools (future)

Site for browsing bartools, the tools used to augment posts and site experience.


### Deployment Tools

Gulp is used to expediate many common tasks particularly for builds and deployment.  Gulp is used in order to keep flexibility high as the setup of which services belong in which EVM's may change in the future.  Other deployment tools may work but for now gulp and some manual labour is in use until enough patterned usage needs emerge.


## Building Releases

The project is first initialized as an umbrella app but as separate releases per app in the exrm style:

### One time requirement
mix release.init --release-per-app

### Only for apps that have static assets (js/css/images):
cd apps/smileys/assets
./node_modules/brunch/bin/brunch b -p

### Back in the base dir of smileys_umbrella:
MIX_ENV=prod mix phoenix.digest

### First release:
MIX_ENV=prod mix release --env=prod --name=smileys
MIX_ENV=prod mix release --env=prod --name=smileysapi
MIX_ENV=prod mix release --env=prod --name=smileyscaretaker

### On subsequent releases:
MIX_ENV=prod mix release --env=prod --upgrade --name=smileys
MIX_ENV=prod mix release --env=prod --upgrade --name=smileysapi
MIX_ENV=prod mix release --env=prod --upgrade --name=smileyscaretaker


### Releasing the releases

TODO


## Smileys Future?
<commit_msg>Another readme fix<commit_after>## SmileysUmbrella

The umbrella contains all (and only) the deployable services that comprise the Smiley's experience.  Setting it up to run locally can be straightforward but be a lot of work the first time probably, as some services may be unfamiliar.


### Smileys

The smileys.pub website.  Contains routing and some logic for the service of the site.


### Smileysapi

The api.smileys.pub api that provides a GraphQL interface to access many of the same features of the site.


### Smileysprocesses

The process service.  This runs Cron style jobs on the same VM as the api and website. Example, it handles post deterioration so that stale content gets lowered.


### Smileysbartools (future)

Site for browsing bartools, the tools used to augment posts and site experience.


### Deployment Tools

Gulp is used to expediate many common tasks particularly for builds and deployment.  Gulp is used in order to keep flexibility high as the setup of which services belong in which EVM's may change in the future.  Other deployment tools may work but for now gulp and some manual labour is in use until enough patterned usage needs emerge.


## Building Releases

The project is first initialized as an umbrella app but as separate releases per app in the exrm style:

### One time requirement
```
mix release.init --release-per-app
```

### Only for apps that have static assets (js/css/images):
```
cd apps/smileys/assets
```
```
./node_modules/brunch/bin/brunch b -p
```

### Back in the base dir of smileys_umbrella:
```
MIX_ENV=prod mix phoenix.digest
```

### First release:
```
MIX_ENV=prod mix release --env=prod --name=smileys
```
```
MIX_ENV=prod mix release --env=prod --name=smileysapi
```
```
MIX_ENV=prod mix release --env=prod --name=smileyscaretaker
```

### On subsequent releases:
```
MIX_ENV=prod mix release --env=prod --upgrade --name=smileys
```
```
MIX_ENV=prod mix release --env=prod --upgrade --name=smileysapi
```
```
MIX_ENV=prod mix release --env=prod --upgrade --name=smileyscaretaker
```


### Releasing the releases

TODO


## Smileys Future?

{'fraction_non_alphanumeric': 0.08182038247397724, 'fraction_numerical': 0.0, 'mean_word_length': 4.250317662007624, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, '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': '1807044', 'n_tokens_mistral': 1235, 'n_tokens_neox': 1141, 'n_words': 550}