CODEWITHSUNDEEP
deploymentplayframework
Joshua Gunder
Joshua Gunder

Reputation: 245

Deploying my first play app, i'm so lost

I've decided to go with Apache as the http server in front of my play app. The server team at my company says they installed Apache and Python and play on the target server. I'm code complete, so here's where I don't know what to do next.

  1. How do i "compile" my play java app?
  2. What folders do I deploy, which ones do I not deploy?
  3. Where on the target server hard drive do I place the webapp I'm deploying?
  4. How do i tell apache where I deployed the play webapp to on the disk?
  5. How do I make it so that apache and play are now always running and don't require I be logged in on the target server?
  6. Yeah I'm new to linux
  7. Please help I'm lost.

Thanks in advance Josh

Upvotes: 2

Views: 274

Answers (1)

emt14
emt14

Reputation: 4896

Read the Preparing for production section before anything else.

How do i "compile" my play java app?

Play does that for you when you laucnh play start. However you can use the play precompile command before starting the app.

What folders do I deploy, which ones do I not deploy?

app, conf and public. You might have some 3rd party lib dir too.

Where on the target server hard drive do I place the webapp I'm deploying?

I don't think it really matters.

How do i tell apache where I deployed the play webapp to on the disk?

Apache act as a reverse proxy (forwards every requests to your app and serves the reponses back to client). For this you need to edit the apache's httpd.conf

How do I make it so that apache and play are now always running and don't require I be logged in on the target server?

You need to start the apps as daemon threads which I think apache does by default. the command play start should run play in the background.

Upvotes: 1

Related Questions