aws-sam-cli VS toolbox

aws-sam-cli-linux

Does anyone have any success with API Gateway/Lamba for local environment with hot-reloading? I was playing around with “sam local start-api” a few weeks ago with along with CDK but it doesn’t seem like hot-reloading is supported, and need to manually restart for code changes to reflect, which is currently stopping me from trying out the API Gateway/Lamba combo further due to inefficient DX. Here’s a GitHub issue about it: https://github.com/aws/aws-sam-cli/issues/901

Mostly due to lack of proper documentation it was difficult to get the HTTPApi syntax correct. The yaml file is very picky for CORS configuration on an HTTPApi. Luckily I found this github issue which allowed me to troubleshoot my yaml file.

No, it's not just muscle memory. It doesn't work with podman. That's what I'm talking about https://github.com/aws/aws-sam-cli/issues/1668

AWS SAM CLI with the support of Typescript is still in Beta. If you want more advanced features maybe you should not use it. Lately, in version 1.49.0 External and Loader properties have been added. If you want to share your feedback and/or requests this issue has been created.

I spent a while creating a custom runtime to use the native-image agent to harvest config from my Lambda, and then patching sam cli to work in Docker user networks... after pushing through all that, I still didn't get a working build - the native-image compiler just doesn't support everything (or didn't support my feature set, at the time - there has been a new release since then). In my case I think it was Guice that defeated me.

SAM support for TypeScript has been lagging for some time, but a pull request was just merged that should change that. It looks like we'll be able to add an aws_sam key in the package.json file to enable building within the SAM engine as part of sam build. Although this PR has been merged to aws-lambda-builders, the engine behind sam build, it will still need to be added to aws-sam-cli and released (to much fanfare, one expects) before it can be used with SAM.

I am installing SAM CLI on windows and its super simple. All I need to do is Click on this MSI installer.

sem-version java 8 wget https://github.com/aws/aws-sam-cli/releases/latest/download/aws-sam-cli-linux-x86_64.zip unzip aws-sam-cli-linux-x86_64.zip -d sam-installation sudo ./sam-installation/install checkout cd java-app-backend cache restore build-java-app-backend-$SEMAPHORE_GIT_BRANCH sam deploy --no-confirm-changeset --stack-name serverless-web-application-java-backend --capabilities CAPABILITY_AUTO_EXPAND CAPABILITY_IAM

The team has both made a ton of effort switching off their proprietary Skia based rendering tech and adopting standard Wayland, and has put forward huge effort to making running incredibly well integrated real Linux containers just work.

The headline is true. ChromeOS is Linux with Google’s desktop environment. But it obfuscates the details. It's a damned by omission statement. It has some really good sauce to help you not notice often, but it's not at all a Linux desktop environment one can regularly use. You can do a lot of Linux desktop-y things but only through well crafted special unique wrapped processes that mostly but not fully help mock & emulate a regular Linux desktop. Even though it now runs Wayland, the apps you want to run will have atypical intermediates up the wazoo.

And no one else uses any of this tech. ChromiumOs has so much interesting container tech, does such an interesting job making containers think they have a regular Linux / FreeDesktop environment. It's far far far far deeper virtualization than for example https://github.com/containers/toolbox . But you know what? Google has made zero effort to get these pieces adopted elsewhere. It's open source but not intended for use outside Chromium/ChromeOS. I respect & think ChromeOS is a quite viable Linux, and it's so much closer to the metal & more interesting, amazing tech, but my gods Microsoft has gone 300x further to establish wsl2 as a sustainable community effort folks could use & target, in a way that ChromiumOS has done nothing about.

It's sad how Google has transformed from a company that appreciated & worked with ecosystems, that drove things collectively forward, into an individual player that does their own things & delivers from on high. ChromiumOS is such an incredible effort, but it's so internernally drive & focused, and it's hard to believe in such a wildcat effort, even though it's so so good. It keeps coming into better alignment with Linux Desktop actual, but via shims and emulations that no one else cares about or which seems marketed elsewhere. And that inward focus makes the whole effort both so exceptional & promising, but suspect. Such a different nearby but alternative & separately governed universe. ChromiumOS/ChromeOS do excellent at faking being a Linux desktop, and wonderfully have increasingly drawn more strength from that universe, but are still wholly their own very distinct very separate very controller other space. In many ways that's great, secure, good, and miraculously transparently done. But it's still hard to really trust, being such a weird alien impostor, faking so much for end user apps, and there's tension in believing ChromeOS will keep straddling the rift in pro-user manifestations forever.

I'm really, really happy with my current setup of Fedora immutable + toolbox [0]. This tool lets you create containers that are fully integrated with the system, so you have acces to the entire Fedora repos, can run graphical apps, etc. while still having everything inside a container in your home directory. That means no Flatpak required. Highly recommended.

[0] https://containertoolbx.org

Seems like toolbox is also in this space; https://github.com/containers/toolbox

With Silverblue the core repos are very similar to what you'd have on regular Fedora. With more of a philosophical shift about where you're supposed to install things from. The idea being that the base OS is immutable and you keep it fairly minimal - even though you are technically free to install any of Fedora packages to it. And then you install user applications through Flatpak and toolbx. Where these more user space focussed applications are installed to your home directory and are sandboxed away from actual access to your OS. With iOS/Android style application permissions like "Give app permission to access camera" and "Give app permission to modify files in home directory". Allowing you even further customise the sandboxing of applications. Do you really want that app to have access to your microphone?

I'd probably try running it on the host system first. If you want to use your nvidia gpu inside toolbox, you would indeed need to install the drivers in the container: https://github.com/containers/toolbox/issues/116

Use toolbox on CentOS or Ubuntu if you want a Fedora environment with more up to date tools: https://containertoolbx.org/