Shulou(Shulou.com)06/01 Report--

This article introduces the knowledge about "docker as initiator and cloud devops selection method". In the actual case operation process, many people will encounter such difficulties. Next, let Xiaobian lead you to learn how to deal with these situations! I hope you can read carefully and learn something!

legacy engager and devops cloud build

The above selections all have several common characteristics. 1. In this engitor, it is an assembly running environment. This language environment "collects and synthesizes online" the source code logic submitted by users in a fragmented way. It is a cloud-constructed development environment class program. 2, and the engine app formed should run with the help of this engine, because it should output the application under this source code for the source code fragment. This is in line with our usual requirements and standards for engitor selection.

So can you build an engitor that can still be oriented to src logic output on one end and application output on the other end instead of just requiring that the input must be source code and the output must be APP? (In a nutshell, generically build arbitrary programs), and do not require running under the above specific initiator? Is it still called an engitor? Does it still make sense?

After all, we want to get a universal engitor that will traditionally go from (Linux ecosystem start,CUI, only OS kernel and toolchain at that time), automate the compilation process of multi-language source programs/binaries involved in the development of any complex application, package the packaging process of multi-language vm, take into account these traditional orchestration techniques of build scripts and package management techniques of OS, and even cloud the build itself and build service externalization. Feed remote build-cloud build,. Form automated, cloud-scripted compilation results, and take this as the running target, only responsible for writing things on the final APP.

This is essentially a single requirement to accept arbitrary constructs on the input and generate arbitrary programs on the output. Such an engitor actually runs as os for enginx, in order to be able to run langsys on all possible language systems on it for engitor. And an engitor doesn't have to be a jupyter+web execution environment-style "cloud build" and middleware package. For example, it can be a "cloud build" and middleware package made up of any program (non-source code fragments of a language, binary or non-IDE class production process). It can have no input or output in the sense of an engitor. However, it can still be applied to the engitor exception.

So how do you integrate that, and that's actually what devops does. Traditionally, we used various virtual machines for development on PCs, so we now have dockers and devops.

docker as engine and cloud IDE.

In that passage we talked about jupyter as well as jupyter hub. In fact, it is equivalent to docker version of github+dockerhub composed of devops.

Docker as a generic build technology and container, docker and docker-compose are actually two separate processes, docker is only responsible for run, and github is equivalent to the engineering environment for collecting source code in ide, so what else can we get? For example, in combination with ellie above, we can put this ellie ide in the case of combining docker and gitlab cl for elmlang. Make a cloud IDE.

"docker as initiator and cloud devops selection method is what" content introduced here, thank you for reading. If you want to know more about industry-related knowledge, you can pay attention to the website. Xiaobian will output more high-quality practical articles for everyone!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.