Thanks Mark (and Matthias). That's very useful info which I'll stash for another time.

In this case I really don't want to use the LC code over HTTP. It is purely a utility to run locally on this machine at scheduled intervals, in support of some other processes.

For several reasons it would be more convenient to run it as a stack rather than just a script, though it would be possible to go the latter way.

So two questions:

- just to be clear, does LiveCode Server only work receiving requests from Apache/nginx/whatever? Or can it be run from the command line?

- is there a way to install ordinary LiveCode on a headless linux box? Or will the installer demand a GUI to complete?

Many thanks,

Ben

On 31/01/2021 02:22, Mark Talluto wrote:
Hi Ben,

My favorite method is to build server code with standalones and script only stacks. You can run them headless using the -ui method as you proposed earlier. You can have the standalone act as a starter stack that loads in your script only stacks as libraries. This model makes it easy to do future updates because they are not built into the standalone itself.

Place standalone and stack files here:
- Apache
IP Number/home/standalone
/home/libaries/stack files here

- nginx
IP/usr/local/bin/standalone
/bin/libraries/stack files here

Each executable is always on for performance. They use very little cpu when they are waiting for something to do. In my experience, they rest a 0% between loops and jump to around 3% when checking on the workload. They will jump up to some other value when they are processing. When done, they return to the 0-3% consumption.

We use PHP to receive incoming posts to the VM. After PHP does its thing, it passes the posted request to the LiveCode standalone. The process repeats itself as data is posted to the VM.

This has been a proven model for us. We have used it for many years with LiveCloud.

You can use this model in many ways. It will depend on what you are trying to accomplish.

Best regards,

Mark Talluto
livecloud.io <http://livecloud.io>
nursenotes.net <http://nursenotes.net/>
canelasoftware.com <http://www.canelasoftware.com/>




On Jan 30, 2021, at 8:34 AM, Ben Rubinstein via use-livecode <use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>> wrote:

Hi Matthias,

Thanks for answering.

I haven't looked into Livecode Server. When you say I could run livecode scripts directly from shell, does that means scripts, but not stacks?

Is Livecode Server easier to install on a 'headless' system? Is there somewhere I should look to find explanation of differences/pros/cons of Server versus IDE editions?

thank you,

Ben

On 29/01/2021 20:30, matthias rebbe via use-livecode wrote:
Ben,
is there a reason why you do not install/use Livecode Server instead of Livecode IDE on your system?
You could run livecode scripts directly from shell.
Regards,
Matthias
-
Matthias Rebbe
Life Is Too Short For Boring Code
Am 29.01.2021 um 19:44 schrieb Ben Rubinstein via use-livecode <use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>>:

So I want to install LC on a headless - i.e. no GUI, access over SSH - Ubuntu 20.

(Then I'll be using it to run a particular stack on a cron job.)

I've done this a long time ago with a standalone - but in this case I'd rather be able to do it with a stack.

The only thing that I know about is "-ui" but I'm not even far enough along to make use of this.

My first question is what's the best way to install it? Do I download the installer, e.g. "LiveCodeCommunityInstaller-9_6_1-Linux.x64", move it to the server and run it there? Or is that going to be a GUI installer?

Are there options I need to know about like where it should go?

And then are there tips about where I put my stacks, how to see error or debugging output, how the stack reads command line parameters etc?

Any and all advice welcome - especially of course "go and read this guide over here you idiot".

TIA,

Ben

_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com <mailto: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 <mailto: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 <mailto: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

Reply via email to