This is a
playground to test code. It runs a full
Node.js environment and already has all of
npm’s 400,000 packages pre-installed, including
insight-bitcore with all
npm packages installed. Try it out:
insight-bitcore lists no main file and has no index.js, so it can't be directly required. If this is a mistake, please let us know. It may however contain internal files that you can require manually:
This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.
insight is an open-source bitcoin blockchain explorer with complete REST and websocket APIs. Insight runs in NodeJS, uses AngularJS for the front-end and LevelDB for storage.
Check some screenshots and more details at insight's project homepage.
Insight project is now split into two repositories. One for the API and for the front-end. This repository is for the front-end, which will install the API as a NPM dependency.
Node.js v0.10.x - Download and Install Node.js.
NPM - Node.js package manager, should be automatically installed when you get node.js.
Check the Prerequisites section above before installing.
To install Insight, clone the main repository:
$ git clone https://github.com/bitpay/insight.git && cd insight
$ npm install
Run the main application:
$ npm start
Then open a browser and go to:
If insight reports problems connecting to bitcoind please check the CONFIGURATION section of insight-api README. To set the environment variables run something like:
$ INSIGHT_NETWORK=livenet BITCOIND_USER=user BITCOIND_PASS=pass INSIGHT_PUBLIC_PATH=public npm start
Please note that the app will need to sync its internal database with the blockchain state, which may take some time. You can check sync progress from within the web interface. More details about that process on insight-api README.
To use Nginx as a reverse proxy for Insight, use the following base configuration
To run insight locally for development mode:
Install bower dependencies:
$ bower install
To compile and minify the web application's assets:
$ grunt compile
There is a convinent Gruntfile.js for automation during editing the code
In case you are developing insight and insight-api toghether, you can do the following:
$ cd $IROOT/insight $ grunt
in other terminal:
$ cd $IROOT/insight-api $ ln -s ../insight/public $ INSIGHT_PUBLIC_PATH=public node insight.js
at insight-api's home path (edit the path according your setup).
also in the insight-api path. (So you will have two grunt processes running, one for insight and one for insight-api).
insight use angular-gettext for multilanguage support.
To enable a text to be translated, add the translate directive to html tags. See more details here. Then, run:
This action will create a template.pot file in po/ folder. You can open it with some PO editor (Poedit). Read this guide to learn how to edit/update/import PO files from a generated POT file. PO file will be generated inside po/ folder.
Finally changes your default language from public/src/js/config
gettextCatalog.currentLanguage = 'es';
This line will take a look at any *.po files inside po/ folder, e.g. po/es.po, po/nl.po. After any change do not forget to run grunt compile.
Contributions and suggestions are welcomed at insight github repository.
(The MIT License)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.