'allo
I'm trying to put together some sort of proposal for tightening up our in-house development environment, mainly for developing and maintaining ASP.Net websites, because the current system we have is no longer any use.
I'm one of two developers here at a small web dev company (which is growing pretty fast), and our current system involves us developing sites locally on our machines, then simply uploading them to our web server. We have no way of centrally managing code or databases. However, this is fine as up until now we've only had our own projects to work on. One major problem with this is the fact that more often than not we're forced to work with live data.
Soon though we're both going to be working on the same projects, and I feel this re-hash of our development environment is necessary. We have an in-house Windows server (which only serves Outlook and Saleslogix) which we use to store source code on (mainly for our PHP sites) but other than that it doesn't really do anything. I would personally like to put it to better use.
So I'm really just after some suggestions on how I can clean this up a bit and get some sort of structure in place. At the moment I'm thinking:
* Using our in-house server to serve websites in development using IIS
* Installing SubVersion on the server for source control (so that we develope the site using our own local copies)
* Installing SQL Server on our in-house server to serve the data. The exact version of SQL Server i'm unsure of - would Express edition suffice?
* When it comes to deploying the site to our live site, simply ftp the site into place on our internet web server. We would also need some sort of SQL Server running on their also, again i'm unsure of which version.
Does anyone have any thoughts and suggestions about this? I would much appreciate the help.
I'm trying to put together some sort of proposal for tightening up our in-house development environment, mainly for developing and maintaining ASP.Net websites, because the current system we have is no longer any use.
I'm one of two developers here at a small web dev company (which is growing pretty fast), and our current system involves us developing sites locally on our machines, then simply uploading them to our web server. We have no way of centrally managing code or databases. However, this is fine as up until now we've only had our own projects to work on. One major problem with this is the fact that more often than not we're forced to work with live data.
Soon though we're both going to be working on the same projects, and I feel this re-hash of our development environment is necessary. We have an in-house Windows server (which only serves Outlook and Saleslogix) which we use to store source code on (mainly for our PHP sites) but other than that it doesn't really do anything. I would personally like to put it to better use.
So I'm really just after some suggestions on how I can clean this up a bit and get some sort of structure in place. At the moment I'm thinking:
* Using our in-house server to serve websites in development using IIS
* Installing SubVersion on the server for source control (so that we develope the site using our own local copies)
* Installing SQL Server on our in-house server to serve the data. The exact version of SQL Server i'm unsure of - would Express edition suffice?
* When it comes to deploying the site to our live site, simply ftp the site into place on our internet web server. We would also need some sort of SQL Server running on their also, again i'm unsure of which version.
Does anyone have any thoughts and suggestions about this? I would much appreciate the help.