Linux – Apache places uploaded files in /tmp. Can I change that to another directory

apache-2.2fileslinuxupload

Is there a configuration that changes the directory where apache web server temporarily places uploaded files? I have access to httpd/conf.d

I'm on a machine where /tmp is very size constrained and have a requirement to allow file uploads that are larger than the available space on /tmp.

Environment: fedora 18, apache web server 2.4.6-2, passenger and ruby on rails.

EDIT: there's some discussion around the office that it's passenger (because this is a ruby on rails app) not apache that determines the location of the temporary file upload. I'm going under the assumption that it's apache but please correct me if I'm wrong.

Best Answer

The temporary file location seems to be set by the scripting program that you choose. In PHP, for example, the temporary upload location is set by the upload_temp_dir directive.

upload_temp_dir = /somewhere/else

As far as Ruby on Rails goes, I found this ServerFault question that describes it as a change to the 'tmpdir' property of Rails' initializer object.

class Dir
  def self.tmpdir
    "/your_directory/"
  end
end

To parrot the user who answered this question in the other thread, make sure that the folder you specify is writable by the user for Apache.

Related Solutions

Why is the Rails app under Passenger occasionally grinding to a halt

One resource that I found useful was the section of the Passenger users guide where they talk about this:

If one of your application instances is frozen (stopped responding), then you can figure out where it is frozen by killing it with SIGABRT. This will cause the application to raise an exception, with a backtrace.

Linux – How to setup Apache with FastCGI and Ruby

Well, in the meantime, I figured this one out. Since there was no concise writeup on this subject, here is the beginning of one. When I have all the bugs ironed out I'll submit this to some tutorial sites.

Make sure that the base fastcgi apache module is installed. If you use ArchLinux as I do, mod_fcgid on the aur works. In other distributions, install either mod_fcgid or mod_fastcgi. (For those who wonder the difference, I don't think there is much, so I went for the one with more activity.)
In your httpd.conf file, activate the module by adding a line to beginning of your LoadModule definitions. Not sure if it matters which distributions, but on Arch it was Loadmodule fcgid_module modules/mod_fcgid.so
Add a new section to your httpd.conf. I put this just under the cgid_module section, but I'm pretty sure location would be arbitrary.
```
<IfModule fcgid_module>
  AddHandler fcgid-script .fgci
</IfModule>
```
Now from my understanding, any file having the .fcgi extension in a directory marked ExecCGI will now be handled by the fastcgi module that was installed. I installed this package to give Ruby the fastcgi bindings, an inside an ExecCGI directory, I wrote this test script test.rb.fcgi
```
#!/usr/bin/ruby -w
require 'fcgi'

count = 0
FCGI.each_cgi do
  puts "Content-type: text/html\n\n"
  puts "Hello, Ruby! FastCGI(#{count})"
  count = count + 1
end
```

Now when you go to that page in your browser, since count is outside the fastcgi loop, it should increment with each page view. If that is so, fcgi is setup correctly.

Best Answer

Related Solutions

Why is the Rails app under Passenger occasionally grinding to a halt

Linux – How to setup Apache with FastCGI and Ruby

Related Topic