Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to v0.2.0 #2

Open
Normalnoise opened this issue Sep 22, 2023 · 0 comments
Open

Upgrade to v0.2.0 #2

Normalnoise opened this issue Sep 22, 2023 · 0 comments

Comments

@Normalnoise
Copy link
Member

How to Upgrade:

Scenario 1: Initial Deployment

If you are a newcomer and just getting started, you can follow the guidelines below to install and deploy the Computing Provider.

Scenario 2: Upgrading to v0.2.0

If you are already running version 0.1.0, please follow these steps to upgrade:

  • Step 1: Modify the configuration file config.toml

    • Add the location of your domain's SSL certificate .crt and .key files to the configuration file:

      [LOG]
      CrtFile = "/YOUR_DOMAIN_NAME_CRT_PATH/server.crt"    // Your domain name SSL .crt file path
      KeyFile = "/YOUR_DOMAIN_NAME_KEY_PATH/server.key"    // Your domain name SSL .key file path
      
    • (Optional) Remove [MCS].AccessToken from the configuration file, generate a new [MCS].ApiKey as follows:

      [MCS]
      ApiKey = ""                                   # Acquired from "https://www.multichain.storage" -> setting -> Create API Key
      
  • Step 2: Pull the latest version of the code and compile the Computing Provider

    git clone https://github.com/lagrangedao/go-computing-provider.git
    
    cd go-computing-provider
    
    git checkout v0.2.0
    
    go mod tidy
    
    go build -o computing-provider main.go
    

    Note:

    • You can also directly use precompiled binary files
    • You can check the current version by running ./computing-provider -v
  • Step 3: Start the Computing Provider

    nohup ./computing-provider >> cp.log 2>&1 & 
    

Need Helps

If you encounter any problems, you can either leave a comment within the document or open an issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant