<commit_before>Standalone Repository Service
==================

Creating a standalone repository service allows you to store and have control over the licensing data that you are publishing into the Copyright Hub (CH) ecosystem.
In order to make that as simple as possible we have created an Amazon Web Services (AWS) Image that you can set up in your AWS with minimal config changes.
In this document we will describe the steps required to get up and running with your own (CH) repository.

Before your start
-----------------------

To fully complete this process you will need to have:
1. An AWS account.
2. A domain with an SSL certificate (e.g. https://copyrighthub.org).
3. The SSL keys for the above certificate.
4. An ssh key to log into the machine you will create (see [here](https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/) for instructions on how to generate ssh keys)



There are three steps to follow:
######  Step 1 - Join the Copyright Hub ecosystem
###### Step 2 - Create a Repository Instance from the AWS Marketplace
###### Step 3 -  Configure the Repository Instance


### Step 1 - Join the Copyright Hub ecosystem

This is currently a process that requires authorisation at every step, so we recommend that you liaise with a CH admin when you are ready to do this, in order to complete the steps in quick succession.

**Go to http://services.copyrighthub.org/** 

**Create an account on http://services.copyrighthub.org/signup**

You will receive an email requesting that you click a link to verify your email address. Note that even after clicking on this link, you may still have to logout of the service.copyrighthub.org system and then re-login in order to fully activate your account.

**Click on "Create a New Organization" and fill in the form.**
<commit_msg>adding instructions for repo from AMI<commit_after>Standalone Repository Service
==================

Creating a standalone repository service allows you to store and have control over the licensing data that you are publishing into the Copyright Hub (CH) ecosystem.
In order to make that as simple as possible we have created an Amazon Web Services (AWS) Image that you can set up in your AWS with minimal config changes.
In this document we will describe the steps required to get up and running with your own (CH) repository.

Before your start
-----------------------

To fully complete this process you will need to have:

1. An AWS account.

2. A domain with an SSL certificate (e.g. https://copyrighthub.org).

3. The SSL keys for the above certificate.

4. An ssh key to log into the machine you will create (see [here](https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/) for instructions on how to generate ssh keys)



There are three steps to follow:
######  Step 1 - Join the Copyright Hub ecosystem
###### Step 2 - Create a Repository Instance from the AWS Marketplace
###### Step 3 -  Configure the Repository Instance


### Step 1 - Join the Copyright Hub ecosystem

This is currently a process that requires authorisation at every step, so we recommend that you liaise with a CH admin when you are ready to do this, in order to complete the steps in quick succession.

**Go to http://services.copyrighthub.org/** 

**Create an account on http://services.copyrighthub.org/signup**

You will receive an email requesting that you click a link to verify your email address. Note that even after clicking on this link, you may still have to logout of the service.copyrighthub.org system and then re-login in order to fully activate your account.

**Click on "Create a New Organization" and fill in the form.**

{'fraction_non_alphanumeric': 0.08455284552845528, 'fraction_numerical': 0.004336043360433604, 'mean_word_length': 3.882275132275132, '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': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4295003', 'n_tokens_mistral': 945, 'n_tokens_neox': 888, 'n_words': 545}