meteor-desktop
meteor-desktop copied to clipboard
how to set ddp url
npm run desktop run http://192.168.1.70:3380
this ,still access to 127.0.01:3000
I'm facing the same issue...
using npm run desktop -- build-installer 192.168.1.44:3000
still access to 127.0.0.1:3000
any thoughts?
Well, this is only happening to me when building from windows. If I build it from linux it works well.
This is the error I'm getting when doing npm run desktop -- build-installer 192.168.1.44:3000 --win
from my windows pc
ERROR meteorApp: error while trying to download index.html for web.cordova, be sure that you are running a mobile target or with --mobile-server: { FetchError: request to http://127.0.0.1:3000/__cordova/index.html failed, reason: connect ECONNREFUSED 127.0.0.1:3000
at ClientRequest.<anonymous> (C:\Users\cribh\Desktop\ledplayer\node_modules\meteor-desktop\node_modules\node-fetch\lib\index.js:1345:11)
at ClientRequest.emit (events.js:182:13)
at Socket.socketErrorListener (_http_client.js:392:9)
at Socket.emit (events.js:182:13)
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
message:
'request to http://127.0.0.1:3000/__cordova/index.html failed, reason: connect ECONNREFUSED 127.0.0.1:3000',
type: 'system',
errno: 'ECONNREFUSED',
code: 'ECONNREFUSED' }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ledplayer@ desktop-installer-linux: `meteor-desktop -- build-installer 192.168.1.237:3000 --win`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ledplayer@ desktop-installer-linux script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\cribh\AppData\Roaming\npm-cache\_logs\2019-01-10T15_44_50_791Z-debug.log
Okey, finnally managed to make it work. Even if server is running in another machine, you have to run it locally in order to generate the installer or run the Desktop app pointing to the real server ip.
@cbh6 can you share the build script you used to get installer in local environment ?
Hi!, long time ago... I don't remember about this, it was related to one of my last jobs... I can't help tbh sry :(
The only thing I remember is that you need to run the server locally, and just generate the build installer using npm run desktop -- build-installer yourServerIp --win
(--win or the platform you want)
If the server isn't running locally it throws an error
yourServerIp
can point to your local server, or if you are running the server in another machine, just use the ip