I would like to get this app:
https://github.com/lysol/typeto.me/
running on Heroku (or some similar service).
What steps would I need to follow? I'm having a great deal of trouble understanding what to put where.
I already know I need to do something like this:
Can I run coffeescript in Heroku?
for the coffeescript stuff.
So this is super easy to run on dotCloud.com
Here is a demo I just pushed.
Just clone this fork and push it to dotcloud.
create an account on dotcloud.com
install the cli tool
clone the repo git clone git://github.com/3on/typeto.me.git and cd typeto.me
edit the config file and put right value for "publicHost" typetome-[your dotcloud login].dotcloud.com
create an app dotcloud create typetome
push it to the cloud dotcloud push typetome
And that's it!
Heroku has a great article on deploying node.js apps at their devcenter. It is fairly simple, assuming you use NPM for packages, and git for version control.
You can try this site http://wedeploy.com/ with suport Node, Ruby, MongoDB, and others services. Have simple client to manage your apps.
Related
I'm a new beginner in the express environment and i've one question(i know that it's probably a stupid question): once i've created my own app written in node.js, where can i upload this app?
It sounds like you're basically trying to figure out how to deploy a Node application so you can use it publicly.
Good question.
I think the simplest way (and this is just one of many) is to use Heroku. I'm not affiliated with them at all.
Once you've signed up for Heroku, you can essentially deploy your Node app to their service using just a few command line commands:
$ heroku create
$ git push heroku master
$ heroku open
This will essentially create a new Herkou app, deploy your application there, then open your browser to the newly deployed app page so you can test it out.
Heroku is a hosting provider that lets you deploy apps using Git, and handles all of the dependencies, etc.
I've been searching around the web to see what's the best/simplest way to deploy a meteor app, and have found that Meteor Up has been the easiest way to do this.
However, I've been noticing that this works pretty awesome on small apps, now that one of our apps has grown larger than 250mb, Meteor Up has to build and deploy the whole 250mb app again and again for even the smallest change.
With other node applications we have on digital ocean, a simple git pull does the trick without having to re-upload the entire application.
Is there a way to maintain a meteor application with a github/bitbucket repository?
Thanks!
Well, I have found a solution for this.
Reference: PM2 + Meteor Environment Setup
Using meteor build and following the README that it generates, I was able to run the bundle without using meteor up.
This helps at deploying since it skips the process of uploading the entire bundle to the server, instead, just use git pull in the server to pull your code changes and use meteor build to create the build and run it with pm2.
I have worked on a project and its in my local.
I have used express framework with socket and other packages.
I'm new to this and not sure what deployment options we have.
I see some options like AWS, Heroku and etc.
Heroku looks simple.. but at one of the step they are asking to publish to git and clone from there..
I was wondering why do we need to publish to git to deploy it to production.
Currently I have my app in my machine and I run usually by node app.js.
I'm not using any data bases. Can any one guide me how do I go about it?
I'm running a NodeJS app on Openshift using Jenkins for building deployments (and I'm pretty new to both Node and cloud-based servers). My app depends on a package that has a binary component, so I can't just check it into git - it fails when it's executed on the server. I'm wondering what's the best way to deploy these sorts of dependencies. I see that there is an $OPENSHIFT_DEPENDENCIES_DIR (as well as $OPENSHIFT_BUILD_DEPENDENCIES_DIR), but I can't find any information about how (or if) these can be utilized for node modules. It would be great if I could keep all my dependencies on the server and out of my source tree.
Thanks!
Update: I forgot to mention that I need to apply a patch to the package in question, which is why I can't just rely on it being auto-installed via package.json. Plus, it seems awfully redundant/slow to rebuild all your dependencies on every deployment.
I'm also new to nodejs. I've been playing with nodeJs for about 6 months from now. As for my personal experience nodejitsu is the best cloud-hosting service for nodejs. As I said so due to the following reasons.
You can simply install jitsu command line in your terminal
Your app can be deployed with all the dependencies and databases using the package.json file
They support all the types of sockets either
A very good alternative for jitsu is heroku But sometimes heroku fails with Socket.IO and stuff.
I have a build process involving templating and file copying, which produces what I would like to deploy to Heroku.
But Heroku requires to push your source from a git repository.
What I currently see as my only option is to have a separate git repository, that only holds my build history.
My project is a NodeJS server application.
Is there a better approach?
Thanks.
I have create a grunt-init project template that simplifies the develop-build-deploy cycle of NodeJS server apps deployed on Heroku.
Here it is: https://github.com/nicroto/grunt-init-heroku
This will allow you to have a single repository for your server & client apps, AND do actual build work.
I am basically creating an ignored by git build dir, which I synch-up with your Heroku app. And of course scaffold the project with sample init, build and deploy scripts.
I hope this will be helpful to the community. :)