Anyway to keep write new records when move AW's database to another machine?

[directentis1]

Hello, I'm currently using AW on a Docker container (via KASM) and I've mounted its database as a volume.

But as I've noticed, every time I create a new container from the base image, all previous data will be ignored/overridden and a new database is created from scratch.

Perhaps this is related to a session ID or machine ID that keeps changing after a new container session?

Is there a way to keep them unchanged?

---

By the way, how to keep this configuration after closing/reopening AW?

⬇

It keeps reset every time and I need to manually re-tick them.

[ErikBjare]

Perhaps this is related to a session ID or machine ID that keeps changing after a new container session?

There is ~/.config/activitywatch/aw-server/device_id and ~/.config/activitywatch/aw-server-rust/device_id (depending on server), but they shouldn't cause the database to be rewritten as they are just used for new buckets.

Are you sure you've mounted the database correctly in the docker container?

By the way, how to keep this configuration after closing/reopening AW? It keeps reset every time and I need to manually re-tick them.

You change this in the aw-qt.toml, see e.g. https://docs.activitywatch.net/en/latest/migrating.html

[directentis1]

Maybe you mean ~/.local/share/activitywatch/aw-server/device_id?

[directentis1]

I got it, because AW constantly writes to its database, I need to pause it sometimes to write back the files to my mount point.
I've sat up a systemd service to do so.
That solved the problem!

[directentis1]

@ErikBjare
Just another question.
Is there a correct way to terminate AW?

After I send SIGKILL or SIGTERM to AW, the AW sync module close unexpectedly and need to restart.

[0xbrayo]

@ErikBjare Just another question. Is there a correct way to terminate AW?

After I send SIGKILL or SIGTERM to AW, the AW sync module close unexpectedly and need to restart.

This is a known issue with the aw-sync module, will be fixed soon!

[0xbrayo]

ActivityWatch/aw-server-rust#502