firebase-tools VS bubblewrap

And it seems to deploy on first try, but then I got a loop error. Turns out after posting a bug, and getting sent to GitHub, this is a known issue when deploying to Cloud Functions. The fix is to edit your server.ts file, and don't use the process.env['PORT'] variable, as it apparently is already in use.

See issue.

No, just JS. Have you tried this?

In this example, I am using NX monorepo. I have my Angular Universal as one application and cloud functions as another application. If you don’t use NX or even some time has passed since publishing this blog post, you may want to visit Integrate web frameworks with Hosting from Firebase, however, there is an existing issue on Unable to detect the web framework in use when using angular app within nx monorepo.

Support for Sveltekit SSR has been added https://github.com/firebase/firebase-tools/issues/5158

// https://github.com/firebase/firebase-tools/issues/1532 if (admin.apps.length === 0) { admin.initializeApp() } export const deleteAllUserJobs = functions.https.onCall(async (context: functions.https.CallableRequest) => { const uid = context.auth?.uid if (uid === undefined) { throw new functions.https.HttpsError("unauthenticated", "You need to be authenticated to perform this action") } const firestore = admin.firestore() const collectionRef = firestore.collection(`/users/${uid}/jobs`) const collection = await collectionRef.get() logger.debug(`Deleting ${collection.docs.length} docs at "/users/${uid}/jobs"`) // transaction version await firestore.runTransaction(async (transaction) => { for (const doc of collection.docs) { transaction.delete(firestore.doc(`/users/${uid}/jobs/${doc.id}`)) } }) logger.debug(`Deleted ${collection.docs.length} docs at "/users/${uid}/jobs"`) return {"success": true} })

This should be supported via our built-in NextJS support https://firebase.google.com/docs/hosting/frameworks/nextjs if you have troubles with this functionality, please file a bug over on github https://github.com/firebase/firebase-tools

Now that app directory is stable, we support it. Keep an eye on the firebase-tools changelog, we've actively working on things. https://github.com/firebase/firebase-tools/releases

The Firebase CLI, check out the release notes

Nothing nix specific but you may be interested in https://github.com/containers/bubblewrap

Recently, I came across Chainguard and wrote the article How to build Docker Images with Melange and Apko. As a fervent supporter of Kubernetes and GitLab CI, I was eager to experiment with building images using Melange in this particular setup. GitLab's shared Runners work seamlessly with Bubblewrap, eliminating the need for additional configurations. This post is intended for enthusiasts like myself, interested in hosting their own Kubernetes Runners and leveraging the Kubernetes Runner Type of Melange.

```

This is basically manually invoking what Flatpak does:

https://github.com/containers/bubblewrap

This is also useful for more than just security. E.G., you can test how your app would behave on a fresh install by masking your user configuration files. I personally also have a tool that uses it to basically bundle all dependencies from an entire Linux distribution in order to make highly portable AppImages— Been meaning to post that, will get around to it eventually maybe.

The flags above should hide your user data (`--tmpfs`), disable network access (`--unshare-all`), hide/virtualize devices and OS state (`--dev` and `--proc`), and make the rest of the root filesystem read-only (`--ro-bind`­— Including the insecure X11 socket in `/tmp`, which you might want to expose for GUI apps).

Check them against `bwrap --help`; I might have omitted one or two more things you'd need.

While trying to find out more comparison information, found this light on details issue:

https://github.com/containers/bubblewrap/issues/81

It mentions nsjail and minijail.