Camron G. Levanger: Treating Swarm as a Project Dependency

Wed, Oct 2, 2019, 12:00 AM

Camron G. Levanger: Treating Swarm as a Project Dependency Working with a team of engineers in the same codebase can be problematic when it comes to project dependencies. While this is a problem that has been solved many times in various ways, here we will introduce a tool and methodology for treating Swarm as a dev dependency in your project. - A simple command line tool and YAML file in your project will help make sure all engineers are developing against the same version of Swarm. - Pin specific commits/tags/branches to specific versions of Swarm to cut out potential confusion from your workflows. - Learn how to integrate these tools into CI/CD pipelines. - Run multiple instances of any version of Swarm on any machine with a single, short command. - Potential strategies for using the same tools to distribute your software built using Swarm. About Camron Camron is a blockchain/decentralization advocate and currently working as a Senior Architect at Mainframe. A professional musician, competitive marksman, and avid outdoorsman. Well versed in communications and telephony, Camron was focused for many years on high-volume systems performance, building systems capable of handling billions of transactions per day in real-time. Eventually moving into systems architectures and managing devops teams at various start up ventures, Camron brings unique real-world experience to the decentralized space.