Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have applications that have a lot of static content (>60gb) which is updated frequently. It used to be we would manually rsync from vendors and between environments, and our code would rely on naming conventions to find files. Only now are we writing tools that will help with media ingestion, using a database to store filenames.

We still have the problem of keeping tabs on our media across environments and servers. I'm wondering if anyone can share how they keep on top of large amounts of static media content, and how they automate deployment. We only have a couple devs and dev ops, so lightweight, simple solutions are always preferred.

share|improve this question

Well the easy solution is to use star topology. You ingest media to big origin server, and it's replicated across small edge servers.

Ideally you would use XML files to store meta-data with each file on the filesystem. In database you can have index of these.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.