On 03/08/2017 01:43 PM, Barry Warsaw wrote:

On Mar 09, 2017, at 03:02 AM, raditya wrote:

...

Dear mentors, for some reason i'm not able to setup the dev-env on my machine using the SSH key method so i figured that i can do it using HTTPS as well. Is there any drawback of doing so other than the fact that i will have to input my username and password everytime.

If you're only pulling from the GitLab git repo, there shouldn't be any difference in content.

And it's a public repo so you shouldn't need a user/password authentication for https either.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On 03/08/2017 01:43 PM, Barry Warsaw wrote:

On Mar 09, 2017, at 03:02 AM, raditya wrote:

...

Dear mentors, for some reason i'm not able to setup the dev-env on my machine using the SSH key method so i figured that i can do it using HTTPS as well. Is there any drawback of doing so other than the fact that i will have to input my username and password everytime.

If you're only pulling from the GitLab git repo, there shouldn't be any difference in content.

And it's a public repo so you shouldn't need a user/password authentication for https either.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan