General Machine Setup¶
This is setup that needs to be done for multiple types of machines.
Prerequisites¶
- This machine must be running Windows.
- If you're using a Linux machine skip to the setup page of whatever component type it's meant to host.
- You must be okay using chocolatey as your package manager.
Install Chocolatey and Minimal Deps¶
This downloads a minimal install script for chocolatey, git, and python. This step is idempotent and will just do nothing if these are all installed.
-
Open admin powershell and run:
-
Close this powershell terminal and open new ones for future steps.
Download SimpleUAM¶
Get this repo onto the machine somehow, cloning is the default method. If you have a shared drive, placing the repo there will allow local development without constant pushing and pulling.
- Save the repo's final location as:
<repo-root>
Option 1: Clone From Github (HTTP):¶
- Clone from Github via HTTP, replacing
<repo-root>
in the following command:
Option 2: Clone From Github (SSH):¶
- Clone from Github via SSH, replacing
<repo-root>
in the following command:
Option 3: Retrieve From Other Source¶
Details are left to the user.
Initialize Setup Package¶
Initialize pdm and packages for worker setup.
- Navigate an admin powershell to
<repo_root>
. - Setup PDM environment for this repo:
- Test whether setup script was installed:
Result should be a help message showing all of
setup-win
's flags and subcommands.
Get Configuration Directory¶
The configuration directory holds
*.conf.yaml
files that determine how many aspects of a running SimpleUAM system operate.
- Navigate an admin powershell to
<repo_root>
. - Print config directory:
- Save result as
<config-dir>
.
Install Quality of Life Packages (Optional)¶
This installs Firefox, Notepad++, Tess, and other applications that make working on a new windows install more bearable.
- Navigate an admin powershell to
<repo_root>
. - Install the packages:
- Close this powershell terminal and open new ones for future steps.
One of the default QoL packages, Tess, is significantly nicer to use than the native powershell terminal. Consider using it to create an admin powershell instead of the OS-provided terminal.
Setup File Sharing (Optional)¶
If you intend to share files (e.g. results) between workers and clients then set that up now, if you haven't done so already.
If using AWS the instructions for the FSx file share take care of this.
Otherwise shared directory and file server configurations are too varied for us to provide precise instructions. The only real requirement is that worker nodes see the shared file storage as a normal directory.
- Save the shared results directory as
<results-dir>
.
Set up Isis Authentication¶
Various private resources are on git.isis.vanderbilt.edu. So that they aren't made available to the public SimpleUAM will retrieve any non-public information using credentials you provide.
Option 1: Install an API token for git.isis.vanderbilt.edu
(Recommended)¶
We can use an API token to automate some repository and file accesses using Isis that would otherwise require manual authentication.
Create a Personal Access Token¶
- Log into https://git.isis.vanderbilt.edu .
- Save your isis username as:
<isis-auth.user>
- Go to "User Settings" -> "Access Tokens".
- Token Name:
<isis-auth.token-name>
- Expiration Date: 2100-01-01
- Select Scopes:
read_api
: Checkread_repository
: Check- All other others should be unchecked.
- Token Name:
- Click "Create Personal Access Token".
- Save "Your new personal access token" as:
<isis-auth.token>
Configure SimpleUAM to use your token¶
-
Open
<config-dir>/auth.conf.yaml
in a text editor.- Set the
isis_user
field to<isis-auth.user>
- Set the
isis_token
field to<isis-auth.token>
- Set the
Option 2: Install SSH keys for git.isis.vanderbilt.edu
¶
SSH access to Isis, while not strictly necessary, will make future install steps easier and more secure. This doesn't do anything if an API token is already provided.
- Follow the instructions here to set up ssh key based access to the isis server.
Option 3: Skip Authentication¶
If you skip authentication here you will prompted for passwords when cloning repositories and asked to manually download files when needed.
Next Steps¶
Once this setup is complete you can continue to one or more of the following steps. All of the following nodes can coexist on a single windows instance.
Continue to Creo License Server Setup...
Or to Message Broker Setup...
Or to Corpus DB Setup...
Or to Static Corpus Setup...
Or to Worker Node Setup...