ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Forums » Discuss »

Attachment store on a different/other server

Added by Wiki Bit at 2013-11-08 01:12 pm

Hi,

is it possible (has anyone already done it)?
to store the attachements on a different server then the server where chili is running on?

the idea here is :
- chili app runs on server 1 (simple server), with a duplicate on redundant server 2 (inactive, only becomes active if server 1 dies)
- mysql and attachemnts on server 3 (heavy duty server)

Thanks,

Wikibit


Replies (2)

RE: Attachment store on a different/other server - Added by Holger Just at 2013-11-18 12:29 pm

People trying to achieve this often use either a full network share for the attachments (e.g. NFS) and physically store them on a remote server which is equipped for durable storage (proper RAID, ...) or they use DRBD to synch the local files to another server. This is works on block level though, so there is no possibility for a multi-master replication.

For the setup you described, I'd probably start with DRBD as its probably easier to setup than a full NFS server. For both variants, you don't need to change anything in ChiliProject as it still simply store everything on the file system.

RE: Attachment store on a different/other server - Added by Wiki Bit at 2013-12-23 09:31 am

thanks for the info

I will look into that
the other option we are looking at now also is plain rsync + database replication

WB.

(1-2/2)