You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way the server configuration is currently set, we have a single server that runs the database, static file server, and WSGI for Django. Eventually, we'll want the database in a different server, and multiple servers serving our content, with a load balancer to balance load across our servers. We need to figure out how to have multiple databases.
One interesting idea I got from talking to Michael Zhang from EasyCTF is to have a separate API through /api that is accessed through jQuery, allowing us to separate the dynamic and static servers. This way, if the Django code crashed, we could still host our static content.
The text was updated successfully, but these errors were encountered:
The way the server configuration is currently set, we have a single server that runs the database, static file server, and WSGI for Django. Eventually, we'll want the database in a different server, and multiple servers serving our content, with a load balancer to balance load across our servers. We need to figure out how to have multiple databases.
One interesting idea I got from talking to Michael Zhang from EasyCTF is to have a separate API through /api that is accessed through jQuery, allowing us to separate the dynamic and static servers. This way, if the Django code crashed, we could still host our static content.
The text was updated successfully, but these errors were encountered: