Scribd
Upload
6 views1 page

Note

The system is currently undergoing maintenance with a security patch in progress. New features include an Admin Management API for managing MongoDB instances and a Smart-Nav feature that caches appointment requests for easy rebooking. Caution is advised not to expose the management port to the public gateway.

Uploaded by

Dxler YT
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
6 views1 page

Note

The system is currently undergoing maintenance with a security patch in progress. New features include an Admin Management API for managing MongoDB instances and a Smart-Nav feature that caches appointment requests for easy rebooking. Caution is advised not to expose the management port to the public gateway.

Uploaded by

Dxler YT
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

============================================================

SYSTEM ADMINISTRATION LOG - JANUARY 12, 2000


FROM: Samuel Sanders - (known also as admin_65537)
SUBJECT: Maintenance & New Dev Features
============================================================

STATUS: SITE UNDER MAINTENANCE (PATCHING IN PROGRESS)

The scheduling system is currently offline for a security patch


cycle. While the frontend is restricted, I've started coding
the new 'Admin Management API' to handle our MongoDB instances
directly from the backend.

NEW FEATURE: ADMIN MEMBER MANAGEMENT


------------------------------------
The internal API now allows us to force-add members to any
appointment using their unique reference ID. This is for
internal use ONLY on the management port (5000).

Example usage for the dev team:


curl "[Link]
new_user=exampleuser&reference=exampleuser2-JAN1"

NOTE: To simplify the early-stage testing (temporary), I have configured


the backend so that any POST request sent to this route is
automatically REDIRECTED to the GET handler. It's easier to
debug via browser strings for now.

NEW "SMART-NAV" FEATURE (BETA):


-------------------------------
I've implemented a persistent replay buffer. Whenever a user
books an appointment, the backend caches the entire POST
request in db.

Why? If a user accidentally deletes an appointment and wants


to re-book it immediately, the system can "replay" that stored
request at high speed. It saves the user from re-typing
everything.

WARNING: Do not expose port 5000 to the public gateway.


============================================================

/!\ For more details email me so that I can add you to the kick-off meeting I
booked on the app on August, 21st.

You might also like