- separate in two stages: to prepare, and to actually migrate
- in step one, prepare a list of users to be migrated, and store it
compressed as app config
- gzcompress can be used, because we already require zlib
- upon the next calls (step two), slice off the first 5000 users
and migrate them. Re-add job if necessary to repeat.
- downside is that an app config value will in the beginning use the
RAM with any request, until it thins out. Examples: 2m UUIDs (75 MiB)
result in ~40 MiB compressed data, while 0.2Mib for 10 000 UUIDs,
0.4MiB for 20 000 and 4.1 MiB for 200 000. Acceptable.
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
- fallback to background image from old location
- migrate background images to new location as insensitive job
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
