Hi,
I took a stab at updating the cookbooks we use for the website to use
centos8. Motivation was getting a new version of php so we can use
some drupal plugins that dont support php5.4, but i think this was on
the backlog already for a while.
https://github.com/socallinuxexpo/scale-chef/pull/283
To test this out, I spun up scale-web2 with a clone of the production
scale-drupal database, and then pointed my host file at it for
www.socallinuxexpo.org:
I then tested the following:
- chef runs complete end to end
- Backing up / restoring static assets (see backup scripts in
/usr/local/bin or in the scale-drupal cookbook)
- browsing legacy static website (eg
https://socallinuxexpo.org/past/2002/https://socallinuxexpo.org/past/2003/)
- Registering as a speaker, confirming that I got the email and that
my account worked.
- publishing the submitted talk
- creating sponsors/exhibitors/blog post/events/etc
Pending things:
- Centos8 seems to default to using php-fpm instead of mod_php. Not
opposed but it's different. Seems to work fine, but I've not load
tested it or anything.
- drush (https://www.drush.org/) packages no longer seemed to be
present in centos or epel. remi seems to have it but the drush docs
suggest we should be installing this in our drupal code base via
composer instead of as a package. I dont have strong opinions, but we
should figure out the right path before merging.
Cheers,
Ilan
FYI
---------- Forwarded message ---------
From: 'Amazon Web Services, Inc.' via aws-linuxfests <aws(a)linuxfests.org>
Date: Sun, Nov 19, 2023 at 1:42 AM
Subject: [Notification] New charge for public IPv4 addresses starting
February 1, 2024 [AWS Account: 355993445259]
To: <aws(a)linuxfests.org>
Hello,
You are receiving this notification because your AWS account has at
least one public IPv4 address used in the last 30 days.
On July 28, 2023, we announced [1] a new charge for public IPv4
addresses that will come into effect starting February 1, 2024.
For details on your usage, you can look at the AWS Cost and Usage
report. To monitor, analyze, and audit your use of public IPv4
addresses, you can look at Public IP Insights [2].
You can also read our blog post, Identify and Optimize Public IPv4
Address Usage on AWS [3], for information on how to optimize your use
of public IPv4 addresses.
For more details on public IPv4 address pricing, please see the VPC
pricing page [4].
For questions, please reach out to AWS support [5].
[1] https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-…
[2] https://aws.amazon.com/about-aws/whats-new/2023/07/aws-public-ip-insights-v…
[3] https://aws.amazon.com/blogs/networking-and-content-delivery/identify-and-o…
[4] https://aws.amazon.com/vpc/pricing/
[5] https://aws.amazon.com/support
Sincerely,
Amazon Web Services
Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc.
Amazon.com is a registered trademark of Amazon.com, Inc. This message
was produced and distributed by Amazon Web Services Inc., 410 Terry
Ave. North, Seattle, WA 98109-5210
---
Reference: https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn…