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.

Sign up for GitHub

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

Jump to bottom

Easy way to clone a project #47

Closed
azeey opened this issue May 23, 2014 · 11 comments
Closed

Easy way to clone a project #47

azeey opened this issue May 23, 2014 · 11 comments
Assignees
@kecso
Labels
Backlog New feature Suggestion UX/UI

Comments

@azeey
Copy link

azeey commented May 23, 2014

This would be useful for testing plugins. The only way to do this right now seems to be to export the project and import it again.
@volgy
Copy link
Member

volgy commented Mar 31, 2015

It would be great, if this could be used/triggered from a properly formatted URL ('Try' link)

@lattmann lattmann added this to the v0.9.0 milestone Mar 31, 2015
@ksmyth
Copy link
Contributor

ksmyth commented Mar 31, 2015

I have a service to copy a project:
https://gist.github.com/ksmyth/e119642ce02d15575f37

@kecso
Copy link
Member

kecso commented Apr 1, 2015

I have created two short specifications for proposed functionalities:
https://github.com/webgme/webgme/wiki/specSeedProject
https://github.com/webgme/webgme/wiki/specFork

@lattmann
Copy link
Contributor

lattmann commented Apr 1, 2015

Looks good to me. Made minor changes.

@pmeijer
Copy link
Contributor

pmeijer commented Apr 1, 2015

I think it's implied but just to clarify;

To fork a project the user needs read access to that project and the user forking gets full rights to the new project.

Correct?

@kecso
Copy link
Member

kecso commented Apr 1, 2015

Yes.
Additionally, the user has to have 'create' rights but I think that was stated explicitly.
Should I clarify it in the document?

@ksmyth
Copy link
Contributor

ksmyth commented Apr 1, 2015

specSeedProject/Parameters: for performance, I'd add a "squash" parameter. true => branches have 1 commit and lose other history

@kecso
Copy link
Member

kecso commented Apr 1, 2015

In the seedProject service we do not have a history.

did you mean fork?
would you like to completely erase the history?

I am asking as I got confused trying to specify your request.
thanks

@volgy
Copy link
Member

volgy commented Apr 1, 2015

Can't we merge these two "services"? Sorry, I do not see the fundamental difference.

@kecso
Copy link
Member

kecso commented Apr 1, 2015

In the fork you copy the whole project while in the seed, you just create a new one with a single branch from a snapshot.
Fork can be done solely with mongoDB queries, while the seed needs the interpretation of the data model (or the serialized format).
I would even add, that in the 'distant' future we might want to allow the fork to be a 'living' connection among projects letting to user to easily synchronize or even to add changes to the original project (as in case of Git).

kecso added a commit that referenced this issue Apr 3, 2015
@kecso
#47 adding temporary test file for measuring the quickest way for com…
24565e1 
…plete collection cloning
kecso added a commit that referenced this issue Apr 3, 2015
@kecso
#47 first we rearrange REST - now it moved to different module
82e49f1
kecso added a commit that referenced this issue Apr 3, 2015
@kecso
#47 server worker manager have been moved to standalone so it can be …
9ff9ced 
…used in the rest also
kecso added a commit that referenced this issue Apr 3, 2015
@kecso
#47 draft implementation of the service is complete - needs support f…
beb4ad1 
…or client API and tests
kecso added a commit that referenced this issue Apr 4, 2015
@kecso
#47 fixing during first tests - now it seems functioning
d5fb25e
pmeijer pushed a commit that referenced this issue Apr 4, 2015
#47 One middlewareOpts passed to all createExpress*.
0a869d7 
Executor ported to this format. And REST slightly modified to fit too.
pmeijer pushed a commit that referenced this issue Apr 5, 2015
#47 Fix executor bug (log better for node-workers).
aa8bd75
kecso added a commit that referenced this issue Apr 6, 2015
@kecso
#47 client side API extension regarding seed project functionality
7847d94
kecso added a commit that referenced this issue Apr 6, 2015
@kecso
#47 correcting review findings
483bd02
kecso added a commit that referenced this issue Apr 6, 2015
@kecso
#47 corrections of bugs found with manual tests of client API
3e1ead8
lattmann pushed a commit that referenced this issue Apr 6, 2015
#47 first version of listing seed projects.
1dd9fa0
lattmann pushed a commit that referenced this issue Apr 6, 2015
#47 Rename base001 to EmptyProject
8ae8e6a
lattmann pushed a commit that referenced this issue Apr 7, 2015
#47 add ActivePanels and SignalFlowSystem seed projects.
a399b21
kecso added a commit that referenced this issue Apr 7, 2015
@kecso
#47 correcting default behavior to clone master branch
048bfab
lattmann pushed a commit that referenced this issue Apr 7, 2015
#47 #109 #73 get full project list, if ProjectNavigator does not have…
38e8bb7 
… the project.
kecso added a commit that referenced this issue Apr 7, 2015
@kecso
#47 -small fix for open context
ab34534
@kecso kecso mentioned this issue Apr 7, 2015
Merged
lattmann pushed a commit that referenced this issue Apr 7, 2015
#47 remove createBasicProjectSeed use seedProjectAsync instead.
5322e31
pmeijer pushed a commit that referenced this issue Apr 7, 2015
Merge 47_seed_project partial #47
1b12762 
Conflicts:
	src/common/util/opencontext.js
	src/server/standalone.js
lattmann pushed a commit that referenced this issue Apr 9, 2015
#47 add support for listing branches for projects with commit hash.
f0c869f
kecso added a commit that referenced this issue Apr 9, 2015
@kecso
#47 correct parameter naming according to specification
10cdae7
kecso added a commit that referenced this issue Apr 9, 2015
@kecso
#47 creating tests for the client API calls of projectSeed
b885d2b
kecso added a commit that referenced this issue Apr 10, 2015
@kecso
#47 extending failure tests and fix functionality
de77bc4
kecso added a commit that referenced this issue Apr 10, 2015
@kecso
#47 check if default connection limiting solves random mongo connecti…
ba4eea6 
…on issues
kecso added a commit that referenced this issue Apr 10, 2015
@kecso
#47 reverse the config changes
3a47cba
@pmeijer pmeijer mentioned this issue Apr 10, 2015
Merged
pmeijer pushed a commit that referenced this issue Apr 10, 2015
Merge pull request #319 from webgme/issue/47_seed_project_branches
f15b42d 
Paritally #47 seed project branches
kecso added a commit that referenced this issue Apr 10, 2015
@kecso
#47 clearing testing script, now it seems that above a certain size, …
01c6419 
…the dump+restore clearly wins above the other two
@lattmann lattmann modified the milestones: v0.10.0, v0.9.0 Apr 13, 2015
@lattmann
Copy link
Contributor

Patrially resolved in v0.9.0 release.

@lattmann lattmann removed this from the v0.10.0 milestone May 8, 2015
@pmeijer pmeijer closed this as completed Sep 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kecso kecso

Labels
Backlog New feature Suggestion UX/UI
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@azeey @ksmyth @volgy @lattmann @kecso @pmeijer