Making webpy framework accessible from outside the local network Post: 302879728

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Making webpy framework accessible from outside the local network Post 302879728 by frad on Saturday 14th of December 2013 10:02:26 AM

12-14-2013

Registered User

Making webpy framework accessible from outside the local network

I am using ubuntu 12.04.03. I have some basic experience with webpy and I had it working for my LAN just by following the tutorial. The framework needs to be able to be used from outside the local network. I have difficulty seeing how to make the framework accessible from outside the lan. I tried opening a specific port (with "# iptables -A INPUT -p tcp -d 0/0 -s 0/0 --dport 8081 -j ACCEPT" then I check: "# netstat -ln | grep 8081 and I get: tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN" ) and use "python web_py_test.py MY_IP:8081" without success.

If I understand it at all, we can have a computer connected on a wifi with a non-static IP and there is a way to launch our webpy framework which can be accessible from the outside world. I am experimenting with the hello script:

Code:

import web

urls = (
    '/(.*)', 'hello'
)
app = web.application(urls, globals())

class hello:
    def GET(self, name):
        if not name:
            name = 'World'
        return 'Hello, ' + name + '!'

if __name__ == "__main__":
    app.run()
~

I observe that nothing is declared in the script about IPs or ports.

Last edited by frad; 12-14-2013 at 11:04 AM.. Reason: browser crashed

frad

View Public Profile for frad

Find all posts by frad

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...

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. ...

LEARN ABOUT DEBIAN

plack::runner

Plack::Runner(3pm)					User Contributed Perl Documentation					Plack::Runner(3pm)

NAME

       Plack::Runner - plackup core

SYNOPSIS

	 # Your bootstrap script
	 use Plack::Runner;
	 my $app = sub { ... };

	 my $runner = Plack::Runner->new;
	 $runner->parse_options(@ARGV);
	 $runner->run($app);

DESCRIPTION

       Plack::Runner is the core of plackup runner script. You can create your own frontend to run your application or framework, munge command
       line options and pass that to "run" method of this class.

       "run" method does exactly the same thing as the plackup script does, but one notable addition is that you can pass a PSGI application code
       reference directly to the method, rather than via ".psgi" file path or with "-e" switch. This would be useful if you want to make an
       installable PSGI application.

       Also, when "-h" or "--help" switch is passed, the usage text is automatically extracted from your own script using Pod::Usage.

NOTES

       Do not directly call this module from your ".psgi", since that makes your PSGI application unnecessarily depend on plackup and won't run
       other backends like Plack::Handler::Apache2 or mod_psgi.

       If you really want to make your ".psgi" runnable as a standalone script, you can do this:

	 my $app = sub { ... };

	 unless (caller) {
	     require Plack::Runner;
	     my $runner = Plack::Runner->new;
	     $runner->parse_options(@ARGV);
	     return $runner->run($app);
	 }

	 return $app;

       WARNING: this section used to recommend "if (__FILE__ eq $0)" but it's known to be broken since Plack 0.9971, since $0 is now always set to
       the .psgi file path even when you run it from plackup.

SEE ALSO

       plackup

perl v5.14.2							    2012-03-21							Plack::Runner(3pm)