-
Notifications
You must be signed in to change notification settings - Fork 37
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
Push wiki to remote #24
Comments
The major problem that I see here is authentication. When pulling from a remote this might be via https and possible as an anonymous user, but when it comes to pushing you need to be authenticated in most of the cases. To implement this you would have to take care of a huge pile of problems. |
Yeah I was kind of thinking there would be an initial requirement that their credentials would have to be cached with the os. Then, presumably, the git api would be able to push. If a user would try to push (via a button in the ui) and it fails, you could display a helpful error and a 'set up' page outlining how to get the repo/creds set up. You could make it like how an empty GitHub repo will show you the initial set of commands to run to get up and going. |
Please add this feature! I want to backup wiki to Github account |
I need this feature to exist. It would be easiest to achieve using public-key authentication with the git remote. But no, it's not a trivial feature. Damn. In the interim, I could use docker mapping to map the repository to an external repository and have a timer set up to push/pull... hmmm... |
I too would appreciate it if such a feature existed. |
+1 |
+1, just tried to achieve it mapping ssh keys and adding a post-commit hook but it didnt work. I will setup a cronjob for the time being and call it a day |
Is there a place in the interface the push the wiki to a git remote location? It would be cool if there was a "Push" or "Sync" feature. This could be very tricky if there are remote changes that conflict with local, but it would great to do this in the UI
The text was updated successfully, but these errors were encountered: