From the top of my head, sounds like you could accomplish the same by, say, downloading an image of your application’s data off the central node and mounting it read-only? Then you could still reload/harakiri/... the nodes at will but still ensure that the code hasn’t changed (as long as no one has been able to remount the image rw, etc – but better yet use a file system that doesn’t even allow modifications).
I’ve been reading about Docker’s concepts lately, so that’s probably affecting my train of thought there :) /Aarni From: [email protected] [mailto:[email protected]] On Behalf Of est Sent: Wednesday, August 21, 2013 10:39 AM To: uWSGI developers and users list Subject: [uWSGI] offtopic: How difficult is it to build a sourcefile-less Django cluster in uWSGI? Hello, So this crazy idea came to my mind. Since Django (or any other WSGI project) is running with all modules loaded into memory, after the initial loading the local .py and .pyc source files are, in theory, no longer necessary, assume that we don't ever need to reload/restart the system So, 1. Is it totally safe to delete .py and .pyc files after the WSIG project finished loading in current version of uWSGI? (Assume workers don't have to harakiri or reload) 2. Suppose we need to build a cluster that we only store & distribute source file from a central node (e.g. a subscription server) and slave nodes loads python source files via uwsgi protocol or something, How difficult is could this be? This idea could help strengthen runtime security at clustered nodes and gurantee code integraty. Is my idea bad? Just some crazy speculations, all kinds of criticism is welcome :)
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
