Proposal #10 - DevPortal Documentation Update - New Pull Requests (more progress)

avatar

This week, I have only two new pull request for Steemit, Inc. to merge:

  • PR#426 - Add Steem Keychain to resources
  • PR#427 - Services Section Update
  • Future PR - New Recipe: About config.ini

That last one isn't a pull request yet because I'm still working on it. There's a lot that goes into the latest, full-sized config.ini. Here are just some of the sections so far:



I'm keeping the deprecated config options (like edit-script) in the list in order to avoid the Mandela Effect.

A while back, one of the blockchain engineers asked me what the plan was for future changes, when things get out of date and such. I told him I had a plan for that. In the case of the API Definitions, I have a few scripts to help me locate new methods and operations. In the case of future config.ini updates, I have a plan for that too. It's a little less elaborate than the API Definitions. I just have a copy of the config in the repository, tagged with the docker hub hash.

One example of something super interesting that took a little bit of reverse engineering to figure out. This new option called webserver-unix-endpoint. Right away, I knew what it was for. I even remembered there being a pull request for it (#3205). But there weren't any examples that I could see.

So I fired up an instance of tintoy, which took only two minutes to try it out. Turns out the syntax is:

webserver-unix-endpoint = /tmp/steemd.sock

It's intended for node operators who use nginx or jussi on their front ends and steemd running on the same box. Since TCP over localhost is inefficient, the ability to use unix-sockets was added.

With this setting, you can make a curl request like this:

curl -s --data '{
  "jsonrpc": "2.0",
  "method": "condenser_api.get_account_count",
  "params": [],
  "id": 1
}' --unix-socket /tmp/steemd.sock http:

Sometimes, it's stuff like that what takes a while to verify. I could throw in any old string and it'd work. But most often, you want to have a reasonable value for something like a webserver-unix-endpoint. If you didn't know what it was, you might put in an IP or something. Then steemd would just create a file with the name of the file set to the IP, which would look really funny if you did that. Um, not that I attempted that or anything. I know what a unix-socket is. Ok, yes. I did test it like that at first.

For many of these options, there's not much to say. But for some, there's an entire undocumented plugin associated with the option.

Another group of options that I found rather interesting:



So I'm investigating these, and I ran across issue #3168. What's that all about? Well, it's about me testing the testnet right after HF20, trying to get ahead of any new problems. Although, I wish we could say for sure it found bugs, had it not been added, we wouldn't have had as much testnet coverage in HF21.



0
0
0.000
5 comments
avatar

Thank you for keeping the documentation updated.

0
0
0.000
avatar

Thanks for your hard work and congrats on being the one funded proposal which definitely deserves it.

So many useless proposals which is a great way to advertise cheaply at the moment.

0
0
0.000
avatar

What an amazing job to dig into your memory and in the many issues on github.
Kudos! 👍

0
0
0.000
avatar

This post has been included in the latest edition of The Steem News - a compilation of the key news stories on the Steem blockchain.

0
0
0.000
avatar

Hi, @inertia!

You just got a 1.01% upvote from SteemPlus!
To get higher upvotes, earn more SteemPlus Points (SPP). On your Steemit wallet, check your SPP balance and click on "How to earn SPP?" to find out all the ways to earn.
If you're not using SteemPlus yet, please check our last posts in here to see the many ways in which SteemPlus can improve your Steem experience on Steemit and Busy.

0
0
0.000