Site Sponsors:
Installing PIP3 on Ubuntu Server 16.04 
p.s: After setting-up LAMP-py, if you need other modules:
curl "https://bootstrap.pypa.io/get-pip.py" -o "get-pip.py"
python3 get-pip.py --user

Be sure to 'curl that 'get using the https - Using plain-ol http no longer works.

[ view entry ] ( 691 views )   |  permalink  |  related link
Whose STILL better @Python? 
Apologies for previous posts on political topics - I hate to care so much about non-technical issues - but I do.

Maybe you do, too?

Getting back to what we all know and love, surely the best way to push a post BACK, be to push something onto the stack, BEFORE it?

With such a laudable goal placed FIRMLY in mind, allow me to note that - even though Python 2.7 is decidedly deprecated - how, even at this late stage in the game - Ubuntu has the hands-down BEST Python 3 support for Apache2.

I cannot understand how tenured veterans are yet in denial over the ultimate demise of the 2.x standard... over the epoch, that pattern of deprivation has taken place over, and over, over, and over .. and over (!) again?

Indeed, Python 3 "just works" so well out-of-the-box (*) that I recently gave up at even trying to get the LAMP2 (Python3 + PHP) 'stack to work under CentOS 7. --At the day's ending, turn-key is ever so much to be preferred, 'oer toss-and-turn!


LAMP-Py?


... we are even running Ubuntu 16.04 - even as so decidedly dated - upon our clouds ... to absolutely great effect!

GO - DADDY, GO! (That pun ... intended!)

8-)

Note: Following the previous ('how to' link, below) we yet (P2) had to:
apt search php7
apt search libapache2-mod-php7
-then, with respect to our option set, and in as much as php -v was a dud:
apt-get install php
apt-get install libapache2-mod-php7.0

To be followed by the requisite:
systemctl restart apache2

(*) (how to)


[ view entry ] ( 1006 views )   |  permalink  |  related link
Hey Amazon - Where's the RESET button? 
It is probably entirely my fault - yet it still happened.

Re-directing 'web site A-records - creating permissions - zones - VPCs.

Was all working great, then BOOM. Health checks pass, but public IP addresses cannot be reached. -Even when all ports have been enabled? IP CDRs matching on the inside, and well as the 'out?

That was last weekend.

This weekend, the last straw came when I created a new VPC - and my default VPC automatically disappeared.

Yikes - I must have done something wrong ... and though I delete it all - painstakingly re-doing it all from scratch - the guts remain ever-yet messed-up.

I suppose that is a complement really - when it comes to pushing the limits of what is supposed to be a tech-savvy, robust, billion-dollar cloud offering - whose your 'dadday? (*)

p.s. FWIW, our "quick fix" AWS solution was to delete my company account ... faceless fortunes a'willing, we might be 'ale to start it over again - in a month or so?

(*) UPDATE: Far from being intended as a pun - went to godaddy.com to set up a 'server. Got it installed, updated, + HTTPD, and Python 3.6 (3.7 decidedly a no-go) in less than an hour. All that with totally cool, my-fellow-American, web-savvy technical support from a gal who was not afraid to research & recommend the very best solution for our long-standing account.

'Roger that.


[ view entry ] ( 410 views )   |  permalink

<Back | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | Next> Last>>