#42 closed enhancement (fixed)
config.json should be renamed to config_dist.json
Reported by: | wbronsema | Owned by: | madair |
---|---|---|---|
Priority: | P2 | Milestone: | 1.1 |
Component: | Core | Version: | 1.0.4 |
Severity: | Trivial | Keywords: | |
Cc: | Browser: | All | |
External ID: | Operating System: | All | |
state: | Approved |
Description ¶
config.json is always in a modified state because this file is custom configured per installation. I propose to rename it config_dist.json so as to not interfere with the update and commit operations.
The only downside is if something is added then you run the risk of missing that in your own personal json.config.
Thougts?
Change History (10)
comment:1 by , 17 years ago
Milestone: | → 1.1 |
---|---|
state: | New → Approved |
Status: | new → assigned |
comment:2 by , 16 years ago
comment:3 by , 16 years ago
I'm undecided on the best approach here. I like the fact that we can run fusion as-is from SVN, it makes development a lot easier, and this change would facilitate that.
I think we should go ahead and rename it in SVN.
comment:4 by , 16 years ago
comment:6 by , 16 years ago
comment:7 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
updated thee wiki and INSTALLATION.TXT files in 1.1 and trunk
in principle this would be good but it would add an additional step in the installation process to copy that file to config.json and edit if required.
Do we want to do this?