Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Making webpy framework accessible from outside the local network Post 302879763 by bakunin on Sunday 15th of December 2013 05:13:45 AM
Old 12-15-2013
I think i should mention that i do not know this "webpy framework", but i am pretty seasoned in networking. So, please bear with me when my questions are sometimes asking the (for you) obvious.

Quote:
Originally Posted by frad
There is no outside network.
As it is, i don't think so. To quote you:

Quote:
Originally Posted by frad
The framework needs to be able to be used from outside the local network.
If this is not an "outside network", what else is it? How is it connected to your "local network"? (I suspect this is the Wifi-box you mentioned, but just to be sure. And do you have routing enabled on this box or does it act as a switch?)

Quote:
Originally Posted by frad
What I want to do is to arrive to the result that everyone (with his own computer, with his own internet connection) will be able to type a specific ip and port on his webrowser and see my webpy framework. The user should be able to enter some variables and launch a calculation (as I am doing locally) that will run on my computer.
OK. First question: with "everyone" you mean "anybody on the internet" (like, for instance, me) or "anyone connected to the box i spoke above" (the Wifi-LAN connection)?

Second question, as i do not know webpy: does one need a browser (or any other software like a terminal emulation, ....) to do so or does it have its own protocol and client/server applications?

I hope this helps.

bakunin
 

2 More Discussions You Might Find Interesting

1. IP Networking

ssh server is attachable from local network not from another network

hello i have a ubuntu ssh server that i can acess from any of my comnputers but only if they are on the same wireless network as the server. i tested trhis my tehtehring my samsung blackjack to my windows partition and installing openssh to windows it works when windows is on the wireless but no... (1 Reply)
Discussion started by: old noob
1 Replies

2. Infrastructure Monitoring

SF4800 SC not accessible thru network

Hi All, I have my SC setup as attached below but I am having problem accessing the port thru network. sc0 was accessible only after i failed over the configuratios to sc1 (now then sc1 was not pingable :(). Just wondering is there anything wrong with my sc settings? Appreciate your advice. ... (4 Replies)
Discussion started by: honmin
4 Replies
SHELL-QUOTE(1p) 					User Contributed Perl Documentation					   SHELL-QUOTE(1p)

NAME
shell-quote - quote arguments for safe use, unmodified in a shell command SYNOPSIS
shell-quote [switch]... arg... DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands or files with embedded white space or shell globbing characters safely. Here are a few examples. EXAMPLES
ssh preserving args When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and passes them to "$SHELL -c". This doesn't work as intended: ssh host touch 'hi there' # fails It creates 2 files, hi and there. Instead, do this: cmd=`shell-quote touch 'hi there'` ssh host "$cmd" This gives you just 1 file, hi there. process find output It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote: eval set -- `find -type f -print0 | xargs -0 shell-quote --` debug shell scripts shell-quote is better than echo for debugging shell scripts. debug() { [ -z "$debug" ] || shell-quote "debug:" "$@" } With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can. save a command for later shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are things the user can't pass through), you can do something like this: user_switches= while [ $# != 0 ] do case x$1 in x--pass-through) [ $# -gt 1 ] || die "need an argument for $1" user_switches="$user_switches "`shell-quote -- "$2"` shift;; # process other switches esac shift done # later eval "shell-quote some-command $user_switches my args" OPTIONS
--debug Turn debugging on. --help Show the usage message and die. --version Show the version number and exit. AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions. AUTHOR
Roderick Schertler <roderick@argon.org> perl v5.8.4 2005-05-03 SHELL-QUOTE(1p)
All times are GMT -4. The time now is 06:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy