On 4 May 2018, at 05:49, christophe.billiottet@webdna.us wrote:For those who want to =setup WebDNA.fcgi on several vhosts on Windows, we ran some =quick tests just now to confirm you can do this on a vanilla IIS server. =We do not have Plesk to test with unfortunately.---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us
BTW, we did not include a webdna.ini file in the previous =..zip We didn=E2=80=99t include the Admin interface either. It is just =the binaries.So, if you want the WebDNA folder, the link =isand =it includes a webdna.ini as well as the last interface =version.
If someone followed my other directions, and wants to switch, =first they should remove the server-wide "Handler Mappings" they added =on *.dna.
As an =example, lets assume you have two sites with their file path like =this:
C:\inetpub\vhosts\test-site-1.webdna.us\httpdocs
C:\inetpub\vhosts\test-site-2.webdna.us\httpdocs
You could then put copies of the directory with the WebDNA =executables and webdna.ini at:
C:\inetpub\vhosts\test-site-1.webdna.us\WebDNA
C:\inetpub\vhosts\test-site-2.webdna.us\WebDNA
Click on each site in IIS Manager, doube-click Handler =Mappings, right click then "Add Module Mapping...". Setup like =follows:
<olonehengnmnlmlg.png>=;
Click Yes when it asks to add a FastCGI =entry. Do this for all necessary sites.
Then go to the main IIS Server on the left menu, double-click ="FastCGI Settings". Adjust the Max. Instances on each executable to =1:
<ecahnpfmiholckpe.png>=;- chris
|
On 4 May 2018, at 05:49, christophe.billiottet@webdna.us wrote:For those who want to =setup WebDNA.fcgi on several vhosts on Windows, we ran some =quick tests just now to confirm you can do this on a vanilla IIS server. =We do not have Plesk to test with unfortunately.---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us
BTW, we did not include a webdna.ini file in the previous =..zip We didn=E2=80=99t include the Admin interface either. It is just =the binaries.So, if you want the WebDNA folder, the link =isand =it includes a webdna.ini as well as the last interface =version.
If someone followed my other directions, and wants to switch, =first they should remove the server-wide "Handler Mappings" they added =on *.dna.
As an =example, lets assume you have two sites with their file path like =this:
C:\inetpub\vhosts\test-site-1.webdna.us\httpdocs
C:\inetpub\vhosts\test-site-2.webdna.us\httpdocs
You could then put copies of the directory with the WebDNA =executables and webdna.ini at:
C:\inetpub\vhosts\test-site-1.webdna.us\WebDNA
C:\inetpub\vhosts\test-site-2.webdna.us\WebDNA
Click on each site in IIS Manager, doube-click Handler =Mappings, right click then "Add Module Mapping...". Setup like =follows:
<olonehengnmnlmlg.png>=;
Click Yes when it asks to add a FastCGI =entry. Do this for all necessary sites.
Then go to the main IIS Server on the left menu, double-click ="FastCGI Settings". Adjust the Max. Instances on each executable to =1:
<ecahnpfmiholckpe.png>=;- chris
DOWNLOAD WEBDNA NOW!
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...