Open GoogleCodeExporter opened 9 years ago
Hello Heath,
Hope you didn't lose your modified db.ini.
Looks like a nice bug you caught. The way AppSnap works is to copy its local
db.ini
to the cache. This is so that you can have one master copy that you can
distribute to
clients. However, clients will also copy their db.ini to the cache, overwriting
your
changes.
Will have to add code to fix this but meanwhile, what you could do is maintain
your
db.ini in a separate location than the cache folder and point clients to that
location in the config.ini 'location' parameter. Next, you can update your
clients to
load this custom db.ini. Will be a few manual steps but at least you can get it
to work.
Hope that helps.
Original comment by ganesh...@gmail.com
on 9 Oct 2009 at 6:17
I moved my custom DB to another location on the server and changed the pointer
but it
still will recreate the DB.ini on the shared cache folder. Any other
suggestions.
I've attached my config.ini. I've tested a lot of settings trying to get it to
work
how I want it to...
Original comment by heathlan...@gmail.com
on 9 Oct 2009 at 8:04
Attachments:
AppSnap still loads db.ini from it's local folder. You need to run an update
first on each client to get the
custom db on the client. Then it will work fine.
For your purposes, ignore the copy of db.ini in the shared cache. Until I fix
this bug, it is useless.
Original comment by ganesh...@gmail.com
on 12 Oct 2009 at 2:21
How do I run that "update"?
I'm currently only testing the client on my workstation. I put my custom
"db.ini"
file in the "C:\Program Files\AppSnap" directory where it is installed on my
workstation. The custom "db.ini" file is also on the shared_cache folder on the
server as well. When I run the appsnap -l or the appsnap gui it list many
apps. I
also tried copying my custom "db.ini" and using "userdb.ini" and it still loads
all
those extra apps.
Original comment by heathlan...@gmail.com
on 12 Oct 2009 at 3:13
I reinstalled it and swapped db.ini before running the app the first time and it
seems to work.
Original comment by heathlan...@gmail.com
on 12 Oct 2009 at 4:12
Original issue reported on code.google.com by
heathlan...@gmail.com
on 9 Oct 2009 at 2:32