couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Ramage (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1690) Fauxton templating task needs to read from settings.json
Date Fri, 15 Mar 2013 16:24:12 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603483#comment-13603483
] 

Ryan Ramage commented on COUCHDB-1690:
--------------------------------------

Hey, not totally related, but I got the jenkins build pushing to a custom location with the
following command:

node node_modules/couchapp/bin.js push ./couchapp.js http://admin:pass@awesomplace.com/ohyeah

Note pretty but a workaround for those with auth on their couch.
                
> 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

Mime
View raw message