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.

Sign up for GitHub

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

Jump to bottom

Log file path should be configurable #18

Open
mwrock opened this issue Sep 16, 2014 · 2 comments
Open

Log file path should be configurable #18

mwrock opened this issue Sep 16, 2014 · 2 comments
Labels
0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint Improvement Issues that enhances existing functionality, or adds new features Priority_LOW Issues that are low priority, and will most likely only be fixed by the community

Comments

@mwrock
Copy link
Member

mwrock commented Sep 16, 2014

Migrated from https://boxstarter.codeplex.com/workitem/50

Set-BoxstarterConfig should also be able to change where log files are stored. We will need to make a log file specific to machine/user as well incase the location is centralized.
@jreadytalk
Copy link

This would be nice. I'm facing it trying to get boxstarter.log to be under c:\vagrant and persist through reboots. It would then be good to mention it in the "Boxstarter Log File" section of Installing Packages.

@jreadytalk
Copy link

...on second thought, it would also be awesome if setting "$boxstarter.log = c:\path" would persist through reboots.

@mwrock mwrock mentioned this issue Nov 27, 2014
Closed
@pauby pauby added Bug Issues where something has happened which was not expected or intended 0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint Priority_LOW Issues that are low priority, and will most likely only be fixed by the community Improvement Issues that enhances existing functionality, or adds new features and removed Bug Issues where something has happened which was not expected or intended labels Mar 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint Improvement Issues that enhances existing functionality, or adds new features Priority_LOW Issues that are low priority, and will most likely only be fixed by the community
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mwrock @jreadytalk @pauby