https://github.com/luandro/ssb-nodejs-mobile
A starter project for running Secure Scuttlebutt using NodeJs Mobile project
https://github.com/luandro/ssb-nodejs-mobile
Last synced: 11 months ago
JSON representation
A starter project for running Secure Scuttlebutt using NodeJs Mobile project
- Host: GitHub
- URL: https://github.com/luandro/ssb-nodejs-mobile
- Owner: luandro
- Created: 2018-04-04T13:32:06.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2018-08-02T12:24:42.000Z (almost 8 years ago)
- Last Synced: 2025-04-02T02:13:13.852Z (about 1 year ago)
- Language: JavaScript
- Homepage:
- Size: 1.17 MB
- Stars: 18
- Watchers: 6
- Forks: 3
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Scuttlebot on nodejs-mobile
Experimentation for running [scuttlebot](https://github.com/ssbc/scuttlebot) with [nodejs-mobile-react-native](https://github.com/janeasystems/nodejs-mobile-react-native).
## Goals
- proof-of-concept Android :white_check_mark:
- proof-of-concept iOS :white_check_mark:
- support more native modules (sodium, leveldown, utp-native) :x:
## Usage
```
git clone https://github.com/luandro/ssb-nodejs-mobile.git
cd ssb-nodejs-mobile
npm i
```
Than open the project's `./android` directory in Android Studio in order to download all the necessary dependencies.
Enter the NodeJS project directory and run `npm install` which will also run `npm run prepare` to patch `nodejs-mobile-react-native`.
`npm run dev` to start Android development and logging.
Use `adb logcat -s "NODEJS-MOBILE"` to log NodeJS application.
## Fixes that made this possible
- [Scuttlebot fork](https://github.com/luandro/scuttlebot) (uses [chloride](https://github.com/dominictarr/chloride) instead of [sodium-native](https://github.com/sodium-friends/sodium-native))
- [NodeJS Mobile - name collision error](https://github.com/janeasystems/nodejs-mobile/issues/34#issuecomment-358142287)
- [NodeJS Mobile - folders starting with underscore not copied on Android](https://github.com/janeasystems/nodejs-mobile/issues/60#issuecomment-381288106)