Open adamsoffer opened 8 years ago
I've been neglecting deploy because this is still very much in flux. We're not quite ready to start actively supporting deploy, but if you'd like to take a first stab, that would be great.
We'll be happy to help you figure out out, but we'll need a bit more to go on than "struggling to deploy" to even know where to begin to address the issues. =)
Can you report the errors you're encountering, OS, Node & npm versions, etc..?
Thanks so much for offering to help. Very kind. I actually finally got it working on AWS Elastic Beanstalk. I think the issue was that the port number was defaulting to 3000 because process.env.APP_PORT wasn't being set and AWS EB didn't like that.
Totally understand putting off deploy instructions until the end. Very much looking forward to your book!!
Makes sense. =)
Thanks. Working on a radical simplification of this boilerplate as we speak...
Awesome can't wait :0)
Let me know if you'd like some help with that simplification you mentioned you were working on - would love to see what you have in store :)
p.s. I forked this repo a month ago and it's done wonders for my workflow. Thanks a million. Simplest/cleanest universal react boilerplate out there IMO.
Thanks... the simplification I'm talking about is the react-easy-universal library, which is not yet production ready, but getting close...
I'm not the greatest at devops and I'm struggling to deploy this build to both Heroku and AWS. It would be nice if the docs included a simple set of deployment instructions.