Github user kxepal commented on the pull request:
https://github.com/apache/couchdb/pull/251#issuecomment-47710093
@sebastianrothbucher
Nice found! As far as I see, there is no `copy:ace` rule for `debug` target:
https://github.com/apache/couchdb/blob/master/src/fauxton/Gruntfile.js#L462
However, problem gets to be fun since in `settings.json` both `release` and
`couchapp` are uses `dist/debug` artefact:
https://github.com/apache/couchdb/blob/master/src/fauxton/settings.json.default#L34
So I wonder if we could get broken Fauxton build for making CouchDB release.
/cc @garrensmith
P.S. Modifying `share/couchdb/www/fauxton` is a bad idea: lets start from
that on CouchDB uninstall/upgrade your package manager may not remove all the
stuff correctly, so you have a chance to get broken install or just pollute
your system with obsolete files. If you really want to work with static
content, better add the following option to your CouchDB config:
```
[httpd_global_handlers]
_fauxton = {couch_httpd_misc_handlers, handle_utils_dir_req,
"path_to_couchdb/src/fauxton/dist/release"}
```
and browse `http://localhost:5984/_fauxton` without copying things and
touching installed files in your system.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
