redundancy in rewards.rchain.coop development, admin

[dckc]

Benefit to RChain

reliable rewards.rchain.coop maintenance and service even when @dckc is unavailable

See VotingTrouble for why this is particularly important / urgent.

cc @zsluedem @kitblake @jimscarver

Budget and Objective

Please make the issue SMART: Specific, Measurable, Achievable, Realistic, Timely.

Estimated Budget of Task: $1200
Estimated Timeline Required to Complete the Task: 1 to 4 days
How will we measure completion? one or more other admins can

• one or more staging environments are available to test changes (cf. Establish community managed test and staging environments #830)
• at least two admins are authorized and able to directly administer the service

Legal

Task Submitter shall not submit Tasks that will involve RHOC being transacted in any manner that (i) jeopardizes RHOC’s status as a software access token or other relevant and applicable description of the RHOC as an “asset”—not a security— or (2) violates, in any manner, applicable U.S. Securities laws.

[David405]

@dckc what time can you be available for a code walkthrough?

Also, I think some data such as voting records have been deleted from the database

[David405]

By the way, were there any recent changes you made before the application started throwing these errors?

[dckc]

Yes, there are recent changes; I detailed them in VotingTrouble.

About a code walkthrough: go ahead and suggest some times. And between now and those times, please study the code to some extent on your own and write down at least a couple questions.

[David405]

How about office hours tomorrow? I should have looked at VotingTrouble and rchain-dbr to a little more detailed extent by then.

[dckc]

Office hours tomorrow should work.

[dckc]

Also, I think some data such as voting records have been deleted from the database

What makes you think so?

[jimscarver]

The ssh issue was solved. database management and dump loading is provides by webmin.
I think https://rewards-test.rhobot.net/ is good to go as a staging area for rchain-dbr

[David405]

@dckc, it is not an issue, at first, I couldn't find some voting records but they all seem to be in place now

[dckc]

OK... bonus points to anybody who clones rchain-dbr, makes any visible change and deploys it to rewards-test.

Also: go ahead and try loading a database dump.

[David405]

I cloned rchain-dbr into rewards-test but I am yet to make any changes, also, I tried executing sql from https://rewards.rchain.coop/bak/2018-08-04%2007:50:08.sql.gz but I am getting ERROR 1215 (HY000) at line 102 in file: '/tmp/.webmin/455554_16252_2_exec_file.cgi': Cannot add foreign key constraint
cc: @jimscarver

[David405]

Upon further investigation, here's what I found https://stackoverflow.com/questions/15534977/mysql-cannot-add-foreign-key-constraint

[David405]

@dckc I created a pull request using test branch to commit a change to the master branch of the rewards app.

@jimscarver I tried to deploy the change to https://rewards-test.rhobot.net/ but I can't do that because I don't have the right permissions, kindly grant me permission so I could test changes before committing to the rewards app.

[David405]

We ( Jim and I) are working on updating the logo but have a hard time figuring out where the favicon was placed.

[dckc]

favicon? I'm not aware that there is one.

[David405]

We were able to deploy changes to the logo and favicon, see https://rewards-test.rhobot.net/

I also saw your comment on the pull request, I would edit it to accommodate further changes and resubmit it.

[David405]

@dckc I am having troubles pushing changes from my github account, I keep getting a permission denied: 403 error, this makes it difficult to make a pull request from rewards-test to commit the changes there.

[dckc]

Did you add your own fork as a remote? You shouldn't expect to be able to push to someone else's fork. Getting a 403 in that case is normal. As usual, it's best if you detail exactly what steps led to the problem. Exactly what command? From what directory? It's possible that you may need to clone the source to your home directory on rewards-test. You could check the video recording of our session where Jim pushed a change to his fork

…

On Tue, Aug 7, 2018, 1:34 AM David Asamonye ***@***.***> wrote: @dckc <https://github.com/dckc> I am having troubles pushing changes from my github account, I keep getting a permission denied: 403 error, this makes it difficult to make a pull request from rewards-test to commit the changes there. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#872 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJNynjPiUs-dRwjjaMQLL3CyLxuyTbjks5uOTT0gaJpZM4VuSh9> .

[jimscarver]

David did a fork on github and pushed a update with and error in it. I thought we did a git push david of the fix. If there are updates maybe another git push david is needed?
What else is needed to get david's changes into production?

[David405]

@jimscarver Yeah we did but when I tried it again to update the favicon, it threw a permission denied error

[whereyouatwimm]

I'd like to assist with this. It's my first week as a member so I'm still working on getting set up with the coop, but i've spent some of my time reviewing this issue and the source.

@David405 wanna get together and look at your permissions error? i have feeling it's working as git is intended to and we'll need to set up your fork as remote, as Dan references above, or get your pull request merged

[David405]

Hi @whereyouatwimm you are welcome, we got that fixed already, thanks for showing interest. Are you on discord?

[dckc]

Does anybody see time to work on this? Either starting independently or pairing with me?

https://github.com/dckc/rchain-dbr/issues/12 responsive design conflicts with backups, sync

[David405]

I am available to work on this, I can remember you making the complaint while we were installing the responsive theme

[dckc]

@Viraculous asked where the theme is:

• 469690e https://github.com/dckc/xataface-responsive-theme

(ref #792 (comment) )

[dckc]

@David405 I don't see any votes for budget nor reward in August. Is that on purpose?

[David405]

I haven't started entering rewards for the month yet, I usually do that at the beginning of each new month

[dckc]

I encourage you to start voting earlier. Feel free to vote $1 or something, just as a place-holder or starting point for negotiation.

This month in particular, I'm travelling to RCon3, so there's no guarantee I can back your vote before the 9th.

[David405]

I have added my vote

[dckc]

@David405 it doesn't make sense to claim 100% of the budget; the objective is only 1/2 done. "at least two admins are authorized and able to directly administer the service" is still todo. Let's cut the budget in half, ok?

[David405]

@dckc I really do not have any problem at all with half the budget, I only voted 100% rewards because when I saw your 30% vote I was wondering who the other 70% was for since the other two participants (yourself and @jimscarver) are covered by SOW.

By the way, hope you enjoyed your flight to Germany?

[dckc]

rewards for this issue look good now.

[David405]

@dckc , @jimscarver and I commit to applying the "4-eyes" policy in administering services to the rewards app

[kitblake]

How much activity took place under this issue in Sept?

[dckc]

Not a lot, from a quick look at Colab discord logs. We started getting access to production for @jimscarver and @David405 but got stalled somewhere... I'm still standing by for an ssh key from @David405 , I guess.

[jimscarver]

The activity was not too successful in Sept. We did not make progress. Hopefully we can other eyes on this and sponsorship. I can do some 2nd level support but not be a primary administrator. We need to get better with git to do the job effectively.

[David405]

@dckc I wasn't aware you needed an ssh key from me, I understood from the discussion we had (@dckc, @jimscarver, me) had in the #rewards-support channel in COLab that you wanted @jimscarver and @David405 to have a single admin access.

[dckc]

Yes, my request wasn't all that clear and we didn't manage to get together by voice to get on the same page.

I assumed the usual best practices for ssh keys, which is to not share them.

[David405]

So what is the way forward? Perhaps we could finalize during Saturday's office hours?

[dckc]

Share your public key.

[dckc]

@whereyouatwimm thanks for agreeing to help.

As we discussed, I granted you access using an ssh public key ending in cZGZ7wRlmK6v6lGA05v//DGUT [email protected].

We agreed to review details in my office hours (#403) tomorrow.