Software Developer (mostly Elixir).
Mainly here to read.
Fediverse https://social.deusch.me/@steffen

@steffend.me
Thank you for looking so thoroughly! Thatās doing a lot to keep us all safe šš»
Maybe a bit surprising, but the article ends with a shoutout to Phoenix and Tidewave š¬
Very nice, I wish you all the best and hope that it succeeds. Happy to pay for a personal plan once they are available š°
The thing looks awesome btw! Sorry Iām just a bit sad that such content gets exclusively posted over there š
Maybe I should tell him to not only post on the Nazi-site (or even better not post there at all) and instead do it somewhere people can actually see it, without needing a Nazi-accountā¦
You need it assuming you donāt use sticky sessions at your load balancer, otherwise individual longpoll requests might get router to different nodes and if they cannot communicate via clustering, LiveViews would frequently do full remounts when you donāt expect them to.
I heard in the podcast that youāre not planning to use clustering. That means that you also canāt use longpoll for users where websocket is broken, which could lead to bad UX. If you decide to do clustering, you could also route git through the cluster instead of deciding at the reverse proxy š
Nice, happy to help test or contribute :)
@peterullrich.com For the firecracker runners, do you plan to make those open source? I like self hosting runners, but I don't feel good using them on public repos if the jobs are not isolated. So a way to run KVM based ephemeral runners for each job would be awesome for non-hosted ones too #pushin
But the existing code is still completely fine even on latest 1.8. There is one very good reason to always update to latest, even while older versions still get security patches: they donāt get bug fixes. So you might run into known issues on older versions that wonāt get fixed.
But thatās not a reason not to update, since generally old patterns are at most deprecated and your existing code will still work (just add phoenix_view as a dependency for that example). So people sometimes feel like they need to update to the latest and greatest idioms to use latest Phoenix.
I know Iām late to hear the latest episode, but since it looks like that last post was not fully clear: what Iām trying to say is that Iāve seen people saying something similar to āoh weāre still on 1.6 because we use Phoenix.View and didnāt have time to update to Phoenix.Componentā or similar.
Apparently there is money for open source if you are racist enough
šØ Announcing Pushin šØ
Now officially: I'm announcing Pushin.eu, a git hosting platform built and run entirely in Europe. Think GitHub/GitLab but European, better, and faster. Built with #ElixirLang and #RustLang.
Just CLONE the repo. Thereās no fucking need to render commits and blames to HTML for your stupid scraping. And they call it artificial INTELLIGENCE.
And thatās still the reasonable part. Add those to robots.txt and youāll get tons of requests from residential proxies claiming to be chrome on windows etc.; I had to shut my forgejo hosted Linux repo down and move it to GitHub due to those stupid crawlers.
btw nice to see a privacy policy on the site now, note that it does not render nicely on mobile at the moment
@peterullrich.com if you need a stresstest for pushin.eu, host a fork of the Linux kernel or another repository with 100000+ commits. I just had to make another repository on my Foregjo instance private because AI crawlers pinned my CPU at 100% for hours, trying to crawl git blames of a mesa forkā¦