No bitbucket credentials on the wiki about doorbot-setup HOT 6 CLOSED

Added you as an admin.

Sent from my mobile phone hence brevity and errors

On 13 Jun 2015, at 09:49, Adrian McEwen [email protected] wrote:

I can't find any way to add my bitbucket user (amcewen) to the DoES repository, so can't clone the config repository.

—
Reply to this email directly or view it on GitHub.

from doorbot-setup.

And me too please (DefProc)

is this the de-facto place to sign-up to get access now then?

from doorbot-setup.

It works ;-) Now added, we only get 5 users on the free plan, we're now at 3.

from doorbot-setup.

Ta,

Is the update process documented anywhere?

What happens about new ringtones now?

from doorbot-setup.

See issues #2 and #11, and DoESLiverpool/somebody-should#166 :-)

But basically, no. My current process is:

• ssh into doorbot1
• tail logcards/scans.log
• Add the new person to config.yaml on my local machine, not the doorbot and push that to bitbucket
• On the doorbot, git pull to get the new config
• Run reload-all-config to copy it across to doorbots 2 and 3

from doorbot-setup.

I've made an rfid-keyboard to allow easier collection of the RFID UIDs: https://git.defproc.co.uk/DefProc/rfid-keyboard

So now, with the device plugged in as a USB keyboard, the process to add/search though a local clone of doorbot-setup can be done without ssh'ing to a doorbot for an ID number.

With the rfid-keyboard plugged in (and having set the keyboard map to QWERTY!):

• Add the new person to config.yaml on your local repo, not the doorbot (scan the card where you need to input the UID)
• commit & push that to bitbucket
• On the doorbot, cd logcards/doorbot-setup && git pull to get the new config
• Run ~/reload-all-config.sh to copy it across to doorbots 2 and 3

from doorbot-setup.