Scott - have you looked at %Installer?  That should be the first place that you start for trying to create a deployment from scratch.  This is how Ensemble, HealthShare and TrakCare instances get initialized by the installer and I know a lot of customers have used this with great success.

Also, the Enterprise Manager which is coming out in 2016.2 may be of interest in this area as well.

Benjamin,

You might be running into some security issues (check the audit DB to confirm).  Or, you might not have it working because you have "Lock CSP Name" set to "Yes" in one of the web applications (ref: http://docs.intersystems.com/cache20152/csp/docbook/DocBook.UI.Page.cls?KEY=GCSP_config#GCSP_lockcsp).

I just did a quick test as follows in my 2015.1 instance:

1) Created a SAMPLES2 namespace with new SAMPLES2 DB

2) Package mapped "csp" from SAMPLES namespace to SAMPLES2 namespace

3) Edited /csp/samples2 web application as follows:

- added Unauthenticated

- added %DB_SAMPLES Application Role

- Unchecked "Lock CSP Name" AND "Autocompile" (this should be done in both /csp/samples and /csp/samples2)

- pointed "CSP Files Physical Path" to c:\intersystems\e20151\csp\samples\ 

After this I was then able to see /csp/samples2/form.csp (although with errors because I didn't map the Samples.* package to the Samples Namespace).

So it appears to work - you just need to figure out which of the above pieces you missed :)

HTH!

Ben

I asume since you used MyPage.csp in your example you are doing tag-based and not class-based CSP development?   

Remember that tag-based .csp files compile into classes within the namespace (by default these are csp.* classes).  So you could package-map csp.* (or whatever package you configure your CSP pages to compile into) from your Readonly namespace to the XYZ namespace, and then you could point the /csp/xyz application to the source directory holding the csp pages.  I think this is likely to do what you want (although I haven't tested it).  

Scott,

Code.InterSystems.com was launched but then not advertised because of the Developer Community effort.  It is still supported and will remain open and available until such time as all functionality is available on the Developer Community and all content has been moved to make it accessible here.  Feel free to make use of that site until you see announcements about it being moved.  It works with InterSystems SSO so you can use your existing account.

Ben

To echo what Tom said, this is becoming more and more critical for me as well.  I really don't have time to click a link every time I get a Community update in order to see if its something I am interested in (or can contribute to) or not.  

I also agree with the removal of the decoration, etc.  Just the content with a link to the thread at the bottom of the email please.