Quadlet: ищите исходник, если сервис не появился Файл .container ещё не systemd-сервис. При загрузке и перечитывании конфигурации генератор Quadlet превращает его в .service. Если сервис не найден, проверьте каталог исходника и контекст systemd: rootless работает с пользовательскими units, rootful — с системными. Затем проверьте вывод генератора в режиме dry-run. Ошибка синтаксиса или опция из более новой версии Po…

Channel
Библиотека девопса | DevOps, SRE, Sysadmin
@devopsslib
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Polls · Citations · Telegram's recommendations · Cite this entry
10,326subscribers
-85 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001261760700 |
|---|---|
| Type | Channel |
| Username | @devopsslib |
| Description | Все самое полезное для девопсера в одном канале. Наши курсы: https://clc.to/ZJ7Z1w По рекламе: @tproger_sales_bot Для обратной связи: @proglibrary_feeedback_bot РКН: https://gosuslugi.ru/snet/6798b4e4509aba56522d1787 Заявка: 8137718351 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 54 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/devopsslib |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 07:18 | 10,326 | -1 |
| 8 Nov 2026, 17:16 | 10,327 | -1 |
| 7 Nov 2026, 10:56 | 10,328 | -3 |
| 6 Nov 2026, 08:49 | 10,331 | +2 |
| 5 Nov 2026, 09:57 | 10,329 | +1 |
| 2 Nov 2026, 12:28 | 10,328 | -3 |
| 1 Nov 2026, 13:09 | 10,331 | -2 |
| 31 Oct 2026, 10:36 | 10,333 | -3 |
| 30 Oct 2026, 08:54 | 10,336 | -4 |
| 29 Oct 2026, 08:17 | 10,340 | +2 |
| 28 Oct 2026, 04:27 | 10,338 | -4 |
| 27 Oct 2026, 04:37 | 10,342 | -5 |
| 26 Oct 2026, 04:20 | 10,347 | -8 |
| 24 Oct 2026, 08:05 | 10,355 | -2 |
| 23 Oct 2026, 04:37 | 10,357 | -3 |
| 22 Oct 2026, 06:45 | 10,360 | -1 |
| 21 Oct 2026, 00:57 | 10,361 | -2 |
| 19 Oct 2026, 21:45 | 10,363 | -3 |
| 18 Oct 2026, 03:06 | 10,366 | +2 |
| 16 Oct 2026, 03:06 | 10,364 | first reading |
Engagement
47 posts held, back to 21 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 56 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 8.28%
- avg views ÷ 10,326 subscribers
- Avg views / post
- 855
- 26 posts measured
- Reaction rate
- 0.173%
- reactions ÷ views · ER floor
- Posts in window
- 26
- of 47 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 4 of 26 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 47 (21 July 2026 – 11 November 2026) |
| Views total | 22,236 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 11:16 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- ≈2,070
- Videos
- ≈84
- Links
- ≈3,540
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 8s
- Average length
- 8s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
119 reactions across 19 posts, in 13 distinct kinds. The most used accounts for 31.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ⚡ | 38 | 31.9% | |
| 👍 | 28 | 23.5% | |
| ❤ | 23 | 19.3% | |
| 😁 | 8 | 6.72% | |
| 🔥 | 5 | 4.20% | |
| 🎉 | 4 | 3.36% | |
| 🤩 | 4 | 3.36% | |
| 🌚 | 2 | 1.68% | |
| 💯 | 2 | 1.68% | |
| 🤔 | 2 | 1.68% | |
| 👏 | 1 | 0.84% | |
| 👾 | 1 | 0.84% | |
| 😢 | 1 | 0.84% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 47 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 119 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 47 most recent posts we hold, published 21 July 2026 to 11 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 26 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
PreSync-миграция должна выдерживать повторный запуск При полном sync в Argo CD hook может запуститься снова из-за изменения, не связанного с БД. Поэтому миграционный скрипт должен учитывать уже выполненные шаги и безопасно переносить повторный запуск. Пароль тоже зависит от порядка фаз. PreSync идёт раньше обычного Secret из того же Application. Hook получит старое значение или не запустится, если Secret ещё нет. В…
Stern читает логи в двух режимах Stern собирает логи нескольких Pod и контейнеров Kubernetes. В режиме живого слежения он подхватывает новые подходящие Pod. Но перед широким запросом стоит проверить --max-log-requests. Без --no-follow значение по умолчанию — 50. При достижении лимита одновременных запросов Stern завершается с ошибкой. С --no-follow значение по умолчанию — 5: оно ограничивает число параллельных чте…
Ротация токена не сбрасывает кэш BuildKit Содержимое build-secret не входит в ключ кэша Docker BuildKit. Если заменить только токен, закэшированный шаг может сохраниться. Secret ID и путь монтирования участвуют в cache checksum. Их изменение инвалидирует кэш. Если после ротации нужно выполнить шаг заново, Docker предлагает менять build argument этого шага с произвольной несекретной ревизией. Сам токен передают чер…
Запись создана. Почему DNS ещё отвечает NXDOMAIN? Рекурсивный резолвер мог получить NXDOMAIN ещё до создания записи и сохранить отрицательный ответ. Изменение авторитетной зоны само по себе не стирает этот кэш. По RFC 2308 TTL такого ответа берут как минимум из SOA.MINIMUM и TTL самой SOA. Пока ответ хранится в кэше, TTL отсчитывается вниз. После нуля использовать этот кэшированный ответ нельзя. На схеме условный …
Опечатку в matrix можно поймать до запуска CI В матрице workflow объявлен os, а в runs-on указан matrix.arch. actionlint замечает отсутствующее свойство локально, без отправки workflow на GitHub. В примере на карточке actionlint 1.7.12 для macOS arm64 вернул exit 1 с диагностикой про arch. После единственной замены matrix.arch на matrix.os тот же вызов вернул exit 0 без сообщений. Использован официальный бинарник, …
Куда положить pod name в Loki Имена Pod и process ID дают много уникальных значений. Если сделать их индексными labels в Loki, растёт кардинальность индекса. Structured metadata позволяет прикрепить такие поля к записи без индексации и без добавления в текст лога. Поля возвращаются с результатами запроса, по ним можно фильтровать. Для этого нужны индекс tsdb, schema ≥13, chunk format V4 и включённый allow_structure…
Проверяем HTTPS на другом IP curl --resolve подменяет адрес только для заданной пары hostname:port. Имя из URL остаётся в SNI и используется для проверки сертификата. Одного заголовка Host для этого недостаточно. Локальный стенд на карточке: TLS-сервер на 127.0.0.1:8443, сертификат с SAN app.test, тестовый CA в ca.pem. Команда выполнена в zsh на macOS с curl 8.7.1. Сервер получил SNI app.test и Host app.test:8443. …
Pod уже удаляется, а serving всё ещё true У endpoint в EndpointSlice есть три условия: serving, terminating и ready. Для Pod поле serving отражает его Ready. Значение terminating становится true, когда Pod получает deletion timestamp, обычно ещё до остановки контейнеров. Поэтому сочетание serving=true, terminating=true возможно. Значение ready при этом false: оно означает «обслуживает и не завершается». Исключение …
❤1👍1
Lockfile с ноутбука может не покрывать Linux runner Если provider впервые установили из mirror, в .terraform.lock.hcl могут остаться checksums только текущей платформы. На другой архитектуре проверка пакета тогда не сойдётся. Это возможный сценарий, не обязательный сбой любого macOS → Linux. В каталоге корневого модуля Terraform 0.14+ можно заранее добавить суммы для целевых платформ: terraform providers lock \ -…
🔐 Высокий score systemd — повод открыть настройки сервиса У systemd-analyze есть проверка sandboxing-настроек unit. Для Linux с systemd и установленным nginx: systemd-analyze security --no-pager nginx.service Подставьте свой service unit и проверьте поддержку команды в установленной версии. Она читает конфигурацию, ничего не меняет. Нужен доступ к system manager. В ответе будет таблица ограничений и overall exposur…
👍2👏1
Почему memory_limiter ставят перед batch В OpenTelemetry Collector порядок processors влияет на то, куда вернётся отказ при нехватке памяти. README рекомендует memory_limiter первым, чтобы backpressure дошёл до receiver. Фрагмент списка processors в своём pipeline: processors: [memory_limiter, batch] Оба processor нужно отдельно объявить в конфигурации. Проверьте их наличие в своей версии и сборке Collector. При п…
Showing the 12 most recent of 47 posts we hold for @devopsslib. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Posts recorded as deleted after publishing
We recorded 3 posts on @devopsslib as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 10 November 2026
- Most recent seen missing
- 10 November 2026
- Median time before seen missing
- 15 days
- Seen missing in the last 30 days
- 3
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Преимущество __serialize()/__unserialize() (PHP 7.4) над __sleep()/__wakeup()?
- Быстрее в 10 раз23%
- Возвращает/принимает произвольный массив32%
- Работает без объявления в классе23%
- Автоматически даёт JSON22%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 47 most recent posts we hold, published 21 July 2026 to 11 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
@proglib_academy · 3,8404 postsБиблиотека собеса по DevOps | вопросы с собеседований
@devops_interview_lib · 3,4771 postБиблиотека задач по DevOps | тесты, код, задания
@devops_problems_lib · 3,0131 postБиблиотека задач по PHP | тесты, код, задания
@php_problems_lib · 2,2751 post
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 8 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
@devopssjob · 4,57524 postsБиблиотека программиста 🇷🇺
@lib_it3 · 994 postsПубликация вакансий в Proglib.io
@proglib_hh · 3224 postsПрайс - Библиотека программиста (Proglib.io)
@proglib_advertising · 1012 postsФреймворк Django
@django360 · 111 postIT Channels 🌍
@itchannels · 2,0661 postPython в Telegram
@itpython · 171 posttalismanovIT
@talismanovIT · 1641 post
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@hahacker_news · 25,231
Telegram ranks this channel #5 of 59 here — alongside 58 others — read 14 September 2026
@DevOPSitsec · 23,892
Telegram ranks this channel #7 of 90 here — alongside 89 others — read 18 September 2026
@ITSTAND_ORG · 164,814
Telegram ranks this channel #8 of 98 here — alongside 97 others — read 9 September 2026
@devopsina · 23,569
Telegram ranks this channel #9 of 90 here — alongside 89 others — read 18 September 2026
@bashdays · 23,621
Telegram ranks this channel #10 of 94 here — alongside 93 others — read 18 September 2026
@pyproglib · 36,972
Telegram ranks this channel #11 of 84 here — alongside 83 others — read 1 September 2026
@devopslibrary · 19,870
Telegram ranks this channel #12 of 94 here — alongside 93 others — read 30 September 2026
@goproglib · 23,894
Telegram ranks this channel #16 of 91 here — alongside 90 others — read 17 September 2026
@rebrain_devops · 28,735
Telegram ranks this channel #16 of 94 here — alongside 93 others — read 9 September 2026
@proglibrary · 77,612
Telegram ranks this channel #17 of 82 here — alongside 81 others — read 19 August 2026
@devopsforlove · 44,606
Telegram ranks this channel #20 of 95 here — alongside 94 others — read 9 September 2026
@devops_jobs_feed · 22,271
Telegram ranks this channel #24 of 95 here — alongside 94 others — read 22 September 2026
@javaproglib · 21,787
Telegram ranks this channel #25 of 88 here — alongside 87 others — read 21 September 2026
@linuxacademiya · 28,647
Telegram ranks this channel #26 of 84 here — alongside 83 others — read 9 September 2026
@Selectel · 62,423
Telegram ranks this channel #35 of 96 here — alongside 95 others — read 21 August 2026
@frontendproglib · 20,611
Telegram ranks this channel #36 of 93 here — alongside 92 others — read 25 September 2026
@Golang_google · 40,453
Telegram ranks this channel #36 of 90 here — alongside 89 others — read 30 August 2026
@srv_admin · 32,701
Telegram ranks this channel #40 of 96 here — alongside 95 others — read 5 September 2026
@os_linux_ru · 19,536
Telegram ranks this channel #46 of 87 here — alongside 86 others — read 1 October 2026
@i_odmin_book · 18,778
Telegram ranks this channel #52 of 83 here — alongside 82 others — read 5 October 2026
@i_odmin · 26,713
Telegram ranks this channel #52 of 89 here — alongside 88 others — read 12 September 2026
This channel appears in 21 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 10 November 2026 — this entry's latest reading, not the date you are reading this.
“Библиотека девопса | DevOps, SRE, Sysadmin” (@devopsslib), 10,326 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/devopsslib.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.