龙讯旷腾 pwmat Wiki

本页面只读。您可以查看源文件，但不能更改它。如果您觉得这是系统错误，请联系管理员。
====== Installing the PWstudio CPU version ======

<wrap important>
This page assumes you already have Docker installed (if not, go back to the [[en:pwstudio:start|home page]] and pick the installation chapter for your system). If you're new to this and not yet comfortable with the terminal, we also recommend reading [[en:pwstudio:readme|Read this before installing]] and [[en:pwstudio:mobaxterm|the MobaXterm beginner tutorial]] first.
</wrap>

===== 1. Requirements =====

  * Docker installed (check with ''docker --version'' — if you see a version number, it's installed)

===== 2. Install the server.py service on the host machine =====

Installation instructions: click the link, [[en:pwstudio:server|Installing the server.py service on Linux]], and follow the guide to set up the license service before moving to the next step. This step is what lets you obtain a valid qflow license afterward — don't skip it.

===== 3. Import the image =====

<code bash>
sudo docker pull ccr.ccs.tencentyun.com/lxkt/qflowcpu:latest
</code>

This step downloads the PWstudio CPU image to the server. Depending on your network it may take anywhere from a few minutes to over ten minutes; the terminal will keep showing download progress the whole time, which is normal — please be patient. There's no requirement for which directory you run this from.

===== 4. Start the container =====

<code bash>
sudo docker run -d --name qflowcpu \
  -v /var/tmp/pwmat_host_secret:/var/tmp/pwmat_host_secret:ro \
  --ulimit memlock=-1:-1 --ulimit stack=-1:-1 \
  --shm-size=128G --privileged -e SELINUX=disabled -p 80:80 -p 81:81 -p 2297:2297 -p 5010:5010 \
  --hostname=mstation ccr.ccs.tencentyun.com/lxkt/qflowcpu:latest
</code>

If this succeeds, it will usually print a long string of letters and numbers (the container ID), meaning the container has started. You can use ''docker ps'' to check whether it's running normally (''STATUS'' showing "Up ..." means it's fine).

<WRAP center round todo 10%>
81:81 must not be changed. Port 81 inside the container must be mapped to port 81 on the host machine.

Check which containers are currently running:

<code bash>
docker ps
</code>

Check all containers (running or stopped):

<code bash>
docker ps -a
</code>

After running this you'll see a table. If there's a row with ''qflowcpu'' under ''NAMES'' and ''Up ...'' under ''STATUS'' (e.g. "Up 5 minutes"), the container is running normally.

Before starting a new container, if a container with the same name already exists, you need to stop and remove the old one first:

<code bash>
docker stop qflowcpu
</code>

Remove the old container of the same type:
<code bash>
docker rm qflowcpu
</code>

After stopping and removing it, just run the ''docker run'' command above again.

<WRAP center round alert 60%>
  - Removing a container also removes the data stored inside it❗
  - Qflow workflows stored inside the container cannot be exported
</WRAP>

</WRAP>


===== 5. Logging into the container, uploading/downloading files =====

  * Log in / upload / download via an SSH client<wrap notice>recommended</wrap>

^ Address        ^ Port  ^ Username  ^ Password             ^
| [host IP]  | 2297    | pwmat   | PWmat2022        |
| [host IP]  | 2297    | root    | PWmatSimplyBest  |

In the table above, replace ''[host IP]'' with your server's real IP address — fill in everything else exactly as shown, no changes needed.

<wrap tip>
If you don't yet know how to log in with an SSH client or upload/download files, see this beginner tutorial: [[en:pwstudio:mobaxterm|How to log in to a server and upload/download files with MobaXterm]]
</wrap>

  * Or you can access the container directly with a docker command

<code bash>
docker exec -it qflowcpu bash

# When you're done, exit back to the host
exit
</code>

===== 6. Accessing Qstudio and Qflow =====

From this point on, switch to using a **web browser** (Chrome or Edge recommended) and go to: %%http://[host IP]%%

^ Account ^ Password ^
| 15000000000 | PWmat2022 |

If pasting the password says it's wrong, this may be a browser compatibility issue — just type the password manually instead.

~~DISCUSSION:off~~