# Detailed installation guide + control panel | Super detailed tutorial for installing discourse + control panel

**URL:** <https://meta.discourse.org/t/detailed-installation-guide-control-panel-discourse/278426>\
**Category:** Sysadmins\
**Tags:** chinese-translation\
**Created:** [September 9, 2023, 4:59pm UTC](https://meta.discourse.org/t/detailed-installation-guide-control-panel-discourse/278426 "2023-09-09T16:59:47Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![zengyunsi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zengyunsi/32/265722_2.png) [@zengyunsi](https://meta.discourse.org/u/zengyunsi)\
**Post date:** [September 10, 2023, 12:32pm UTC](https://meta.discourse.org/t/detailed-installation-guide-control-panel-discourse/278426/5 "2023-09-10T12:32:50Z")

</div>

😅 But editing the configuration file, I found that rebuilding didn’t work, and changing the environment variables in the container took effect in seconds, saving the trouble of rebuilding. Whether the plug-in has any effect is temporarily unclear.

Before, I didn’t type  
sudo -s  
and kept getting errors, and I didn’t know where the problem was…

Master, do you know how to use the API with a Chinese username? The header cannot contain Chinese characters.

😅 I say, tinkering with the configuration file proved fruitless, as the rebuild didn’t take effect. However, altering the container’s environment variables worked like a charm in mere seconds, sparing me the bother of rebuilding. The impact on plugins remains uncertain for the time being.

Previously, I’d neglected to enter ‘sudo -s’, resulting in a barrage of error messages. I was utterly flummoxed as to the source of the problem.

I say, old chap, might you know how a Chinese username could utilise the API? The header, you see, mustn’t contain Chinese characters.

---

_[View the full topic](https://meta.discourse.org/t/detailed-installation-guide-control-panel-discourse/278426)._