Hi, @ryanchristo. I have been migrating my app-in-progress to layer on top of Colony Starter so that I can stay up to date with colony more easily, without having to manage all the dependencies, etc. myself. It’s generally going ok but i have two requests:
Is it possible to move the colonyNetwork code outside of the
src folder? Generally the src folder is for code that is specifically a part of an app, not a dependency of an app. Having it in the src folder affects code lookup and other things and can slow down operation of a code editor/IDE like VSCode.
Of course you could just move it to another folder outside of
src, but for long term viability and usefulness you may want to look into turning it into a npm installed package itself. Two examples of other CLIs that do this are:
- Vue-cli (an awesome, very well designed cli tool), has a component called
vue-cli-servicethat handles various commands that are needed. You could create a colony-cli-service that handled things like starting ganache and trufflepig, etc. It is described here: https://cli.vuejs.org/guide/cli-service.html#using-the-binary
- Zeppelin OS has its use
zoscli, which I am also using as a part of my project because I like their upgradeable contract system: https://github.com/zeppelinos/zos
I hope we reach a point some time soon where there is one cli that works with all contract libraries and packages that are needed, but we are definitely not there yet.
Is it possible to anticipate that users of Colony Starter will want to make and deploy their own additional contracts on top or along side Colony? If you could set up Colony Starter with the assumption that people will be adding more contracts and deploying them with Truffle or Zos that would be great. I have added what I need for now, but that has involved installing two versions of Truffle, for example. It would be great if only one install of Truffle, etc. was needed.
Thanks for considering these things that will make Colony Starter a richer tool for a wider range of developers.