Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs for deploying to digital ocean would be appreciated #541

Open
rickbrunstedt opened this issue Nov 13, 2015 · 8 comments
Open

docs for deploying to digital ocean would be appreciated #541

rickbrunstedt opened this issue Nov 13, 2015 · 8 comments

Comments

@rickbrunstedt
Copy link

I have quite hard to figure out how to deploy to digital ocean. Atm I git clone in the digital ocean machine every time. But that isn't very efficient.

@quicksnap
Copy link
Collaborator

I think we would consider a PR for some deployment instructions, but IMO it may be out of scope for this project.

Various platform deployments can differ significantly. It'd be tough to maintain that.

@justingreenberg
Copy link
Contributor

@quicksnap i agree vendor-specific deployment instructions are outside the scope of this project... the heroku instructions are really just incidental to erik's live example

@erikras
Copy link
Owner

erikras commented Nov 15, 2015

That said, if someone wanted to submit a docs/deployment/DigitialOcean.md, it wouldn't hurt anything. But it's not a support role that any of the project's primary contributors need concern themselves with. It would be nice, however, if as people figured out how to deploy to different platforms, they wanted to give back a little about their adventure to lubricate the path for subsequent travelers. Perhaps such a call to action in the readme would be beneficial.

@whatifif
Copy link

@erikras
I have some trouble in deploying this app to Heroku, which you already succeeded as clearly seen in demo of this app. It would be great help if there is a document about how to deploy to Heroku.

Thanks for sharing this great work.

@erikras
Copy link
Owner

erikras commented Nov 17, 2015

@whatifif Like this?

@whatifif
Copy link

I followed the procedure as mentioned in doc:

To get this project to work on Heroku, you need to:
Remove the "PORT": 8080 line from the betterScripts / start-prod section of package.json.
heroku config:set NODE_ENV=production
heroku config:set NODE_PATH=./src
heroku config:set NPM_CONFIG_PRODUCTION=false
This is to enable webpack to run the build on deploy.
The first deploy might take a while, but after that your node_modules dir should be cached.

But still there is error:
/app/node_modules/babel/node_modules/babel-core/lib/polyfill.js:8
2015-11-18T04:47:22.761132+00:00 app[web.1]: [0] throw new Error("only one instance of babel/polyfill is allowed");

Heroku branch sends same error as above.

@whatifif
Copy link

I successfully launched the Heroku branch by commenting out the "require('babel/polyfill');" in "src/config.js (line 1)" and keeping "require('babel/polyfill');" in "src/client.js" (line 4).

@bluematter
Copy link

bluematter commented Nov 27, 2016

I am using git to deploy. So I have a repo on my Digital Ocean instance. I just push code and my work tree is always in sync with my local code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants