Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 51AE6200B8B for ; Tue, 4 Oct 2016 17:28:32 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 503AC160ACC; Tue, 4 Oct 2016 15:28:32 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4830B160AC7 for ; Tue, 4 Oct 2016 17:28:31 +0200 (CEST) Received: (qmail 44007 invoked by uid 500); 4 Oct 2016 15:28:30 -0000 Mailing-List: contact user-help@predictionio.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@predictionio.incubator.apache.org Delivered-To: mailing list user@predictionio.incubator.apache.org Received: (qmail 43997 invoked by uid 99); 4 Oct 2016 15:28:30 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Oct 2016 15:28:30 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 128D5CCCD6 for ; Tue, 4 Oct 2016 15:28:30 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.898 X-Spam-Level: * X-Spam-Status: No, score=1.898 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=heroku.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id dGwR758h9MUL for ; Tue, 4 Oct 2016 15:28:25 +0000 (UTC) Received: from mail-pf0-f176.google.com (mail-pf0-f176.google.com [209.85.192.176]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 1F4865FBC2 for ; Tue, 4 Oct 2016 15:28:25 +0000 (UTC) Received: by mail-pf0-f176.google.com with SMTP id i85so25556492pfa.3 for ; Tue, 04 Oct 2016 08:28:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heroku.com; s=google; h=from:message-id:mime-version:subject:date:references:to:in-reply-to; bh=LEpMWFf16TgBPQ5raYVInE+ComKjog5sYKRDBv6HgBs=; b=4Jt0izUBrQuXHWs2FhHkkdIfIQlaT73pmMJLwvxAg4WX7SRP9RQU3Q0LUmhylksbkM wAcnN5XoSc+KsBfY/POn3nuVdoVx2zU6dxTSi3jPurpVekGU32447yJ2l45DyBkDZarR m+O/Sxju0nJ5JRum37I9eZnzQrBv4jSvZysXLH/uf/bqMkv/4JxKeZlJ6z6CAVdupwvD qj7RukPFc4AhdslL5NayQX1V4t7mnbneiNK+1bHi2z8HirMB1vXYZUlcfwxBhj6fFvLS KsvuofjQjfKbuKSbw4+ItpyR90dNoeFq/p5fvgbI1jj6sHwycCIZCdHwqviTNbnkIbI2 dTiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :references:to:in-reply-to; bh=LEpMWFf16TgBPQ5raYVInE+ComKjog5sYKRDBv6HgBs=; b=AJyqB17aBs4Jgfk/FY73fPMwFnFOZxsbyljBXuFaJNHFiE8hnm8bG6lmK+nI9lD34H 9MQ3/fJOqxiuZiOAkyzOrf6BEN4pepg4hTibGW65iQaDlUCqoiX6jBmEWSpNkNBvEo/R iuiWmw09NlfcfRGPAMgWB+1R268fZ74xeolmrRA8KsACn7OxE76oDGz3a1rXLemTXLpd 8g6Vmk4FMQgqHZ35z9MrwDXgtK+rvHfcxKkZqwbbXbzkC+IpR73mSOW0XbSJRf96Azfg aVi5M2bEkOuK+UbdpEXGjOATC81UjBeDnhTWj37Fj74u6+4Oh9+z9ID0GkY4XsPe6vzw qILQ== X-Gm-Message-State: AA6/9RlYaSu1+rBDFoSyPOOtUpeDsvscHc4apUmfnqT0Y3wgtOqYEk/u6JBVob4XbYqsg0yJ X-Received: by 10.98.77.2 with SMTP id a2mr6899819pfb.138.1475594903585; Tue, 04 Oct 2016 08:28:23 -0700 (PDT) Received: from [10.0.1.17] (c-50-174-42-77.hsd1.ca.comcast.net. [50.174.42.77]) by smtp.gmail.com with ESMTPSA id m82sm56118350pfk.64.2016.10.04.08.28.22 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 04 Oct 2016 08:28:23 -0700 (PDT) From: Mars Hall Content-Type: multipart/alternative; boundary="Apple-Mail=_D906C692-AECE-49E2-98F7-9E34CD76D81D" Message-Id: <8B87D528-AD20-4E5C-AC76-58C86E4E1C69@heroku.com> Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Running predictionIO on a web server other than localhost Date: Tue, 4 Oct 2016 08:28:22 -0700 References: To: user@predictionio.incubator.apache.org In-Reply-To: X-Mailer: Apple Mail (2.3124) archived-at: Tue, 04 Oct 2016 15:28:32 -0000 --Apple-Mail=_D906C692-AECE-49E2-98F7-9E34CD76D81D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Jenna, Today at Dreamforce (the Salesforce conference) we're presenting this = PredictionIO Heroku buildpack in a developer session called "Exploring = Machine Learning on Heroku": https://github.com/heroku/predictionio-buildpack = The README is a tailored guide to getting an attribute-based classifier = running. To use the buildpack for engines of your own choosing, follow = the more generalized (and more complex) CUSTOM docs: https://github.com/heroku/predictionio-buildpack/blob/master/CUSTOM.md = If you decide to try it out, please post Github issues with questions, = problems, or feedback! *Mars Hall Customer Facing Architect Salesforce App Cloud / Heroku San Francisco, California On Tue, Oct 4, 2016 at 05:34 Sunny > wrote: Hello Jenna, Deployment in local is fine if you are running lightweight jobs and = using it just for hands-on and learning purpose, no need to bear extra = cost of the additional computing power of cloud services. In case you are into heavy weight research work or running a production = system and wants it to be accessible from around the globe, private or = hybrid or using available cloud services like AWS is must. -- Tapo On Tue, 4 Oct 2016 at 06:23 Jenna Kwon > wrote: Dear Mr. Szeto, Thank you so much for your reply. I saw some posts demonstrating = deployment of event server & engine via Heroku. I also saw that there = used to be deployment through AWS. In what case would I want to do that = instead of keeping them local? Best Regards, Jenna Kwon=20 On Mon, Oct 3, 2016 at 5:45 PM, Donald Szeto > wrote: Hi Jenna, You probably want to have a reverse proxy in front of your app = (localhost:3000) so that it is exposed to the Internet via standard = ports (80 for HTTP or 443 for HTTPS). Your app can communicate to the = event server and engine over localhost. They don't need to be exposed to = the Internet. Your app should be using one of PredictionIO SDKs to = interact with the event server and engine. Regards, Donald On Sun, Oct 2, 2016 at 3:07 PM, Jenna Kwon > wrote: Hello! I am a beginner so please excuse me if my question is rudimentary. I've followed a demo for Tapster Comics Recommendation = (http://predictionio.incubator.apache.org/demo/tapster/ = ) and have a = good understanding of deploying the engine, app and event server on = localhost. My app ran on localhost:3000, engine ran on localhost:8000, and = eventserver ran on localhost:7000. I would like to now deploy these on a web server. The "app" would be a = specific website. How would I hook up and deploy eventserver and = predictionIO engine to gather information from that specific website?=20 Would it just be a matter of changing environmental variables in = pio-env.sh (in predictionIO installation directory) as well as those in = app's directory? For example, would I substitute "localhost" with a web = server?=20 Thank you! Best Regards, Jenna Kwon=20 --=20 Jenna Kwon B.S. Computer Science '17| Georgia Institute of Technology=20 Denning Technology and Management Scholar=20 GT Tennis Club | GT Trailblazers www.jennakwon.com (541)908-2963 --=20 Jenna Kwon B.S. Computer Science '17| Georgia Institute of Technology=20 Denning Technology and Management Scholar=20 GT Tennis Club | GT Trailblazers www.jennakwon.com (541)908-2963 --Apple-Mail=_D906C692-AECE-49E2-98F7-9E34CD76D81D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi Jenna,

Today at Dreamforce = (the Salesforce conference) we're presenting this PredictionIO Heroku = buildpack in a developer session called "Exploring Machine Learning on = Heroku":

https://github.com/heroku/predictionio-buildpack

The README is a tailored guide to getting an = attribute-based classifier running. To use the buildpack for engines of = your own choosing, follow the more generalized (and more complex) CUSTOM = docs:

https://github.com/heroku/predictionio-buildpack/blob/master/CU= STOM.md

If you decide to try it out, = please post Github issues with questions, problems, or feedback!

*Mars Hall
Customer Facing Architect
Salesforce App = Cloud / Heroku
San Francisco, California


On Tue, Oct 4, 2016 at = 05:34 Sunny <sunnystarin@gmail.com> wrote:
Hello Jenna,

Deployment in local is fine if you are running = lightweight jobs and using it just for hands-on and learning purpose, no = need to bear extra cost of the additional computing power of cloud = services.
In case you are into heavy weight = research work or running a production system and wants it to be = accessible from around the globe, private or hybrid or using available = cloud services like AWS is must.

-- = Tapo

On Tue, 4 Oct 2016 at = 06:23 Jenna Kwon <jinkwon06@gmail.com> = wrote:
Dear Mr. = Szeto,

Thank you so much for your reply. I saw some posts = demonstrating deployment of event server & engine via Heroku. I also = saw that there used to be deployment through AWS. In what case would I = want to do that instead of keeping them local?

Best Regards,
Jenna = Kwon 

On Mon, Oct 3, = 2016 at 5:45 PM, Donald Szeto <donald@apache.org> wrote:
Hi = Jenna,

You probably want to have a reverse proxy in front = of your app (localhost:3000) so that it is exposed to the Internet via = standard ports (80 for HTTP or 443 for HTTPS). Your app can communicate = to the event server and engine over localhost. They don't need to be = exposed to the Internet. Your app should be using one of PredictionIO = SDKs to interact with the event server and engine.

Regards,
Donald



--
Jenna Kwon
B.S. Computer Science '17| Georgia Institute of = Technology 
Denning Technology and = Management Scholar 
GT Tennis Club | GT = Trailblazers
(541)908-2963



= --Apple-Mail=_D906C692-AECE-49E2-98F7-9E34CD76D81D--