About the pathing

P

Pj1

New member
Hello
Am I able to create to create foldering like
server\_public\ - which would be shown on external browser as a wwwroot and index.php could then require ".\..\externally_inaccessible_stuff.php"; (which still was were compiled in the exe)

I tried to select c:\dev\myproject\ as a wwwroot and c:\dev\myproject\_public\index.php as a home page on exeoutput, but when exe was running, it was only accessible at http://localhost:8080/_public/index.php

altho if I select c:\dev\myproject\_public\ as a wwwroot and index.php there as a homepage c:\dev\project\ files will not be included in the exe

dunno how to explain this better :D You got the point, i'd like to include php under wwwroot that are not directly "user accessible"

Thanks <3
 
By default, in an ExeOutput app, the "public" folder is the "Data" virtual subfolder of the EXE.
This explains it:

Accessing Files in Compiled PHP Applications - ExeOutput for PHP

Learn how to access local, compiled, or external files in your PHP applications created with ExeOutput. Manage file access and troubleshoot common 'file missing' errors.
www.exeoutput.com www.exeoutput.com

And you can change "Data" if you don't want that. It's also optional to use: ExeOutput makes all PHP files available as if they were in that virtual folder.
 
gdgsupport said:
By default, in an ExeOutput app, the "public" folder is the "Data" virtual subfolder of the EXE.
This explains it:

Accessing Files in Compiled PHP Applications - ExeOutput for PHP

Learn how to access local, compiled, or external files in your PHP applications created with ExeOutput. Manage file access and troubleshoot common 'file missing' errors.
www.exeoutput.com www.exeoutput.com

And you can change "Data" if you don't want that. It's also optional to use: ExeOutput makes all PHP files available as if they were in that virtual folder.
Click to expand...
Yea i read that, but i don't figger what's the point of changing the name of the data folder if all the files are still reachable with browser when internal webserver is enabled? I'd like to include php files in the exe that are not reachable via browser, but could be reached with php code when needed.
like
PHP: 
# rootfolder:
# Templates/layout.html
# Templates/menu.html
# Config/config.php
# Data/index.php   <-- starting homepage

# and then in index.php just;
<?php
    include_once("../Config/config.php");
    require("../Templates/layout.html");
?>

It would be awesome to directly give Exeoutput my whole project folder and then just mark the public folder which will be used as a starting point. Much less unnecessary hassle..!

Thanks <3
 
Pj1 said:
I'd like to include php files in the exe that are not reachable via browser, but could be reached with php code when needed.
like
Click to expand...
Well, that's already the case if you choose the homepage in the "public" subfolder and the project source folder in the root directory of your website.
 
gdgsupport said:
Well, that's already the case if you choose the homepage in the "public" subfolder and the project source folder in the root directory of your website.
Click to expand...
It's not. Root directory is always reachable

App runs allright the way you described - but If I turn on internal webserver at 8080, I have to open http://localhost:8080/public/ instead of just http://localhost:8080 and "hidden" files can be reached from http://localost:8080/hidden_gui_template.html or http://localhost/hiddenfolder/hiddendata.dat

Access to those files can't be denied with .htaccess either

It would be great if "application root" would default to "webroot" as like it is now, - but instead of selecting homepage file (which should be standardly index.php anyway) - webroot itself could be changed to different subfolder within "application root" - and this way rest of the files in "application root" would stay hidden, but reacheable from php, and app would run at it's base address http://heserver/ or http://localhost:8080/

This would fix the thing, and be more like standards in web servers
 
Last edited:
Yes, this access is possible thanks to the new external HTTP webserver feature. We'll study about that possibility.
Indeed, the concept of a homepage (or "index" page) is particularly relevant for GUI applications only.
 
You must log in or register to reply here.
Back
Top