Seeker

Appearance

Deployment Steps ​

Walks through how to get a machine ready to have seeker deployed to it as well as how to set up the github action runner

Hardware Reqs ​

  • Digital Ocean style server or better
    • The more compute the better because we read the assets and process metadata so this is faster with a better machine

Software Reqs ​

  • Ubuntu Linux
  • Docker

Machine Setup ​

  • Create an admin user for seeker (Chris)
  • Ensure docker-compose can run
  • Get Domain Setup
    • DNS/CNAME/ANAME etc
  • Get Traefik setup

Repo Setup ​

  • Create a branch for this deployment

Action Runner Setup ​

Google API ​

  • Create a new project seeker-whatever
  • App Name: Seeker - Studio Rendering
  • User Support Email: chrissprance@gmail.com
  • Application Homepage: https://seeker.studiorendering.com
  • Authorized Domain: studiorendering.com
  • Developer Contact Information: chrissprance@gmail.com

Client OAuth ID ​

  • Create a new project and create a Client OAuth ID
md
- name: `Seeker - Studio Rendering`
- Authorized JavaScript origins: `https://seeker.studiorendering.com`
- Authorized redirect URIs: `https://seeker.studiorendering.com/api/auth/callback/google`
  • That will generate a client id and a client secret
    • make sure to update that in .env under GOOGLE_CLIENT_ID & GOOGLE_CLIENT_SECRET

Github API OAuth ​

Network Drive ​

In order for local storage to work there are a few steps that need to be taken if you want to use a network drive:

  • This needs to be added to the /etc/fstab
    • //[SERVER-IP]/[Share] /mnt/[Share] cifs vers=2.0,credentials=/home/[USERNAME]/.smbcredentials 0 0
  • Then you can run: sudo mount /mnt/sonnyash-models
  • We also need to make sure to create a bind mount in the docker-compose.prod.yml file under the backend service
yml
backend:
  ...
  volumes:
    - '/mnt/[SHARE]:/mnt/[SHARE]'
  ...