i am thinking of releasing a rails application as a gem. it's sort of a wiki application which also stores user data in the db directory. what would be a good way to go to avoid the user data being overwritten, when a gem update is done?
example:
1) user gets version 1 of the gem/application. the data is stored in the gem directory.
2) user performs a gem update and gets version 1.1 -> the data is lost! (because there is a second directory now)
my questions are:
thanks! z
我猜想使用SVN或Git是分发和更新应用程序的最佳方法。
Gem is a bad idea for an application.
I would look into Warbler: http://caldersphere.rubyforge.org/warbler/
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.