没有不值得去解决的问题,也没有不值得去学习的技术!

Analyzing and Resolving Chinese Character Support for Rancher Environment Variables

After completing the upgrade again, I enter the container to check and find that the variables in the configuration file have been replaced. Therefore, the issue of variables not being replaced is essentially unrelated to Chinese

1. View the \build\c_files\config\init\config0.sh file.

ShellScript

sed -i "s@PCS_API_CFG_CPU_PARAMS_XCONTENT@PCS_API_CFG_CPU_PARAMS_XCONTENT@g" /sobey/www/pcs-api/environments/dev/common/config/params-local.php;
sed -i "s@PCS_API_CFG_CPU_PARAMS_XCONTENT@PCS_API_CFG_CPU_PARAMS_XCONTENT@g" /sobey/www/pcs-api/environments/prod/common/config/params-local.php;
sed -i "s@PCS_API_CFG_CPU_PARAMS_PCS@PCS_API_CFG_CPU_PARAMS_PCS@g" /sobey/www/pcs-api/environments/dev/common/config/params-local.php;
sed -i "s@PCS_API_CFG_CPU_PARAMS_PCS@PCS_API_CFG_CPU_PARAMS_PCS@g" /sobey/www/pcs-api/environments/prod/common/config/params-local.php;
sed -i "s@PCS_API_CFG_CPU_PARAMS_SOURCE@$PCS_API_CFG_CPU_PARAMS_SOURCE@g" /sobey/www/pcs-api/environments/dev/common/config/params-local.php;
sed -i "s@PCS_API_CFG_CPU_PARAMS_SOURCE@$PCS_API_CFG_CPU_PARAMS_SOURCE@g" /sobey/www/pcs-api/environments/prod/common/config/params-local.php;

2. In the Rancher environment variables, the values of PCS_API_CFG_CPU_PARAMS_XCONTENT and PCS_API_CFG_CPU_PARAMS_PCS are in Chinese, as shown in Figure 1.

In the Rancher environment variables, the values of PCS_API_CFG_CPU_PARAMS_XCONTENT and PCS_API_CFG_CPU_PARAMS_PCS are in Chinese
Figure 1

3. After the upgrade is complete, I enter the container to check and find that the variables in the configuration file have not been replaced, as shown in Figure 2.

After the upgrade is complete, I enter the container to check and find that the variables in the configuration file have not been replaced
Figure 2

4. I edit the \build\c_files\config\init\config0.sh file and replace @ with @$ in the variable parts involving Chinese; the $ was previously missing.

ShellScript

sed -i "s@PCS_API_CFG_CPU_PARAMS_XCONTENT@$PCS_API_CFG_CPU_PARAMS_XCONTENT@g" /sobey/www/pcs-api/environments/dev/common/config/params-local.php;
sed -i "s@PCS_API_CFG_CPU_PARAMS_XCONTENT@$PCS_API_CFG_CPU_PARAMS_XCONTENT@g" /sobey/www/pcs-api/environments/prod/common/config/params-local.php;
sed -i "s@PCS_API_CFG_CPU_PARAMS_PCS@$PCS_API_CFG_CPU_PARAMS_PCS@g" /sobey/www/pcs-api/environments/dev/common/config/params-local.php;
sed -i "s@PCS_API_CFG_CPU_PARAMS_PCS@$PCS_API_CFG_CPU_PARAMS_PCS@g" /sobey/www/pcs-api/environments/prod/common/config/params-local.php;
sed -i "s@PCS_API_CFG_CPU_PARAMS_SOURCE@$PCS_API_CFG_CPU_PARAMS_SOURCE@g" /sobey/www/pcs-api/environments/dev/common/config/params-local.php;
sed -i "s@PCS_API_CFG_CPU_PARAMS_SOURCE@$PCS_API_CFG_CPU_PARAMS_SOURCE@g" /sobey/www/pcs-api/environments/prod/common/config/params-local.php;

5. After completing the upgrade again, I enter the container to check and find that the variables in the configuration file have been replaced. Therefore, the issue of variables not being replaced is essentially unrelated to Chinese, as shown in Figure 3.

After completing the upgrade again, I enter the container to check and find that the variables in the configuration file have been replaced. Therefore, the issue of variables not being replaced is essentially unrelated to Chinese
Figure 3

关于作者 · 持续学习与技术实践

我是一名拥有 15 年以上开发经验的技术从业者,自 2013 年起持续运营个人技术博客,记录工作与个人项目中遇到的真实问题,以及解决问题过程中的探索、实践和思考。

除了技术写作,我也在持续开发和维护自己的独立项目,探索新技术和新工具在实际场景中的应用。我始终相信,没有不值得去解决的问题,也没有不值得去学习的技术。

如果这篇文章对你有所帮助,欢迎浏览博客中的其他文章,也欢迎交流技术经验与想法。

关于我  ·  GitHub  ·  邮件联系