In order to get help regarding LindaX Wallet:
- Go to our Discord channel to connect with the community for instant help.
- Search for similar issues and potential help.
- Or create a new issue and provide as much information as you can to recreate your problem.
Contributions via Pull Requests are welcome. You can see where to help looking for issues with the Enhancement or Bug labels. We can help guide you towards the solution.
You can also help by responding to issues.
If you want to install the app from a pre-built version on the release page, you can simply run the executable after download.
For updating, simply download the new version and copy it over the old one (keep a backup of the old one if you want to be sure).
In order to install from .zip files, please install libgconf2-4 first:
apt-get install libgconf2-4The data folder for LindaX Wallet depends on your operating system:
- Windows
%APPDATA%\LindaX Wallet - macOS
~/Library/Application\ Support/LindaX Wallet - Linux
~/.config/LindaX Wallet
For development, a Meteor server assists with live reload and CSS injection.
Once a the LindaX Wallet version is released the Meteor frontend part is bundled using the meteor-build-client npm package to create pure static files.
To run the LindaX Wallet in development you need:
- Node.js
v7.x(use the preferred installation method for your OS) - Meteor javascript app framework
- Yarn package manager
Install the latter ones via:
$ curl https://install.meteor.com/ | sh
$ curl -o- -L https://yarnpkg.com/install.sh | bashNow you're ready to initialize the LindaX Wallet for development:
$ git clone https://github.com/thelindaprojectinc/lindax-wallet.git
$ cd LindaX-Wallet
$ yarnFor development we start the interface with a Meteor server for auto-reload etc.
Start the interface in a separate terminal window:
$ yarn dev:meteorStart the LindaX Wallet interface in a separate terminal window:
$ yarn dev:walletIn the original window you can then start the wallet with:
$ yarn dev:electronNOTE: Client binaries (e.g. glinx) specified in clientBinaries.json will be checked during every startup and downloaded if out-of-date, binaries are stored in the config folder.
NOTE: use --help to display available options, e.g. --loglevel debug (or trace) for verbose output
You can pass command-line options directly to Glinx by prefixing them with --node- in
the command-line invocation:
$ yarn dev:electron --node-rpcport 19343 --node-networkid 2The --rpc wallet option is a special case. If you set this to an IPC socket file
path then the --ipcpath option automatically gets set, i.e.:
$ yarn dev:electron --rpc path/to/glinx.ipc...is the same as doing...
$ yarn dev:electron --rpc /my/glinx.ipc --node-ipcpath /path/to/glinx.ipcIf you would like to quickly set up a local private network on your computer, run:
glinx --devLook for the IPC path in the resulting glinx output, then start the wallet with:
$ yarn dev:electron --rpc path/to/glinx.ipcOur build system relies on gulp and electron-builder.
Cross-platform builds require additional electron-builder dependencies.
$ brew install rpm$ brew install wine --without-x11 mono makensis$ brew install gnu-tar libicns graphicsmagick xzTo generate the LindaX Wallet:
$ yarn build:walletThe generated binaries will be under dist_wallet/release.
To build binaries for specific platforms (default: all available) use the following flags:
$ yarn build:wallet --mac # mac
$ yarn build:wallet --linux # linux
$ yarn build:wallet --win # windowsWhen building a binary, you can optionally skip some tasks — generally for testing purposes.
$ yarn build:wallet --mac --skipTasks=bundling-interface,release-distPrints the SHA-256 checksums of the distributables.
It expects installer/zip files to be in the generated folders e.g. dist_wallet/release
$ yarn task checksums [--wallet]Any other gulp task can be run using yarn task.
$ yarn task clean-dist-
Install release globally:
$ yarn global add release
-
Create a git tag and a GitHub release:
$ release <major|minor|patch>
-
A generated release draft will open in the default browser. Edit the information and add assets as necessary.
Tests run using Spectron, a webdriver.io runner built for Electron.
First make sure to build the LindaX Wallet with:
$ yarn build:walletThen run the tests:
$ yarn test:unit:once
$ yarn test:e2eNote: Integration tests are not yet supported on Windows.