<commit_before># Credentials

Credentials for use with GCS will automatically be loaded using [Google
application default credentials][app-default-credentials]. The easiest way to
set this up is using the [gcloud tool][]:

    gcloud auth login

Alternatively, you can set the `GOOGLE_APPLICATION_CREDENTIALS` environment
variable to the path to a JSON key file downloaded from the Google Developers
Console:

    GOOGLE_APPLICATION_CREDENTIALS=/path/to/key.json gcsfuse [...]

[gcloud tool]: https://cloud.google.com/sdk/gcloud/
[app-default-credentials]: https://developers.google.com/identity/protocols/application-default-credentials#howtheywork


# Basic usage

Create the directory into which you want to mount the gcsfuse bucket:

    mkdir /path/to/mount/point

In order to mount the bucket named `my-bucket`, invoke the gcsfuse binary
as follows:

    gcsfuse my-bucket /path/to/mount/point

You should be able to see your bucket contents if you run `ls
/path/to/mount/point`. To later unmount the bucket, either kill the gcsfuse
process with a SIGINT or run `umount /path/to/mount/point`. (On Linux, you may
need to replace `umount` with `fusermount -u`.)


# Running as a daemon

gcsfuse runs as a foreground process, writing log messages to stderr. This
makes it easy to test out and terminate by pressing Ctrl-C, and to redirect its
output to where you like. However, it is common to want to put gcsfuse into the
background, detaching it from the terminal that started it. Advanced users also
want to manage gcsfuse log output, perhaps sending it to syslog.
<commit_msg>Make it clearer that the end user should own the mount point.<commit_after># Credentials

Credentials for use with GCS will automatically be loaded using [Google
application default credentials][app-default-credentials]. The easiest way to
set this up is using the [gcloud tool][]:

    gcloud auth login

Alternatively, you can set the `GOOGLE_APPLICATION_CREDENTIALS` environment
variable to the path to a JSON key file downloaded from the Google Developers
Console:

    GOOGLE_APPLICATION_CREDENTIALS=/path/to/key.json gcsfuse [...]

[gcloud tool]: https://cloud.google.com/sdk/gcloud/
[app-default-credentials]: https://developers.google.com/identity/protocols/application-default-credentials#howtheywork


# Basic usage

As the user that will mount and use the file system, create the directory into
which you want to mount the gcsfuse bucket:

    mkdir /path/to/mount/point

In order to mount the bucket named `my-bucket`, invoke the gcsfuse binary
as follows:

    gcsfuse my-bucket /path/to/mount/point

You should be able to see your bucket contents if you run `ls
/path/to/mount/point`. To later unmount the bucket, either kill the gcsfuse
process with a SIGINT or run `umount /path/to/mount/point`. (On Linux, you may
need to replace `umount` with `fusermount -u`.)


# Running as a daemon

gcsfuse runs as a foreground process, writing log messages to stderr. This
makes it easy to test out and terminate by pressing Ctrl-C, and to redirect its
output to where you like. However, it is common to want to put gcsfuse into the
background, detaching it from the terminal that started it. Advanced users also
want to manage gcsfuse log output, perhaps sending it to syslog.

{'fraction_non_alphanumeric': 0.06672788490970309, 'fraction_numerical': 0.0, 'mean_word_length': 4.339869281045751, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7101786', 'n_tokens_mistral': 954, 'n_tokens_neox': 908, 'n_words': 432}