When we are many working on the same project, to setup a bridge between me and my fellow developers to sync our development on agreed project with various checks and balances.
Expected result
Synced development environment. Like git just much more basic... and inside of JCB.
Actual result
The feature does not exist automatically.
Additional comments
I have developed a similar project to sync databases with each-other, so I have ready an authentication tool, and the basic outline to make this work.
Who would be interested in this kind of feature?
### Steps to reproduce the issue
When we are many working on the same project, to setup a bridge between me and my fellow developers to sync our development on agreed project with various checks and balances.
### Expected result
Synced development environment. Like git just much more basic... and inside of JCB.
### Actual result
The feature does not exist automatically.
### Additional comments
I have developed a similar project to sync databases with each-other, so I have ready an authentication tool, and the basic outline to make this work.
# Who would be interested in this kind of feature?
I would like this, we can use it for JCB itself 👍 it will save us so much trouble if it is automated. The packages manager already does most of the work!
I would like this, we can use it for JCB itself :+1: it will save us so much trouble if it is automated. The packages manager already does most of the work!
I am thinking this is such a huge improvement to JCB and it requires so much work, that I am wondering if we should not make it a paid option.
I have spend so much time on this, it is really very powerful. I think we need to have a chat about this. I mean it only us who responded to this anyway. So why share it?
I am thinking this is such a huge improvement to JCB and it requires so much work, that I am wondering if we should not make it a paid option.
I have spend so much time on this, it is really very powerful. I think we need to have a chat about this. I mean it only us who responded to this anyway. So why share it?
Okay at this time, I am moving this feature out of JCB into its own component. I will keep updating this issue. We are planning to make this available as an addon-component.
Okay at this time, I am moving this feature out of JCB into its own component. I will keep updating this issue. We are planning to make this available as an addon-component.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Steps to reproduce the issue
When we are many working on the same project, to setup a bridge between me and my fellow developers to sync our development on agreed project with various checks and balances.
Expected result
Synced development environment. Like git just much more basic... and inside of JCB.
Actual result
The feature does not exist automatically.
Additional comments
I have developed a similar project to sync databases with each-other, so I have ready an authentication tool, and the basic outline to make this work.
Who would be interested in this kind of feature?
I would like this, we can use it for JCB itself 👍 it will save us so much trouble if it is automated. The packages manager already does most of the work!
I am thinking this is such a huge improvement to JCB and it requires so much work, that I am wondering if we should not make it a paid option.
I have spend so much time on this, it is really very powerful. I think we need to have a chat about this. I mean it only us who responded to this anyway. So why share it?
Hi I know I am little late to the party, but hey I would really like this feature!
Tell me what kind of security is going to be used here?
Okay at this time, I am moving this feature out of JCB into its own component. I will keep updating this issue. We are planning to make this available as an addon-component.
@Tony301 I am working on using our own in-house CA system like a browser. So RSA keys will be used to encrypt the communication.
I am closing this, feature request and placing it on the back burner, for latter.
I think that it's worth paying for this feature. It's a Premium enhancement..
I agree this is a premium feature, hope it is not on the back-burner to long.