docs: 修改发布文档action和文档地址

.github/workflows/docs.yml

@@ -5,16 +5,39 @@ on:
       - '1.0'
     paths:
       - 'packages/fes-doc/**/**'
+      - 'package.json'
 jobs:
+  # build-and-deploy:
+  #   runs-on: ubuntu-latest
+  #   steps:
+    # - name: Checkout
+    #   uses: actions/checkout@master
+    # - name: Build and Deploy
+    #   uses: JamesIves/github-pages-deploy-action@master
+    #   env:
+    #     ACCESS_TOKEN: ${{ secrets.ACCESS_TOKEN }}
+    #     BRANCH: gh-pages
+    #     FOLDER: packages/fes-doc/docs/.vuepress/dist
+    #     BUILD_SCRIPT: cd packages/fes-doc && npm install && npm run build && cd ../../
   build-and-deploy:
     runs-on: ubuntu-latest
     steps:
     - name: Checkout
-      uses: actions/checkout@master
-    - name: Build and Deploy
-      uses: JamesIves/github-pages-deploy-action@master
+      uses: actions/checkout@v2.3.1
+    
+    - name: Install and Build 🔧 # This example project is built using npm and outputs the result to the 'build' folder. Replace with the commands required to build your project, or remove this step entirely if your site is pre-built.
+      run: cd packages/fes-doc & yarn && yarn build
+
+    - name: Deploy
+      uses: easingthemes/ssh-deploy@main
       env:
-        ACCESS_TOKEN: ${{ secrets.ACCESS_TOKEN }}
-        BRANCH: gh-pages
-        FOLDER: packages/fes-doc/docs/.vuepress/dist
-        BUILD_SCRIPT: cd packages/fes-doc && npm install && npm run build && cd ../../
+        # 本地.ssh文件下的私钥id_rsa，存在secrets的TOKEN中
+        SSH_PRIVATE_KEY: ${{ secrets.HARRYWAN_PRIVATE_KEY }} 
+        # 源目录，相对于$GITHUB_WORKSPACE根目录的路径
+        SOURCE: packages/fes-doc/docs/.vuepress/dist
+        # 服务器域名
+        REMOTE_HOST: ${{ secrets.TX_IP }}
+        # 腾讯云默认用户名为root
+        REMOTE_USER: root 
+        # 目标目录
+        TARGET: /data/web-packages/p/fesjs/1.0

packages/fes-doc/test.md

@@ -27,7 +27,7 @@ fes 主要解决的问题在于：
 ### 对未来的期望
 
 * 分析 fes 构建并进行优化
-  * 不支持高版本的 node
+  * 不支持高版本 node
   * 构建输出需要优化，目前只改一个文件，几乎更新了每一个文件。理论上我只更新一个业务 js，只更新一个 chunk
 * 模块化
   * 目前的实现 page 下面的组件都会解析成 page，但是之前看外包代码的时候，很多外包还是会把页面级别的模块放在 page 下面。