'Server' without Apache etc. - basic nOOb question
Posted: Mon Jan 20, 2014 8:21 pm
Hiya!
I've spent quite some time reading tutorials, searching the forum, but to no avail.
Seems the most used (and described) use case of the server is to deliver web pages, in a LAMP environment.
But I only want a (faceless) server (or a -ui standalone) as a service, doing things like such:
- Listening on a certain port for incoming (socket?) connections.
- Verify that these connections are from valid (authorized) machines, and respond only in such cases.
- Making sure there's a connection to the main LAN-Database.
- Receiving data to process, or data that 'order' a special reply.
- Return the data that was required (from LAN-DB using stored SQL statements and parameters from 'the client')
Basically I want such a beast as a connection controller/ maintainer between the (potentially unsafe) website out there, and my highly secured server LAN (it's running here). The PHP guys at the website (resp. their code) will send their requests, and I (resp. my code in the server LAN) will check it for authorization, validity and whatever, and if I feel comfortable, I'll send an SQL query to my database, and return a result to the PHP guys that they may embed in their shiny web site.
Vice verse, they may send me data to alter the database, I'll do my security checks, plausibility checks, and if all is well, I'd fire up an "UPDATE * IN MYTABLE WHERE ..."
Such LiveCode server / Standalone solution should run faceless, as a service under Win 2K server (at first), or under a Linux server system (later, CentOS preferred). Databases used are to be ignored, I have connected LC to any DB I needed yet w/o any real problems.
-----------------------------------------
My problem now is if to use server, and if, how to use it in cmd-line modus, or if to use a Standalone (shouldn't be a problem on Win-Server, but on Linux: Read this ...).
I don't want/ need a full blown LAMP. I want an LC as the only open service on this machine, because there are severe security reasons. We don't want a lot of running services that are not needed, and we don't want to check open ports after any other update. There will be LC listening only (and RDP/VNC maybe later, with RDP/VNC as a way to use an LC app, as a future project ...))
So, how to do such best, without inventing the wheel for the 1.001th time?
Then, is there any information about the load a LC server (or a -ui standalone) would put onto a common web presence? I'd love to have one running at the web site, to be accessed by my PHP guys (and to give me access to _their_ MySQL DB for updating)?
I don't expect long how-to's. Don't bother, plz, gimmi a link. I can read for myself.
But if someone with experience in this area has expertise, I'd be more then happy to read about. Should I get my project running, it'll run under the community edition, i.e. GPL.
I might add, this thread may point to a similar question, maybe they should be merged? Think the documentation for server besides web-site-making is rather sparse, and the LC docu isn't much helpful, too ...
Have a good time!
I've spent quite some time reading tutorials, searching the forum, but to no avail.
Seems the most used (and described) use case of the server is to deliver web pages, in a LAMP environment.
But I only want a (faceless) server (or a -ui standalone) as a service, doing things like such:
- Listening on a certain port for incoming (socket?) connections.
- Verify that these connections are from valid (authorized) machines, and respond only in such cases.
- Making sure there's a connection to the main LAN-Database.
- Receiving data to process, or data that 'order' a special reply.
- Return the data that was required (from LAN-DB using stored SQL statements and parameters from 'the client')
Basically I want such a beast as a connection controller/ maintainer between the (potentially unsafe) website out there, and my highly secured server LAN (it's running here). The PHP guys at the website (resp. their code) will send their requests, and I (resp. my code in the server LAN) will check it for authorization, validity and whatever, and if I feel comfortable, I'll send an SQL query to my database, and return a result to the PHP guys that they may embed in their shiny web site.
Vice verse, they may send me data to alter the database, I'll do my security checks, plausibility checks, and if all is well, I'd fire up an "UPDATE * IN MYTABLE WHERE ..."
Such LiveCode server / Standalone solution should run faceless, as a service under Win 2K server (at first), or under a Linux server system (later, CentOS preferred). Databases used are to be ignored, I have connected LC to any DB I needed yet w/o any real problems.
-----------------------------------------
My problem now is if to use server, and if, how to use it in cmd-line modus, or if to use a Standalone (shouldn't be a problem on Win-Server, but on Linux: Read this ...).
I don't want/ need a full blown LAMP. I want an LC as the only open service on this machine, because there are severe security reasons. We don't want a lot of running services that are not needed, and we don't want to check open ports after any other update. There will be LC listening only (and RDP/VNC maybe later, with RDP/VNC as a way to use an LC app, as a future project ...))
So, how to do such best, without inventing the wheel for the 1.001th time?
Then, is there any information about the load a LC server (or a -ui standalone) would put onto a common web presence? I'd love to have one running at the web site, to be accessed by my PHP guys (and to give me access to _their_ MySQL DB for updating)?
I don't expect long how-to's. Don't bother, plz, gimmi a link. I can read for myself.
But if someone with experience in this area has expertise, I'd be more then happy to read about. Should I get my project running, it'll run under the community edition, i.e. GPL.
I might add, this thread may point to a similar question, maybe they should be merged? Think the documentation for server besides web-site-making is rather sparse, and the LC docu isn't much helpful, too ...
Have a good time!