Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Builds for each platform #584

Open
kernelwhisperer opened this issue Jul 5, 2019 · 0 comments
Open

Builds for each platform #584

kernelwhisperer opened this issue Jul 5, 2019 · 0 comments
Labels
💬 needs discussion A feature not yet agreed on that needs more discussion

Comments

@kernelwhisperer
Copy link
Contributor

Feature

Currently we install the CLI from npm and it gets built locally.
We could package binaries for each platform just like go-ipfs.

This is a step further (from shrinkfiles) to reduce issues related to dependencies, in particular issues with node versions (see #461 ) and npm persmissions (see #549 ) and some of which are difficult to debug (#551).

Possible way of doing it: https://dev.to/jochemstoel/bundle-your-node-app-to-a-single-executable-for-windows-linux-and-osx-2c89

Reduce maintenance overhead by integrating with Aragon Desktop

Aragon Desktop is an Electron app that packages node and has builds for multiple platforms.

Integrating the CLI with the Aragon Desktop would mean fewer downloads for developers (assuming aragon run & aragon start would work with Aragon Desktop and less hassle for maintainers as we would be doing this platform building in only one place.

Possible flow

The flow for users:

  • Download Aragon Desktop
  • Press ~ and open an integrated terminal that has the dao cli installed

The flow for devs:

  • Download Aragon Desktop: Hacker Edition or go to Settings > Enable dev tools
  • This will expose in the terminal the dev-cli which you can use to set up a local environment.

Bundling everything in aragon-desktop and downloading extra versions over IPFS can help with networking: instead of relying on npm, github and ipfs (see #505 ) people just need to download 1 hash from our gateway or from any peer that has it.

When one of these services we rely on goes down there isn't much we can do...

@kernelwhisperer kernelwhisperer added the 💬 needs discussion A feature not yet agreed on that needs more discussion label Jul 5, 2019
@stale stale bot added the abandoned label Jan 1, 2020
@aragon aragon deleted a comment from stale bot Jan 2, 2020
@stale stale bot removed the abandoned label Jan 2, 2020
@stale stale bot added the abandoned label Jul 1, 2020
@macor161 macor161 removed the abandoned label Jul 1, 2020
@aragon aragon deleted a comment from stale bot Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💬 needs discussion A feature not yet agreed on that needs more discussion
Projects
None yet
Development

No branches or pull requests

2 participants