/tmp folder used by frankenphp is not the /tmp folder that I can access via ssh ??

[geoidesic]

Hi, I'm very confused..

If I upload a PHP script and then have that php script list the contents of the /tmp folder, the contents are completely different to if I ssh into the server and do ls /tmp?

I guess that frankenphp has its own tmp folder squirrelled away somewhere that it's using. How can I find the actual path to that?

[dunglas]

FrankenPHP doesn't have its own /tmp folder. Your issue is likely unrelated to FrankenPHP.

[withinboredom]

Your environment likely has the temporary file location customized. Check the output of tempnam() to see where it puts the files. Not all temporary files go to /tmp, which is usually reserved for system files, not arbitrary applications (at least on a production system). Some admins will create a ramdisk for temporary files instead of /tmp as well.

[geoidesic]

Ok I tried that. tempnam requires arguments, can't be run without them, so presumably you meant this:

<?php
echo '<pre>';
$result = tempnam("/tmp", "FOO");
print_r($result);
echo "\n";
print_r(sys_get_temp_dir());
echo "\n";

The output from running the script via the browser is

/tmp/FOOMeNIMn
/tmp

However, on the CLI that file is not created in /tmp.
Once again, I can only find it if I browse to a php script that includes print_r(shell_exec('ls /tmp'));

I'd be happy to give you root access to this server if you would like to see it in action.

[geoidesic]

Interestingly... I decided to change the root folder in the Caddyfile, and that reset the contents of the ghost /tmp folder. So it feels like it is a /tmp folder that is related to the virtual host that's set up in the caddy file.

I went a step further and noticed that the ghost /tmp folder empties each time I restart the frankenphp systemd. Further evidence that it's related to frankenphp or at least to the service.

[geoidesic]

Ah... It must be a systemd thing. I notice this setting in systemd/frankenphp:

PrivateTmp=true

[withinboredom]

Ok I tried that. tempnam requires arguments, can't be run without them, so presumably you meant this:

Per documentation:

Creates a file with a unique filename, with access permission set to 0600, in the specified directory. If the directory does not exist or is not writable, tempnam() may generate a file in the system's temporary directory, and return the full path to that file, including its name.

So tempnam('/') (assuming it isn't running as root), will return the current temporary directory.

In any case, glad you figured it out.