#project deployment

How to deploy laravel project from git to shared hosting server ?

If you’ve worked in IT for a time, you've possibly been involved with some project work. Whether it’s a software deployment or possibly a hardware upgrade, there comes a time in a project where after all the arranging the solution is deployed to the company for mainstream use. I actually enjoy working on these deployments! The single thing these kind of projects have in common is that the deployment and implementation of these are usually done beyond business hours. This happens so it has minimal effect on the users. I’ve been involved with many project deployments within the last couple of years, and I’ve come to discover that I actually enjoy them. Yes, it’s true, I personally enjoy coming in to work on the end of the week to deploy something to a company. No, I’m not crazy - here’s why! Months Of Planning And Hard Work Finally Pays Off The deployment of a software or infrastructure project is normally the closing stage of the entire project. An idea was established, months or years in the past, from a business need, an issue with the way the company does something, or an upgrade that has been needed. Lots of planning has gone on to get various teams and individuals involved with the project, to obtain the budget for the project planned and approved, and to organise the process to get from one point to another. Prior to the deployment weekend (maybe it's a single night, but the concepts are the same) there is a lot of planning that happens. The desired people are contacted, the individual steps and times are prepared and decision points are made. After many months of planning, the project team all comes together and implements the solution. Getting work done in this environment at this time actually causes you to recognise that all those months of planning and work are finally paying off. The organization will ultimately reap the benefits of the implementation. This might be installing some new routers in the network system, a deployment of a new operating system to a company, or the upgrade of a custom software system. That’s one of the reasons I enjoy software deployment weekends. There Is A Good Feeling Of Teamwork Once the project team comes together to operate on the weekend, or through the deployment window, everybody has agreed to achieve a good outcome. They have all been involved in the project at some level or another. Dependant upon the company and the type of project, some individuals could be working remotely, or you may all be positioned in the one office. Sure, there are many other things that you'd like to do at night time or on a weekend - seeing friends or family, for example. On the other hand, everyone commits to the project and makes the effort to come into work and do their part for the system. Because there's a limited time to get the work done, there's a feeling of motivation and teamwork that is evident within these deployments. It’s something I enjoy and I like getting work done in these environments. There’s no gossip or timewasting - everyone is there to get a job done and done well. Delivering Great Benefits To The Company One more reason I enjoy working on project deployment weekends is recognising the rewards that I’m delivering to the company by doing this work. As I stated earlier, it doesn’t matter what kind of deployment you’re doing for a company, the users will see the rewards of it in one way or another. Many deployments I’ve been involved in are software project deployments. A system is switched off over the weekend, upgrades are made, servers are configured, tests are run and the deployment is concluded. Following this process, the users of the system are available to use the freshly installed software - something which should deliver great benefits to them and the company. The sense of providing value and giving this benefit to this company is a big motivator for me, not merely with the project deployment weekends, but doing work in the IT industry on the whole.