Let me see if I can be both useful and carry the metaphor forward here:
When traveling on a submarine long enough, anything that looks like a safe island seems a desirable goal. And if what you're looking for is to leave the water, going for dry land can be a good direction.Mariasole wrote:The submarine of inexperience is safe, he has passed the iceberg!
It 'was tough, but we made it...
For this reason I ask Admiral Gaskin and the members of the LC Fleet Experienced, humbly and respectfully:
You can write a PHP file that sent to a server do a test and say:
"Ok on this machine you can run Live Code X? Congratulations now you can abandon PHP! "
or
"No, sorry, this machine can not run Live Code Server X because they lack these files: so.so and up.dll and us.pl and IO.zxspectrum"
It would be a great help also for the server providers that in this way will know which dll install inside the server to run LCS...
It would be a help to all the little IXBot (ineXperiencedBot, - bots as submarine, of course not robots -) that circulate in the seas with servers icebergs heavy million tons!!!
But look around you: the ocean is teeming with life! It is the source of all life, even that which lives on the island.
How do we thrive underwater as richly as the fish surrounding us?
Scripting engines like LiveCode, PHP, Python, Perl, Ruby, etc. are all useful, but when working on a server there's one language to rule them all, one as natural to a server system as water to a fish: bash.
Long before GUIs, terminals were our only interface. Over time systems evolved, and just as some creatures grew fins strong enough to crawl out of the sea onto beaches, GUIs evolved on top of command-line interfaces (CLIs).
And even now in our GUI-dominated world, CLIs remain at the heart of most systems, whether bash in OS X and Linux or PowerShell in Windows.
GUIs take a lot of CPU time and RAM, so most servers don't include a GUI at all. But any server worth using will provide support for Secure Shell (SSH).
SSH lets you log into any machine you have an account on, anywhere in the world, and once logged in it's as good as if you had the machine on your desk in front of you, able to do nearly anything through Terminal you could do with a local box.
The challenge with SSH is that you need to know what to type, whereas in a GUI the commands are already typed for us in menus.
There are MANY resources for learning to use shell online, and if you like I can find some for you. Basic commands like "ssh" to log in, "cd" to change directories, and things like that are easy to learn, and you don't need to know many to get started. As time permits I hope to get back to a project I started a while back with a tutorial on bash for LiveCoders, but there are so many great bash resources out there I'm not sure it's needed.
Here I'll just give you a non-obvious one for the purpose at hand:
Code: Select all
ldd ./livecode-server somescript.lcIn fact, just running the server app with a script passed to it can be useful, as it'll usually output any error info - same as above but without the "ldd" command:
Code: Select all
./livecode-server somescript.lcYou never need to worry about that. Here in the States we have many English speakers less articulate in their writing than you.(In future trips I'll bring a grammar of English)
PS: I've taken a break from prog rock lately, catching up on other genres from that period. Lately I've been listening to Parliament-Funkadelic, and given how fond you are of closing posts with a quote, I'll paraphrase one from them as it may provide further inspiration for learning the server-native bash language:
"Free your mind...and the rest will follow".
.
.
!