When developing gRPC using Tonic_, it is necessary to properly incorporate protobuf in addition to building the server process.
Tonic uses PROST!, which is slightly different from the flow generated by the protoc command.

Alain, a code generation CLI tool equivalent to the logic of this article, is distributed as open source.

proto include

Consider the following example of embedding protobuf code.

You can set up latest version with rbenv.
Get rbenv as a distribution package or rbenv-installer is available for the latest rbenv.

curl -fsSL https://github.com/rbenv/rbenv-installer/raw/HEAD/bin/rbenv-installer | bash

rbenv-installer clones rbenv repo under $HOME/.rbenv/.
Then ~/.rbenv/bin/rbenv init shows a snippet for .bashrc.

While gRPC and protobuf was initially led by Google, protobuf-javascript is not maintained actively.

At this time, ConnectRPC’s web client and protobuf-es set is more active.

Asterisk’s configuration consists of numerous file sets. The dial plan, routing by number, is defined in extensions.conf.

Example of a simple extension

The dial plan follows the syntax as shown below:

[internal]

exten => _1XX,1,Dial(PJSIP/${EXTEN},30)
same => n,Hangup()

The structure of a block that matches each called number is as follows:

sqldef is a CLI tool to maintain RDBMS schema along with corresponding configs.
It is a ridgepole clone written in Go.

Unlike standard migrations in popular web frameworks, their configs define the whole schema instead of the differences between schema versions. With traditional migrations, you cannot confirm the implemented schema in the database until the migration is applied. However, ridgepole and sqldef treat the configuration as the specification, making this aspect decisively different.