These are chat archives for azukiapp/azk

2nd
Jan 2016
Bartek Kus
@Bartekus
Jan 02 2016 14:20
How do you address this issues azk: [timeout] Make sure the start command binds port to the 0.0.0.0 interface, not only to the localhost interface.?
Gullit Miranda
@gullitmiranda
Jan 02 2016 14:24
hi @Bartekus
Bartek Kus
@Bartekus
Jan 02 2016 14:24
Hello @gullitmiranda
it wasn't much help with sugestions
I've got a node server
Gullit Miranda
@gullitmiranda
Jan 02 2016 14:26
you're right. I think we can roll contributions to it =D
Bartek Kus
@Bartekus
Jan 02 2016 14:27
I've been looking at the node.js example but that one doesnt have any visible binding in place unfortunately
Gullit Miranda
@gullitmiranda
Jan 02 2016 14:27
You are using the HTTP_PORT or other env to raise the service node?
Bartek Kus
@Bartekus
Jan 02 2016 14:29
NODE_ENV=production
Gullit Miranda
@gullitmiranda
Jan 02 2016 14:30
no. env to PORT =D
Bartek Kus
@Bartekus
Jan 02 2016 14:30
so I'd say env
Gullit Miranda
@gullitmiranda
Jan 02 2016 14:30
like example
Bartek Kus
@Bartekus
Jan 02 2016 14:39
still exactly the same problem
why is it trying to connect to 32772 .... Failure to reach port 32772 from http://r3bel.dev.azk.io after 60000 milliseconds
I'm trying to do build from scratch but it's oddly difficult, I thought clean node with no database should work np
is redis a dependency?
Bartek Kus
@Bartekus
Jan 02 2016 14:55
"scripts": {
"clean": "rimraf dist",
"build:webpack": "NODE_ENV=production webpack --config webpack.config.prod.js",
"build": "npm run clean && npm run build:webpack",
"start": "node devServer.js",
"lint": "eslint source"
},

var path = require('path');
var express = require('express');
var webpack = require('webpack');
var config = require('./webpack.config.dev');

var PORT = process.env.HTTP_PORT || 3000;

var app = express();
var compiler = webpack(config);

app.use(require('webpack-dev-middleware')(compiler, {
noInfo: true,
publicPath: config.output.publicPath,
stats: { colors: true }
}));

app.use(require('webpack-hot-middleware')(compiler));

app.get('*', function(req, res) {
res.sendFile(path.join(__dirname, 'index.html'));
});

app.listen(PORT, 'localhost', function(err) {
if (err) {
console.log(err);
return;
}

console.log('Listening at http://localhost:' + PORT);
});

var BrowserSyncPlugin = require('browser-sync-webpack-plugin');
var webpack = require('webpack');

module.exports = {
devtool: 'cheap-module-eval-source-map',
context: dirname + '/source',
entry: [
'eventsource-polyfill',
'webpack-hot-middleware/client',
'./index'
],
output: {
path:
dirname + '/build',
filename: 'bundle.js',
publicPath: '/static/'
},
plugins: [
new webpack.HotModuleReplacementPlugin(),
new webpack.NoErrorsPlugin(),
new BrowserSyncPlugin(
{
host: 'localhost',
port: 3333,
uiPort: 3444,
proxy: 'http://localhost:3000/'
},
{
reload: false
}
)
],
module: {
loaders: [{
test: /.jsx?/,
include: __dirname + '/source',
loaders: ['babel']
}]
}
};

that all the config Ive got, still exactly the same problem
Gullit Miranda
@gullitmiranda
Jan 02 2016 15:09
You tried disable BrowserSync?
many users the Webpack. including ourselves.
Bartek Kus
@Bartekus
Jan 02 2016 15:10
I extend the webpack with the browsersyncplugin so technically its just webpack middleware proxy
ok I'm stupid
lol I feel really dumb but it was 3333 not 3000, that's why it wasnt working
Gullit Miranda
@gullitmiranda
Jan 02 2016 15:42
kkkk relax. make the same mistake often: p
:D
everything working right now?
Bartek Kus
@Bartekus
Jan 02 2016 15:43
yup, like a charm :)
Gullit Miranda
@gullitmiranda
Jan 02 2016 15:44
very nice =D