Docker Configuration and Orchestration Wizard with Kubernetes and Rancher Support

Docker Configuration and Orchestration Wizard with Kubernetes and Rancher Support

2022-09-14 0 1,467
Resource Number 38440 Last Updated 2025-02-24
¥ 0 USD Upgrade VIP
Download Notice Demo
Can't download? Please contact customer service to submit a link error!
Value-added Service: Installation Guide Environment Configuration Secondary Development Template Modification Source Code Installation

Product Details 商品属性

  • Language: HTML
  • Database:
  • License: License-Free
  • Source Code: Fully Open Source
  • Specification: Full Website Source
  • Delivery: Automatic (instant download after payment)

Dckr is a wizard-based build tool for container configuration and orchestration based on Docker. (Supports Docker, Compose, Kubernets, and Rancher resource file wizard builds)

 

Project Objectives
Through the semantic UI wizard-style guidance to build relevant container configurations and orchestrate files, you can reduce your learning cost.
Through the conversion function, you can easily convert the configuration files of different container products to and from each other, which greatly improves your work efficiency.
The YAML files you build with it are compliant, freeing you from the pain of writing YAML files due to formatting issues such as indentation.
It allows you to easily make changes to the relevant configuration items, and then click the build button to change the content of the editor accordingly; It can be used to assist in container-related teaching.
Its implementation scheme can provide some ideas or even a solution for various requirements such as “generating configuration files through semantic UI”.
Get started quickly

Run locally

git clone https://github.com/LGSKOKO/Dckr.git

cd Dckr

npm install

npm run serve

Server deployment

#1. Modify the request.js file in the src directory of the project to change localhost to the specific backend deployment IP address
#2. Execute the following command
npm run build
#3. Copy the dist directory to the installed and configured web server (apache or nginx, etc.).
#4. Enter the corresponding http address and you’re done!!
Project structure
.
├── public // Static resource file
│ ├── favicon.jpg // Project icon
│ └── index.html // Project html entry file
├── screenshots // Project screenshots
├── src // source directory
│ ├── components // components
│ │ ├── DockerCompose // Compose module component
│ │ │ ├── Step1.vue
│ │ │ ├── Step2.vue
│ │ │ ├── Step3.vue
│ │ │ ├── Step4.vue
│ │ ├── Dockerfile // Docker module component
│ │ │ ├── Step1.vue
│ │ │ ├── Step2.vue
│ │ │ ├── Step3.vue
│ │ │ ├── Step4.vue
│ │ │ ├── Step5.vue
│ │ ├── Kubernetes // Kubernetes module components
│ │ │ ├── common // The most basic component of the Kubernetes module
│ │ │ | ├── Base.vue // Fill in the basic information component
│ │ │ | ├── Container.vue // Fill in the container configuration component
│ │ │ | ├── Other.vue // Fill in the other information component
│ │ │ | └── Volume.vue // Fill in the disk mount information component
│ │ │ ├── template // Abstract a layer of components on a common basis
│ │ │ | ├── OtherTemplate.vue // OtherTemplate component of Deployment and ReplicaSet components
│ │ │ | └── PodTemplate.vue // PodTemplate component of Deployment and ReplicaSet components
│ │ │ ├── ConfigMap.vue // ConfigMap template component
│ │ │ ├── Deployment.vue // Deployment template component
│ │ │ ├── Pod.vue // Pod template component
│ │ │ ├── ReplicaSet.vue // ReplicaSet template component
│ │ │ ├── Secret.vue // Secret template component
│ │ │ └── Sevice.vue // Service template component
│ │ ├── Editor.vue // Editor public component
│ │ ├── Header.vue // Header.vue // Header.vue
│ │ └── Sider.vue // sidebar public component
│ ├── router
│ │ └── index.js // Routing configuration
│ ├── store
│ │ └── index.js // Vuex configuration
│ ├── view
│ │ ├── CreateDockerCompose.vue // Compose module page
│ │ ├── CreateDockerfile.vue // Docker module page
│ │ ├── CreateKubernetes.vue // Kubernetes module page
│ │ ├── CreateRancher.vue // Racnher module page
│ │ └── Home.vue // Main page
│ ├── App.vue // Page entry file
│ ├── commonUtil.js // Customize the tool file
│ ├── main.js // Program entry file, load various common components
│ └── request.vue // Customize the project request file
└──
Run a screenshot

Docker module
 

 

Compose module

 

 

Kubernetes module

Guided builds

 

 

Rancher module

 

 

资源下载此资源为免费资源立即下载
Telegram:@John_Software
☆☆☆☆☆0 pts · 0 reviews
Updated 2025-02-24

Q&A

No questions yet. Ask the seller!

Reviews

No reviews yet. Share your experience after purchase.

Disclaimer: This article is published by a third party and represents the views of the author only and has nothing to do with this website. This site does not make any guarantee or commitment to the authenticity, completeness and timeliness of this article and all or part of its content, please readers for reference only, and please verify the relevant content. The publication or republication of articles by this website for the purpose of conveying more information does not mean that it endorses its views or confirms its description, nor does it mean that this website is responsible for its authenticity.

TopTinker Design & Images Docker Configuration and Orchestration Wizard with Kubernetes and Rancher Support https://toptinker.com/38440.html

商家类型:个人(声明)

Share free open-source source code

Q&A
  • 1. Automatic: After making an online payment, click the (Download) link to download the source code; 2. Manual: Contact the seller or the official to check if the template is consistent. Then, place an order and make payment online. The seller ships the goods, and both parties inspect and confirm that there are no issues. TopTinker will then settle the payment for the seller. Note: Please ensure to place your order and make payment through TopTinker. If you do not place your order and make payment through TopTinker, and the seller sends fake source code or encounters any issues, TopTinker will not assist in resolving them, nor can we guarantee your funds!
View details
  • 1. Default transaction cycle for source code: The seller manually ships the goods within 1-3 days. The amount paid by the user will be held in escrow by TopTinker until 7 days after the transaction is completed and both parties confirm that there are no issues. TopTinker will then settle with the seller. In case of any disputes, TopTinker will have staff to assist in handling until the dispute is resolved or a refund is made! If the buyer places an order and makes payment not through TopTinker, any issues and disputes have nothing to do with TopTinker, and TopTinker will not be responsible for any liabilities!
View details
  • 1. TopTinker will permanently archive the transaction process between both parties and snapshots of the traded goods to ensure the authenticity, validity, and security of the transaction! 2. TopTinker cannot guarantee services such as "permanent package updates" and "permanent technical support" after the merchant's commitment. Buyers are advised to identify these services on their own. If necessary, they can contact TopTinker for assistance; 3. When both website demonstration and image demonstration exist in the source code, and the text descriptions of the website and images are inconsistent, the text description of the image shall prevail as the basis for dispute resolution (excluding special statements or agreements); 4. If there is no statement such as "no legal basis for refund" or similar content, any indication on the product that "once sold, no refunds will be supported" or other similar declarations shall be deemed invalid; 5. Before the buyer places an order and makes payment, the transaction details agreed upon by both parties via WhatsApp or email can also serve as the basis for dispute resolution (in case of any inconsistency between the agreement and the description of the conflict, the agreement shall prevail); 6. Since chat records and email records can serve as the basis for dispute resolution, both parties should only communicate with each other through the contact information left on the system when contacting each other, in order to prevent the other party from denying their own commitments. 7. Although the probability of disputes is low, it is essential to retain important information such as chat records, text messages, and email records, in case a dispute arises, so that TopTinker can intervene quickly.
View details
  • 1. As a third-party intermediary platform, TopTinker solely protects transaction security and the rights and interests of both buyers and sellers based on the transaction contract (product description, agreed content before the transaction); 2. For online trading projects not on the TopTinker platform, any consequences are unrelated to this platform; regardless of the reason why the seller requests an offline transaction, please contact the administrator to report.
View details

Related Source code

TopTinker Customer Service

24-hour online professional services