We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When you install it to another drive than c:\
it search in the wrong drive for config.json
Error: ENOENT, no such file or directory 'D:\Dokumente und Einstellungen\andreas.tilemill\config.json'
should be looking in
C:\Dokumente und Einstellungen\andreas.tilemill\config.json
The text was updated successfully, but these errors were encountered:
going to take a look at fixing this after release.
Sorry, something went wrong.
@misterboo - curious - are you admin on your machine? (see #1200)
no ... i just installed it to d:\ ...
it seems tilemill looks on the Installdrive for config.json
if i install to e:\ it looks there for config.json
But anyway #1200 could be the same issue ... as i now as administrator you don't have an own userdirectory
so tilemill try to find config.json in the root C:.tilemill\config.json
I guess the issue is HOMEPATH
this resove in Windows to \Dokumente und Einstellungen\andreas
that means without the Driveletter
as Administrator HOMEPATH is set to ""
probably tilemill or node takes the Driveletter from the drive tilemill is startet ...
probably you should use USERPROFILE in index.js
process.env.HOME = process.env.USERPROFILE;
ecd1144
@misterboo - thanks USERPROFILE seems to work well (committed), avoiding the need to use HOMEDRIVE + HOMEPATH.
USERPROFILE
HOMEDRIVE
HOMEPATH
No branches or pull requests
When you install it to another drive than c:\
it search in the wrong drive for config.json
Error: ENOENT, no such file or directory
'D:\Dokumente und Einstellungen\andreas.tilemill\config.json'
should be looking in
C:\Dokumente und Einstellungen\andreas.tilemill\config.json
The text was updated successfully, but these errors were encountered: