nacos installation and configuration

I. nacos installation

• Official Documentation: https://nacos.io/en-cn/docs/what-is-nacos.html
• docker install nacos: docker run --name nacos-standalone -e MODE=standalone -e JVM_XMS=512m -e JVM_XMX=512m -e JVM_XMN=256m -p 8848:8848-d nacos/nacos-server:latest
• Notes
  • The memory of the virtual machine should be enough. My allocation is 4G memory. If the above JVM settings are default, it will be very large
  • Because this is relatively large, so be patient, and make sure that Ali's mirror has been configured

• At the same time, it can be configured to automatically start at boot: docker container update --restart=always 770ecbd6b209, (770ecbd6b209 is modified to its own container id)
  

---

Second, nacos visit

• Access address: http://192.168.124.51:8848/nacos/index.html, (192.168.124.51 is modified to your own virtual machine ipaddress)
  

• Default username and password: nacos/nacos
  

---

Third, nacos configuration details

1 - Configuration Management - New Configuration

2 - Namespace

• Namespaces and profiles:
  • The main function is to isolate the configuration set, that is, to isolate the Data ID;
  • Some configuration sets can be placed under a namespace
  • Configuration set can be simply understood as a configuration set (Data ID) is a configuration file
  • Data ID can also be more flexible. For example, it is possible to configure DB as a Data ID, consul as a Data ID, etc.
• Microservices:
  - Because there are many services involved in microservices, namespace is a very good choice;
  - We can create a namespace for each service;
  - each namespace contains web services and srv services: eg user_web, user_srv
• Namespace - New: After successful creation, a namespace ID will be created for us by default

3 - Namespaces - Add Configuration Management

• After creating the namespace, you can view the newly added namespace in configuration management
  
  
  

4 - Group

• Throw a question: We can indeed isolate microservices now, but how do the development, testing, and production environments of different microservices differ
• Use groups to solve the above problems: When we create a new configuration set, fill in the group Group to distinguish whether it is a development, test or production environment (note that this group cannot be modified, so inWhen creating a new one, you need to fill in the corresponding group)
  
• Clone Configuration Group
  
  
  
• We can also use the same Data Id and use different Groups to distinguish them