Thanks for sharing the play & react integration source codes. I have a few problems on deployment in production mode. Could you consider how to solve the issue of my used case?

• Back-end needs to download some images file from a server.
• Front-end serves the files downloaded.
• It works perfectly on development mode run by sbt run.
• Deployment on production is done by sbt dist, unzip target/universal/xxxx.zip, cd xxx, ./bin/xxx Dplay.http.secret.key=lqkejrnjnjfajsdjfajhsdfhjasdf -Dconfig.file=/home/ubuntu/code/xxx/conf/application.conf -Dhttp.port=8080
• Downloaded files are under xxx/public/images/
• Front-end cannot serve the downloaded images file.
• What I should need to change the config or controller to serve the file under xxx/public/images folder?
  Thank you.

i have version 1 for my application , who the front end files are .scala.html in directory /app/views.
and now i want to use react js for another front end files for my project.
It s is possible?
can i integrate front end file with react (/ui/src/*)
and all run in port 9000 ?

Thanks in advance

I get this error on localhost:3000 when i run "sbt run"

I cloned the repo, localhost:3000 works exactly as intended. But trying to access Play Framework at localhost:9000 returns an Action Not Found Error, the console gives me a 404 Not Found Error.

When I do sbt run, everything runs fine. If I stop the application with Ctrl + C (Windows), the React part keeps running.
Is it possible to shut down both together?

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Hi,

I cloned the project and tried starting it.
When using sbt run, the front-end doesn't start so localhost:3000 doesn't work.
The terminal logs Starting the development server..., but nothing happens after that.

I have to manually start the front-end with npm run start on another terminal for it to work ...

Hello,
First of all thank you very much for React's contribution with Play2. I am studying to integrate into my projects.

By the logic of the website article and the reading that was performed, the project was raised in a development environment using the sbt run command.

When executing this command it internally executes the scripts for React but React does not start correctly, I need to go manually to the /ui folder and execute the npm start command and then it works.

This is normal or just by running the sbt run command it runs all.

The idea is to deploy this application on heroku.

Best regards

• git clone and run sbt build

~/code/java-play-react-seed$ sbt build
[info] Loading settings from plugins.sbt ...
[info] Loading project definition from /home/ubuntu/code/java-play-react-seed/project
[info] Loading settings from build.sbt,ui-build.sbt ...
[info] Set current project to java-play-react-seed (in build file:/home/ubuntu/code/java-play-react-seed/)
[error] Not a valid command: build
[error] Not a valid project ID: build
[error] Expected ':'
[error] Not a valid key: build (similar: loadedBuild, uiProdBuild)
[error] build
[error]      ^
[INFO] [11/20/2018 09:36:58.437] [Thread-2] [CoordinatedShutdown(akka://sbt-web)] Starting coordinated shutdown from JVM shutdown hook