relative Config path combined with Custom-PATH

[6543]

./gitea --config ./custom/conf/app.1.11.ini
will create&use a config at ./custom/custom/conf/app.1.11.ini

gitea version: current master
1.11.x also afected

[lunny]

So the expected is a relative path to current directory.

[6543]

if i put a ./ on a relative path i expect it is the same as $(pwd)/

[6543]

but in generell i would not expect path change when using relative paths

[6543]

gitea/modules/setting/setting.go

Lines 512 to 514 in 1d7b750

	} else if !filepath.IsAbs(CustomConf) {
	CustomConf = path.Join(CustomPath, CustomConf)
	}

[guillep2k]

Yes, I've noticed this problem when I added the path info to the doctor. Config path is relative to custom dir, not to the current working directory as I expected. Not a fan of that, but I guess that changing that behaviour would be quite breaking, especially because we create app.ini if we don't find it.

[zeripath]

Yup. It's difficult to change once it's there - that's why I kept it that way.

Gitea 2?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

[6543]

ping - we can leave the funct as it wors but add a check if path starts with ./ <- if so its relative to current path

[stale]

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

[6543]

works on current version - dont know why

think some updated lib did the job