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

Cloning private repo fails #89

Open
bradleyhodges opened this issue May 8, 2018 · 2 comments
Open

Cloning private repo fails #89

bradleyhodges opened this issue May 8, 2018 · 2 comments

Comments

@bradleyhodges
Copy link

bradleyhodges commented May 8, 2018

sudo systemctl status caddy.service -l produces the following error:

May 08 06:55:02 app-1 systemd[1]: Started Caddy HTTP/2 web server.
May 08 06:55:02 app-1 caddy[23804]: Activating privacy features... done.
May 08 06:55:02 app-1 caddy[23804]: 2018/05/08 06:55:02 cannot git clone into /var/www, directory not empty
May 08 06:55:02 app-1 systemd[1]: caddy.service: Main process exited, code=exited, status=1/FAILURE
May 08 06:55:02 app-1 systemd[1]: caddy.service: Unit entered failed state.
May 08 06:55:02 app-1 systemd[1]: caddy.service: Failed with result 'exit-code'.

The /var/www directory is completely empty, but every time I start caddy, it adds a ".ssh" directory to it. Any ideas?

Caddy file is:

git { repo https://github.com/username/repo.git branch master key /ssh/id_rsa hook /servicePush password }

@abiosoft
Copy link
Owner

When using private key, use ssh format. i.e. [email protected]:username/repo

@lukehaas
Copy link

Same issue here.
I'm specifying my key as being in /root/.ssh but caddy will still try and use /var/www/.ssh and fail.

My repo address is in format [email protected]:username/repo

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

3 participants