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

Move private stuff to gitlabs #299

Closed
johnmckerrell opened this Issue Jun 14, 2016 · 7 comments

Comments

Projects
None yet
4 participants
@johnmckerrell
Member

johnmckerrell commented Jun 14, 2016

Organisers stuff from wiki.doesliverpool.com and stuff currently in bitbucket

@DefProc

This comment has been minimized.

Show comment
Hide comment
@DefProc

DefProc Jun 14, 2016

gitlab.com/DoESLiverpool exists, but I'll need your gitlab.com accounts to add you.

DefProc commented Jun 14, 2016

gitlab.com/DoESLiverpool exists, but I'll need your gitlab.com accounts to add you.

@amcewen

This comment has been minimized.

Show comment
Hide comment
@amcewen

amcewen Oct 4, 2016

Member

Rolled over to next organisers meeting.

Member

amcewen commented Oct 4, 2016

Rolled over to next organisers meeting.

@amcewen

This comment has been minimized.

Show comment
Hide comment
@amcewen

amcewen Nov 10, 2016

Member

So, we're moving to gitlab for private stuff because we've hit the limit of users allowed for the free version of bitbucket. Still ongoing.

Member

amcewen commented Nov 10, 2016

So, we're moving to gitlab for private stuff because we've hit the limit of users allowed for the free version of bitbucket. Still ongoing.

@johnmckerrell

This comment has been minimized.

Show comment
Hide comment
@johnmckerrell

johnmckerrell Nov 10, 2016

Member

Destroy bitbucket when complete

Member

johnmckerrell commented Nov 10, 2016

Destroy bitbucket when complete

@DefProc

This comment has been minimized.

Show comment
Hide comment
@DefProc

DefProc Nov 10, 2016

The bitbucket repos are there (and have been for 5 months now!). I've just updated the doorbots to the most recent version and invited some organisers.

DefProc commented Nov 10, 2016

The bitbucket repos are there (and have been for 5 months now!). I've just updated the doorbots to the most recent version and invited some organisers.

@johnmckerrell

This comment has been minimized.

Show comment
Hide comment
@johnmckerrell

johnmckerrell Nov 10, 2016

Member

You mean gitlab right?

On 10 Nov 2016, at 16:48, Patrick Fenner notifications@github.com wrote:

The bitbucket repos are there (and have been for 5 months now!). I've just updated the doorbots to the most recent version and invited some organisers.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #299 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AABqa01JZqyM8GmcAA9jRbzqBx5Lf65Wks5q80rkgaJpZM4I1S2E.

Member

johnmckerrell commented Nov 10, 2016

You mean gitlab right?

On 10 Nov 2016, at 16:48, Patrick Fenner notifications@github.com wrote:

The bitbucket repos are there (and have been for 5 months now!). I've just updated the doorbots to the most recent version and invited some organisers.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #299 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AABqa01JZqyM8GmcAA9jRbzqBx5Lf65Wks5q80rkgaJpZM4I1S2E.

@amcewen

This comment has been minimized.

Show comment
Hide comment
@amcewen

amcewen Nov 10, 2016

Member

Dunno what @DefProc means but he hadn't updated the doorbots to point to gitlab. As I discovered when I tried to add a new card :-/

I've added a DoESDevices user to Gitlab.com, which has Doorbot1's ssh key set up, so doorbot1 can pull code down. I've cloned the gitlab.com repo onto doorbot1 (and it's then copied over locally to doorbots 2 and 3, so I've not updated their git repos) and deleted the _config.yaml file from the bitbucket repo as a quick-and-dirty way to make it obvious to people that they should move to the gitlab.com repo :-D

Member

amcewen commented Nov 10, 2016

Dunno what @DefProc means but he hadn't updated the doorbots to point to gitlab. As I discovered when I tried to add a new card :-/

I've added a DoESDevices user to Gitlab.com, which has Doorbot1's ssh key set up, so doorbot1 can pull code down. I've cloned the gitlab.com repo onto doorbot1 (and it's then copied over locally to doorbots 2 and 3, so I've not updated their git repos) and deleted the _config.yaml file from the bitbucket repo as a quick-and-dirty way to make it obvious to people that they should move to the gitlab.com repo :-D

@DoESsean DoESsean closed this Dec 14, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment