casey2n1tech/private_rubuntu repository overview

Rust fills the roles of server and application orchestrator. The "latest" image is/should be named "base", meaning minimum. If you want to use Rust but have no other demands; start with the latest or base. The more specific your project is in conjunction with how closely your ultimate use case aligns with mine will determine if you can or should move up or down (or laterally) in the repo tag sequence. I use tags as a use case identifier & phase (level of customization) (and not necessarily versions (of Rust or Ubuntu). For example, the base tag (currently the "latest") is Rust on top of Ubuntu in a docker container with VS Code for control and interaction. You can go any way you want to with it. You may need to add things but not remove them. The next tag will have things added and perform a specific set of tasks against a specific target. As soon as my target or tasks veer away from yours, at that point stop, go back one version (tag), and use that image. The goal is to produce a set of images that anyone can use and simply add and not remove to create their denEnv. Tags are not always vertical or hierarchical. There are just as many lateral images that have the same amount/level of customization but are different. Same tag/customization level, but a different use case.