On 11/12/2015 04:12 PM, Sam Ruby wrote: > On Thu, Nov 12, 2015 at 9:57 AM, Daniel Gruno <[email protected]> wrote: >> Gentle ping - it would be nice to get some feedback here :) >> >> With regards, >> Daniel. >> >> On 10/11/2015, 3:13:38 PM, Daniel Gruno <[email protected]> wrote: >>> >>> So, let's start by gathering a bunch of people interested in configuring >>> and monitoring an election (with multiple issues to vote on), and then >>> let's get some folks to volunteer as voters. > > Are there instructions someplace for setting up and monitoring an > election on your own hardware?
http://svn.apache.org/repos/asf/steve/trunk/pysteve/GETTING_STARTED.txt It's a very minimal install guide. I'll see if I have spare cycles to elaborate a bit on how to install, but in my experience, it's just a matter of pulling the pysteve contents into a CGI-enabled httpd instance and having a standard elasticsearch (if you choose to use that) DB running on the same machine. In the case of ASF's vote-wip instance, it uses LDAP auth which then goes to steve.cfg and checks which rights you have on the machine. I have set up you as an admin of the vote-wip instance, so you should be able to see/do everything there. As for monitoring: When you create an election, you specify who is designated as monitor of the election. Right before you invite everyone to an election, you click 'Cue monitors' in the admin interface, and they will receive a link to the monitoring site along with some checksum values. This link stuff needs some improvements (some uniqueness added to it), but the basics work as intended. With regards, Daniel. > > - Sam Ruby >
