On 01/11/2017 08:19 PM, Roger Oberholtzer wrote:
On Wed, Jan 11, 2017 at 10:27 AM, Simon Lees
wrote: Sounds like you'd probably be better suited running Leap on that server possibly.
We had a long thought on that. It's job in life is to supply Apache-based services (Python and PHP), and subversion source control. It also runs docker, Jenkins, and various compilers.
Because of it's location, external access audits check the version of the things accessible. Once they are past their use-by date, we are required to update them (our current activity). One can update non TW OSs only for so long. After a while, too much is out-of-date to make an update of a single component feasible. For example, we just tried to update subversion on 12.3. Subversion has surprisingly many dependencies these days. Especially for things like accessing it via Apache. So, we decided that TW may allow us to keep these machines current for a longer period of time. Our experience with TW in other contexts has been great.
I don't need php5 and php7 at the same time. I just want to stay with php5 for a short while while we remove the need for PHP all together.
Not sure if it helps but Leap is designed so that once a year you can easily update from 42.1->42.2->42.3 etc without too much fuss which should allow you to keep them recent enough without too much hassle. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adeliade Australia, UTC+9:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B