Hi guys,
I have some question about the "EXTRA_HOSTS", I installing devibox on remote server, this server has 2 IP public "37.xxx.." and private "10.xx.." I want that when I visit mypublicproj.com who is linked to the public ip, it will redirected to my devilbox project "myproj.loc" ?
I have some question about the "EXTRA_HOSTS", I installing devibox on remote server, this server has 2 IP public "37.xxx.." and private "10.xx.." I want that when I visit mypublicproj.com who is linked to the public ip, it will redirected to my devilbox project "myproj.loc" ?
EXTRA_HOSTS=mypublicproj.com=myproj.loc ? thats right ?
@juanjosezg, your ~/.ssh folder is mounted on startup by devilbox. Read more here: https://devilbox.readthedocs.io/en/latest/configuration-files/env-file.html?highlight=~%2F.ssh#host-path-ssh-dir
To fix the problem you have to fix the perms on your host system; devilbox has nothing to do with it. Do this:
... from a terminal:
chmod 600 ~/id_rsa
... and you're done!
vscode: make sure that you're woking from within a "workspace":
{
"version": "0.2.0",
"configurations": [
{
"name": "Listen for Xdebug",
"type": "php",
"request": "launch",
"port": 9000,
"pathMappings": {
"/shared/httpd/[some-site-folder]/[the-docroot]": "${workspaceFolder}/[the-docroot]/"
}
}
]
}
The really important bits are:
"port": 9000,
"pathMappings": {
"/shared/httpd/[some-site-folder]/[the-docroot]": "${workspaceFolder}/[the-docroot]/"
}
devilbox has voodoo for passing port 9000 to/from the docker container. work with 9000 or change the voodoo; your call.
... and now for the picky bit. "${workspaceFolder}/[the-docroot]/" needs a trailing slash or your breakpoints won't grab. If you have the trailing slash. If you have the trailing slash and your breakpoints still aren't hitting try checking "everything":
host system: make sure that you've setup a network interface alias. read about that here: https://devilbox.readthedocs.io/en/latest/howto/xdebug/host-address-alias-an-mac.html#howto-host-address-alias-on-mac
... And now for the part that you actually asked for; the xdebug.ini file. You'll need to setup the file to match the version of php that you're using and the config vars in my file are for Xdebug 3 ... as translated from Xdebug 2 using this: https://xdebug.org/docs/upgrade_guide — so you may need to go the other direction if you're using a different version of php. Here's the contents (the important bits) of my [devilbox-root]/cfg/php-ini-7.4/devilbox-php.xdebug.ini file:
Whoops, almost forgot. You need a cookie set in your browser for the current page that you're debugging. Here's the content of a bookmarklet that I use to spin up a xdebug.idkey cookie:
To add that, right click (or ctrl+click) the Chrome bookmark bar then choose "Add Page":
To make sure everything is A<=>B you can shell into the devilbox and give the xdebug.log file, specified in the xdebug.ini file (above) a tail -f:
tail -f /var/log/php/xdebug.log
if everything is connecting you'll get this bit of magic pixie powder:
... dig the smiley face on the end; because awesome, thats why.
==> log/apache-2.4/qualitydigest.com-error.log <==
[Wed Sep 15 16:46:59.355296 2021] [proxy_fcgi:error] [pid 1097:tid 140406884910848] [client 172.16.238.1:64840] AH01067: Failed to read FastCGI header, referer: http://somesite.com.loc/
[Wed Sep 15 16:46:59.356665 2021] [proxy_fcgi:error] [pid 1097:tid 140406884910848] (104)Connection reset by peer: [client 172.16.238.1:64840] AH01075: Error dispatching request to : , referer: http://somesite.com.loc/
==> log/apache-2.4/somesite.com-access.log <==
172.16.238.1 - - [15/Sep/2021:16:44:44 -0600] "GET / HTTP/1.1" 503 299 "http://somesite.com.loc/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:92.0) Gecko/20100101 Firefox/92.0"
Does anyone know how to keep proxy_fcgi — or whatever part of the stack gets bored with me looking at the contents of variables — from timing out and punching back with a 503?
Hi all, I'm stuck on something and I could use some help.
I'm having Postman send over a GET request with an Authorization header, but it's not getting to PHP. Apache is probably discarding it, for security reasons. I have tried several ways to tell Apache NOT to do this, but nothing is working. Here's what I've tried:
- Adding custom vhost templates to /my-project/.devilbox with the appropriate directives, and confirmed they're being picked up
- Adding a custom .conf file to /devilbox/cfg/apache-2.4
- Making changes directly to my .htaccess files in my webapp (CakePHP v3)
I've restarted the Devilbox countless times but I'm getting nowhere with this. Any help would be appreciated.
3 replies
Nvm. my question, I am now sure I am running the work container. It just doesn't contain drush. If anyone could explain to me how to get drush in there I would be grateful. If I read this correctly it should already be? https://github.com/devilbox/docker-php-fpm
I've been following the installation instructions and I've reached the point where I'm supposed to be able to access the Devilbox intranet. However, when I try to access it on the port I've assigned in the .env file (the machine I run my containers on has a web server that uses ports 80 & 443 so I assigned Devilbox to 30080 and 30443), I get a connection timeout message in Chrome. I'm accessing this from another machine on the same LAN, would that be a problem?
Hi, I'm trying to install devilbox on my machine and I'm able to access the intranet from my local machine. I keep getting a timeout and I can't figure out what I'm doing wrong
Hi, how can I add crontab? crontab -e * php -q "/var/www/html/cron.php" >/dev/null 2>&1
I tried connect to container Httpd and php to add : update; install cron; and crontab -e; add >> crontab -e * php -q "/var/www/html/cron.php" >/dev/null 2>&1 ... But not work. could someone hlep. Thanks