Why modifying the template in an external editor does not take effect

Template cache mechanism description

Auto CMS uses memory cache optimization strategies in the production environment:

1. Preloading at startup:Load the template files all at once into memory when the service starts
   
2. Render acceleration:Directly read memory template for page requests to avoid repeated disk I/O operations
   
3. Performance advantages:Reduce server load, enhance web page response speed to the millisecond level
   

Development modification注意事项

When modifying template files through external editors (Baota panel/VSCode, etc.):

• ✖ Modifications only affect disk files
  
• ✖ Memory cache template will not update automatically
  
• ✔ It needs to take effect in the following way:
  
• ▸ Restart the service (for production environment)
  
• ▸ Switch to development environment (recommended for development stage)
  

Environment Configuration Guide

Open the root directory underconfig.json，foundenvConfigure, and make modifications.

Development mode (development)

Note that each request reading the template in real-time will increase the server load

{
    ...
    "server": {
        "env": "development",
        ...
    }
}

Applicable scenarios: template debugging period, website development stage Performance impact: increased server I/O

生产模式(production)

{
    ...
    "server": {
        "env": "production",
        ...
    }
}

**实践：

1. 开发期保持development模式
   
2. 上线前完成全量测试
   
3. Deploy and switch to production mode
   
4. Template update must follow the 'modify→restart' process