Pulling is typically the simpler way to manage deploying code via git (though you'll probably outgrow this idea eventually, opting for something like puppet or chef to manage deployments). It's something you'll need to build yourself, using gitlab as part of the tooling. There are ways to do this with gitlab's CI/CD infrastructure, but because everyone's production is different, there's no one-size-fits-all way to implement it for everyone. I feel I should be able to do it from within GitLab Is this all the right way to be doing things? I feel I should be able to do it from within GitLab, but I couldn't find it and ended up doing something like this on my webserver instead: Perfect, my files are now committed into GitLab Perfect, my files from GitLab are now on my laptop in PhpStorm Perfect, my files from the live webserver are now in GitLab So I want to edit in PhpStorm, which will then push to GitLab, which in turn will push to production? Is that right? I will also set up a staging environment to push to first.Ĭomplete newb, sorry if I'm making little sense!Ĭreate myproject on GitLab (from blank template) I know the fact that it's just me makes it a glorified to-do list, but I still want it. I really like gitlab for the issue tracking etc even though I'm a one-man band. I should probably install GitLab on my server rather than use their SaaS, but one step at a time! ![]() I want to modernise my workflow though, so have installed PhpStorm on my Windows 10 laptop, and paid for a year of GitLab (I want private repositories). Very occasional errors/downtime for my users felt ok. I know this is bad, but it's my site, my business and I'm the sole developer, and I've felt happy to take the risk. ![]() Over the last couple of years I'm even "naughtier", and just use Vim on the server, editing live files directly. ![]() I always used to edit in notepad++ and then FTP changes to the live server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |