Indexer tweaks
Ash258 opened this issue · comments
DB
manifests|old_manifests|buckets
- created_at - simple
created_at timestamp NOT NULL DEFAULT NOW()-- DEV - updated_at - more complex. With triggers? or just manually handle it? -- DEV
- deprecated - will be handled manually from manager/cmd/db -- DEV
- In case of archived, it will be just removed from db
- Test migrations -- DEV
Installation statistics - #211
- Work out concept
- Prevent manipulations
- Different versions stats from same manifest
- Update process
- Recent failed operations
- Allow user to disable it
Processing
- Handle deprecations/move
- Document bucket allowance and process
- Array for query
Invoke-DatabaseQuery -ScriptBlock[] - Export to modules
- Parallelism?
- Periodical verification runs
- Weekly test of all URLs -> report to DB -> monitor -> trigger -> build up recommended commands to web host txt file
General
- Dependencies update
- Weekly report of all dependencies changelog
- DB Update will be 2 steps verification - site 2 site in different container on different host
- DB Replication
- Adjust backups - 3|2|2
- Ansible
- Load balancing
Base bucket has to be adopted after 0.6.5 and added manually to fallback function
- Prevent manifests with encoding issues, being accepted in main
- Notify first in error log to trigger monitoring
- Auto recover
- rm
- git pull
- Check archived manifests addition
Duplication happen for some reason on full re-indexing.
Install redirect
Installs script take 2
Patching
Migration