#location ha_run_lock file

1 messages ยท Page 1 of 1 (latest)

coral orchid
#

The why is simple, you had a running instance targeting that directory.
From now on, everyone will have this file. This file is how the logic determines if something else is also running against the same configuration.
It is not an indicator of 2 instances using the same configuration directory, but at least one.

So the issue(?) would be to move it into .storage.

bright orchid
#

ah okay

#

Clear

#

I will write something up to suggest to move it to .storage

final thicket
#

Indeed, I'm seeing the same .ha_run.lock file in my config directory.

mossy iris
#

Yea moving it makes sense to me

#

not really a bug, more of a task / discussion

#

but at least it is tracked

#

The fact the lock exists is normal in applications (although we didn't have one)

bright orchid
#

I noticed it because of the Github link in VSCode

mossy iris
#

Tagged ๐Ÿ‘

#

thanks!

#

PS You can tag yourself as well I think?

bright orchid
#

Yeah, I can

#

keep forgetting that

sick heath
bright orchid
#

oh wait, you already posted it here, I posted it in the main thread as well now ๐Ÿ™‚

#

location ha_run_lock file

mossy iris
#

I kinda disagree

#

if anything the db shouldn't be in the root either