I’m new to BPM’Online and I’m a little fuzzy on some terminology when it comes to setting up developer’s environments. I have read all the PDFs I could find, but have questions.
I have setup a standalone dev/test server with BPM, IIS, SQL, Redis and SVN on it, all working as expected.
I also created a couple of developer’s pc with BPM, IIS, Redis, SQL and SVN client.
My newbie questions:
· I don’t completely understand when to create a workspace vs. just pointing a package to a SVN repository for each developer. Are both needed, what are the use case?
· Should each developer have their own workspace and SVN repository? How are they used together?
· Are workspaces only needed for cloud development? If not, do files get copied or created under a new IIS application folder when a workspace is created?
If anyone can share with me what is working for them in terms of setup or if they have any insights on setup or best practices I would greatly appreciate it. Trying to get things right out of the gate. Screen shots or images of your setup whould be great!
Thanks again.
https://academy.bpmonline.com/documents/technic-sdk/7-8/how-start-development
https://academy.bpmonline.com/documents/technic-sdk/7-8/organizing-development-environment
Like
Dear John,
Since your application is deployed on site, you can go two ways:
Create a second (development) workspace on the same application or use different application(IIS + DB) for each developer.
No matter with way you go, you need to connect the application packages of each developer to the single SVN repository.
In this case, when developing within the same schema, the developer, who started first will be able to commit, however, in case another developer wants to use this schema, it will be blocked while the first one is working.
This will secure you from committing the same schema from two or more developers at once.
After you will be ready, you can upload changed from your developing workspace to the productive workspace.
Therefore, answering your question regarding workspaces: if your developers use separated applications(IIS+DB) then there is no need for workspaces. However, if they are working within one application (e.g. cloud) - workspaces are a good practise to distinguish development from productive environment.