In order to prevent regular issues with the notoriously npm-issue-ridden Aragon CLI module, this removes it as a direct dependency and requires it to be installed as a system dependency.
Also adds Truffle as a system dependency to the docs (which was missing before).
The latest Aragon CLI asks has a lot of prompts for every contract deployment. I'll see if we can remove those by specifying more arguments upfront.
In order to prevent regular issues with the notoriously npm-issue-ridden Aragon CLI module, this removes it as a direct dependency and requires it to be installed as a system dependency.
Also adds Truffle as a system dependency to the docs (which was missing before).
The latest Aragon CLI asks has a lot of prompts for every contract deployment. I'll see if we can remove those by specifying more arguments upfront.
refs #158
this is awesome! thanks for looking into it.
maybe we can add the used/tested aragon and truffle version to the readme?
and I think that's a kredits-2
this is awesome! thanks for looking into it.
maybe we can add the used/tested aragon and truffle version to the readme?
and I think that's a `kredits-2`
maybe we can add the used/tested aragon and truffle version to the readme?
Then we have to update it like every two days. They release a lot over at Aragon. :)
and I think that's a kredits-2
Nah, 1 is perfectly fine. Didn't take long.
> maybe we can add the used/tested aragon and truffle version to the readme?
Then we have to update it like every two days. They release *a lot* over at Aragon. :)
> and I think that's a `kredits-2`
Nah, 1 is perfectly fine. Didn't take long.
Then we have to update it like every two days. They release a lot over at Aragon. :)
yep, but also breaking changes. - at least we have to keep in mind which versions we are using/supporting
> Then we have to update it like every two days. They release _a lot_ over at Aragon. :)
yep, but also breaking changes. - at least we have to keep in mind which versions we are using/supporting
Whoever sees something breaking with the latest version on their system should open an issue imo.
We can then at least do a bootstrap on Travis, too, but testing every single truffle script on Travis e.g. would be quite the effort.
Whoever sees something breaking with the latest version on their system should open an issue imo.
We can then at least do a bootstrap on Travis, too, but testing every single truffle script on Travis e.g. would be quite the effort.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In order to prevent regular issues with the notoriously npm-issue-ridden Aragon CLI module, this removes it as a direct dependency and requires it to be installed as a system dependency.
Also adds Truffle as a system dependency to the docs (which was missing before).
The latest Aragon CLI asks has a lot of prompts for every contract deployment. I'll see if we can remove those by specifying more arguments upfront.
refs #158
this is awesome! thanks for looking into it.
maybe we can add the used/tested aragon and truffle version to the readme?
and I think that's a
kredits-2Then we have to update it like every two days. They release a lot over at Aragon. :)
Nah, 1 is perfectly fine. Didn't take long.
Tests are also green after adding sys deps. Merging...
yep, but also breaking changes. - at least we have to keep in mind which versions we are using/supporting
Whoever sees something breaking with the latest version on their system should open an issue imo.
We can then at least do a bootstrap on Travis, too, but testing every single truffle script on Travis e.g. would be quite the effort.