Advice on new git / deployment workflow
I work with a small team that until recently didn’t use source control. I’m working on the layout of our development/deployment workflow with git. I would appreciate and advice or insight you might have.
Advice on new git / deployment workflow
I work with a small team that until recently didn’t use source control. I’m working on the layout of our development/deployment workflow with git. I would appreciate and advice or insight you might have.
Advice on new git / deployment workflow
I work with a small team that until recently didn’t use source control. I’m working on the layout of our development/deployment workflow with git. I would appreciate and advice or insight you might have.
Advice on new git / deployment workflow
I work with a small team that until recently didn’t use source control. I’m working on the layout of our development/deployment workflow with git. I would appreciate and advice or insight you might have.
Data Storage patterns for intermediate saving a web-based workflow form
Background: I am developing a wizard based web form where users can log in an fill in some details and press next and previous to go back and forth in the wizard before they actually submit. When the user submits I would make a service call that performs some processing on the data.
Data Storage patterns for intermediate saving a web-based workflow form
Background: I am developing a wizard based web form where users can log in an fill in some details and press next and previous to go back and forth in the wizard before they actually submit. When the user submits I would make a service call that performs some processing on the data.
Data Storage patterns for intermediate saving a web-based workflow form
Background: I am developing a wizard based web form where users can log in an fill in some details and press next and previous to go back and forth in the wizard before they actually submit. When the user submits I would make a service call that performs some processing on the data.
Data Storage patterns for intermediate saving a web-based workflow form
Background: I am developing a wizard based web form where users can log in an fill in some details and press next and previous to go back and forth in the wizard before they actually submit. When the user submits I would make a service call that performs some processing on the data.
Data Storage patterns for intermediate saving a web-based workflow form
Background: I am developing a wizard based web form where users can log in an fill in some details and press next and previous to go back and forth in the wizard before they actually submit. When the user submits I would make a service call that performs some processing on the data.
Samba/git Workflow too complicated
I’m a lead developer for a small company and I’ve recently came across a way to implement version control (git) on our workflow because the company is growing. In terms of infrastructure we have a couple of “production” servers, a development(accessible over the internet) server and an internal development server with internet access but blocked by a hardware firewall. Our current workflow consists of: