Best practice to be updated?

[rootical]

Maybe for some it is a trivial question but not for me so far.

I like your code style and application setup, as i can see meanjs is being updated regularly.

So could you please tell me, whats the best way to keep my project based on meanjs updated? I can mention a few - but the question is, how would you do it?

[amoshaviv]

Hi @rootical,

This is one of our main concerns for the future major version, since we're really not happy with current solutions.

Currently the best approach would be to clone the repository, then keep it updated using git pull & merge. This means there are certain files that you should avoid modifying(e.g., express.js, config.js, passport.js, etc.).

The challenge is making updates easier without harming the project openness, readability, and flexibility. That is why we're still working on finding the best approach. Until then, using git is the best solution.

Thank you for your patience.
Cheers,
Amos

[naartjie]

This is something I am also very interested in. I have some thoughts on this, which granted, are not very well structured (yet), but maybe pouring some of them out here the community can help ;-)

This project is still in it's infancy and changing rapidly, which is why it's nice to have access to anything and everything right in the root of your project, but I think somewhere down the line, meanjs would be a dependency you add in your node_modules, much like you do with express. With yo, doing the boilerplate for you, which you can then alter. The separation between core framework (in node_modules), and the mean boilerplate/scaffold'ed code in your project root, would make upgrading mean more manageable.

@rootical I think you should mention your thoughts on this as well, and I invite other users to chip in. I think it would be beneficial to get an idea on where everyone is on this.

@amoshaviv @roieki do you guys have any specific plans, directions in mind, or are you just seeing which direction the project will sway?

[naartjie]

PS Would it not be easier to reason about all the logistics if we decouple the A, and think of client and server as separate. Theoretically a user should be able to use any view framework he chooses, much like he should be able to easily swap out the server side templating engines.

PPS Please don't thake this the wrong way, I'm not suggesting the MAN stack :P

[MichaelJCole]

+1 for MEAN as a npm module w/ yoeman for boilerplate.

On Wed, May 7, 2014 at 4:10 AM, Marcin Jekot notifications@github.comwrote:

This is something I am also very interested in. I have some thoughts on
this, which granted, are not very well structured (yet), but maybe pouring
some of them out here the community can help ;-)

This project is still in it's infancy and changing rapidly, which is why
it's nice to have access to anything and everything right in the root of
your project, but I think somewhere down the line, meanjs would be a
dependency you add in your node_modules, much like you do with express.
With yo, doing the boilerplate for you, which you can then alter. The
separation between core framework (in node_modules), and the mean
boilerplate/scaffold'ed code in your project root, would make upgrading
mean more manageable.

@rootical /~https://github.com/rootical I think you should mention your
thoughts on this as well, and I invite other users to chip in. I think it
would be beneficial to get an idea on where everyone is on this.

@amoshaviv /~https://github.com/amoshaviv @roieki/~https://github.com/roiekido you guys have any specific plans, directions in mind, or are you just
seeing which direction the project will sway?

—
Reply to this email directly or view it on GitHub/~https://github.com//issues/50#issuecomment-42404948
.

Michael Cole
http://Powma.com
(512) 333-4372

[MichaelJCole]

Hey, one more thing about this, github doesn't support private forks.

So, I think my options are:

• duplicate repo (no pull requests upstream)
• fork MEAN in a repo for pull requests. Copy changes over (what I'm doing now)
• commit private code to my public fork (not what I want)

Is there some way to do this I'm missing?

EDIT: this might be a way, but it's pretty complicated. http://stackoverflow.com/a/14243407/1483977

[naartjie]

@MichaelJCole I normally have 2 remotes on my projects:

⇒  git remote -v
mean.js git@github.com:meanjs/mean.git (fetch)
mean.js git@github.com:meanjs/mean.git (push)
origin  ssh://git@private-repo/project.git (fetch)
origin  ssh://git@private-repo/project.git (push)

Still, merging is not fun.

[MichaelJCole]

Hey, I wrote a blog post about this: http://blog.powma.com/git-you-some-mean-js-setup-advanced-git/