You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have realised that OAuth can be used to create the clone (including write access) to a repo.
This means the @jekylledit user would not need to be used at all - and after installation of the JekyllEdit - the web could just ask the admin user for his GitHub OAuth permission to GitHub and clone the repo he specify for him.
The application Client ID / Client Secret is registered under klokantech organisation.
It could be passed to Docker via a system variable - so non-klokantech deploys are easy.
The text was updated successfully, but these errors were encountered:
I have realised that OAuth can be used to create the clone (including write access) to a repo.
This means the @jekylledit user would not need to be used at all - and after installation of the JekyllEdit - the web could just ask the admin user for his GitHub OAuth permission to GitHub and clone the repo he specify for him.
This will make first deploy significantly easier.
Cloning is done this way:
(from https://github.com/blog/1270-easier-builds-and-deployments-using-git-over-https-and-oauth)
To request the OAuth token there is a simple Web Application Flow - https://developer.github.com/v3/oauth/#web-application-flow
@o1da is using it already in our clientportal project.
The application Client ID / Client Secret is registered under klokantech organisation.
It could be passed to Docker via a system variable - so non-klokantech deploys are easy.
The text was updated successfully, but these errors were encountered: