🎯 What can I work on ? (openfoodfacts-infrastructure)

[teolemon]

Before you dive, we encourage you to read the README, including our superb architecture diagrams.
We have a monthly infrastructure meeting where we discuss current affairs. We can schedule ad-hoc calls if you'd like to help. The README will tell you how to get in touch.

📚 Better documentation

Beta Give feedback

1. Document undocumented VMs #428
   📚 documentation +1

🎯 Areas of focus

Beta Give feedback

1. Backup (Tracker issue) #338
   0 of 3
   backup +1
2. Wiki (tracker) #360
   3 of 9
   wiki ✨ enhancement +2
3. Blog (tracker) #362
   1 of 3
   blog +1
4. Odoo (Tracker) #361
   0 of 5
   Odoo +1
5. Analytics improvements (tracking) #108
   ✨ enhancement +1
6. Deployment automation (tracker) #425
   0 of 9
   +0
7. 📨 Mail (Tracker) #426
   1 of 5
   📨 email +1
8. 💥 Things on fire 🔥🔥🔥 or to fix in production (tracker) #427
   0 of 6
   🎯 P0 +1

🐳 Improve Docker deployment situation (important)

Beta Give feedback

1. Make network, volumes and names better manageable and more secure #146
   🎯 P1 +1
2. Connect off1 / off2 prod telegraf to new influxdb #74
   Grafana influxdb monitoring off1 off2 🎯 P1 +6

📈 Monitoring

Beta Give feedback

1. Add a health test to ensure the Zammad Elastic Search is always up #101
   monitoring zammad 🔎 Elastic +3
2. Connect off1 / off2 prod telegraf to new influxdb #74
   Grafana influxdb monitoring off1 off2 🎯 P1 +6
3. We have to move monitoring on it's own VM #89
   monitoring 🎯 P1 +2
   
4. Get back old grafana monitoring dashboard #73
   Grafana monitoring +2

Auth

• see https://github.com/openfoodfacts/openfoodfacts-auth

🔢 DNS

Beta Give feedback

1. We need a secondary DNS hosted by another provider #70
   ⭐ top issue DNS +2
   

🔒 SSL

Beta Give feedback

1. SSL certificate issue for *.openfoodfacts.org prevents connection for some old clients #65
   🔒 SSL +1
2. Migrate Scan.party to HTTPS #153
   🔒 SSL +1

Good practices