diff --git a/docs/en/1.14.5/publishing.html b/docs/en/1.14.5/publishing.html index eb9659c8ba..bd8b48366c 100644 --- a/docs/en/1.14.5/publishing.html +++ b/docs/en/1.14.5/publishing.html @@ -335,6 +335,37 @@ GH_TOKEN: $(GH_TOKEN) displayName: 'yarn install and build' +

Using Drone

+
    +
  1. Create a new ssh key that will be the deploy key for your project.
    2. +
  2. Name your private and public keys to be specific and so that it does not overwrite your other ssh keys.
    3. +
  3. Go to https://github.com/USERNAME/REPO/settings/keys and add a new deploy key by pasting in our public key you just generated.
    4. +
  4. Open your Drone.io dashboard and login. The URL looks like https://cloud.drone.io/USERNAME/REPO.
    5. +
  5. Click on the repository, click on activate repository, and add a secret called git_deploy_private_key with your private key value that you just generated.
    6. +
  6. Create a .drone.yml on the root of your repository with below text.
    7. +
+
# .drone.yml
+kind: pipeline
+type: docker
+trigger:
+  event:
+    - tag
+- name: Website
+  image: node
+  commands:
+    - mkdir -p $HOME/.ssh
+    - ssh-keyscan -t rsa github.com >> $HOME/.ssh/known_hosts
+    - echo "$GITHUB_PRIVATE_KEY > $HOME/.ssh/id_rsa"
+    - chmod 0600 $HOME/.ssh/id_rsa
+    - cd website
+    - npm i
+    - npm run publish-gh-pages
+  environment:
+    USE_SSH: true
+    GIT_USER: $DRONE_COMMIT_AUTHOR
+    GITHUB_PRIVATE_KEY: git_deploy_private_key
+
+

Now, whenever you push a new tag to github, this trigger will start the drone ci job to publish your website.

Hosting on ZEIT Now

With ZEIT Now, you can deploy your site and connect it to GitHub or GitLab to automatically receive a new deployment every time you push a commit.

Hosting on Netlify

@@ -386,7 +417,7 @@

Alter your siteConfig.js to add a property 'githubHost' which represents the GitHub Enterprise hostname. Alternatively, set an environment variable GITHUB_HOST when executing the publish command.

-
Last updated on 7/24/2020 by Anshul Goyal
← Creating your siteDocker →