Ok, so this is the scenario. We are about to insource one of our webapplications, however, my companys it-policies are very strict, so I'm not quite sure how to maintain the app after insourcing.
Setup:
- The server is Win2k3, the app is ASP/ASP.NET and all my machines are Windows.
- The intranet proxy only allows 80 and 443 traffic. All traffic _must_ go through the proxy.
- I may be allowed RDP access from the intranet to the server, but nothing else.
- The server is to be exposed only to internet. All server management is through either a VMWare Console (it's a VM) or through a KVMIP (if we make it a physical server).
- I can open everything I want on the server for incoming, but to access it I then need to be off the intranet and on a "clean" internet hookup.
I have no idea how to manage this server. I have been thinking about using an external service such as GitHub. And adding some sort of automatic update so that if I commit to a certain branch it automagically gets downloaded to the server and set in production.
I guess I could also use dropbox... Or some kind of webdav system?
Any suggestions?
(EDIT: Changed title. Old title: Strict company policies vs workflow)
