Jeff,

<< After a few more hours I got it all working. A fun experience for me. I
played around with changing the IIS "webserver" to a different port (it
doesn't seem to want me to remove or disable it) - then I changed EWBsrvr to
port 80 and set the content folder - and that seems to make things easier.
But I'm glad to finally understand it !! >>

Great, I'm glad that things are working well for you.

Tim Young
Elevate Software
www.elevatesoft.com

Okay, I'm deploying my app to my dedicated server.

Turned IIS off, I am going to use EWB web server. I have started the process and I believe answered all the questions properly. I am running on port 80

So in my local computer to do;
http://website.com

and I get this error
Resource / not found


I feel like I'm so close.

I copied the html and .js file to a directory on my C drive on my server, and I added that to the ewb web server Content Folder. I left the default document blank. I checkmarked enable cross-origin resource sharing.

I lave the Database Resource Name, and the other 2 as they defaulted. I didn't create any directories or anything for those. I setup the database, and datasets that I'm using in my little ewb app.

That's about it.

I am so close, but not quite there.

Any help would be greatly appreciated.

Big Al

> So in my local computer to do;
> http://website.com
>
> and I get this error
> Resource / not found

You didn't specify which document to load, try instead:

http://website.com/<mystartpage.html>
normally
http://website.com/index.html

>I left the default document blank.
I you enter <mystartpage.html> here e.g., it's sufficient to use this URL:

http://website.com/

Note the closing slash! It's necessary in EWB

Uli

>Uli Becker wrote:


>You didn't specify which document to load, try instead:

>http://website.com/<mystartpage.html>
>normally
>http://website.com/index.html


>I you enter <mystartpage.html> here e.g., it's sufficient to use this URL:

>http://website.com/

>Note the closing slash! It's necessary in EWB

>Uli


Uli, Thanks. I don't want the user to have to enter the trailing slash, not very intuitive, so I'll go with option 1.
Thanks again

Big Al wrote:

> don't want the user to have to enter the trailing slash, not very intuitive,

I'd hope that the EWB server sorts that itself. The trailing slash is actually a part of the URL, so is often defaulted. The file name that follows can be whatever you want, but if you have specified a default that would be best, so that they can just do the web site URL and get going quickest. I only use the full file name for added functions like admin applications.

--

Matthew Jones

Matthew,

> I'd hope that the EWB server sorts that itself.

I suggested that some time ago - maybe it's on the list as an EWBServer
enhancement.

Uli

Uli,

<< Note the closing slash! It's necessary in EWB >>

I just tried it here and it works fine without the trailing slash (2.06 B1).

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<< I just tried it here and it works fine without the trailing slash (2.06 B1).>>

Just tried it as well and it doesn't work here. Using the latest build.

Uli

Uli,

<<Just tried it as well and it doesn't work here. Using the latest build.  >>

Okay....this is what I've got:

Content folder: c:\ewbtest\painttest\output
Default document: project1.html

URL used in the browser (Edge/Chrome tested):

http://localhost:8080

Using the external EWB Web Server (2.06 B1).

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> URL used in the browser (Edge/Chrome tested):
> http://localhost:8080

Correct for the root - but if you use a subfolder, you need a trailing
slash.

http://localhost:8080/mysite

wouldn't work.

Uli