Setting up tools

• Make sure you have a Github account and you can access the -apps organisation
• Install ‣ on your local machine - you do not need to engage with the tool further directly for now

sudo curl -o /usr/local/bin/cog -L <https://github.com/replicate/cog/releases/latest/download/cog_`uname> -s`_`uname -m`
sudo chmod +x /usr/local/bin/cog

You can learn more about how to use cog and docker here:

GitHub - openlab-apps/lab-reverse_complement at 1-command-line-stage

What is a Container? - Docker

Creating a Fork in a LabDAO controlled repo

• open a fork and move the application to your private repo or openlab-apps (https://github.com/openlab-apps) - get in touch with a maintainer if you have trouble forking the project into openlab-apps due to permission issues.
• rename the repository if needed. Our norms are:
  • all lowercase
  • no spaces
  • underscores _ over hyphens-
• if it is a pre-release repository, you can set the visibility to private, although we recommend building in the open
• clone the repository from Github to your local machine for working on it
• set up a “staging” branch in the Github repo - it is best practice to work on staging only and merge into main

git checkout -b staging
git push --set-upstream origin staging

Dockerising the tool

We have tried working with tools such as ‣ and ‣, but so far have not been able to identify a solution that really works reliably (have not tried hard enough probably).

• create a Dockerfile in the base repo
• commit the introduced Dockerfile to the repo and push changes to Github