Looks like we can't reproduce the issue or there's a problem in the test case provided.
Sencha Premium Member
Changed application appFolder writes designer.[js|html] always in the root deploy dir
Designer files (.js and .html) are always written to the deploy root, all MVC files are written to the changed appFolder, e.g.:
Deploy path in Settings: /deploy/
The changed appFolder: ext/app
designer.[js|html] -> /deploy/
MVC files -> /deploy/ext/app
This is by design! How/why would you have liked it to work?
deploy into an environment with static-route
I also find it strange that the deploy route is affected by the appFolder. Why should a deploy behaviour be changed by a project configuration? Well this is to general... An example for a potential problem:
Am I missing something? Thanks for your help and a great project. love it so far!
well your double entering it in this case. Simply make your deploy path /webapp/
The limitation is that by convention MVC requires an app folder that has models/ views/ controllers/ etc .. underneath it.
Know that in the future we'll be evolving the deploy to do move than rsync / xcopy files. Think "sencha app build production" aka better integration with SDKTools to deploy your application for production
I was wondering, is there is a way to configure appFolder directory to be relative to the app.js file? due when i call app.js it look for the app folder in the root folder, that is not correct.
Can you give me example pathing? I'm not fully understanding the question.