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

Have CKAN generate a log of its installs/uninstalls/upgrades #1144

Open
linuxgurugamer opened this issue Jun 21, 2015 · 5 comments
Open

Have CKAN generate a log of its installs/uninstalls/upgrades #1144

linuxgurugamer opened this issue Jun 21, 2015 · 5 comments
Labels
Core (ckan.dll) Issues affecting the core part of CKAN Enhancement New features or functionality ★☆☆

Comments

@linuxgurugamer
Copy link
Contributor

Sometimes, when I'm trying to figure out a problem, I delete a number of different mods, one at a time. When done, I try to reinstall them, but there isn't a session history that I can find.
Essentially, what I'm suggesting is to write the output which gets written to the "Installing mods" tab to a log file, possibly with a date/timestamp.

@Rohaq
Copy link

Rohaq commented Jul 3, 2015

I'd also like to see some kind of historic record of mods installed/updated: Something's broken MechJeb's autowarp for me, but unfortunately, as I hit the "Mark all updated" button, ran the (numerous) changes, and then closed CKAN, I have no way of figuring out what might have broken it :(

@mheguy mheguy changed the title Session history Have CKAN generate a log of its installs/uninstalls/upgrades Jul 19, 2015
@mheguy mheguy added Enhancement New features or functionality Core (ckan.dll) Issues affecting the core part of CKAN ★☆☆ labels Jul 19, 2015
@mheguy
Copy link
Contributor

mheguy commented Jul 19, 2015

This could dovetail nicely into #1155

@blnk2007
Copy link

blnk2007 commented Feb 8, 2016

Any work done on this? It would be very helpful!

@HebaruSan
Copy link
Member

See also #434.

@HebaruSan
Copy link
Member

Thanks to #1881, save this file alongside your ckan.exe and change WARN to INFO, and you get a nice enough CKAN.log file:

However, it could be easier to read (just installs/upgrades/removes and other things the user cares about) and easier to configure (without editing XML). Leaving this open for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core (ckan.dll) Issues affecting the core part of CKAN Enhancement New features or functionality ★☆☆
Projects
None yet
Development

No branches or pull requests

5 participants