21

Have an exciting project to share or a problem that you are trying to solve?

This is a general open thread to talk about what you're working on - or want to work on!

Feel free to share ideas, ask for help, or just fill us in on your cool project :)

Anything goes in terms of topics, just as long as it is STEM-related.

Have an exciting project to share or a problem that you are trying to solve? This is a general open thread to talk about what you're working on - or want to work on! Feel free to share ideas, ask for help, or just fill us in on your cool project :) Anything goes in terms of topics, just as long as it is STEM-related.

29 comments

Ah I just mean general google nosiness, eg: needing an account to write things in a shared doc. Idk exactly what data they harvest but there's no reason people should have to have accounts to do realtime text editing together, especially if the doc can be password-protected to stop randomers editing it. I've been thinking about lightweight options for private judge discussion for the fiction prize; I wanted something that wouldn't be massive overhead to host myself (or to ask a trusted party to host) if people didn't want to give data to a third party or make an account anywhere else. And anyone can write in any publicly hosted instance, but nothing can be deleted from the history once it's up, so I think we need to be able to delete files in case someone pastes personal details into one by accident. So I think that would mean it needs to be self-hosted, so if people were concerned about the security of me hosting it, I'd definitely want to have it all automated so nobody else got that maintenance burden and I could just go 'here is script, point it at your ip' to the host.

Ah, that makes sense. Having to create an alt Google account to edit a doc is really burdensome, plus the risk of unintentionally logging in/editing with a main Google account. I am excited to see what you come up with :)

Yeah, I almost never click on google docs links, even if I know I'm logged out, because I'm so paranoid. What if I logged in in my sleep??? :P So far I've found there's a well-maintained etherpad ansible role and some official docker stuff in the repo; docker stuff seems a bit barebones, though. I was hoping to use it so I wouldn't have to do too much database-configuration, but it looks like it requires pretty much just as much work as a manual install, just with some added confusion because I don't use the docker CLI enough to remember the options. :P Whereas the ansible role does the db side too, and has tasks for updating and so on. I'm still kind of tempted to just write a shellscript, but it would be nice for things to be easy to update, and I'd have to write config for the db collation stuff anyway. I think it depends on a separate nodejs ansible role, so hey, was hoping for something a bit nicer than piping a curl to bash. I think I'll write the shellscript since that's very easy to do locally, then try out the ansible role when I can get to a machine with a VM and see if it's straightforward or if it's a pain in the neck for reasons that aren't obvious from a distance. The plus side with ansible is that I already have ansible aws config ready from a box I was using for something else, so that wouldn't need much tweaking, though aws is expensive so I should really find a different host. (plus, bah, amazon) Well now I'm thinking out loud...

It worrrrrks! :D I apparently have no memory of ansible, but I muddled through. The upstream etherpad role covers most stuff; aside from local config, the only important missing bit = the dependencies for mysql, but I happened to have those written down for another project. :P So I now have a readme typed up with instructions and an example playbook; will tidy and post in a bit.