Always alternatives. May or not be worth your time investment but here is something that works for me in the case of a quote system for a widely dispered sales team--
I use a launch style stack. This loads a stack from a URL. I do not use a standard web server for this (too much extra stuff) but instead use an open source object server, minio. This also gives me a means to inactivate an "account" without relying on the desktop app. Local "Launch" App (uses distinct supplied user keys not passwords to operate from local PC) On Launch opens a 'Menu Stack'. A tool/stack from the menu stack is loaded from the menu by creating a tempurl from the object store for that stack object and then simply "go stack url, etc". All in LC... The Menu loads various 'tools'. This could easily be your "cities" Maintenance on this is pretty simple-- update the menu stack if there are new tools you want to provide. Update the individual stacks/tools if only changing a particular stack/tool. Since the logic is run locally there isn't really a scale limit imposed by the "server" side. In terms of isolation/security, when I create a registration for a user I also create an s3 account for that user and apply a policy based access control (simple json form). The s3 key generation is part of the registration system and are delivered encrypted to the local app as part of that account creation. The s3 user account can easily be 'turned off' at the s3 host side if the user is no longer with the company, etc. An updated registration can also be easily sent if the user wants to have multiple apps on multiple machines or upgrades the local pc, etc Mark On Aug 2, 2025, at 7:42 AM, jbv via use-livecode <use-livecode@lists.runrev.com> wrote: Hi list, Years ago I built a desktop app with LC, and the client is still using it. Users of the app work in the same company but are scattered in different cities. Since there were small differences between cities, I found it easier to build a slightly different version of the app for each city, with different login & pwd. Now the client would like to be able to switch from one app to another (from one city to another) without quitting the app, launching the app of another city, entering new login & pwd, etc. An option could be simply to download the stack & card scripts for other cities from a remote server and replace the current scripts in the standalone with new scripts. The app features a main stack and no more than 10 substacks. The structure (fields, buttons, etc.) are identical, only the scripts and some data (downloaded at startup) are different. So my question is : is replacing all scripts of a standalone on the fly possible ? If yes, is it a good idea, is there any safety issue, and are there alternatives ? Thank you in advance. jbv _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
