Cool, thanks. I have been using putty and winSCP pretty extensively for about a year now - but I won't even need that to access the web2py app files, because I managed to get a samba server up and running...
What I meant by 'accessing the admin app', was that when we have a server-error, we can access the ticket using the web-interface, and figure out what's wrong. Without that, we would have to manually copy-over the ticket (error-file) into a dev windows-based workstation, and use the dev-server running locally - and that becomes tedious pretty fast. It's actually a very common use-case, as most web-server deployments are on minimalist-distributions, and not all feature ssl... I actually would have expexted the prevalance of such a use-case to already be known and accounted for by now... I am in the process of working-out porting the centos-uwsgi shell script into ansible roles, but that's taking a while, and I'm still not sure I wanna ditch gevent just-yet (at least not altogether) Anyways, I'll check that trunc-script, thanks. -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
