To be used with RealDeviceMap macless solutions.
Central repository for macless client configurations without having to keep track of multiple remote configs and urls. Assign different configurations to different devices and different backends (RealDeviceMap / Lorgnette). When devices connect for the first time, if they don't exist they are created, if the device doesn't have a config assigned, it will try to auto-assign a default config if one exists.
You can also pre-create devices and assign configs yourself if needed. Rest endpoint tooling to get screenshot, active logged in account, restart game, reboot device, or view device logs and more.
- Custom config assignments
- Screenshot preview
- Device logging
- Device endpoint tooling
- and more...
- GoCheats
- Kevin
- AI
Normal
- Create new database
dcm
with utf8_unicode_ci/utf8mb4 character sets and collation - Clone repository
git clone https://github.com/versx/DeviceConfigManager
- Install dependencies
npm install
- Copy config
cp src/config.example.json src/config.json
- Fill out config
vi src/config.json
- Run
npm start
- Access via http://machineip:port/ using username:
root
and passwordpass123!
- Change default password via the Settings page
- (Optional) Setup DCMAgent on the machines the phones are connected to in order to restart the actual device.
Docker
- Create new database
dcm
with utf8_unicode_ci/utf8mb4 character sets and collation - Clone repository
git clone https://github.com/versx/DeviceConfigManager
- Copy docker-compose
cp docker-compose.example.yml docker-compose.yml
- Copy config
cp src/config.example.json src/config.json
- Fill out config
vi src/config.json
- Run
docker-compose up -d --build
- Access via http://machineip:port/ using username:
root
and passwordpass123!
- Change default password via the Settings page
- (Optional) Setup DCMAgent on the machines the phones are connected to in order to restart the actual device.
Normal
git pull
- Run
npm install
in root folder - Run
npm start
Docker
git pull
- Run
docker-compose up -d --build
Q.) Why are devices showing my HAProxy IP address?
A.) You need to make sure to set option forwardfor
in your haproxy.cfg file under defaults so the x-forward-for
header is sent with the request and the real IP is used.
Q.) Why are devices not connecting to backend or sending data to data endpoints?
A.) Make sure to not include the /raw
or /controler
endpoints in the Backend Url
and Data Endpoints
config options. These are automatically appended to each URL address.
Q.) Will I be able to view screenshots and use the device endpoint tools with devices using mac internet sharing?
A.) No, since it uses the connected machine's IP address for internet sharing.
- Unable to set schedule that switches between days, i.e. Start 11pm and Ends 2am.
Once everything is setup and running appropriately, you can add this to PM2 ecosystem.config.js file so it is automatically started:
module.exports = {
apps : [
{
name: 'DeviceConfigManager',
script: 'index.js',
cwd: '/home/username/DeviceConfigManager/src/',
instances: 1,
autorestart: true,
watch: false,
max_memory_restart: '1G',
out_file: 'NULL'
}
]
};