Yes, I understand it's not a web2py problem, I was just wondering if there was a way of achieving that without restarting uwsgi process.
I can see the need of restarting the process that runs the app after updating that app. However, most of the times, the update involves changes to static files (css, some javascript, maybe some images), and I'm forced to restart uwsgi process when the app code hasn't actually changed. Moreover: I'm running a lot of web2py applications (between 40 and 50), and I don't like the idea of restarting the uwsgi process that serves all that apps just because I had to update some css files in just one app. But I understand this is not web2py related, I was just wondering if it would be possible to do it in another way. I will look into Mercurial to see if there is a way of updating just the files that have actually changed, don't know if this would actually work. Another obvious thing to do is avoiding frecuent small updates and, instead, updating the app once in a while with all the changes needed. However in my case this is not possible, because each app correspond to a customer, and sometimes the customer needs the change to be applied inmediately. El miércoles, 17 de junio de 2015, 3:39:07 (UTC-3), Niphlod escribió: > > beside from the fact that is hardly a web2py problem, what the heck ? you > udpate the app and you don't want to reload the process that runs it ? > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
