-
Notifications
You must be signed in to change notification settings - Fork 72
Home
I've been away for a while, a lot has changed, we now have AI which I didnt have before, but I lost my Jenkins environment, I'm working on building that back up and working on smashing through the Issues tracker.
- Updating the perl to mordernise it a bit where I can, without breaking its universality (Thats why I need Jenkins)
- getting rid of Deprecated Python and bringing it back to pure Perl (OS Detection)
- Adding new Distros, removing Outdated ones (dont worry the option to override will still be there)
- I'll never support anything other than apache running in worker mode with mod_php
- PHP-FPM
- Event and Worker Mode, aand any other modes other than prefork
Ok truth be told, I maintained this heavily while I worked at an MSP, where we supported LAMP (mpm_prefork and mod_php), then I was at rick of redundancy and moved on, and the world also moved on, I realised people had largelt stopped using prefork mode and mod_php and thatred switching to event or worker modes and php-fpm, which are just different beasts, and well beyond the scope of a tool like apache2buddy.
Selfish reasons, if i am honest. I want to get into DevOps, I already Dev, and already Ops (Senior System Administrator), but I still dont really do DevOps. So Im re-igniting my passion for Jenkins, and this is the biggest project I have, with the larest requirement for testing, in fact, when apachebuddy.pl (the daddy to apachy2buddy.pl) was first developed, it only supported RedHat. Those of you willing to show your age, will remember the reason an remit for apache2buddy.pl to be born was to add support for Ubuntu and Debian systems (hence - apache2 buddy - if you see what I did there), however it now supports many other systems and more need to be added (Bitnami, Gentoo, Rocky, AlmaLinux) so much so that I can no longer test it by hand, like I used to - Im reliant on CI/CD tools like Jenkins to help me pass all the tests.
The Number One priority for me right now is to rebuild the Jenkins, get the pipeline going again, see whats breaking, and add issue trackers for those fix and get the CURRENT pipeline to pass, and then work my way through the issue Tracker.
This serves three purposes:
- Help me improve my CI/CD skills
- Refresh my Perl Knowledge
- Get apache2buddy.pl back to MAINTAINED status.
The domain is gone. You can still use curl-pipe-to-perl but you need to use the command / GitHub url given in the readme, which is in my opinion much safer, as I was never quite comfortable with the curl-pipe-to-perl on the apache2buddy.pl domain - as root - I mean, it seemed quite cute back in the early 2010's but then typosquatting became a thing and one wrong typo could get you root compromised ... so yeah...nahhhh dont do that.
Also im pleased the domain is gone, because it was costing me actual money each year to maintain / renew (and no i could'nt buy a 10 year domain registration, it had to be renewed annually - at quite a cost!).
I'll run Jenkins on a local Vagrant VM so I only pay for elecricity while its running, it wont be on all the time. So It wont cost me real money liek the domain did.
Yes, but look, this is free / opensource software (free as in freedon), I never intended to monetise it, so it also happens to be free as in beer and I don't know how the tax works, unless I do some research and set up a Business or Foundation to take the funding or something, to separate it from my own personal income, then most of it is going to go straight to the taxman in income tax rather than keep the lights on.
Sending me money is just going to create a tax headache. So thank you though, but keep your money. Just appreciate that I have a day job and a life and it just takes time.
YES! You can fork this, and make pull requests (from staging), once I get Jenkins back up and running, I'll set up the CI/CD pipeline to do the tests, and I'll approve an merge into the main (master) branch. A lof of repos now use main as the main branch, but this repo is very old and still uses master as its main branch, I only merge from staging into master after the tests have passed.
[1] http://www.techrepublic.com/article/how-to-tune-apache-in-seconds-with-apache2buddy-pl/ [2] http://www.itkonwledge.com/how-you-can-tune-apache-within-minutes-with-apache2buddy-pl/ [3] https://www.linode.com/docs/websites/apache-tips-and-tricks/tuning-your-apache-server [4] https://www.123-reg.co.uk/terms/renewal_restrictions_terms/