Stefan Larsson wrote > Thank you for the answer. The connections are no problem, I was thinking > more in terms of the relation of the folder structure and the generate.py > script. I have been thinking some more about this since posting and I > would > like to separate the SDK and the generate.py script from the exposed > folders. One way would be to use file system links, but another way would > be to generate the source and build folders in a different location. I > would like to integrate generate.py into the build system such that it is > executed automatically and when deploying I don't want unnecessary files > to > be visible to any client. > > But I guess that during development it should be possible to skip > generate.py by generating everying (generate.py source-all if I recall > correctly). > > /Stefan Larsson
The quick and maybe dirty way I do this is to just manually run the ./generate.py build, whenever I want to deply and I deploy only the build folder of my app. So, the ./generate.py build is not in my continuous integration system, although I could do this as well. Using IIS webdeploy I can include or exclude which files to deploy. -- View this message in context: http://qooxdoo.678.n2.nabble.com/Play2-framework-qooxdoo-best-practices-tp7586751p7586761.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
