...search?
A: Although I referenced the design from CachyOS packages search, I entirely wrote the code myself. The original uses Next.js on Docker while retrieving package information from its dedicated api endpoint, whereas this project uses SvelteKit with Vercel for hosting and Neon for...
...the system’s exposure, wouldn’t it?
Enter jails. The lightweight answer to containerisation, that’s been around for a long time before Docker became trendy.
Setting up a Jail
As with everything in the tech industry, there are at least half a dozen different ways to achieve the same...
...bloats and clutters on system level (systemd, package management, snaps, flatpacks). But ultimately client/end device future belongs to microkernels - if only for ease of using myriad of drivers.
Server will belong to FreeBSD....once the Docker phase implodes, thanks to it's poor security design.
...would have one of his famous hissy fits. And the FAANG don't care, their scale is such that an individual OS node is no longer important enough to worry about; they instead build much larger systems (for an example, look at gRPC, MapReduce and Borg, which created Hadoop, Docker and Kubernetes).
If your interest in FlatPak is security, then a Jail is probably best. Linux doesn't have a standard approach to this so hence why FlatPak, Docker, Snaps and all that other crap exist.
If your interest in it is avoiding spraying cruft all over the filesystem, just use pkg_fetch(8) and extract...
...is the preferred/standard way of deploying an application to FreeBSD? I have a Go app, and on my local dev machine I run it and test it with Docker. I have also deployed it in the past using Docker to a VPS when doing a real world stress test. But AFAIK docker does not run on FreeBSD or...
...for Alpine and Ubuntu with userlands in /compat/alpine and /compat/ubuntu . For containers builds, I settled on just using Alpine and adjusted docker-compose.yml to pull Alpine based dependencies. They ran fine in Docker on Alpine Linux on real hardware and in Podman on FreeBSD with Alpine...
...micro-kernel eventually. Because of driver-hell....and security/stability.
FreeBSD will be for servers using bhyve virtualization, because Docker (or Podman run as root), combined with systemd linux containers will be deemed security risk. Jails will become Alcatraz or they will not survive...
...I confused Discourse with Discord.
Why FreeBSD does not use Discourse is probably because
a) it is based on Ruby on Rails and
b) you will get only szpport when nunning from a Docker container.
c) installing it ffrom scratch without docker is possible but s a PITA and updating it then a...
Indeed, probs for the best. I do tend to upset Docker kids when I introduce them to reality but they simply can't understand.
Yep. The handbook documents loads of 3rd party ports. Some good; some not so good. None of them are officially part of FreeBSD.
...perl 5.40.2 by adjusting the plist, removing the failed components of the make, and then rerunning make install.
I did note that Lyrion has a docker build available. My next step would have been to install it that way. I have an alpine bhyve instance running docker and could have stuck it...
...about ZFS, Bhyve and so on.
xibo - I agree with your points, but I will probably aim to get stuff running first, then work on better (non-docker) installation later. Your migration path looks good - I am retiring soon from paid work, so I can put some effort into it going forward. What ever...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.