When I was in high school, I was the director of the school magazine club, that makes me be a little bit familiar with publishing. I started to use Hugo since 2017, gradually build the corresponding workflow and tools, and have some notes here. Regardless of entry or application, I hope you can get some clips that can improve your work efficiency :)
Over the past few years, I have continued to find some time to sort out the learning, and some of the results will be released as open source. I hope to bring out some ideas, considerations, various discussions and exchanges. It contains PHP, which I have never abandoned. The original design purpose of the container that I have organized this time is to combine php-fpm and nginx to form a simplified environment that can easily enable Laravel to operate in a cloud-native environment, AWS Fargate, Amazon ECS and other environments, to achieve application-first goal. I use it as a base for training, consulting and implementation of several teams, various comparison tests, including future comparisons of x86/ARM computing architectures, and so on.
- The released Docker image is placed in Docker Hub: dwchiang/nginx-php-fpm
- The original Dockerfiles are placed in GitHub: dwchiang/nginx-php-fpm
- If you like this project, feel free to use it into your project, or share it with friends, or click a star for this project ⭐ :)
- If you are also interested in this topic [Running Laravel on Amazon ECS], you can refer to this self-service online workshop: dwchiang/laravel-on-aws-ecs-workshops.
This article may be updated in the future.
(Illustration: Afternoon-tea with Grilled Halloumi Cheese. Not-so-related to this article, I know XDD. When writing such a long post, you know :p Image source: by Ernest, in London.)
This month Pahud invited us - a group of AWS Hero and AWS Builders to use AWS CDK to code around CloudFront Extensions (CloudFront Lambda@Edge). From my long todo list, I found a topic related to OAuth 2.0 that I have always wanted to do. It’s a perfect timing to try and see how to implement a CloudFront Extension solution in AWS CDK (Cloud Development Kit) with
.env environment variable settings, so that you can easily set your favorite IdP (Identity Provider), and then set the parameters generated by the IdP into
.env file. You can use this CloudFront Extension CDK solution to complete the deployment. After practicing, it should be completed within 20 minutes.
This article is organized in order for future education and training material, and is divided into three parts:
- At the beginning, we will introduce use cases, architecture, OAuth 2.0 protocol flow, and Grant Type: Authorization Code process
- Then select and configure a IdP you like (this part is expected to be expanded and updated in the future)
- Finally, “CloudFront Extension OAuth2 Getting Started” takes everyone to actually operate this CDK
Today I was chasing the information of AWS Pi Week to celebrate AWS 15th Anniversary for S3 Birthday, but I am also very happy to see that Amazon ECS announced a new feature that everyone asks for a long long time: Amazon ECS Exec.
This article is created based on these reference:
- Massimo Re Ferre’s article on the official blog: “NEW – Using Amazon ECS Exec to access your containers on AWS Fargate and Amazon EC2"，
- And Amazon ECS official document: “Using Amazon ECS Exec for debugging”
Then let’s try it through the AWS CLI interface, let’s try to see Amazon ECS Exec traverse directly to a container on Amazon ECS (EC2).
In recent years, TSDB (Time Series Database) has gradually been pulled out due to its particularity. It is suitable for IoT applications or DevOps/Apps analysis scenarios. To AWS products is Amazon Timestream. Using AWS’s advantages in distributed computing and storage, Amazon Timestream has been created with Serverless architecture and high scalability, which makes people quite curious about its underlying structure.
In this short sharing, I captured three key points:
- The use cases of Time Series Database and the strengths/advantages of Amazon Timestream.
- Adjust the composition structure of the data write based on the billing structure rules. (How to modify code to reduce price from $25 to $0.78)
- Best practices for querying processing.
Not so deep dive, but it’s a 30-minute session that covers architectural concepts and terminology. Suitable for friends who are comparing various TSDBs for a quick overview.
This session brought by Richard Barry, the founder of FreeRTOS, is helpful to understand quickly, when face development and deployment of IoT edge devices at scale. The key points to be faced Architecture , Process and Details.
Of course, we can choose to implement all the architectures, processes and details by ourselves, or choose existing solutions on the market, such as open source projects such as FreeRTOS, which has been integrated to various AWS IoT services (such as generating encryption keys, establishing encrypted communication channels and data transmission). So that your product team has more options and flexibility in the process of technology selection.
This session is recommended for everyone “ who want to quickly grasp the IoT edge device development options, deployment architecture and process ”.
If you are about to start an IoT project, this IOT203 sharing uses the “working backwards” method to push back and define customers.
Roughly disassemble the entire project cycle into three paragraphs: “Idea”, “Prototype”, and “Production”. Each paragraph has its own pits to step on.
If you want to go faster (say less than half year), you can find the original professional service. If you want to try it yourself, doing customer definition and previewing existing architecture reference in AWS IoT Solution Repository are the two cornerstones.
For me as a layman, this Lightning Talk is for the purpose of capturing keywords and major categories. Looking at the wording in the industrial field, the film mainly reads the slides. For those who are already in progress, you don’t need to watch this session. For those who have not yet, you can skip to the end to find a suitable partner to get started faster.
You can consider referring to this official blog article “Connected Factory Solution based on AWS IoT for Industry 4.0 success”, basically the same content, you can take time to watch other sessions.
Dirk Didascalou (VP, IoT, AWS) used “If you knew the state of every thing and could reason on top of that data…” “What problems would you solve?” to break the session and bring out the two major uses of IoT: Operational efficiency and Revenue growth, and three iterative cycles Edge and devices, Connectivity and control, Analytics and ML/AI, and use this framework to introduce the current status of the global use of AWS IoT (tens of thousands of customers , 90% Fortune 100, 0.5B+ Active endpoints per month, 0.5T+ Payload messages per month), and industry and academia case introductions such as 1NCE, Lenovo, Carrier, HITACHI Lumada, Univ of MELBOURNE.
When introducing the transformation of tomorrow, he started by saying that AWS develops new features with customers, and uses colors to bring out the four process changes. After the infrastructure is set, it will move towards analysis and industry. Followed five questions to introduce the corresponding major feature releases this year. Finally, introduce the Vector energy company of New Zealand and Australia to conclude. The introduction of energy applications with the concept of app store is also a good way to understand.
(Illustration: Formosan Blue Magpie, which is a endemic species in Taiwan, flapping its wings. Image source: Wikipedia。)
One of our iOS app built by Flutter is having Missing Compliance status in the TestFlight section in App Store Connect. We need to manage it via the App Store Connect UI all the time when we distribute a build into App Store Connect.