sokrypton / sokrypton/ColabFold

About MsaServer issue

Open
#551 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
2.9k
Forks
747
PR merge metrics
No merged PRs in 30d

Description

Hi , I want to build MSA service through MsaServer inside ColabFold, and I want to let other users use localcolabfold to search MSA in the MSA service I built. but I'm having 3 problems.

1, I don't know how to make sure the MSA service is built successfully? Is there any easy way to test it?

2, About the ColabFold/MsaServer/config.json content, it is as follows:

{
    "app": "colabfold",
    "verbose": true,
    "server" : {
        // you might want to change the port
       	"address"    : "127.0.0.0:80",
        "dbmanagment": false,
        "cors"       : true
    },

My server IP is 157.148.21.131, so do I need to change 127.0.0.0 to 157.148.21.131? Does the port always need to be set to 80,and is it possible to change it to another port?

3、To provide external service, do I need to change "ExecStart=/path-to-mmseqs-server-home/msa-server -local -config /path-to-mmseqs-server-home/config.json" in ColabFold/MsaServer/systemd-example-mmseqs-server.service to "ExecStart=/path-to-mmseqs-server-home/msa-server -server -config /path-to-mmseqs-server-home/config.json”

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with ColabFold/MsaServer/config.json and ColabFold/MsaServer/systemd-example-mmseqs-server.service, then trace how the MsaServer is started for local and external use. Define a simple service verification procedure and document the address, port, and service-mode settings needed for localcolabfold clients.

Written by the indexing model from the issue text.

Assessment

Domain
backend, bioinformatics
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.