Matthew Gregory wrote:
> OK, well it's good to see I'm not going mad!
>
> We have the following file structure:
> \projects
> \custom
> \client <--- this is where config.json is
> \source <--- index.html here
> \class
> \custom <--- our classes in here
> \build
> \qooxdoo-sdk <--- the sdk
>
> On our development machines we have http://server/custom mapped to
> \projects\custom\client so http://server/custom/source and
> http://server/custom/build are available.
> We then have http://server/custom/source/qx mapped to the sdk directory.
> Like this in apache:
>
> Alias /custom/source/qx "C:/Projects/custom/qooxdoo-sdk/frontend/framework"
> Alias /custom "C:/Projects/custom/client"
>
> So what is the preferred method now? We cannot expose the whole of
> \projects\custom\ because it contains other files. Should we move the
> sdk into the client folder?
>
Your configuration is on a dev system, right?! It shouldn't hurt
exposing more structure on an internal development system. Or do you
host development and production on the same system?!
In the unlikely case that you are forced to have these constraints in
place, this is what I would do:
* Change the sdk alias:
Alias /qooxdoo-sdk "C:/Projects/custom/qooxdoo-sdk"
This will render relative uri's like '../../qooxdoo-sdk' from
/custom/source/index.html valid.
This should do the job. Is this feasible for you?
But again, I strongly recommend for various reasons to have at least a
2-tier environment (development - production). Which is all easy to
achieve these days, even on a single hardware, through machine
virtualization (vmware, xen,...), virtual web servers (apache's vhosts)
with separate ports etc.
HTH,
Thomas
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
