Thanks for getting back to me @fool. Apologies for the bluntness in my previous message, it was a frustrating and stressful evening trying to get this to work.
So yes, my repository has the folders
backend at root. So, in the past, I would set the base directory of the deploy config to
website and it would deploy the website directory as desired. Now, with base directory of
website it deploys root for some reason…which means users need to go to https://joinbeaut.com/website to see anything which is obviously horrendous.
I’ve tried using
website/website in both base directory and publish directory as you’ve suggested previously (and tried again now just to confirm), but then it throws the expected error saying that the directory doesn’t exist, because it doesn’t.
Whatever changes your development team have made to the deployment process, it now appears that deploying a non-root directory doesn’t work. I actually made a mistake in my previous reply though; I can confirm the workaround of adding the
. to the publish directory “works”…well it seems to work if I look at the deployed bundle, but it’s taking a hell of a long time to propagate to my custom domain?! Shouldn’t it reflect instantaneously given the load balancing architecture in Netlify? I still need to go to https://joinbeaut.com/website to see anything. Any advice?
Can your dev team get a fix in for this? It’s most definitely not a nice user experience, and although my initial experience with Netlify has been great, this incident is worrying and disappointing. I can’t rely on a service where things break underneath me as I’m sure you can understand.