Git Push from research.bugmark.net

[Andy L]

We've had some discussion about how to push changes from `research.bugmark.net`.

The challenge is that we're using a shared account - `dep...@research.bugmark.net` - and we'd like to push changes using our GitHub identity.

There are two approaches that we can take.

1) is to setup separate accounts on the server

2) is to keep using the shared account, and enable people to push with their own GitHub identity

Here is a howto:  https://stackoverflow.com/questions/26590232/git-push-multiple-accounts

To make this work, we'd probably add a bash alias like "git_identity georg", "git_identity malvika"  to set identity before pushing.

I think 2) would be better, to eliminate the overhead of separate accounts and server instances.

But maybe not.

@Georg and @Malvika - WDYT?

[Georg Link]

Thanks Andy,

I think option 1 is better.

Option 2 requires us to constantly reset our users when we want to commit and it would be easy to forget and submit as the last person logged on.

Option 1 allows us to have our own GIT settings and not have to change them. The files can live in a shared directory that we all have access to.

Best,

Georg

--
You received this message because you are subscribed to the Google Groups "bugmark_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bugmark_dev+unsubscribe@googlegroups.com.
To post to this group, send email to bugma...@googlegroups.com.
Visit this group at https://groups.google.com/group/bugmark_dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/bugmark_dev/e3975ca8-45d9-44ee-beaf-32a77db94908%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Andy Leak]

@Georg - OK I'll set up Option1. 

All servers will be configured for both production (on `deploy@<hostname>.bugmark.net`) and development (one development account per user).

For development, should we have one shared source directory for all, or separate source directories in each user account? 

I suppose we could also have a shared tmux development session, rather than one for every user.  WDYT? 

--

an...@r210.com
650-823-0836

[Georg Link]

I agree with you. One shared source and one shared tmux session. Otherwise, we need a good manual for how to update our own source files and we could not easily see each other's console.

Georg

[Georg Link]

I solved this differently:

Push to HTTPS and authenticate with username and access token.

Create access token first: https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/

Best,

Georg