Thank you for creating this video. Never thought of this at all. Although I can't implement it on a react or node app, I appreciate knowing that something like this can be done.
A few days ago, the first time in my life, I have rent space on this shared hosting provider. I was puzzled because I knew about the deployment process only in theory. But you saved my day. Thank you a lot. You have a new subscriber :)
I did this video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-ebWJbbUT4TA.html , you can do the same thing for Next.js apps or React apps, however, as you will see in this video this approach is far from ideal. It may work better for you, if you have a better hosting, but I would not host node apps on shared hosting just yet.
No problem, however better check this video out, it's much better workflow than what is presented in this video. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-UNWIXYSZfZY.html
I was closely following this tutorial and noticed that when setting up the Git Version Control repository, you chose to create it directly using cPanel's management tools, as opposed to cloning it from an externally hosted Git repository. What if I want to integrate with my private Git repository? What would be the method in that scenario?
Amazing tutorial as always, let me ask can I use this to deploy wordpress sites? And do you know something about wordpress migration database like laravel?
You can of course. However, the database is always going to be a pain point with WP unfortunately. Git is just for files, and you will have to deploy your DB by hand. WP doesn't have migrations. And even if it did, it wouldn't help, because most of the options and configurations are written in database.
I would use it on any size project, using FTP do deploy your site is outdated and also not exactly secure. I think this is much better, if your hosting supports it of course.
i am not getting post-receive inside hooks. i am getting all this --applypatch-msg.sample fsmonitor-watchman.sample pre-applypatch.sample pre-merge-commit.sample pre-push.sample pre-receive.sample commit-msg.sample post-update.sample pre-commit.sample prepare-commit-msg.sample pre-rebase.sample update.sample--- please help anyone
First of all nice tutorial..nice work! I am curious if its possible when to upload on github automatic push and on server..with that example that made i need to add a remote repository of github and push the code..and after another remote repo with ssh for server. so i need to push second time to server.. can i make one push to github and github push automatic to ssh repo server?? thanks, happy coding!
Not sure if it's exactly what you need, but take a look at this episode: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-UNWIXYSZfZY.html here I'm using github actions to deploy to shared hosting, it's a better way then what I did in this video. So maybe you can use that to acomplish what you need.
@@WatchandLearnTutorials i check your video..thats better solution for me! but you sync file with ftp and package SamKirkland / FTP-Deploy-Action. it is posible to sync with something else? like ssh?
@@gt-tech For my site I used this guide: itnext.io/deploy-next-js-apps-using-github-actions-6322261757bc but I'm deploying it to Digital Ocean so I can install whatever I need, which may not be the case for shared hosting. And this is going through ssh and git. So essentially whenever I publish something to master, the server does git pull of the new version. So there is no need for FTP.
@@WatchandLearnTutorials thats better but its only for frontend frameworks javascript? or its possible to use for backend php frameworks? nothing change digital ocean or other provider! all its VMs so its the same! what OS do you have at yor vm and use that guide? Thank for help!
HELP!? thanks for your great tutorial. I am running into a problem. i have two branches... master/dev. dev controls dev.mysite.com and master controls prod.mysite.com. my branches are clean and committed before i perform any checkouts.... yet when i push a committed change on the DEV i often get "failed to push some refs"... "working directory has unstaged changes"... yet it GIT STATUS says my working tree is clean... do you have any idea or tips (or a video) on how to work clean between both branches on the same git repo? its great to be able to have different files controlled in the same repo. I'm fairly new to git... thank you so much
@@TheReisners I don't know, sorry. This video is just to show that something like this can be done, but I found out that Git on shared hosting, and running node.js apps on shared hosting have problems. So I would advise to use something like Github and Github actions for this. I will try to make a video about it.
@@WatchandLearnTutorials Buddy, first of all, when I create git repo in GIT Version Control in cpanel , my git repo shows an error "System could not found any branch in your repository". 2nd issue is , I can clone remote repo but whenever I try to push to remote server nothing happen. By Nothing, I mean no prompt for username and password appear. Solve my issues please???
@@kv_clips I would suggest that you ignore this video and try to make a setup like in this video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-UNWIXYSZfZY.html it solves the same problem, but in much nicer and more elegant way. Also, here you should not have any trouble with git, because your repo will be hosted on GitHub. Git on shared hosting can be pain in the a** as you can see for yourself, somewhere it works, somewhere it doesn't it all depends on the hosting.
Great tutorial! You showed how to do this if you have a simple website hosted on the main domain (on a VPS). But how you suggest dealing with a website that already has multiple subdomains? I have 8 subdomains (for different aspects of the business) and each one requires a staging and dev environment, but I don't want to do crm.staging.domain(dot)com for each subdomain. Each subdomain also requires direct access to the server's SQL database, so the staging sites can't(?) be on a separate server/domain (Correct me if I am wrong). What are your thoughts (or anyones' thoughts) on how you would get around this?
Well first of all if your staging and other sites are on subdomains, they can also be on the same server, so that means that they would be able to access the DB without a problem. Even if they are on separate server, you can still access the DB, you just have to allow access to the port of the DB. Usually that is 3306 I think, or something like that. Also you need to have multiple subdomains for staging servers, I don't know how you would get around that. Now since you are dealing with a lot of sites and subdomains, you would really need a dev ops guy or girl to setup everything right. This is not a trivial functionality that you are looking for. And also I don't think this should be done on a shared hosting, using some VPS platform or something like AWS or Digital Ocean would be much better for that. Also you can take a look at this video ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-UNWIXYSZfZY.html , it's an updated version of this one, so that may also give you some ideas on how to handle this.
