# horizon Published articles for horizon. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Logarithmic auto-scaling for Laravel Horizon DevFeed: [Logarithmic auto-scaling for Laravel Horizon]() Original publisher: [Read original article]() Author: Freek Van der Herten (freek@spatie.be) Published: 2026-09-12T12:30:30Z Content type: article Language: en Sources: [freek.dev - all blogposts]() Topics: [Laravel](), [realtime](), [Development]() Tags: [horizon](), [laravel](), [performance](), [queues](), [realtime](), [scaling]() ### AI overview This article explains how logarithmic auto-scaling can be added to Laravel Horizon. Log-based weighting helps prevent large queue spikes from starving smaller realtime queues while still allocating enough workers to large backlogs. ### Source excerpt A thoughtful write-up on adding logarithmic auto-scaling to Laravel Horizon. It shows how log-based weighting keeps huge queue spikes from starving smaller realtime queues while still giving large backlogs enough workers. Read more ## Stepping Out Of The Knowledge Zone DevFeed: [Stepping Out Of The Knowledge Zone]() Original publisher: [Read original article]() Published: 2022-04-13T00:00:00Z Content type: opinion Language: en Sources: [Artsy]() Topics: [Elixir](), [Learning](), [Ruby](), [Rails]() Tags: [backend](), [blog](), [blog-post](), [cypress](), [elixir](), [forque](), [front-end](), [horizon](), [integrity](), [learning](), [ruby](), [ruby-on-rails](), [teams](), [velocity]() ### AI overview A first-person reflection on moving beyond familiar Ruby on Rails work and embracing the challenge of learning Elixir. The author connects this transition to Artsy shipping work and a broader willingness to remain open to being a beginner. ### Source excerpt As I am writing my first blog post for Artsy, here is a short introduction on who I am: My name is Kaja and I am an engineer in our Berlin entity. As a Ruby-born programmer I am calling myself a backend engineer, but that also may change and is more about emotional identification and less about what I actually do (as you will see in this blog post). My background is not in engineering at all. In university I graduated in philosophy and historical linguistics, both the most impractical but most beautifully theoretical subjects I can think of. I really love being in the world of ideas and thought experiments that challenge the current status of what is, as opposed to what is thinkable. At Artsy I am currently working in the PX (Partner Experience) Team and since I joined 1 year ago, most of my time in the PX team has been dedicated to the implementation of the Artsy Shipping feature. In the backend I helped tying the ties between the external ARTA-API (a white glove shipping company) and our own service that is managing the shipping and order statuses of the artworks that are ordered online. In the front end I implemented some forms for that feature and some so called hooks. I felt like a fish in the water with these tasks, because the company that I had worked at before was a shipping company and I did the same thing from the other side of the API relationship. In the same language (Ruby on Rails). Here is another fact about me that is a premises for what comes next: I enjoy to be a learner of new things much more than being an expert about things that I already know. Of course being an expert is also flattering the ego, but after a while it can feel repetitive and make your soul feel old and tired. While the experience of being new to something and not an expert at all can give you a rejuvenating prickle. On the other side it can be scary to admit not knowing something and also the ego will feel small and hurt. But I learned that overcoming the hurt ego is my way to ## Ubuntu 18.04 images published in cPouta and ePouta DevFeed: [Ubuntu 18.04 images published in cPouta and ePouta]() Original publisher: [Read original article]() Author: Unknown (noreply@blogger.com) Published: 2018-10-17T07:30:00Z Content type: release Language: en Sources: [CSC - IT Center For Science - Cloud Team]() Topics: [Ubuntu](), [Cloud](), [ssh](), [Command-line interface](), [releases]() Tags: [cli](), [cloud](), [cpouta](), [diskimage](), [ed25519](), [epouta](), [horizon](), [image](), [lts](), [openstack](), [release](), [ssh](), [ubuntu]() ### AI overview Ubuntu 18.04 LTS images are available in the cPouta and ePouta cloud environments. The article explains that the images use Canonical's unmodified image, the default SSH user is ubuntu, and users can upload other Ubuntu cloud images or configure users with cloud-init and the OpenStack CLI. ### Source excerpt Hello Ubuntu fan boys and girls! An image containing latest LTS Ubuntu release (18.04 Bionic Beaver) is now available in c and ePouta! This time we opted to use the image provided by Canonical without any modifications. This means the user used to ssh in is now "ubuntu" instead of "cloud-user". In any case, trying to ssh in as root will tell you which user to ssh in as In case you want to try even newer versions of Ubuntu, say the "in-between" releases like 18.10 Cosmic Cuttlefish - head over to http://cloud-images.ubuntu.com/ , select the release and fetch the "cloudimg-amd64.img" - for example "cosmic-server-cloudimg-amd64.img" - which is a QCOW2 image. This you can then upload as an image in your c/ePouta project. Our user guide has some pictures and instructions how to work with and upload new images: https://research.csc.fi/pouta-adding-images To add your ssh key under a new "cloud-user" (in case you don't want to use ubuntu user) you can do something like below. First create a file that has the cloud-init user data. Then use that file as input to the openstack CLI tool. $ cat cloud-init.cfg #cloud-config users: - default: - default_user: name: cloud-user gecos: Cloud User sudo: ["ALL=(ALL) NOPASSWD:ALL"] ssh_authorized_keys: - ssh-ed25519 AAAAMYKEYQ user@email.example.org And then the openstack CLI command : $ openstack server create ubuntu1804 --flavor standard.small --image Ubuntu-18.04 --key mykey --security-group default --security-group ssh-group --user-data cloud-init.cfg It is if course possible to use horizon to supply the user data as well. p.s. Yes, ed25519 keys works this way! The web interface openstack horizon still does not support them yet.