After a "successful" deployment (no errors in Team City or Octopus), when visiting the staging site, the front-end works fine, but when I go to the back office I get a blank screen (should be Umbraco v7.4.3)
I'd recommend installing the same version of Umbraco locally, then copy your production files locally and compare the two installs to see if the production version is missing any files.
Also, this can sometimes be a sign that you need to clear a few caches (e.g., delete the App_Data folder and your browser cache).
Missing files after Octopus Deploy
After a "successful" deployment (no errors in Team City or Octopus), when visiting the staging site, the front-end works fine, but when I go to the back office I get a blank screen (should be Umbraco v7.4.3)
http://i.imgur.com/4tQC3sc.png
Just wondering if anyone can tell me what that is a symptom of? Missing files? Need an extra step to rebuild again?
Just some ideas or clues would help.
Thanks.
I'd recommend installing the same version of Umbraco locally, then copy your production files locally and compare the two installs to see if the production version is missing any files.
Also, this can sometimes be a sign that you need to clear a few caches (e.g., delete the
App_Data
folder and your browser cache).Thanks for the reply. I actually tried both those after the original post.
My steps in TC are (roughly, from memory);
Trigger build from git commit
Restore packages from nuget
Build .sln
Package using Octopack
Push .nupkg
Then Octopus kicks in and deploys.
When I turned the .nupkg out to a .zip and compared it to a vanilla download of 7.4.3 i can see a bunch of files missing.
I'm thinking the Octopack step is ignoring files for some reason.
Also, a direct pull from git, restore and rebuild worked perfectly from within VS2015.
Deleting indexes / temp / cache in App_Data did nothing.
I need to modify the build steps or try a different approach. It's really annoying because I'm so close the build setup I need.
Did you manage to get this working? And was there any online how-to you've followed to get this working?
is working on a reply...