Derby UI Boot no longer works at all in my setup. about d-bootstrap

[nickewansmith]

Issue due to order of variables?

[lefnire]

did you mean to close the ticket, or did you actually get it working again? I'm experiencing the same issue with other components: HabitRPG/habitica#864 - i believe recent changes in Derby may have broken its component library functionality.

[enjalot]

by order of variables do you mean order of including the components?
i used derby new to test this:
https://github.com/enjalot/derby-demo

found out I had to put all the component includes, i.e. derby.use(...) before the call to derby.createApp

submitted a pull request to derby

[nickewansmith]

Yes, I found something about this "before the call to derby.createApp" on Google.

I'm pretty sure that I did not change anything in my code before the components just stopped working... but I couldn't be completely certain so I closed the issue. No one else seemed to be having any issues, lol.

I ended up resolving the issue by re-ordering my requires based on the statement above.

I think I ordered them so that there is no possible way that things can go wrong? I am pretty new to Derby and Node so maybe someone else would have suggestions.

Ex.

//Server
var
http = require('http')
, express = require('express')
, expressApp = express()
, server = module.exports = http.Server(expressApp)
, path = require('path')
, gzippo = require('gzippo')
, MongoStore = require('connect-mongo')(express)
, racer = require('racer-db-mongo')
, dbUri = 'mongodb://localhost/yourdatabase'
, serverError = require('./serverError')
, ONE_YEAR = 1000 * 60 * 60 * 24 * 365
, root = path.dirname(path.dirname(__dirname))
, publicPath = path.join(root, 'public')

//get derby
var derby = require('derby')
derby.use(derby.logPlugin)
derby.use(racer)
//other stuff derby will use is in the app, as well as the derby.createApp function
var app = require('../app')
//not really sure if this should be here, but just incase
module.exports = server

//create derby stores
//init derby auth
//etc
//start server

[lefnire]

Yep, turns out derby.createApp has to come after component initialization
in lib/app/index.js after all. Twas news to me as well. Glad you found it

On Saturday, April 27, 2013, Nicholas Smith wrote:

Yes, I found something about this "before the call to derby.createApp" on
Google.

I'm pretty sure that I did not change anything in my code before the
components just stopped working... but I couldn't be completely certain so
I closed the issue. No one else seemed to be having any issues, lol.

I ended up resolving the issue by re-ordering my requires based on the
statement above.

I think I ordered them so that there is no possible way that things can go
wrong? I am pretty new to Derby and Node so maybe someone else would have
suggestions.

Ex.

//Server
var

http = require('http')

, express = require('express')
, expressApp = express()
, server = module.exports = http.Server(expressApp)
, path = require('path')
, gzippo = require('gzippo')
, MongoStore = require('connect-mongo')(express)
, racer = require('racer-db-mongo')
, dbUri = 'mongodb://localhost/yourdatabase'

, serverError = require('./serverError')
, ONE_YEAR = 1000 * 60 * 60 * 24 * 365
, root = path.dirname(path.dirname(__dirname))
, publicPath = path.join(root, 'public')

//get derby
var derby = require('derby')
derby.use(derby.logPlugin)
derby.use(racer)
//other stuff derby will use is in the app, as well as the derby.createApp
function
var app = require('../app')
//not really sure if this should be here, but just incase
module.exports = server

//create derby stores
//init derby auth
//etc
//start server

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-17117427
.