>> Can you explain what "install 2+ pyjs applications" means? Can you >> give a (real world) example? Can you describe the build / deployment >> process? > > all: index admin > > index: index.py PageLoader.py index.html > pyjsbuild --no-keep-lib-files --no-compile-inplace --print-statements \ > --apploader-file=index.html \ > index > > admin: admin.py edit.py admin.html > pyjsbuild --no-keep-lib-files --no-compile-inplace --print-statements \ > --apploader-file=admin.html \ > admin
If I understand correctly the 2 apploader files come from the application directory (i.e. where the application's .py source files are located), not the ./public folder. This is obviously necessary - unless you want your "injected changes" be overwritten each time the other app is built. Should we maybe make this the default behavior in future? I think both use cases will coexist, a) that you have a no special HTML file that loads the bootstrap script, and b) that you have a full-featured Website project with your HTML document already there waiting for the bootstrap loader script tag to be injected. Probably depends on what is the more common use case. In any case, the --apploader option makes sense! :-) (Sorry for my comment earlier) Peter
