Server standalones
Posted: Wed Dec 18, 2013 4:20 pm
The title says it all. I need 'em. I have server products in development for which the GPL License governing the Community Edition would be inappropriate, and I need to run password-protected libraries.
Historically I've just built my own using the Linux engine and running with -ui, but while this used to work well it's increasingly problematic. Issues with using Linux standalones have included among the servers I've tested on dependency on libraries not normally installed in server configurations, and "exit on signal 11" errors preventing the app from running.
If there's a way to resolve these in the Linux desktop engine that would be my preference, so I can continue to use the setup I have. But I imagine this would require a change to the way libraries are linked. If it's possible to avoid dependency on libraries not normally found on servers when running with -ui then let's do it, but if not I'm prepared to abandon command-line apps altogether and just use Livecode Server instead.
Now that we can use libraries in LC Server, changing my setup is minor; bigger is the loss to the community of the flexibility provided by the option to use Linux standalones if we prefer, but maybe I'm the only one doing that so perhaps it's not a major concern.
Either way, I need some solution to be able to put a compatible LC engine on servers which can load password-protected libraries, and do so without any registration or licensing actions required by my users.
Apparently the Server Edition I can download via my RunRev account runs password-protected stacks, so that much is good. But since there's no documentation included, not even a license, it's unclear what I can and cannot do with it. For example, can I rename the executable file to reflect my company's own branding?
Looking at the bigger picture, is there a need for others to be able to run with -ui under as many different systems, including servers, as I have?
If so, is it practical to explore ways to make the behavior with -ui more closely reflect that of LiveCode Server?
Historically I've just built my own using the Linux engine and running with -ui, but while this used to work well it's increasingly problematic. Issues with using Linux standalones have included among the servers I've tested on dependency on libraries not normally installed in server configurations, and "exit on signal 11" errors preventing the app from running.
If there's a way to resolve these in the Linux desktop engine that would be my preference, so I can continue to use the setup I have. But I imagine this would require a change to the way libraries are linked. If it's possible to avoid dependency on libraries not normally found on servers when running with -ui then let's do it, but if not I'm prepared to abandon command-line apps altogether and just use Livecode Server instead.
Now that we can use libraries in LC Server, changing my setup is minor; bigger is the loss to the community of the flexibility provided by the option to use Linux standalones if we prefer, but maybe I'm the only one doing that so perhaps it's not a major concern.
Either way, I need some solution to be able to put a compatible LC engine on servers which can load password-protected libraries, and do so without any registration or licensing actions required by my users.
Apparently the Server Edition I can download via my RunRev account runs password-protected stacks, so that much is good. But since there's no documentation included, not even a license, it's unclear what I can and cannot do with it. For example, can I rename the executable file to reflect my company's own branding?
Looking at the bigger picture, is there a need for others to be able to run with -ui under as many different systems, including servers, as I have?
If so, is it practical to explore ways to make the behavior with -ui more closely reflect that of LiveCode Server?