|
|
# Setup New Shop Guide Line
|
|
|
## Queuing
|
|
|
|
|
|
### goQueue.json
|
|
|
|
|
|
The `goQueue.json` was split to `shop-info.json`, `central-server.json`, `queue.json`, `cron-time.json`.
|
|
|
The system status like `serviceEnable`, `remoteQueuingEnable` was saved to database.
|
|
|
|
|
|
But this link <http://localhost:89/goQueue.json> still work.
|
|
|
|
|
|
|
|
|
### Change shop code and other shop information
|
|
|
|
|
|
You should go to edit the shop-info.json
|
|
|
```
|
|
|
"shopcode"
|
|
|
"shopaddress"
|
|
|
"shopaddressEN"
|
|
|
"shopTel"
|
|
|
```
|
|
|
|
|
|
### Connect to Central Server
|
|
|
|
|
|
**If this shop need to connect to a central server, aka, CMS for reporting, digital signage, and remote queuing**
|
|
|
|
|
|
You need to change the central server URL (`"url"`) in `central-server.json`
|
|
|
|
|
|
|
|
|
If the shop cannot reach the Internet. You can change the `"enable"` from `true` to `false` in `central-server.json`
|
|
|
|
|
|
### Digital Signage
|
|
|
|
|
|
All the folders for signage was grouped in
|
|
|
`C:\webGo\queue_v3\nodejs\signage`
|
|
|
|
|
|
The signage file contents will save to
|
|
|
`C:\webGo\queue_v3\nodejs\signage\files`
|
|
|
|
|
|
A virtual directory <http://localhost:89/files/> was mapped to this folder.
|
|
|
|
|
|
### Remote Queuing
|
|
|
**Fixed Public IP no longer needed for remote queuing**
|
|
|
A **socket-receiver** program was take the role of the fix IP.
|
|
|
|
|
|
You should change the `"socketClientName"` to same with `"shopcode"` in shop-info.json
|
|
|
|
|
|
Also you should change the base path of `"socketioForwardUrl"` in shop-info.json to same with the `shopcode`
|
|
|
|
|
|
>For Example
|
|
|
>-
|
|
|
>If the `"shopcode"` is "**Sample**"
|
|
|
>
|
|
|
>`"socketioForwardUrl"` should set to "http://goqueue.cloudapp.net:9100/**Sample**"
|
|
|
>
|
|
|
>`"socketClientName"` should set to "**Sample**" |
|
|
\ No newline at end of file |