Nice idea. Loving the way you're adding in your domains.co.za affiliate link on the sly![]()
I don't understand.
I thought cli is the command line?
Remember everyone got on my case last time for using the GUI git app instead of using git in CLI in other words what relevance does this have on git itself? or am I missing something?
Lots of different ways. Me?
Master = production/live
Integration/Development = set of feature work that's approved and waiting to be merged to master
feature/whatever = created from master, dev done in there, pull/merge request sent to integration once done
Deploy your site with git;
If it is possible to do this with Cpanel would someone be so kind as to tell me how?
https://gist.github.com/oodavid/1809044
===
I am soon going to make another thread to get advice on how to setup a web server "correctly"
In other words I will get a centos server and then do everything from scratch via CLI whoop whoop that will be new for me since I am/was a GUI person.
Since we moved from centos to Ubuntu, life is a whole lot simpler.
Not following. The flow makes work and continuous releases easy. Every time a change happens in integration a build is kicked off and if it passes it is automatically merged to master (latest prod). Every merge to master is tagged with the build number which is the "version" number.Not so great with multi-versioned products.. Inevitably you end up with:
Master - latest prod
Version x.x - why?? Due to maintaining versions
Dev - which is integrated back into version or master
Perforce is awesome in that respect
I am soon going to make another thread to get advice on how to setup a web server "correctly"
In other words I will get a centos server and then do everything from scratch via CLI whoop whoop that will be new for me since I am/was a GUI person.

Google search
site:digitalocean.com setup centos nginx
But why the pain? Use Ubuntu server and get on with your life![]()
Nginx because nobody has time to try figure out how to configure Apache. I'm lazy like that.nginx vs apache?
Nginx because nobody has time to try figure out how to configure Apache. I'm lazy like that.
Nginx does not have any ability to process dynamic content natively. To handle PHP and other requests for dynamic content, Nginx must pass to an external processor for execution and wait for the rendered content to be sent back. The results can then be relayed to the client.
Nginx does not interpret .htaccess files, nor does it provide any mechanism for evaluating per-directory configuration outside of the main configuration file.
ok...No thanks
![]()
Nginx because nobody has time to try figure out how to configure Apache. I'm lazy like that.
ok...
EDIT: I installed PHP (don't ask why) on my machine the other day. To get that external processor working I readded a couple of lines in the nginx config file that was commented out by default and added index.php as a default page. Done.
That is one problem solved.
Now the .htaccess bit.
I want to get a VPS and be able to serve multiple websites I think it's called Vhosts or soemthing and then each site has their own .htaccess file.
Hope that makes sense.
This is new territory for me I was born as a Cpanel baby
nginx vs apache?