<commit_before>## JuliaBox - Hosted IJulia Containers

Try [JuliaBox](http://www.juliabox.org). Join our [Mailing List](https://groups.google.com/forum/#!forum/julia-box)

Our goal is to make it easy for users of Julia to access and run Julia
anywhere without any fuss. Use Julia through the browser, access tons
of processors and memory, suck in data from anywhere, and have it
always accessible through any device you use so long as it has a
browser.

Currently, the primary usage model is IJulia notebooks. We also have a
shell, and we plan to make it easy to do things such as deploying your
Julia code server-side behind REST APIs, without having to deal with
all the hassle of infrastructure management.

The only constraint is imagination (and server cost).

### Features

- Runs each IJulia session in its own sandboxed container.
- A bash session is also started in the container - can be used to run the Julia console REPL.
- File transfer facility into a session's container.
- File synchronization with remote git repositories &amp; Google Drive.
- Basic admin screen to delete old/inactive sessions.
- Login via. Google authentication.
- Auto cleanup of sessions based on inactivity.
- Ability to limit memory and CPU allocated for user sessions.
- [Packages installed](PACKAGES.md)
<commit_msg>Small README update. Fix #109.<commit_after>## JuliaBox

JuliaBox is hosted online at
[http://www.juliabox.org/](http://www.juliabox.org). Join our [Mailing
List](https://groups.google.com/forum/#!forum/julia-box).

Our goal is to provide the best Julia experience we can. We want to
make it easy for Julia users to run Julia anywhere without too much
fuss. Use Julia through the browser, access lots of processors and
memory, suck in data from anywhere, and have it always accessible
through any device you use so long as it has a browser.

Currently, the primary usage model is IJulia notebooks. We also have a
shell, and we plan to make it easy to do things such as deploying your
Julia code server-side behind REST APIs, without having to deal with
all the hassle of infrastructure management.

The only constraint is imagination (and server cost).

## Features

- Runs each IJulia session in its own sandboxed container.
- A bash session is also started in the container - can be used to run the Julia console REPL.
- File transfer facility into a session's container.
- File synchronization with remote git repositories &amp; Google Drive.
- Basic admin screen to delete old/inactive sessions.
- Login via. Google authentication.
- Auto cleanup of sessions based on inactivity.
- Ability to limit memory and CPU allocated for user sessions.
- [Packages installed](PACKAGES.md)

{'fraction_non_alphanumeric': 0.05982905982905983, 'fraction_numerical': 0.0011148272017837235, 'mean_word_length': 4.186897880539499, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 3, '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': '6731771', 'n_tokens_mistral': 725, 'n_tokens_neox': 683, 'n_words': 393}