v0.1.0-beta3
·
961 commits
to develop
since this release
System Administration Changes
Breaking changes
- To improve dfuse instrumented
nodeosbinary processing speed, we had to make incompatible changes to data exchange format going out ofnodeos. This requires you to upgrade your dfuse instrumentednodeosbinary to latest version (https://github.com/dfuse-io/eos/releases/tag/v2.0.5-dm-12.0). Follow instructions in at https://github.com/dfuse-io/dfuse-eosio/blob/develop/DEPENDENCIES.md#dfuse-instrumented-eosio-prebuilt-binaries to install the latest version for your platform. --mindreader-working-dirdefault value is now{dfuse-data-dir}/mindreader/workinstead of{dfuse-data-dir}/mindreaderthis is to prevent mindreader from walking files into the working dir and trying to upload and delete nodes system files likefork_db.dat- The Changed section below lists a bunch of breaking changes regarding command-line flags.
Added
- Added
--eosq-available-networksjson string to configure the network section of eosq.
{
"id": "id.1",
"name": "Network Name",
"is_test": false,
"logo": "/images/network-logo.png",
"url": "https://www.example.com/"
},
]
- Added
--eosq-default-networkstring to configure the default network eosq - Added
--eosq-disable-analyticsbool to configure eosq analytics - Added
--eosq-display-pricebool to configure if eosq displays prices - Added
--eosq-price-tickerstring to configure if eosq price ticker - Added
--eosq-on-demandbool to configure if eosq serves an on-demand network - Added
--eosq-disable-tokenmetabool to configure if eosq disables tokenmenta - Added
--eosq-environmentenvironment where eosq will run (local, dev, production) - Added
--apiproxy-autocert-domains,--apiproxy-autocert-cache-dirand--apiproxy-https-listen-addrto serve SSL directly from proxy.
Removed
- Removed the
--merger-store-timeoutflag. Not needed anymore, as some sensible timeouts have been put here and there, using the latest[email protected]that is context-aware.
Changed
- We improve by 4x times the performance of dfuse instrumented
nodeosbinary on heavy EOS Mainnet blocks. This required changes tonodeosdata exchange format, so you will need to upgrade it, see theBreakingchange entry at top of this section. - Fixed behavior of
--eosq-api-endpoint-urlto allow specifying protocol (ex: https://api.mydomain.com) - The
kvdb-loaderapplication was renamedtrxdb-loader. In general what was (confusingly) namedkvdbis nowtrxdb, so thatkvdbcan now take on its full meaning of a lean key-value storage abstraction (which is also used by FluxDB).- All
--kvdb-loaderflags have been renamed to--trxdb-loader. - Metrics ID for
kvdb-loaderhas been changed totrxdb-loader(check your dashboards)
- All
- The
--mindreader-merge-and-upload-directlywas renamed to--mindreader-merge-and-store-directly. --common-blocks-store-urlnow replaces all of these flags:--mindreader-merged-blocks-store-url,--relayer-blocks-store,--fluxdb-blocks-store,--kvdb-loader-blocks-store,--blockmeta-blocks-store,--search-indexer-blocks-store,--search-live-blocks-store,--search-forkresolver-blocks-store,--eosws-blocks-store
--common-oneblock-store-urlnow replaces these flags:--mindreader-oneblock-store-url,--merger-one-block-path
--common-backup-store-urlnow replaces these flags:--node-manager-backup-store-url,--mindreader-backup-store-url
--search-common-indices-store-urlnow replaces these flags:--search-indexer-indices-store,--search-archive-indices-store
--common-blockstream-addrnow replaces these flags:--fluxdb-block-stream-addr,--kvdb-loader-block-stream-addr,--blockmeta-block-stream-addr,--search-indexer-block-stream-addr,--search-live-block-stream-addr,--eosws-block-stream-addr
--common-blockmeta-addrnow replaces these flags:--search-indexer-blockmeta-addr,--search-router-blockmeta-addr,--search-live-blockmeta-addr,--eosws-block-meta-addr,--dgraphql-block-meta-addr
--common-network-idnow replaces this flag:--dgraphql-network-id--common-auth-pluginnow replaces these flags:--dgraphql-auth-plugin,--eosws-auth-plugin
--fluxdb-statedb-dsnreplaces--fluxdb-kvdb-store-dsn(to avoid confusion between what's actually stored inkvdband how FluxDB is using it (as a simple kv store).--trxdb-loader-parallel-file-download-countreplaces--kvdb-parallel-file-download-count--common-trxdb-dsnreplaces these flags:--blockmeta-kvdb-dsn,--abicodec-kvdb-dsn,--eosws-kvdb-dsn,--dgraphql-kvdb-dsn,--kvdb-loader-kvdb-dsn
- Changed default value for storage URL for
fluxdbandkvbd(now namedtrxdb)
Fixed
--kvdb-loader-chain-idnot being taken into account. This affected the decoding of public keys during thekvdbloading process.