Jarvis Upgrade: Difference between revisions
Created page with "JARVIS really could do with a major software update. Security concerns aside, newer <code>ssh</code> clients have long deprecated or hard-blocked the ciphers that Jarvis' old <code>ssh</code> server supports, so connectivity is becoming a pain. == Services == JARVIS runs various services with varying degrees of utility regarding the operation of the space. None are security-critical (e.g. space access etc), but some would be missed if they went away. This pag..." |
(No difference)
|
Latest revision as of 14:10, 8 June 2025
JARVIS really could do with a major software update. Security concerns aside, newer ssh clients have long deprecated or hard-blocked the ciphers that Jarvis' old ssh server supports, so connectivity is becoming a pain.
Services
JARVIS runs various services with varying degrees of utility regarding the operation of the space. None are security-critical (e.g. space access etc), but some would be missed if they went away.
This page documents these services in the hope that when we get round to upgrading, it can serve as a to do list for the configuration of a new/upgraded VM.
/home/shared
To-do: make a list of devices / share names & params here
Remote SSH config
- Map WAN:3000 to Jarvis:22 [not part of Jarvis' config] - might need to update after Jarvis upgrade depending on network config.
User public_html
- Config Apache
MQTT Broker
There's an MQTT broker running that publishes less sensitive info (i.e. not anything that would open doors / credit account balances from note reader etc):
- Device status messages
- Machine bookings
- Temperatures
- Discord notifications
- Urchin & DonationBot chatter
- Door status notifications
- Urchin/DontationBot chatter
User cron jobs
Some people have cron jobs executing on Jarvis for their own purposes.
Please add
If you know of other things that would need to be re-configured in the event Jarvis is replaced, please add here.