[ { "date": 29200953600, "slug": "info", "title": "re:Web Project Infos", "body": "
re:Web is a small add-in binary that enables classic web applications to run on AWS Lambda.<\/p>\n
For a detailed description, please see the README on Github.<\/p>\n
Github project page<\/a><\/p>\n<\/li>\n re:Web blog<\/a> (this site)<\/p>\n<\/li>\n re:Web in the Amazon ECR Public Gallery<\/a><\/p>\n<\/li>\n re:Web in the Serverless Application Repository<\/a> EXPERIMENTAL<\/em><\/strong><\/p>\n<\/li>\n<\/ul>\n For bug reports, pull requests and other issues please use Github.<\/p>\n For everything else:<\/p>\n A basic Wordpress installation runs fine on re:Web, but one major obstacle for many\nreal-world uses is large assets:<\/p>\n API Gateway \/ Application Load Balancer put some hefty size limits on uploads and\ndownloads -- for example, using very large images will lead to errors.<\/p>\n There are two plugins which help a lot to make Wordpress work nicely with large assets:<\/p>\n S3 Uploads<\/a> offloads all such assets to\nS3, so Wordpress\/re:Web don't have to deal with delivery of those assets at all\n(therefore bypassing the size restrictions)<\/p>\n<\/li>\n Tuxedo Big File Uploads<\/a>\nreplaces the Wordpress file upload function to use chunked transfers instead<\/p>\n<\/li>\n<\/ul>\n With both plugins installed, uploading and delivering large assets works nicely.<\/p>\n Note that it's most likely necessary to install them manually (unzip to the Wordpress\nplugin folder in EFS), because their installation takes longer than API Gateway's maximum\ntimeout.<\/p>",
"image": "",
"excerpt": "Large assets require special handling with re:Web. Luckily, there are two great Wordpress plugins that help to deal with this.",
"tags": [
"wordpress",
"howto"
]
},
{
"date": 1618704000,
"slug": "php-nginx-sar",
"title": "re:Web for PHP + nginx in the Serverless Application Repository",
"body": " There is now a re:Web package in the AWS Serverless Application Repository that comes ready-to-go\nwith nginx and php-fpm included.<\/p>\n Usage goes something like this:<\/p>\n Make sure you have an EFS Access Point that will be your \"web root\", with at least a\nsimple Deploy the package from the Serverless Application Repository<\/a><\/p>\n<\/li>\n For deployment, you will need to provide<\/p>\n Wait for the deployment to complete -- you can monitor progress in the \"Deployments\"\ntab (should take 2-5 minutes)<\/p>\n<\/li>\n After deployment, go to the API Gateway Console and find the Invoke URL<\/em><\/p>\n<\/li>\n<\/ul>\n There will be a Lambda function and a corresponding API Gateway that's ready\nto serve web requests and even full PHP applications from your EFS. Just open the Invoke URL\nin your browser.<\/p>\n A potential next step might be to manually add a Custom Domain Name to API Gateway, or configure\nan Application Load Balancer to connect to that Lambda. And to put some content there, for example\nsome PHP application.<\/p>\n To delete the deployment, simply delete the stack in CloudFormation.<\/p>\n Note that I consider this re:Web package even more experimental than re:Web itself :-) If you\ngive this a try, let me know<\/a>!<\/p>",
"image": "",
"excerpt": "An experimental re:Web package with nginx and PHP is now available in the AWS Serverless Application Repository.",
"tags": [
"info"
]
},
{
"date": 1617667200,
"slug": "dogfood",
"title": "Dogfood!",
"body": " To have something akin to a production site (lol), I've decided to give re:Web a homepage \/ blog.<\/p>\n It will be a good place to post news and updates.<\/p>\n And it runs on re:Web, hence the title.<\/p>\n This site runs on Nicholas<\/a>, \"a lightweight, flat-file, easy to use & nearly-headless blogging system\".\nThis was a coincidental discovery, but it's pretty nice so far! I love simple things.<\/p>\n Nicholas is PHP without external dependencies (no database!), so it's an awesome fit for nginx+php powered by re:Web!<\/p>\n Thanks to Lambda + re:Web, this blog is blazingly fast,\nit would scale to BBC-levels of traffic<\/a>\nunmodified1<\/a><\/sup>, and is highly available in three\ndifferent Availability Zones<\/a>.<\/p>\n And it costs roughly... nothing!<\/p>\n Well, besides AWS default quotas. Still, default quotas will handle more traffic than you'll ever need. ↩<\/a><\/p>\n<\/li>\n<\/ol>\n<\/div>",
"image": "https:\/\/tty.neveragain.de\/assets\/falling-into-water-is-prohibited.jpeg",
"excerpt": "In a shocking first, I'm trying my own dogfood.",
"tags": [
"yadayada"
]
}
]Contact<\/h3>\n
\n
\n
\n
index.html<\/code> for testing<\/p>\n<\/li>\n
\n
\n\n