@dan003400 @jasonfried That said, I think it's quite likely we'll bring Solid Queue into the ONCE apps over time, and probably drop Redis too, as things evolve.
@dan003400 @jasonfried It was to keep persisted state to a bare minimum for simplicity. In Writebook's case, there are no jobs that need to survive restarts; discarding that state when the container stops gives a nice clean slate to reason about during upgrades. & we already had Redis for Action Cable.
@tghastings @37signals@dhh @tghastings if you do a `once update`, does that resolve the problem? I believe this is now fixed in the latest release, but please let me know if you're still seeing it after that.
Today's the day: Writebook is here! And it's free.
https://t.co/LSqaxN3IGm
Blogging and posting on social is easy. But why is it so hard to publish a whole book on the web? It’s not anymore. Writebook is remarkably simple software that allows you to publish text and pictures in a simple, browsable online book format.
It's perfect for publishing instruction manuals), a collection of short stories, poetry, graphic novels, handbooks, and anything that fits better together than apart.
Writebook isn't a service, it's software you download and install on your own server. We've made it incredibly easy to get going — it just takes a few minutes. Even non-technical folks can get it all set up. We'll email you a single command you paste into a terminal and it takes care of the rest. No maintenance required either, it takes care of itself, auto-updates, etc.
And it also comes with all the Rails code so you can see how it's built, modify it for your own use, and learn how applications like this are made.
So, grab it and dive in! We'd love to see what you publish.
https://t.co/LSqaxN3IGm
@LVNilesh@jasonfried@LVNilesh make sure your proxy is forwarding the `Host` header. That will allow Writebook to form URLs correctly.
e.g. for nginx it'd be something like:
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://192.168.1.253:5555;
@tlakomy@aarondfrancis @aeduhm @fideloper There's also the option of using HTTP routing support from your language/framework, which can help avoid that big `switch()`. I often do that in Go with gorilla/mux, for example.
@fideloper Building as one app also means you can treat Lambda as just another deployment target. That way, the same app can also be run locally for dev, or in a Fargate container, or what have you.
@JackEllis@alexbdebrie@aarondfrancis@tlakomy @aeduhm @fideloper Yes, good point. Even just managing the concurrency requirements (including reserved concurrency if you need it) can be a lot tricker when you have many small parts to consider.
@alexbdebrie@aarondfrancis@tlakomy @aeduhm @fideloper Agreed. Also while smaller functions may have quicker cold starts, you now have more functions that will need to be started and kept warm — so potentially more opportunities for cold starts to occur. Which one fares better in practice can really depend on your specific use case.
Some great points in this thread! It's a good reminder of how language comparisons can often do more harm than good. As Russ rightly says, it's not a zero sum game.
I wasn’t going to say anything, but since ZDNet has republished the AWS “Sustainability with Rust” blog post, a short thread about why that post is misleading (at best) about Go. 1/
The other nice thing is that as the CDK keeps improving, many tasks get simpler.
e.g. I had a section on how to build Go code when deploying to ARM. But with recent CDK versions that's handled automatically (per the `architecture` prop) so that's one less thing to do!
@funcOfJoe I actually quite like this! 😊 Especially if the BucketObject could also be a child of the Bucket, rather than a related sibling, to express the hierarchy/ownership.
There is a risk you’re reinventing XML as configuration 😂 but it’s an interesting idea!
Just bought (and looking forward to reading) - Make the Most of #AWS Lambda with Go - https://t.co/tTSxkGPgsI by @kevinmcconnell . Looks like it has plenty of code inside. CC: @golang .
Just upgraded some CDK code from v1 to v2 and it was a complete non-event — in a good way! :)
90% of it is just updating imports, but the docs have a nice guide covering all the details. https://t.co/AGUdZQrBBt #AWS#awscdk
Enjoying seeing the recent discussions about Rails and its continued relevance for current web app development. However it’s also good to remember there are *many* productive and sensible ways to build software these days.
Like with most things, if you go looking for the One True Way you’ll find zealotry and ignorance. But if you keep an open mind there is an awful lot to learn from the experience and approaches of others.