Work report (2)

Recently, I can only use the evening time to write about my personal affairs kkitDeploy, Weekends and other rest days are all arranged out . Official account will also be broken. I hope you will understand ！

kkitDeploy It is the second full stack project of open source , This project may be nothing in the eyes of others , But I put enough effort into it .kkitDeploy It's a gift for myself , In memory of my old man IT All the detours we have taken . I will always maintain this project . Alibaba cloud will be connected in the future , Huawei cloud and other public clouds ,k8s,swarm And container layout tools .vmware,kvm Virtual platform , We still have a lot of work to do ！

Every time shell It's really crazy to test the effect over and over again after the script ！ Writing makes you afraid ！

Simply report to you kkitDeploy1.0 Development progress of .

1、 Bottom shell Script optimization rewriting completed 80%, Including the optimization and improvement of all previous one click deployment scripts .

2、 Add automatic identification yml File function , So you can deploy yml It will be very, very convenient to file .

3、 Add a task timeout forced exit function .

4、websocket complete .

Functions and difficulties under development ：

1、 No perceptual upgrade , I will expand the script pool and upgrade scripts from time to time bug. To avoid frequent updates, users must automatically obtain source side script updates , And synchronize to the client in a relatively timely manner .

difficulty ： The script pool dynamic update design is completed , But the dynamic update of classification metadata still needs to be considered ！ For example, the database class adds scripts , How to increase the classification ？ Reinitialize redis Metadata ？？？

kkitDeploy The design is VUE+django+redis+shell framework , To avoid overlapping with the company code , Only information flow and data flow can be rewritten , So it's no use ansible, No relational databases ！

If there is a relational database, you can initialize the cascading menu data through the self association table . Similar to another version of the architecture ：

These data and cascading relationships are extracted from the database .

You may need to reorganize the metadata format ？ I feel like I'm going to rewrite the front end !!!

Zhenima shit!!!

I'll think about it again , Brother Rong, think again ！~

After this, the architecture will be finalized ！！ The rest is easy ！