PHP project is in my public_html folder of my home directory. Project settings > Targets has the web server url set correctly to http://localhost/~username/projectfolder. Under general it will not put the folder I choose for webroot folder. I keep click it and select the correct folder but the field doens’t change. Development environment is set to own server, php server model.
I have a route for / set to /index.php. I have two other routes set for /login to /login.php and /register to /register.php. Both /login and /register work.
So when I try to correct, it asks to copy files to the new location and then locks up. I can click on elements i’ve added to a page but that’s it, nothing else. I have to force it closed and reopen, which then everything is working.
I’ve fixed the issue with where the projects files are stored. However to use the route / I have created i have to put it as ./ to make it work. Which I didn’t have to do on windows using xamp.
Still not sure why i can’t point the web root folder to anywhere unless i create a new folder inside my project… so maybe this isn’t the problem.
Secondly you’re saying that it asks to copy files to the new location and then locks up.
In my short experience with Linux so far, this makes me think of a permission problem? The way it works in Linux is still not 100% clear to me… but the fact that I gotta use sudo for editing most files makes me very suspicious that Wappler needs sudo rights to do the copy action. And doesn’t have a way to handle that, so it locks up.
You could perhaps test this by making it so you don’t need to sudo. I think there’s a way to do this, but again, I’m a linux newb
it’s all in my home folder, so permissions shouldn’t be an issue. the copying files thing happens when you change web roots etc… it moves the files. I actually had two projects, one in nodejs and the other in php that did the same thing. I ran into issues with the nodejs project and moved back over to php. For some reason when I did, most of my issues went away. Such as sessions suddenly not working. The route issue still perplexes me. I’m not going to switch it docker as once i’m finished it’ll end up in apache.
The other reason for dropping node was hosting this app was easier for me in apache. I have zero experience with nodejs hosting and that meant I was putting it in heroku, digitalocean apps, etc. We have our own dedicated hosting server and db servers so that made my choice clearer.