Home
DevCentral
Search
Configure Global Search
Log In
Transactions
T1255
Change Details
Change Details
Old
New
Diff
Currently, infra.nasqueron.org is live, with a servers logs parsed from https://api.nasqueron.org/servers-log/all.json This proof of concept all.json file has been generated by a script from the `Freenode #nasqueron-ops` IRC logs. There is code for a production Rust service to receive data for this document, and to serve this document at rSERVERSLOG. But it's not in production. Yet, I need **NOW** to setup a new Docker engine, upgrade our Mastodon instance, etc. and I'd really like an up-to-date servers log visible. As such, I offer to implement: - on api.nasqueron.org (rAPI), an endpoint to receive a JSON payload and append it to all.json (in PHP, so we can directly run it from current API webserver) - on Dæghrefn or Wearg (rVIPER), the client side to communicate with this API (good news is that part won't change when we kick rSERVERLOGS in production)
Currently, infra.nasqueron.org is live, with a servers logs parsed from https://api.nasqueron.org/servers-log/all.json This proof of concept all.json file has been generated by a script from the `Freenode #nasqueron-ops` IRC logs. There is code for a production Rust service to receive data for this document, and to serve this document at rSERVERSLOG. But it's not in production. Yet, I need **NOW** to setup a new Docker engine, upgrade our Mastodon instance, etc. and I'd really like an up-to-date servers log visible. As such, I offer to implement: - on api.nasqueron.org (rAPI), an endpoint to receive a JSON payload and append it to all.json (in PHP, so we can directly run it from current API webserver) - on Dæghrefn or Wearg (rVIPER), the client side to communicate with this API (good news is that part won't change when we kick rSERVERLOGS in production)
Continue