APP_DATA_PATH vs WORK_PATH

[ghnp5]

Hello.
I've just realized that I have these two configs the same:

WORK_PATH = /data/gitea
APP_DATA_PATH = /data/gitea

When reviewing the example app.example.ini, I see that APP_DATA_PATH should have its own dedicated folder.

Is there a risk in having both of these the same? Like, if there are directories with the same name that could conflict with each other?

If I want to move APP_DATA_PATH to its own directory, is there an easy way to know which subdirectories I need to move into that new APP_DATA_PATH?

Many thanks!

[wxiaoguang]

I think you are using docker, nothing need to do.

Is there a risk in having both of these the same?

At the moment, no, Gitea will do the best to avoid conflicting.

If I want to move APP_DATA_PATH to its own directory, is there an easy way to know which subdirectories I need to move into that new APP_DATA_PATH?

Not that easy.

[ghnp5]

Thank you for your reply.

Yes - I'm using Docker. But in terms of filesystem structure, there is probably no much difference, so that's why I didn't mention it.

Not that easy.

Ah ok. If it was a matter of simply moving a number of folders to the new location, I'd be happy to do it.
However, if there are hardcoded locations in the database and other places, after the first run, then I understand why it may be hard.

Thank you again.

actions_artifacts
actions_log
attachments
avatars
conf
home
indexers
jwt
log
packages
queues
repo-archive
repo-avatars
tmp

[wxiaoguang]

Not that easy.

Ah ok. If it was a matter of simply moving a number of folders to the new location, I'd be happy to do it. However, if there are hardcoded locations in the database and other places, after the first run, then I understand why it may be hard.

It's not worth to do that, and it would break the docker's default config (although the default config is not that right, since it has been widely used so it won't cause problem)

[wxiaoguang]

I think this issue could be closed?

[ghnp5]

Sure. I appreciate your replies. Thanks!