Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Boilerplate

github.com

Post reply on HN
Print view View original

31–40 of 62 posts

Re: AWS Boilerplate

#31

Post by celim307 »

whalesalad wrote: post #25
nixgeek wrote: post #24

Initial reaction to seeing HN showing me “AWS Boilerplate (github.com)” was I thought AWS had launched a new service and it was potentially open source. Please consider renaming to something like ‘Boilerplate for AWS’ since it would avoid confusion that this is something official from AWS, and because such a name is less likely to cause trademark issues per the AWS Trademark Guidelines. https://aws.amazon.com/tradema…

Yeah, my first thought was oh shit Amplify has been replaced here we go again.

Amplify is so shit

Re: AWS Boilerplate

#32

Post by dcveloper »

karakanb wrote: post #6

Shameless plug – I am building something similar to this for PHP with Laravel, Docker, Kubernetes, Helm, CI/CD, along with ready-made pages and tests: https://nana-landing.netlify.app/

Are the Documentation or "Get Started" links supposed to work?

Re: AWS Boilerplate

#33

Post by karakanb »

dcveloper wrote: post #32
karakanb wrote: post #6

Shameless plug – I am building something similar to this for PHP with Laravel, Docker, Kubernetes, Helm, CI/CD, along with ready-made pages and tests: https://nana-landing.netlify.app/

Are the Documentation or "Get Started" links supposed to work?

nope, not yet unfortunately, I am still working on the documentation, I'll be done in a few weeks hopefully.

Re: AWS Boilerplate

#34

Post by duhi88 »

karakanb wrote: post #6

Shameless plug – I am building something similar to this for PHP with Laravel, Docker, Kubernetes, Helm, CI/CD, along with ready-made pages and tests: https://nana-landing.netlify.app/

Looks solid. Are you using Nova for the backend?

Also, is this intended to be a thing you buy, fork, and make it your own? Or will it be more like a framework where customers receive updates to the core code?

Re: AWS Boilerplate

#35

Post by corytheboyd »

williamdclt wrote: post #16

I used to work at a web agency, and my biggest impactful was without a doubt setting up something similar. Instead of starting from scratch at each new project, or copying config from another project, I wrote a "project generator" that asked you a few questions (Django or symfony? React or vue? NextJS? Terraform?) then generated a fully-configured project for you, including a staging and a production environment. It'…

I have never worked for such an agency, but I actually find value in setting up some of the infrastructure from scratch, at least on the application side. It’s a time to dig into the latest versions of each component, or apply learning you wish you could have on other projects but things got too big to make large architectural changes. It costs a few days, but you’re laying down what should be the forever foundation, that’s worth fully understanding and trusting IMO.

All that being said, rolling AWS infrastructure ad-hoc like this is a terrible experience, but I far less experienced with it. Terraform seems like a great general tool to ease the pain, or something with this project.

Re: AWS Boilerplate

#36

Post by corytheboyd »

nautilus12 wrote: post #3

Anyone else feel like AWS's primary goal isn't actually to make money but to put us all out of a job, but it doesn't quite know how to do so

AWS is sold to software companies, are you suggesting they want to replace their customers with... themselves? If companies could profit from purchasing their own goods I think the world would be a very different place lol

Re: AWS Boilerplate

#38

Post by otabdeveloper4 »

freehunter wrote: post #18
williamdclt wrote: post #16

I used to work at a web agency, and my biggest impactful was without a doubt setting up something similar. Instead of starting from scratch at each new project, or copying config from another project, I wrote a "project generator" that asked you a few questions (Django or symfony? React or vue? NextJS? Terraform?) then generated a fully-configured project for you, including a staging and a production environment. It'…

This is why I love opinionated frameworks, why I love hand-holding tutorials, why I love abstractions. I don’t like code. I don’t like writing it, I don’t like reading it, I don’t like thinking about it. A mechanic doesn’t love his crescent wrench, he loves working on engines. The wrench is just a tool. What I enjoy is the final product and seeing a project come together as time goes on. “The right tool for the job”…

> Django vs Rails vs a huge bundle of JS libraries cobbled together at random... for most programming work it doesn’t matter.

It might not matter to you, but it sure matters for the end user.

This sort of attitude is why blog pages weigh north of 20 Mb and load for minutes nowadays.

Re: AWS Boilerplate

#39

Post by JamesSwift »

corytheboyd wrote: post #35
williamdclt wrote: post #16

I used to work at a web agency, and my biggest impactful was without a doubt setting up something similar. Instead of starting from scratch at each new project, or copying config from another project, I wrote a "project generator" that asked you a few questions (Django or symfony? React or vue? NextJS? Terraform?) then generated a fully-configured project for you, including a staging and a production environment. It'…

I have never worked for such an agency, but I actually find value in setting up some of the infrastructure from scratch, at least on the application side. It’s a time to dig into the latest versions of each component, or apply learning you wish you could have on other projects but things got too big to make large architectural changes. It costs a few days, but you’re laying down what should be the forever foundation,…

That exploratory work is still done... its just done one time by someone who is "best" suited to do it. Then you just stamp out projects leveraging that exploratory work.

Re: AWS Boilerplate

#40

Post by jeremylevy »

zmkzrk wrote: post #37

This looks interesting, nice work. For comparison, I created a full-stack AWS boilerplate with similar aims: https://github.com/stackplanet/sourcestack

Wow, looks great! Can I ask you which tool(s) have you used to make the architecture schema?

[1] https://raw.githubusercontent.com/stackplanet/sourcestack/ma...

Post reply on HN