Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

anchan42's avatar

Deployment loop

Hi All,

I am developing and web app for internal use only. The app will be deployed on our local server without exposure to the outside world. It will be available on the company's network only.

I think the first deployment should not be a problem. I can bodge it through and get it working. However, I need something more systematic for the long-term continuous development/deployment of the app. Are there any best practices to go about that? I have got the Git repository set up on a shared drive and will be using that as a source control. It can and should be used for deployment too, but not sure how. I read somewhere about staging server, but not sure what it means or how to set it up.

Could you guys point me in the right direction, please?

0 likes
5 replies
Tray2's avatar

I would use github and github actions to deploy

anchan42's avatar

@Tray2 I'm not sure they will allow to have to code on github. Are there anything similar I can set up locally?

Snapey's avatar

depends on what type of server it is

although this site is for SiteGround you will get some ideas by reading through the steps https://laravelsharedhosting.novate.co.uk/

A staging server should mimic production as close as possible. You deploy there first and maybe use it for User Acceptance Testing (UAT) before putting the changes live.

1 like

Please or to participate in this conversation.