@members There is a pretty urgent piece of work needed to create a secure backup script for the membership database.
Currently I have to take periodic backups but the data changes throughout the day and ideally it should be backed up once a day at midnight.
We need someone to propose a secure backup, remembering this is a mongo_dump with password hashes and salts, and details about the users name and home address.
The system needs to securely transfer them to another server securely.
I know @courty and @jonathanjo have been looking at the membership system recently. Any other hands would be very welcome. This is mission-critical infrastructure and it’s not fair on Tom for him to be providing tech support for something he’s no longer a member of.
I have all the bot code now and am confident I can recreate the end points / doorbot etc from both a hardware and software perspective… not sure who’s looking at the Raspberry Pi interface at the space or main membership db though @jonathanjo ?
I also have access to internet servers that could be used for backup via sftp or the like if needed.
Courty
We’re talking about the members database at members.southlondonmakerspace.org here though
Backup is one point but we also need to think about general maintenance…
The offer to host the backups on my system still stands…
Courty
The best approach for this is for @systems to be the coordinators of this, (and all ‘systems’ related issues).
At the moment this is @jonathanjo
It’s handy that members have been alerted to the fact that there’s potential work to do, but this approach does little to actually support the relevant @role.
In essence: this should have been raised with @systems for consideration, and not here, in public.
No it was intentionally public because there are a whole load of members who have the skills who could be helping out.
Had you discussed this with Jonathan first?
He is aware it needs doing I believe, however as for if he is doing it or not I have no idea, given that I am generally still maintaining the membership system I doubt it.
Regardless the point is that this is a critically urgent, if not top priority. If this data becomes corrupt it would have very serious consequences. The first of which would be our inability to fulfil a basic legal requirement of having a list of members for company law.
The more obvious issues would be total and utter in ability to control access to the space and tools, discourse permissions and people to signup and change their direct debits.
The point is this is pretty serious.
I don’t really know anything about mongo, but I think it shouldn’t be too difficult to write a script to back things up to Amazon or somewhere else in the meantime.
If we’re looking to make major changes I’d be happy to get involved in that as well. Is there any code or documentation anywhere public?
The membership system doesn’t require major changes to my knowledge but there is a need for it to be maintained and some improvements, I had started going down the road of trying to improve the events logging to allow tool status, temperature logging etc.
Thanks for your offer of help Erik! If you know JS then you’re all set, mongo is really easy I’ve used it with python, nice system. I know a bit of JS but not enough to wade into the membership system.
There’s a public code repository at https://github.com/southlondonmakerspace and @systems and @unknowndomain should be able to get you up to speed on the mechanics of it, feel free to message them and set up a meeting (on/offline).
Although I am not a member any more, I am keen to meet with @systems and @courty and others to discuss the system soon as there are things which I started working on which they should integrate to things like tool control.
I know node and mongo and general sysadmin stuff @systems and happy to help
You have my blessing!
If yourself, Johnathan and Tom can set up a meeting to go through the basics, that’d be a good start 
I can also help out if required (Linux admin, node, mongo…).
@systems @unknowndomain @jonathanjo happy to meet up any time this week/weekend, or an evening next week? Whatever suits.