AgileConfig has had a “big problem” since its launch – its UI is ugly. Because at the beginning of this project is for their own use, even the UI interface is not, all rely on manual configuration in the database. Later, some interfaces were hastily released using the simple code of bootstrap3, and the usability was not good enough. I never stopped thinking about it. Finally during the Chinese New Year began to refurbish the UI. For a back-end programmer, with a standard straight aesthetic, it’s almost impossible to make a nice UI. So it’s a front-end framework. After some research, we decided to use the ant-Design-Pro framework. Ant- Design is currently the most popular front-end component library, Ant- Design – Pro is an official product based on Ant- Design admin background rapid development framework. Ant-design is developed based on React. I have never played React, so I can learn from it. After several preview releases, release-1.2.0 is finally available today.

Release – 1.2.0

  • The entire UI was rewritten using Ant-Design-Pro
  • Support English internationalization







AgileConfig introduction

This is a lightweight configuration center based on.net Core. It’s easy to associate configuration centers with microservices, and if you choose a microservices architecture, you’ll almost certainly need a configuration center. Actually, I’m not here to enjoy the popularity of wechat. There are distributed applications in the world but it’s not a microservice. For example, there are many traditional SOA applications that are distributed, but are not complete microservices architectures. These programs can be difficult to change configuration because they are spread across multiple servers. Or even though some applications are not distributed, but they are containerized, they have a hard time changing the configuration. So I developed AgileConfig not for microservices, but for distributed, container-deployed applications that can read and modify configurations more easily.

AgileConfig is lightweight and easy to deploy, configure, use and learn. It only extracts the necessary functions and is not as complex and huge as Apollo. But it’s good enough to replace webConfig, appSettings. json, etc. If you don’t want to use a microserver bucket, and you don’t want to have to read a bunch of tutorials and a couple of servers to deploy a configuration center, try AgileConfig 🙂

The characteristics of

  1. The deployment is simple, requiring at least one data node and supporting docker deployment
  2. Supports distributed deployment of multiple nodes to ensure high availability
  3. The configuration supports application isolation, and the intra-application configuration supports group isolation
  4. Applications support inheritance, where common configurations can be extracted into one application and then inherited by other applications
  5. Using the long-link technology, the configuration information is pushed to the client in real time
  6. Support IConfiguration, IOptions mode read configuration, the original program can almost without transformation
  7. Configuration modification support version record, roll back configuration at any time
  8. If all nodes fail, the client supports reading the configuration from the local cache
  9. Supports Restful API maintenance configuration

✨✨✨Github address: github.com/kklldog/Agi… Open source is not easy. Welcome to Star ✨✨✨

Demo Address: AgileConfig Server Demo Password: 123456