chore: extract services

Author: gaboesquivel

.env-sample

@@ -1,11 +1,3 @@
-EOSIO_SOCKET_ENDPOINT=ws://50.17.129.61:8080
-EOS_NODEOS_HOST=50.17.118.93
-EOS_NODEOS_PORT=8888
-HASURA_API=http://x.x.x.x:8088/v1/graphql
-HASURA_GRAPHQL_AUTH_HOOK=http://x.x.x.x:3000
-HASURA_GRAPHQL_ADMIN_SECRET=super-secret
-HASURA_HOST=x.x.x.x
-CHAINGRAPH_API_DOMAIN=api.chiangraph.io
-CHAINGRAPH_CODEGEN_KEY=123
-CHAIN_ID=aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906
-MAX_ACTIONS_LIMIT=1000
+AUTH_HOOK=http://localhost:3000
+ADMIN_SECRET=super-secret
+DATABASE_URL=postgres://user:pass@postgres:5432/chaingraph?sslmode=disable

.gitignore

@@ -1,19 +1,8 @@
 .history
-dist/
-node_modules/
+
 *.log
 .DS_Store
-abi.json
 
 .env
 !.env.example
 .ssh
-
-# temporary copy hack
-services/auth/modules
-services/core/modules
-
-services/nginx/*
-!services/nginx/nginx.tmpl
-
-services/eos-api/src/data/*

CONTRIBUTING.md

@@ -1,12 +1,12 @@
-# Contributing to DreamStack RxDemux
+# Contributing to ChainGraph
 
 Interested in contributing? That's awesome! Here are some guidelines to get started quickly and easily:
 
 - [Reporting An Issue](#reporting-an-issue)
   - [Bug Reports](#bug-reports)
   - [Feature Requests](#feature-requests)
   - [Change Requests](#change-requests)
-- [Working on DreamStack RxDemux](#working-on-dreamstack-rxdemux)
+- [Working on ChainGraph](#working-on-chaingraph-node)
   - [Feature Branches](#feature-branches)
   - [Submitting Pull Requests](#submitting-pull-requests)
   - [Testing and Quality Assurance](#testing-and-quality-assurance)
@@ -16,7 +16,7 @@ Interested in contributing? That's awesome! Here are some guidelines to get star
 
 ## Reporting An Issue
 
-If you're about to raise an issue because you think you've found a problem with DreamStack RxDemux
+If you're about to raise an issue because you think you've found a problem with ChainGraph
 , or you'd like to make a request for a new feature in the codebase, or any other reason… please read this first.
 
 The GitHub issue tracker is the preferred channel for [bug reports](#bug-reports), [feature requests](#feature-requests), and [submitting pull requests](#submitting-pull-requests), but please respect the following restrictions:
@@ -35,11 +35,11 @@ Guidelines for bug reports:
    reported.
 
 1. **Check if the issue has been fixed** — look for [closed issues in the
-   current milestone](https://github.com/telosdreamstack/dreamstack-rxdemux/issues?q=is%3Aissue+is%3Aopen) or try to reproduce it using the latest `master` branch.
+   current milestone](https://github.com/chaingraph/chaingraph-node/issues?q=is%3Aissue+is%3Aopen) or try to reproduce it using the latest `master` branch.
 
 A good bug report shouldn't leave others needing to chase you up for more information. Be sure to include the details of your environment and relevant tests that demonstrate the failure.
 
-[Report a bug](https://github.com/telosdreamstack/dreamstack-rxdemux/labels/bug)
+[Report a bug](https://github.com/chaingraph/chaingraph-node/labels/bug)
 
 ### Feature Requests
 
@@ -51,29 +51,29 @@ Feature requests are welcome. Before you submit one be sure to have:
 
 ### Change Requests
 
-Change requests cover both architectural and functional changes to how DreamStack RxDemux works. If you have an idea for a new or different dependency, a refactor, or an improvement to a feature, etc - please be sure to:
+Change requests cover both architectural and functional changes to how ChainGraph works. If you have an idea for a new or different dependency, a refactor, or an improvement to a feature, etc - please be sure to:
 
 1. **Use the GitHub search** and check someone else didn't get there first
 1. Take a moment to think about the best way to make a case for, and explain what you're thinking. Are you sure this shouldn't really be
    a [bug report](#bug-reports) or a [feature request](#feature-requests)? Is it really one idea or is it many? What's the context? What problem are you solving? Why is what you are suggesting better than what's already there?
 
-## Working on DreamStack RxDemux
+## Working on ChainGraph
 
-Code contributions are welcome and encouraged! If you are looking for a good place to start, check out the [good first issue](https://github.com/telosdreamstack/dreamstack-rxdemux/labels/good%20first%20issue) label in GitHub issues.
+Code contributions are welcome and encouraged! If you are looking for a good place to start, check out the [good first issue](https://github.com/chaingraph/chaingraph-node/labels/good%20first%20issue) label in GitHub issues.
 
 Also, please follow these guidelines when submitting code:
 
 ### Submitting Pull Requests
 
 Pull requests are awesome. If you're looking to raise a PR for something which doesn't have an open issue, please think carefully about [raising an issue](#reporting-an-issue) which your PR can close, especially if you're fixing a bug. This makes it more likely that there will be enough information available for your PR to be properly tested and merged.
 
-We follow the [github flow strategy](https://guides.github.com/introduction/flow) for releasing updates. Fork out and create a branch out of master, then create your pull request. We squash the pull requests following conventional commits, we appreciate if you can follow this convention on your commits as well https://developers.blockmatic.io/open-source/contributing-guidelines
+We follow the [github flow strategy](https://guides.github.com/introduction/flow) for releasing updates. Fork out and create a branch out of master, then create your pull request. We squash the pull requests following __conventional commits__, we appreciate if you can follow this convention on your commits as well https://developers.blockmatic.io/open-source/contributing-guidelines
 
 ### Testing and Quality Assurance
 
 Never underestimate just how useful quality assurance is. If you're looking to get involved with the code base and don't know where to start, checking out and testing a pull request is one of the most useful things you could do.
 
-Essentially, [check out the latest develop branch](#working-on-DreamStack-RxDemux), take it for a spin, and if you find anything odd, please follow the [bug report guidelines](#bug-reports) and let us know!
+Essentially, [check out the latest develop branch](#working-on-chaingraph), take it for a spin, and if you find anything odd, please follow the [bug report guidelines](#bug-reports) and let us know!
 
 ## Conduct
 
@@ -138,9 +138,3 @@ By making a contribution to this project, I certify that:
     maintained indefinitely and may be redistributed consistent with
     this project or the open source license(s) involved.
 ```
-
-## References
-
-- Overall CONTRUB adapted from https://github.com/EOSIO/universal-authenticator-library/blob/master/CONTRIBUTING.md
-- Overall CONTRIB adapted from https://github.com/mathjax/MathJax/blob/master/CONTRIBUTING.md
-- Conduct section adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

IMPORTANT.md

@@ -1,4 +1,4 @@
-Copyright (c) 2020 blockmatic.io and its contributors.  All rights reserved.
+Copyright (c) 2021 blockmatic.io and its contributors.  All rights reserved.
 
 The MIT License
 

LICENSE

@@ -2,6 +2,44 @@
 
 A realtime GraphQL API and indexing service for blockchain applications.
 
+## TODO:
+
+- remove hasura-client in favor of node-postgres
+- upgrade hasura engine.
+- update mappings to that it uses primary_key type attrib
+- update schema
+  - review action data saved, reduce space
+  - use pg views for tokens and balances
+- update data indexers 
+- setup jungle and telos streaming
+- improve history loading
+- stress test with eosio.token data
+- restore 
+- update documentation, create a gitbook
+  - document history of the project, philosophy and why not history tools ( cos it's bloated )
+- how to limit socket connections, rate limiting, blacklisting ips.
+- review logger, polluting pm2 logs
+
+### Schemas
+
+Balances
+
+chain - text, primary key
+contract - text, primary key
+account - text, primary key
+balance - text
+symbol - text, primary key
+
+Tokens
+
+chain - text, primary key
+contract - text, primary key
+symbol - text, primary key
+precision - integer
+supply - text
+max_supply - text, nullable
+issuer - text
+
 <!-- START doctoc generated TOC please keep comment here to allow auto update -->
 <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
 
@@ -33,6 +71,17 @@ A realtime GraphQL API and indexing service for blockchain applications.
 - Supports ad-hoc external graph stitching and federation.
 - Supports ad-hoc offchain graphql resolvers.
 
+## Hasura Resources
+
+- [Building your schema](https://docs.hasura.io/1.0/graphql/manual/schema/index.html)
+- [GraphQL Queries](https://docs.hasura.io/1.0/graphql/manual/queries/index.html)
+- [GraphQL Mutations](https://docs.hasura.io/1.0/graphql/manual/mutations/index.html)
+- [GraphQL Subscriptions](https://docs.hasura.io/1.0/graphql/manual/subscriptions/index.html)
+- [Event Triggers](https://docs.hasura.io/1.0/graphql/manual/event-triggers/index.html)
+- [Authentication/Access control](https://docs.hasura.io/1.0/graphql/manual/auth/index.html)
+- [Database Migrations](https://docs.hasura.io/1.0/graphql/manual/migrations/index.html)
+- [Guides/Tutorials/Resources](https://docs.hasura.io/1.0/graphql/manual/guides/index.html)
+
 ## Architecture
 
 <center>

README.md

@@ -6,11 +6,11 @@ silent: true
 tasks:
   console:
     cmds:
-      - hasura console --project services/hasura --admin-secret=$HASURA_GRAPHQL_ADMIN_SECRET
+      - hasura console --admin-secret=$ADMIN_SECRET
 
   seed:
     cmds:
-      - hasura seeds apply --project services/hasura --admin-secret=$HASURA_GRAPHQL_ADMIN_SECRET
+      - hasura seeds apply --admin-secret=$ADMIN_SECRET
 
   up:
     cmds:
@@ -33,14 +33,13 @@ tasks:
 
   boot:
     cmds:
-      - docker-compose up -d --build hasura auth 
-      - sleep 30
-      - hasura migrate apply --project services/hasura --admin-secret=$HASURA_GRAPHQL_ADMIN_SECRET
-      - hasura metadata apply --project services/hasura --admin-secret=$HASURA_GRAPHQL_ADMIN_SECRET
-      - hasura seeds apply --project services/hasura --admin-secret=$HASURA_GRAPHQL_ADMIN_SECRET
-      - docker-compose up -d --build core
+      - docker-compose up -d --build 
+      - sleep 20
+      - hasura migrate apply --admin-secret=$ADMIN_SECRET
+      - hasura metadata apply --admin-secret=$ADMIN_SECRET
+      - hasura seeds apply --admin-secret=$ADMIN_SECRET
 
   apply:
       cmds:
-        - hasura migrate apply --project services/hasura --admin-secret=$HASURA_GRAPHQL_ADMIN_SECRET
-        - hasura metadata apply --project services/hasura --admin-secret=$HASURA_GRAPHQL_ADMIN_SECRET
+        - hasura migrate apply --admin-secret=$ADMIN_SECRET
+        - hasura metadata apply --admin-secret=$ADMIN_SECRET