41–50 of 62 posts
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...
AWS Amplify is in a similar space. It supports several frameworks and the development workflows and infrastructure management are built in to the project. https://aws.amazon.com/amplify/
I urge fellow readers to try and plan out your entire app arch on Amplify before committing to it. I have found it to be a pain in the ass because it tends to want to do everything for you leaving assets/buckets/things like `aws-amplify-23094139-85-3981759387593745983475-us-east-experiment-project` all over your account. I have been using AWS for over 10 years, so I tend to like to keep a clean house and name most of…
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'…
Earlier quoted context omitted.
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.
Nice. This boilerplate can really help people get started quickly. Well done :) On a different note, recently I was looking to learn AWS concepts through online courses. After so much of research I finally found this e-book on Gumroad which is written by Daniel Vassallo who has worked in AWS team for 10+ years. I found this e-book very helpful as a beginner. This book covers most of the topics that you need to learn…
Earlier quoted context omitted.
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...
Sure, I used Lucid Chart https://app.lucidchart.com which has a lovely set of "flat" AWS asset icons.
For folks who are interested in deploying their containers on AWS without "boilerplate", we also have a tool called AWS Copilot which can help simplify setup and management of all the container infrastructure you need :D https://github.com/aws/copilot-cli
Earlier quoted context omitted.
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”…
I feel the same way about rust’s standard lib, which is pretty sparse compared to, say, python and go. Finding libraries for common tasks is the most stressful part of an otherwise stress-free language (first world problems, I know). I get that it’s a trade off, and I get why the designers chose this path, but I would have preferred it the other way.
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?
This is going to be a fork and make it your own; once you get the code it's all yours. I may share security fixes as patch files maybe, but that'd be more of a manual work for everyone rather than an automated update mechanism.