You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2018. It is now read-only.
Logging is currently used to indicate when clients connect/disconnect (via socket.io). This only works for clients using the addon. It would be helpful to also see when clients fetch updates, including clients not using the addon. Without this logging it is hard to figure out if the remote updates are working, especially if the client is slow or has limited bandwidth.
Ideally, cordova-hcp server would log more details about addon clients. The following events should get logged:
connect and disconnect (already implemented)
fetch start
fetch complete
fetch error
update
For each event, include some details about the client:
device id (uniquely identify the client)
platform (iOS or Android)
model (such as iPhone 7)
current web version
For clients not connected via socket.io (not using the addon), requests for individual resources could still be logged, and perhaps some details about the client (platform and model) can be inferred from the user agent header of the request.
The text was updated successfully, but these errors were encountered:
😢 We are not using nordnet/cordova-hot-code-push-cli anymore, and we lack the manpower and the experience needed to maintain it. We are aware of the inconveniece that this may cause you. Feel free to use it as is, or create your own fork.
Logging is currently used to indicate when clients connect/disconnect (via socket.io). This only works for clients using the addon. It would be helpful to also see when clients fetch updates, including clients not using the addon. Without this logging it is hard to figure out if the remote updates are working, especially if the client is slow or has limited bandwidth.
Ideally,
cordova-hcp server
would log more details about addon clients. The following events should get logged:For each event, include some details about the client:
For clients not connected via socket.io (not using the addon), requests for individual resources could still be logged, and perhaps some details about the client (platform and model) can be inferred from the user agent header of the request.
The text was updated successfully, but these errors were encountered: