mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-25 17:06:01 +03:00
[GH-ISSUE #1791] how to modify default configurations #1413
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#1413
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @XiaotianZha on GitHub (Nov 21, 2019).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1791
Impacted versions
Latest Modoboa installer on Centos 7.
Steps to reproduce
Install Modoboa on Centos 7 following install directions.
git clone https://github.com/modoboa/modoboa-installer
cd modoboa-installer/
./run.py mytestdomain.xyz
Current behavior
After installing there is a tips :
Congratulations! You can enjoy Modoboa at https://xxxx (admin:password)
And Modoboa is running now. but the configurations of Modoboa are using default .
I have noticed that there is a file named settings.py, but I'm new to python ,I don't know to make modification be effective.(Restart the server or something like?)
@tonioo commented on GitHub (Nov 22, 2019):
@XiaotianZha You must reload uwsgi every time you update the settings.py file.
@XiaotianZha commented on GitHub (Nov 24, 2019):
I modified the condfiguration of db to a mysql server , after reload uwsgi , there is a Internal Server Error when I access the webmail.
And there is an error log in var/spool/mail/root
I have already use the pip install mysqlclient MySQL-python, but it seems not in install into the write path
@XiaotianZha commented on GitHub (Nov 24, 2019):
I have solved this problem after learning the python virtualenv , now it seems I need to re-built table in the new db