jolt VS Docker-OSX

If you just want movies and shows, check out Jolt. An app I'm building that's meant to be the social hub of your media server.

If you're interested in media serving, Jolt needs a lot of work with many features. The project management isn't quite setup yet for large teams, but I'd be open to chatting about collaboration. :)

I'm working on Jolt which syncs with your Jellyfin server and shows movies and shows you've watched, and you can go to your own profile to see a grid of the media.

Combined with GolangCI-Lint, a project I'm working on right now called Jolt makes sure errors are handled, pointers are used correctly, variable naming is following all the conventions and a bunch of more stuff. Setting up a toolchain like this in Python would be a huge pain.

A couple days ago I posted about Jolt, a social hub for media servers that allows users to rate, review, recommend media and track what they've watched as well as add media to their watchlist, and got a very positive response from this subreddit.

I've been working on a platform that generates suggestions for movies based on what users have watched and their ratings of those movies. The project is Jolt, if you guys want to check that out. Now I'm trying to brainstorm a sort of scoring/weighting algorithm that could take more things into account, when overlapping scores are generated based on the parameters outlined.

I'm also currently working on a project - and have been posting some updates here and on r/selfhosted, called Jolt which takes a social approach to discovery. In addition to using TMDB to find popular shows and movies, as well as generating suggestions based on what you like, it allows you and your friends to discover media together, and recommend it to one another.

I am working on a small open-source project at the moment, called Jolt, for which I really want to keep my CI/CD as simple as possible. I have experience in GitLab and Drone pipelines, as well as some others, but with the publicly available GH Actions I'm having trouble setting up something that does the following:

Hey, I noticed we're both working on extremely similar projects. Jolt also tracks what you've watched, allows you to maintain a watchlist, and generates recommendations based on your ratings.

Hey everyone, yesterday I posted about Jolt, which is a social hub for media servers that is meant to be used hand-in-hand with Jellyfin. With some help from the community, I have semi-automatic builds of the Docker image running now in GitHub Actions, which means that an early version is available to test for those interested!

Running macOS legally requires real mac servers and a bespoke storage solution: https://www.datacenterdynamics.com/en/analysis/not-just-stac...

A self-hosted macOS runner will be more economical in the long-run, if you have a spot you can hook it up at, or if you're fine doing things less than legally, you can use https://github.com/sickcodes/Docker-OSX.

Repositório Docker-OSX - Guidelines, troubleshooting, comandos

> What's the licensing situation on this?

1. This project didn't take explicit permission from Apple to redistribute binaries

2. There are multiple jurisdictions where you don't need to explicitly have such permission, it is implied by law

3. Usage of this software implies you already have macOS system. I'm not a lawyer, but it looks to be covered by section 3 of macOS EULA.

4. There are existing precedents of redistribution of macOS binaries for multiple years aready:

- https://github.com/cirruslabs/macos-image-templates/pkgs/con...

- https://hub.docker.com/r/sickcodes/docker-osx

- https://app.vagrantup.com/jhcook/boxes/macos-sierra

And so on.

Google is “friendlier”, because they run some automated scans on the apk and you’re good. Apple has humans run your app to confirm it does what you claim, as well as a battery of automated scans and since they are using the app I’d imagine they look at network traffic as much as possible. I know iOS isn’t shielded from malicious apps, but there’s malware and viruses all over the play store. That’s because it’s free and “friendlier”.

> At Apple things have gotten way worse. Trying to automate release building is practically impossible and will require hours or CI pipeline debugging with error messages that don't mean what they say.

This isn’t Apple’s fault… every build system sucks up a decent amount of time during initial setup. You can cut down massive amounts of time between iterations by adding some common optimizations:

1. Cache artifacts when that step or job succeeds, so if a subsequent step/job fails, you can adjust it and start up where you left off, using the caches artifact to restore the workspace state. This complicates debugging efforts and I personally don’t do any optimization until the pipeline is reliably green each time. I just deal with slow builds and switch to other stuff or work ahead while they run.

2. Fail fast. The CI run should bail out if any critical steps don’t pass, so anything further down doesn’t run for no reason, burning compute time and delaying queued jobs waiting for a runner. While developing the pipeline, watch the logs and when you see something you don’t like, slap the cancel button, or collect a couple things you need to change and iterate with passes with 2-3 changes.

3. Use adequately spec’s hardware. Xcode is resource heavy and compiles need plenty of memory and cpu cores. Play around with what is a good compromise between power and cost. See if your project builds faster with more cpu cores, or faster cpu cores, etc.

> At least Googles process is quite simple and can be dockerized.

One man’s simple is another man’s “practically impossible”. Simple comes from familiarity and confidence. Anyway, you can totally run your builds in docker if you want to, and many do, but I’d personally not introduce more complexity until you have your pipelines running the slow way with the least amount of mental modeling to do. Once you know it all works, then have a go at running the build you know is good, inside a docker container (which in this case is just packing up kvm/qemu/libvirt to facilitate the running of a vm back on the host, but it means you can run mac containers on Linux runners, which will be much cheaper than Mac runners since those are usually Mac hardware)

https://github.com/sickcodes/Docker-OSX

> Also why do I have to pay Apple $125 a year when it costs $100 in the US? The exchange rate from CHF to USD should be in my favor.

Couple theories. 1. They have additional processing or tax expenses when dealing with your currency which they aren’t going to eat the cost of. 2. The higher price could be to deter abuse if for some reason there is an abnormal amount originating from accounts who pay with that currency.

You can use qemu/libvirt/kvm on any Linux host to run macOS pretty easily these days[1]. I run Ventura on unraid with nvidea gpu passthrough and it’s been fairly painless.

You can also run macOS in docker, but it’s ultimately running through qemu/kvm as well[2]

1. https://github.com/kholia/OSX-KVM

2. https://github.com/sickcodes/Docker-OSX

It would be a better idea to setup bluebubbles if you really want imessages while you wait, if you have an old laptop that you can use as a macos server. https://github.com/sickcodes/Docker-OSX is a brilliant solution for macos vm as a docker container. mac hardware not required