tobilg

You might have a look at https://github.com/tobilg/serverless-aws-static-websites to get a single command deploy including CDN and a domain

You might also look at https://github.com/tobilg/api2html

For a readymade stack similar to what’s described in the article to self-host in your own AWS account have a look at https://ownstats.cloud

Great job, congratulations from an ex-Mesosphere colleague!

Thanks for the comprehensive answer. I have similar experiences, treating the coverage numbers as a KPI will eventually trigger difficult decisions in writing tests.

What I’m wondering is what would make „more sense“ if one wants to track the code quality and test coverage in a broader sense.

Interesting! Do you upload the reports somewhere and do you track the coverage over time?

Yes, that’s the way I’m seeing it as well. SLS is a much better fit when developing services with lots of integrations with other services IMO, with much less code than Terraform.

There’s CDK-TF that was already mentioned in another post. Apart from that I’m not sure what you mean with interoperability, because the resources can only be owned by one stack.

For sure stacks created with those frameworks can use resources that are created by Terraform in other stacks. Serverless for example has its own integration with the Parameter Store for encrypted variables, so that there’s no need to use environment variables in that use case. Terraform would then create the Paramter Store keys which SLS could reference.

I have personally have nothing against Terraform, and we’re using it for a lot of infrastructure-heavy things on our platform, but I think there are way better frameworks when deploying Lambda function.

Particularly the Serverless framework will save you A LOT of boilerplate IAC regarding all the event-driven integrations Lambda currently has to offer, and manages the full build and packaging cycle with the relevant language specific plugins, e.g. for Node or Python.

Others are the CDK, SAM or ARC.

You might be interested in the new DynamoDB to S3 export feature announced this week: https://aws.amazon.com/blogs/aws/new-export-amazon-dynamodb-...

If you have an AWS account, you can use https://ownstats.cloud to self-host website analytics

See https://simpleit.rocks/web/hostings/redirect-http-to-https-a... for example

If you want to host a static website on AWS with one command, and not clicking around in the Console, have a look at https://github.com/tobilg/serverless-aws-static-websites

For fullstack websites, I created https://github.com/tobilg/aws-fullstack-website which will additionally create a API based on API Gateway and its HTTP API feature

You can have a look at https://ownstats.cloud if you happen to have a AWS account available

Shameless plug, you might want to have a look at https://github.com/ownstats/ownstats

If you have an AWS account and want a lightweight, cheap and privacy-friendly alternative, you can have a look at https://github.com/ownstats/ownstats as well.

If you run on AWS and want cheap and privacy-focussed website analytics, you might also look at https://ownstats.cloud/

Might be worthwhile to also check out https://plantuml.com/

While this might be correct, in the a lot of cases you'll also use a lot of plugins for both to enable the desired transpilations and checks...

I should have been more precise in my first comment though.

Hopefully it got a little less „dependency-heavy“ than before. Using eslint and babel tends to add 200mb of dev dependencies to a project...

Germany offers a max of 14 months of „parental allowance“ for new parents. See https://handbookgermany.de/en/live/parental-benefits.html for example

You might have a look at https://ownstats.cloud

If you have access to an AWS account, you can host your own website statistics with very little costs. That’s why I built https://ownstats.cloud/ Would love to get some feedback.

Thanks, l‘ll have a look. Building binaries should be possible with the used lambci/lambda Docker image afaik.

Great, looking forward for your feedback. It’s currently just a weekend project, so it might still have some rough edges...

You can have a look at https://github.com/tobilg/serverless-aws-static-websites if you want to set this up with one command

I struggled with setting up static website hosting on S3, CloudFront, Route53 and ACM, so I created https://github.com/tobilg/serverless-aws-static-websites to automate this via the Serverless framework

If you want to do this with one command, check out https://github.com/tobilg/serverless-aws-static-websites or, if you want to host an API with Lambda as well, https://github.com/tobilg/aws-fullstack-website

Feel free to read the README.md of the repo, in my option it clearly described what gets deployed.

Interesting semantic discussion nevertheless.

With „fullstack“ I meant a Frontend together with a Backend... All with one CloudFormation stack :-)