[TYPO3-dam] fileadmin use in DAM

[georg kuehnberger]

Dan Osipov wrote:
> Yes, we'll have fileadmin directory symlinked to an iSCSI, but we'd like 
> to offload Apache on the main server and serve media files (images and 
> videos) via another server (domain.com for Typo3, media.domain.com for 
> everything in fileadmin).
> 
> So what do you think? Possible?

yes;
- setup your media.domain.com apache server pointing /fileadmin via NFS 
to the iSCSI.
- within TYPO3 using the FE-generation / parsing functions you'd replace 
all links to  */fileadmin/* with media.domain.com/fileadmin ...
- you're done;

hth, regards georg

PS: out of experiance I know that serving static files like file-admin 
does not require very little CPU/Mem, so I fear you wont win too much 
releave for the main server. In case you'd use a reverse proxy in front 
of the main machine you'd gain quite more relieve.

> 
> Dan Osipov
> Calkins Media
> http://danosipov.com/blog/
> 
> georg kuehnberger wrote:
>> Dan Osipov wrote:
>>> We are hoping to have fileadmin on a different server, to offload the 
>>> Typo3 processing server. The DAM urls should point to the different 
>>> URL from the root Typo3 installation, however, looking through the 
>>> code, there are several places where DAM is specifically looking for 
>>> the path to fileadmin. Is it still possible to use a different URL in 
>>> the FE? How?
>>
>> Dan,
>> Did you consider NFS (with symlinks), or any other file-system-linkage 
>> that's transparent to the application, instead of a different URL?
>> We do have an instance with some +250.000 media-files living on a 
>> different server (via NFS), which works fine so far;
>> regards georg
>> BTW: even if NFS is no option, I'd go the route of virtual mounts / 
>> file-systems - there are quite some interesting ones especially in the 
>> area of cloud-computing / storage (like amazon and others do);