Great insight. The v1.1.1 fix will address these issues.

Thanks @codingdefined excellent review.

@helo thanks for the review. Please can you point me to a properly documented code base? I'd be delighted to see an example

The last task by @adrielg is under review.

Thanks. We'll keep improving on this.

It's a privilege to be able to contribute to this awesome community. We're working round the clock to provide all STONErs with a very seamless and intuitive interface to run masternode operations. Really

I will be handling the User's profile page (dashboard). Thanks.

Thanks @amosbastian. All subsequent pull requests will be posted here alongside relevant commits. Thanks for the heads up!

Thanks. I'll add comments on my next one

Great project. It's interesting to see what comes next.

Thanks. Will do that. I'd appreciate resources showing your directives in action please.

Sorry about that. Fixed it mate. Cheers!

Thanks dude. Added my vote to your witness.

Always a pleasure to help. Just drop a line if you need something.

Nice to see a newbie here. Github is the center for code collaboration and open source contribution. It's not as difficult to use as many think. It's worth an exploration. Do that sometime, you'd be glad

It's really easy. You can start at the first post and you'll be here in no time. The code is also available on Github for your convenience.. Cheers and I want to hear from you!

You're welcome.

Noted. Will explore more areas in subsequent posts.

Great article. Running the code. I came across an error. The error message I received gave a printed log containing the message "Mongod.lock is corrupt". How do i fix this? Great article by the

Great work.