search

coreh-deprecated / nide

Beautiful IDE for Node.js
http://coreh.github.com/nide/
713 stars 111 forks source link

Feature: Add Git Push Support #26

Open chrismatthieu opened 12 years ago

chrismatthieu commented 12 years ago

Hi Coreh,

I'm the founder of nodester. I love your NIDE project and I am thinking about ways in which we could integrate the two projects. If NIDE had git push support, Node.JS developers could deploy/push their updates to Nodester and GitHub without leaving NIDE.

Any thoughts?

Regards, Chris

coreh commented 12 years ago

Hey @chrismatthieu,

Thanks! :-) It would be interesting to see Nide integrated somewhere.

I started working on git support on a separate branch some time ago, but there were many use cases I had to deal with, and I was not entirely confident on the direction I was taking in terms of UX.

What exactly are the use cases you have in mind for the git integration? If it's something simple, say:

The user has a single master branch, predefined remotes (origin for github, deploy for Nodester) and only commits and pushes to those origins.

Then it shouldn't be too much work. But if it's something more complex (i.e. the user can create, delete and switch between branches, (s)he can add and remove remotes, perform merges and rebases, create tags), then things start getting really complicated.

Perhaps providing a console on which users could interface with git manually, and providing a simple UI specific for pre-made deploy scripts would be a better idea?

What do you think?

chrismatthieu commented 12 years ago

Hi Marco,

That is exactly what I had in mind. Node.JS apps are created on Nodester using either our CLI or our REST API (http://nodester.com/api.html#rest). The response returns a git repo address. The user could add the nodester remote to their repo and push updates to nodester via NIDE.

To make things even easier, if the use runs a nodester app init from the CLI after creating the app, we actually create a directory and hello world node.js app and add the origin remote pointing to their nodester app and we launch their app at appname.nodester.com! The next step would be to run nide init and then subsequent git pushes to the default origin master go to nodester!

Here is a video of deploying an app to nodester in 39 seconds: http://nodester.com/help.html

We would LOVE to see simple git add/commit/pushes in NIDE so that we can help you promote your project along with Nodester! Let me know what you think...

Cheers, Chris

On Sat, Dec 31, 2011 at 11:36 AM, Marco Aurlio < reply@reply.github.com

wrote:

Hey @chrismatthieu,

Thanks! :-) It would be interesting to see Nide integrated somewhere.

I started working on git support on a separate branch some time ago, but there were many use cases I had to deal with, and I was not entirely confident on the direction I was taking in terms of UX.

What exactly are the use cases you have in mind for the git integration? If it's something simple, say:

The user has a single master branch, predefined remotes (origin for github, deploy for Nodester) and only commits and pushes to those origins.

Then it shouldn't be too much work. But if it's something more complex (i.e. the user can create, delete and switch between branches, (s)he can add and remove remotes, perform merges and rebases, create tags), then things start getting really complicated.

Perhaps providing a console on which users could interface with git manually, and providing a simple UI specific for pre-made deploy scripts would be a better idea?

What do you think?

Reply to this email directly or view it on GitHub: https://github.com/Coreh/nide/issues/26#issuecomment-3322377

balupton commented 12 years ago

Also really interested in this for DocPad. Will do up a nide plugin for DocPad over the next few days and hopefully get it running on heroku and/or nodester.

The use case is someone deploys their docpad project to a cloud server, they want to edit it in the cloud directly, they edit the files, but they need a way to commit it back to the git repo. If nide can add in git support, that would be amazing. Alternatively, with docpad we could already watch for file changes on the directory and do all the committing ourselves - which is also quite feasible.

What's everyones thoughts? Should nide provide an interface for git? Or should the applications embedding nide handle git?

ghost commented 12 years ago

+1 @balupton this is really a fantastic idea. it would allow it to really work for classical development flows.

i really hope this happens with Node. It has so much potential and the code base is clean too.