LiveCode Forums.

Hi folks, Is there a trick to get AutoSSL to pickup a new Addon domain's FQDN and include it in the AutoSSL letsencrypt certificate coverage alongside the on-rev/livecodehosting subdomain itself? I was expecting to be prompted to provide some domain registration page or DNS setting for AutoSSL to di...

FourthWorld wrote: ↑

Wed Jan 22, 2020 9:35 am

If I see enough interest in this thread I'll see what I can do to pull together resources to make using LC Server easier and more productive.

Thanks for your ongoing efforts on behalf of the community, Richard.

I'm curious about how people are using LiveCode Server - please pick the option that best describes how you use it. A: I tried several times to start using LCS on various shared servers, VPS and desktop machines but consistently struggled to get beyond the "hello world" situation - so LCS (and ther...

Hi folks, Reaching out to Unix specialists for help in configuring a Godaddy VPS (CentOS 6 with cPanel / WHM & EasyApache4) for LC Server support... specifically establishing the necessary Apache modules, which are not currently visible in EasyApache4 as options to enable. Whilst EasyApache 4 has mo...

Hi Sean, Thanks for responding. I'm using localhost for initial testing as that is stated as required in the docs and I'm trying to stick as close to the example provided. However, as things are failing long before the return of the token, I think that the return URL is a red herring - for now, at l...

Hi folks, I'm experimenting with the OAuth2 library and have reached the point where I'm getting an authorisation dialogue from the server without any error messages but it's blank. I think I may be missing some required parameters but, I haven't used libraries much and can't see how to access the U...

It got parked at the design stage, as without a production version of LiveCode Server (now delivered) and a decent, player-free web deployment option (still no news on even an ETA for an updated player) my project wasn't feasible in LiveCode.
Good luck!
Keith..

Thanks for the kind words bangkok. As to whether blogs help? IMHO They're not the best vehicle for community collaboration, knowledge management or FAQs and I'd prefer an alternative mechanism to contribute. Blogs are best suited to help people and organisations seeking to position themselves as exp...

Hi folks, I've summarised the knowledge I gleaned from this forum, the list archives and this RunRev lesson http://lessons.runrev.com/spaces/lessons/buckets/814/lessons/16631-Getting-Up-and-Running-with-revServer into a How-to guide. http://blog.clarityforsuccess.com/2011/03/livecode-revserver-on-li...

Hi folks, I promised to publish some notes on the above - new to blogging as well as LiveCode and OSX server, so I hope they help a bit: • OSX Server vs Regular OSX considerations: http://blog.clarityforsuccess.com/2011/02/revserver-on-osx-server-vs-osx.html • Configuring OSX Server for revServer: h...

Mark W's comments on http://quality.runrev.com/qacenter/show_bug.cgi?id=9394 suggests that 4.6 will bring formal recognition of the OSX platform's Command and Alt keys, with key mappings. If implemented correctly, these should make LiveCode a more orthodox OSX application, both when used as a develo...

Yes, I noticed those changes but the scope was still limited to text fields, not OSX deployments or the IDE script editor, etc.

Still, here's hoping!

Hmm, the dev team immediately closed this bug report as a duplicate of the previous feature request 5869, without suitably updating the original. So, I've reopened the report, suggested that 5869 is a small subset of this larger issue and if a bug is to be dropped, it would be well to leave the big ...

Thanks for the advice, Mark. New bug report raised http://quality.runrev.com/qacenter/show_bug.cgi?id=9394

Rechecking the QA site before posting a bug report, I discover that for the OSX platform, what I consider to be a major platform-level, compliance and usability bug, has been languishing as a mere text field enhancement request for over two years http://quality.runrev.com/qacenter/show_bug.cgi?id=58...