Hello fellow Soylentils, I could use some of your insights and suggestions.
I am looking for a lean, mean, and safe open source solution that implements a small blog where I can rant and rave to my heart's delight to my two followers.
To set the scene, I am not looking for something big and/or unwieldy, which basically rules out the major platforms like Drupal, Joomla and Wordpress. The software is going to be self hosted on my existing web server, which already runs Linux with Apache2, MySQL, PHP, Perl, and PostgreSQL (LAMPPP?) on a Debian platform.
I would like the following features:
[Ed. addition follows.]
I am not familiar with the minimum resource requirements for running SoylentNews, but if it would not reasonably fit on a single RPi, maybe adding one or two more would suffice?
What suggestions do YOU have for our fellow Soylentil?
(Score: 0) by Anonymous Coward on Tuesday July 30 2019, @05:16PM (1 child)
The point being that what we're describing is dynamic generation + static caching and not really a static site.
Also, despite 23 years experience, I have no idea what you're talking about with AWS. When you say "consumed by a lambda", are you talking about the lambda function I know or is this another sick perversion where concept is promoted to product name by wretched, overpaid marketing genii?
(Score: 3, Informative) by meustrus on Wednesday July 31 2019, @12:21AM
If you just wanted a static site, you would skip the last half and just have HTML files in S3 served through CloudFront. But the OP wants comments, which is decidedly dynamic. Well, unless you implemented the comment section as an empty div that gets filled in by JavaScript. But I will not help you build a JavaScript-only web site.
S3 = File storage
CloudFront = distributed CDN, can act as an HTTP server for files in S3
DynamoDB = NoSQL database, glorified key-value store
API Gateway = HTTP REST proxy for specific actions in AWS
Kinesis = distributed sharded stream, glorified distributed ring buffer
Lambda = execution of terminating programs based on triggers from other AWS services
The point of all this is to avoid running any daemons yourself by having them all execute in a massive distributed cluster. They call it "serverless", which makes about as much sense as co-opting "lambda" as they have done.
There are similar concepts in Azure, Google Cloud Platform, and OpenStack.
If there isn't at least one reference or primary source, it's not +1 Informative. Maybe the underused +1 Interesting?