4 ms·
I have a git server (gitolite) with a repo and four branches: main, development, testing and production. When im ready to run something on testing, for example
by fauria 13y ago
I have a git server (gitolite) with a repo and four branches: main, development, testing and production.
When im ready to run something on testing, for example, I checkout testing, merge from development and push.
In the remote server, the code it the repo is running with pm2. I use a post-receive hook to npm update everything and pm2 restart.
If everything is ok, and I want to deploy into production, I do the same thing but merging production branch instead.
When I see tools like this, I tend to think that im missing something, or that there might be something wrong with what I do.
What do you think?
- stingraycharles 13y agoThe problem I have with setting up these things yourself is that I usually forget about how I set it up in the first place. Sure you might remember how you set it up 3 months down the road, but what about 3 years? I try to use services or tools that do as much as possible out of the box. It means that I didn't have to manually configure much, which means it will be easier to understand after long periods of time. I know it isn't very hacker-like, but I personally feel there is a gray area that might create more problems than it solves, and I tend to stay on the "safe" side of things.