<commit_before>##About
Base Image which can be used to create an image containing an application requiring an X Window Server. When used in conjunction with `suchja/x11-services` the graphical output can be seen via VNC on any computer accessing the containers.

In contrast to several existing solution the focus here is on a strict separation of concerns. This keeps the images small and focused on exactly one task. 

##Usage

**ATTENTION:** This image is currently under development. Especially security is not considered. So please be aware of this when using it. When development is completed, passwords and other security aspects will be documented here.

###Environment Variables
When you run a container based on the `x11-client` image, you should adjust at least some of its configuration.

tbd.

##Maintenance
The image is build on Docker hub with [Automated builds](http://docs.docker.com/docker-hub/builds/). There is no dedicated maintenance schedule for this image. It is relying on packages from `debian:jessie` and thus I do not assume to update it frequently.<commit_msg>Removes section ATTENTION, because development is nearly completed<commit_after>##About
Base Image which can be used to create an image containing an application requiring an X Window Server. When used in conjunction with `suchja/x11-services` the graphical output can be seen via VNC on any computer accessing the containers.

In contrast to several existing solution the focus here is on a strict separation of concerns. This keeps the images small and focused on exactly one task. Therefore there is no X Window client application installed in this image.

More details can be found [here](https://github.com/suchja/x11server/blob/master/Story.md).

##Usage
Use this image in your Dockerfile's `FROM` statement, if you like to create an image running an xclient application like Wine or Firefox.

###Environment Variables
When you run a container based on the `x11-client` image, you should adjust at least some of its configuration.

tbd.

##Maintenance
The image is build on Docker hub with [Automated builds](http://docs.docker.com/docker-hub/builds/). There is no dedicated maintenance schedule for this image. It is relying on packages from `debian:jessie` and thus I do not assume to update it frequently.
{'fraction_non_alphanumeric': 0.052974381241858444, 'fraction_numerical': 0.004342162396873643, 'mean_word_length': 4.731343283582089, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 1, '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': '1610462', 'n_tokens_mistral': 564, 'n_tokens_neox': 532, 'n_words': 333}