<p>By coincidence, I have found a possible solution via <a href="https://www.edwardthomson.com/blog/github_actions_11_secrets.html" rel="nofollow noreferrer">Github Secrets</a>.</p>

CC BY-SA 4.0
2020-11-19T00:47:06.183Z
GitHub Secrets is indeed the way of doing it, to keep everything in the same place. You could also use an external **deploy** system but that's more work.
Mikael Dúi Bolinder
CC BY-SA 4.0
2020-11-18T19:07:05.363Z
2020-11-18T19:07:05.363Z
Marko A.
<p>I like to start an open-source project via Github where topics (markdown pages) can be created from the community. Via PR the changes get merged to the main repo and then it triggers a Github Action workflow. Inside this workflow, the markdown input gets processed to static HTML pages which should later get deployed to an Nginx web server.</p>
<p>The current (prototyped) deployment is done via <a href="https://github.com/marketplace/actions/scp-files" rel="nofollow noreferrer">SCP for GitHub Actions</a> and <a href="https://github.com/marketplace/actions/ssh-remote-commands" rel="nofollow noreferrer">SSH for GitHub Actions</a>. For both actions, I have to provide the user and password inside the <code>workflow.yml</code> file.</p>
<p>To make the project public I need another approach, where others cannot get the credentials.</p>
<p>How can I realize my idea?</p>

<deployment><continuous-deployment><github><secret-management>
How to deploy static website from public repo via Github Actions to private web server
Marko A.
# How to deploy static website from public repo via Github Actions to private web server

(Asked by: username_0 on 2020-11-18)

I like to start an open-source project via Github where topics (markdown pages) can be created from the community. Via PR the changes get merged to the main repo and then it triggers a Github Action workflow. Inside this workflow, the markdown input gets processed to static HTML pages which should later get deployed to an Nginx web server.

The current (prototyped) deployment is done via [SCP for GitHub Actions](https://github.com/marketplace/actions/scp-files) and [SSH for GitHub Actions](https://github.com/marketplace/actions/ssh-remote-commands). For both actions, I have to provide the user and password inside the `workflow.yml` file.

To make the project public I need another approach, where others cannot get the credentials.

How can I realize my idea?

**Tags:** deployment, continuous-deployment, github, secret-management


---

## 1 answers

### Answer by username_0 on 2020-11-18. Score: 1

By coincidence, I have found a possible solution via [Github Secrets](https://www.edwardthomson.com/blog/github_actions_11_secrets.html).

> **Comments:**
> **username_1**: GitHub Secrets is indeed the way of doing it, to keep everything in the same place. You could also use an external **deploy** system but that's more work.  

---

