15 Apr 2014 8:09 PM #1
Answered: Publishing confusion
Is there a clear reference for the building / publishing process for SA?
When I select 'build web app' from the toolbar, I'd expect SA to build the environment currently selected under build settings, ie, regenerate the files in /build/production or /build/testing, and nothing more.
When I click the 'publish' button from the toolbar, I'd expect SA to copy the contents from /build/production or /build/testing to the publish path. It may also complete a build if required.
As of SA 126.96.36.1996, if I leave the publish path blank under build settings, then run a build, it behaves as proposed above. If I add a 'publish path' under build settings, it not only builds, but also copies the output to the specified path. Ok, we can work with this.
This is where I think the confusion starts.
Under build settings, we specified a publish path. One would expect when they click publish from the toolbar, this is where our compiled project output would end up. It isn't until one clicks 'project settings' and finds there is an option in there ALSO called 'publish path', and that this is the path that 'publish uses', with the 'publish' button copying most of the of the project to that location?
At the very least, it seems that something should be renamed to clarify things?
16 Apr 2014 4:39 AM #2
16 Apr 2014 3:51 PM #3
Thanks for the response. This lines up with what I found whilst writing my original post
I still maintain that for the uninitiated, having two 'publish path' settings leads to confusion.
Also, genuine follow up question, why would one want to publish the entire app, copying many thousands of files?
17 Apr 2014 5:58 AM #4