Scope of this post.
I would love to hear feedback on what sections of LBRY’s rich ecosystem should be developed and expanded on with docker first. See who would use what within the community. Then I can maybe focus on that first. Personally, I’ve thought Spee.ch would be the most impactful but Chainquery would be a pretty good performance booster if we could encourage development backed by it.
My goals
I plan on writing a deployable stateless docker best practices container cluster to the best of my ability. Ideally, this will have a hand full of containers supporting the various components to get a staging environment or even production environment of LBRY and other components running in under a few minutes without having to read anything. The idea is to help enable people through official channels, to boot up an environment to kick the tires and test drive the tech. Some people want to get to know the feel of how something runs in the ideal environment before getting deep down into the mechanics. Because what good an app if it runs like shit and all you have to go on is buying the hype.
Let’s prove this product to the greater community! With Spee.ch we’re already making huge strides to being insanely useful.
What do I mean by Stateless
Stateless means a container wrapping an application in which you can deploy like a lego block, you don’t have to care about what’s inside of the container and by default, it should just work. However, you should be able to configure any if not all of the configs for the appliance inside. The other goal I will have personally with a configuration mechanism will be to not break any future changes to configs as best as possible while keeping the maintainability fairly trivial.
Maintainability
Anyone should be able to glance at what’s happening in the code and contribute a tweak or addition. If you think that I’m doing something in a way that is less than optimal feel free to reach out to me and I’m more than open to learning new and interesting concepts.