Nitrous is the customized condenser (see below) that integrates with the Steem Engine Token Scotbot.
The instructions below are still accurate, but you need a few things to configure. Note: The setup instructions here work only for Linux, macOS and do not work on Windows-based computers.
src/app/client_config.js collects most of the settings that are necessary to configure.
When running, SDC_IMAGE_PROXY_PREFIX and SDC_UPLOAD_IMAGE_URL can be set to
https://steemitimages.com (eventually this dependency should be changed). SDC_IMAGE_PROXY-PREFIX may also
need a trailing /.
Change src/app/assets/images/favicons with your own, and also change
src/app/assets/static/manifest.json and src/server/server-html.jsx accordingly.
Condenser is the react.js web interface to the blockchain-based social media platform, Hive.blog. It uses a Hive compatible blockchain, powered by DPoS Governance and ChainBase DB to store JSON-based content for a plethora of web applications.
We highly recommend using docker to run condenser in production. This is how we run the live com site and it is the most supported (and fastest) method of both building and running condenser. Configuration settings can be set using environment variables (see configuration section below for more information). If you need to install docker, you can get it at https://get.docker.com
To modify, build, and run condenser using docker, it's as simple as pulling in the github repo and issuing one command to build it, like this:
git clone https://github.com/eonwarped/nitrous
cd nitrous
docker build -t="myname/condenser:mybranch" .
docker run -it -p 8080:8080 myname/condenser:mybranch(better if you're planning to do condenser development)
git clone https://github.com/eonwarped/nitrous
cd nitrous
mkdir tmpInstall at least Node.js v12 if you don't already have it.
Condenser is known to successfully build using node 12.6, npm 6.13.4, and yarn 1.22.4.
We use the yarn package manager instead of the default npm. There are
multiple reasons for this, one being that we have hive-js built from
source pulling the gitlab repo as part of the build process and yarn
supports this. This way the library that handles keys can be loaded by
commit hash instead of a version name and cryptographically verified to be
exactly what we expect it to be. Yarn can be installed with npm, but
afterwards you will not need to use npm further.
npm install -g yarn
yarn add babel-cli
yarn install --frozen-lockfile --ignore-optional
yarn run buildTo run condenser in production mode, run:
yarn run productionWhen launching condenser in production mode it will automatically use 1 process per available core. You will be able to access the front-end at http://localhost:8080 by default.
To run condenser in development mode, run:
yarn run startIt will take quite a bit longer to start in this mode (~60s) as it needs to build and start the webpack-dev-server.
By default you will be connected to community public api node at
https://api.hive.blog. This is actually on the real blockchain and
you would use your regular account name and credentials to login - there is
not an official separate testnet at this time. If you intend to run a
full-fledged site relying on your own, we recommend looking into running a
copy of hive (steemd) locally instead
https://gitlab.syncad.com/hive/hive.
yarn debug will build a development version of the codebase and then start the
local server with --inspect-brk so that you can connect a debugging client.
You can use Chromium to connect by finding the remote client at
chrome://inspect/#devices.
The intention is to configure condenser using environment variables. You
can see the names of all of the available configuration environment
variables in config/custom-environment-variables.json. Default values are
stored in config/defaults.json.
Environment variables using an example like this:
export SDC_CLIENT_STEEMD_URL="https://api.hive.blog"
export SDC_SERVER_STEEMD_URL="https://api.hive.blog"Keep in mind environment variables only exist in your active session, so if
you wish to save them for later use you can put them all in a file and
source them in.
If you'd like to statically configure condenser without variables you can
edit the settings directly in config/production.json. If you're running
in development mode, copy config/production.json to config/dev.json
with cp config/production.json config/dev.json and adjust settings in
dev.json.
If you're intending to run condenser in a production environment one
configuration option that you will definitely want to edit is
server_session_secret which can be set by the environment variable
SDC_SESSION_SECRETKEY. To generate a new value for this setting, you can
do this:
node
> crypto.randomBytes(32).toString('base64')
> .exit- Prefer CamelCase js and jsx file names
- Prefer lower case one word directory names
- Keep stylesheet files close to components
- Component's stylesheet file name should match component name
We use prettier to autofromat the
code, with this configuration. Run yarn run fmt to format
everything in src/, or yarn exec -- prettier --config .prettierrc --write src/whatever/file.js for a specific file.
If a component requires a css rule, please use its uppercase name for the class, e.g. "Header" class for the header's root div. We adhere to BEM methodology with exception for Foundation classes, here is an example for the Header component:
<!-- Block -->
<ul class="Header">
...
<!-- Element -->
<li class="Header__menu-item">Menu Item 1</li>
<!-- Element with modifier -->
<li class="Header__menu-item--selected">Element with modifier</li>
</ul>yarn run storybook
yarn test
will run jest
If you want to test a server-side rendered page without using the network, do this:
yarn build
OFFLINE_SSR_TEST=true NODE_ENV=production node --prof lib/server/index.js
This will read data from the blobs in api_mockdata directory. If you want to use another set of mock data, create a similar directory to that one and add an argument OFFLINE_SSR_TEST_DATA_DIR pointing to your new directory.