Bump.. Anyone? Really need to get this sorted. Phone system needs to go up by tomorrow and it isn't possible until we figure this out.
Envoyer - Best practice for non-Laravel software residing in public directory
Hi all,
I started using Envoyer recently and just ran into an issue. I am using Open VBX, an open source phone system powered by Twilio, which needs to be made publicly accessible in the document root of my site. It is stand alone, not a Composer package or anything like that.
The issue is that when I place its directory in my public directory, every time Envoyer deploys my code it starts from scratch with OpenVBX, deleting all of its settings files. OpenVBX is part of my Git repository but I could upload it via FTP rather than Envoyer, but not sure if this would solve the problem.
I saw in another post that someone moved this type of thing "one level up" and used a symbolic link when deploying, but I'm not quite sure how to go about this.
Any help would be appreciated, thanks!
FINALLY solved this (thanks for all the help). I can only assume that PHP code is not executed if it resides ANYWHERE under /storage. So, when Taylor suggested I place a third party PHP app there, apparently it had no hope of ever actually working.
I moved the third party app to the top level directory of the site and created a symbolic link from the current release directory's public folder to it, now everything works. So many wasted hours for something so simple. Also a bit let down not a single person offered to chime in here. Was my question vague? Should I have just known this all along? Odd how some questions just seem to be totally ignored on this forum. :/
Please or to participate in this conversation.