-
Notifications
You must be signed in to change notification settings - Fork 17
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
New installation doesn't copy subfolders and files #18
Comments
Can you submit the install.log? It has some detail about what it copies and what it skips. |
Submit == provide the detailed part of the log starting at the point where it hands over to the PowerShell script, the one from the log file will have debug data. |
If App_Data exists, it will not copy it again - this prevents overwriting of the logs and existing packages. |
Not sure on contents, but a guess is that we did not set recurse properly when there are no contents in the tools folder and it creates it all. Is there another subfolder? |
@ferventcoder where is install.log located? |
My bad 😆, I totally meant the chocolatey.log, did not mean to put that dot in between install and log. |
Same problem here, installed 2.0 using the same dockerfile I used for 0.1.3 and the Folders: App_Data, Bin, Content were missing and accessing the page ended in a runtime error. I have fixed it by manualy moving the missing folders to C:\tools\chocolatey.server inside the container and it works now. |
@ferventcoder here you go |
@FLeven same worked for me. For the time being I just added code into the Puppet module to copy those as a work around. |
Found the issue. Copy-Item won't create the top level folder if it doesn't exist (even if you use |
In the directory we are deploying to, Copy-Item will not create the directory if it does not exist, even if you have selected `-Force` as an option. So ensure the directory exists by creating it before calling Copy-Item.
Fixed in 0.2.1 |
Seems that the app_data and contents folder do not copy to c:\tools\chocolatey.server from the package. Anyone else seeing this?
The text was updated successfully, but these errors were encountered: