Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3EBD2F97A for ; Thu, 4 Apr 2013 13:37:25 +0000 (UTC) Received: (qmail 94022 invoked by uid 500); 4 Apr 2013 13:37:24 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 93985 invoked by uid 500); 4 Apr 2013 13:37:24 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 93959 invoked by uid 99); 4 Apr 2013 13:37:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Apr 2013 13:37:24 +0000 Date: Thu, 4 Apr 2013 13:37:24 +0000 (UTC) From: "Simon Metson (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (COUCHDB-1690) Fauxton templating task needs to read from settings.json MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COUCHDB-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Metson closed COUCHDB-1690. --------------------------------- > Fauxton templating task needs to read from settings.json > -------------------------------------------------------- > > Key: COUCHDB-1690 > URL: https://issues.apache.org/jira/browse/COUCHDB-1690 > Project: CouchDB > Issue Type: Improvement > Components: Fauxton > Reporter: Simon Metson > > The template task currently defines a set of named asset/root combinations (https://github.com/apache/couchdb/blob/fauxton/src/fauxton/grunt.js#L122-L166). This is a little clumsy and brittle (e.g. it means you need to patch fauxton to deploy to a non-standard location). We should get the configuration badger from settings.json, instead of having it hard coded in the grunt.js file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira