sorry, I should have responded earlier. you should not have to put any scripts into the cgi folder, and they would not be usable from web pages.
in my configuration, I've used TWO .htaccess files this one at domain root (top of web space) ------------------------------------------------------------------- Options +ExecCGI FollowSymLinks AddHandler livecode-script .lc .irev DirectoryIndex index.irev index.lc index.php index.html Action livecode-script /cgi-bin/livecode-server/livecode-server ------------------------------------------------------------------- this one inside the cgi-bin directory ------------------------------------------------------------------- Options ExecCGI SetHandler cgi-script ------------------------------------------------------------------- permissions must be set in a certain way and downloaded zips may not be when extracted. this works for me at Dreamhost. Note that this allows PHP and Livecode scripts to co-exist, just use the appropriate suffix and code according to the languages' requirements. LIVECODE SERVER PERMISSIONS THAT WORK AT DREAMHOST <http://media.barncard.com/downloads/LIVECODE_SERVER_SETUP.pdf> -- Stephen Barncard - Sebastopol Ca. USA - Deeds Not Words On Tue, Jul 14, 2015 at 11:42 AM, Thomas von Fintel <run...@vonfintel.org> wrote: > Fiddling with things I finally found a solution. > > In case someone is interested, the new setup is (The numbers in brackets > show permissions): > > |- cgi-bin (775) > |- .htaccess (644) > |- test.lc (644) > |- livecode-community-server.cgi (775) > |- drivers (755) > |- ... (664) > |- externals (775) > |- ... (664) > > The .htaccess now contains: > > AddHandler livecode-script .lc > Action livecode-script /cgi-bin/livecode-community-server.cgi > > Now http://mydomain.com/cgi-bin/test.lc returns the right output of > test.lc > This works with livecode-community-server 7.0.5 > > I didn't try every combination, but it seems I had to change three things: > > 1. Put a ".cgi" after the engines name, change the .htaccess file > accordingly. > 2. Put the script test.lc into the cgi-bin folder. > 3. Drop the first line of the .htaccess file > > > Is it necessary to put the script into the cgi-bin folder? How can you put > it into another folder to avoid clutter? > I wonder ... > > Thomas > > > > Am 13.07.2015 um 09:40 schrieb Thomas von Fintel: > > > I have a working playground site on nosupportlinuxhosting.com that I > want to transfer to a Dreamhost account. > > The setup is: > > > > |- lc > > |- test.lc > > |- .htaccess > > |- cgi-bin > > |- livecode-community-server > > |- drivers > > |- ... > > |- externals > > |- ... > > > > The .htaccess contains: > > Options +ExecCGI FollowSymLinks > > AddHandler livecode-script .lc > > Action livecode-script /cgi-bin/livecode-community-server > > > > Permissions have been checked more than once. > > > > I tried 64-bit and 32-bit versions of the server. > > > > All I get is: > > "Not Found > > The requested URL /cgi-bin/livecode-community-server/lc/test.lc was not > found on this server. > > > > Additionally, a 404 Not Found error was encountered while trying to use > an ErrorDocument to handle the request." > > > > What am I doing wrong? > > > > > > Thanks for any hints > > Thomas > > > > _______________________________________________ > > 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 > > _______________________________________________ > 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 > _______________________________________________ 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
