Pulse Phone docs

Updating

For Pulse Phone 1.5.23 min readUpdated

10. Updating from an older version

Existing numbers, accounts and device records are kept. Phones from the first Pulse version become the Pulse Ultra on the first start, with their numbers, IMEIs and data. Always take stream/ and ui/ from the same release as the rest of the folder.

  1. Keep a copy of your old phone folder, and back up your database. Move the old folder out of resources: two phone folders start two phones. Two folders both named phone (say resources/phone and resources/[phone]/phone) are worse: FXServer runs only one of them and does not tell you which, so the old one may be the one that starts. A copy under another name is named by the start-up check with both folder paths (Copies).
  2. Put the new phone folder in its place. Over FTP, upload it in Binary mode or extract the zip on the server (why). The start-up check names any file that is wrong.
  3. Keep the new configuration files and transfer the settings you changed by their Config names. Version 1.2.7 groups the former individual feature files into config/apps.lua and moves call settings into config/config.lua. Do not overwrite these with the old split files: those files no longer load. Animations, music and trivia retain their own files. Preserve private settings in config/apiKeys.lua if you use it; existing server.cfg credentials continue working. Keep the new translations and merge your own wording where needed. Leave Config.Radio.registerChannelChecks = false unless you want Pulse to manage restricted radio channels.
  4. Copy your files in ownermedia/ back, and your media/ folder if you use the built-in photo store.
  5. Don't copy old bridge/ files back (or the custom-adapter folders of an older version). If you changed one, make the same change in the new file.
  6. New items: nothing to do on ESX, QBCore and ox_inventory. At the first start of the new version Pulse sees the update (the console says Updated Pulse Phone from 1.4.3 to 1.5.0: ..., or "from an earlier version" for a release that did not record its version), adds the new items to the Pulse block of your item file, moves any Pulse item you pasted by hand earlier into that block (never twice), copies the new pictures, and says Restart once to finish when it changed a file. Settings made in Pulse Admin are kept. Other inventories: add the new items from config/items/ (section 4).
  7. Restart. The database updates itself: coming from 1.3.0, the console prints database: brought up to date (2 columns added: phone_devices.last_seen, phone_devices.firstweek) on the first start, and the phone_usage_daily table is created with the others. Nothing to do by hand. A host that does not let the resource create or alter tables: run phone.sql again (section 2); it adds only what is missing. Read the start-up check in the console.

If you kept an older config.lua instead of moving your settings into the new one, settings it doesn't have run on their defaults. To change one, copy that section from the new config/config.lua into yours. For example, without Config.Block dead and cuffed players can't use the phone and downed players can call 911; without Config.Charging no cable is needed (the console says so once); without Config.Store.box phones come without a box. A config.lua kept from an earlier version also keeps its own Config.Device.arrivesOn (the new file says true: new phones arrive switched on) and has no Config.FirstRun or Config.FirstWeek block, so those run on their defaults: the full setup as before, and the first-week card (section 8, "A new phone's first start").

  • Rolling back: put the previous folder back. On MySQL, data written by the newer version stays readable.
  • Without a database, also back up FXServer's key/value store (the db folder in your server data folder) before updating.