Closed eolszewski closed 5 years ago
Most users only use the light node. I think it isn't good to spend too much time making full node setup videos. Especially since these things change fast, and videos are hard to update.
I'm specifically advocating this for developers - what is the path that you typically take to ensure that you haven't broken anything when developing?
With most applications I've worked on recently, we have live reloading and runtime errors will display in the terminal. I haven't really cracked this thing open yet - so I can't say much here, but it would be nice to include that somewhere in the setup (if it exists).
On Tue, 14 Aug 2018, 1:42 PM Zack, notifications@github.com wrote:
Most users only use the light node. I think it isn't good to spend too much time making full node setup videos. Especially since these things change fast, and videos are hard to update.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zack-bitcoin/amoveo/issues/187#issuecomment-412956341, or mute the thread https://github.com/notifications/unsubscribe-auth/ADciDYFBjnE_5PzRC6rJxQOdDG660w3Lks5uQwwLgaJpZM4V8xEt .
If the tests don't pass, then you broke something.
I don't see how a video would help.
What is your process for debugging and updating the software?
Update the code and run the tests - if they pass, then you're good to commit? I'm asking to see if there is CI in the project like this
start from README. you can read about how to run tests.
Running a local test node is a bit lackluster following these instructions - would be very useful to show what you can do out of the box in a video-format when running your local node.