Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The directory with files should be configurable #8

Open
anrichter opened this issue Mar 11, 2012 · 2 comments
Open

The directory with files should be configurable #8

anrichter opened this issue Mar 11, 2012 · 2 comments
Assignees

Comments

@anrichter
Copy link

The folder 'files' that is hardcoded at the moment should be configurable. All my applications use the folder 'system' for alle the files such as user pictures.

So the possibility to define the folder name, which should packed into the backup archive, would be fine :)

@ghost ghost assigned mattconnolly Mar 12, 2012
@mattconnolly
Copy link
Owner

Hmm. It seems saving attachments as files directly to the filesystem is quite uncommon, and as you point out, can be handled very differently.

There might even be more than one folder that should be backed up.

Another consideration is that rake tasks have very poor (and ugly) parameters support from the command line.

I have two ideas for a solution:

  1. Change the task to be using a standalone command-line script instead of a rake task (e.g., "rails" or "bundle")
  2. Specify the folder to be backed up in a config file

I think 2 would be better since you could link the config file to the app in source control so that other deployments would backup/restore in the same manner.

Of, course, other suggestions are welcome! Thoughts?

@anrichter
Copy link
Author

I also think the second solution would be better. I looked at the gem backup and use it now for my backup and partial restore, when i need a restore.

Your gem is perfect for me to bring mysql data from a production system into a sqlite driven development system. And this works now with the fix #7 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants