Rather than trying to store the parameters in a directory, you might consider storing them in a database on a hosted server.
This write-up describes storing records on a hosted server in order to sync device database records but your application would be very similar in that each device would have a unique Id and each parameter could have unique Id and therefore record.
My need was to sync calendars in which user 'A' changes the calendar and sends the change to other users by writing records to the hosted database. The other users query periodically to see it they have any incoming sync records and read them if available. I had hoped to use Erel's JDRC2...
Your front-end app would send the parameters as often as you wish. You could write the php database logic to create a new record or update it if it exists.
If a parameter changes in your front-end app, you could just send the one record, not all of the records.
The front-end app could also query the server database in order to refresh the parameters if needed, especially if the device hardware was changed out.
A 2nd front end app could be written in B4J or B4A to display all of the devices and allow them to be clicked or touched and then the parameters for that device would be displayed. You might want a third front end app for yourself to build the db table.
The models and actual logic for all of these ideas are in the above writeup.
My own hosted server from 1&1 Ionos is only $12.32/month so it is very affordable for most any company.
Handling a sql data base on a server will be a lot easier than trying to send whole files to another server.
Hope this might help.
Cliff McKibbin