Currently translated at 100.0% (1178 of 1178 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1178 of 1178 strings)
Translated using Weblate (German)
Currently translated at 100.0% (1174 of 1174 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1174 of 1174 strings)
Translated using Weblate (German)
Currently translated at 100.0% (1172 of 1172 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1172 of 1172 strings)
Co-authored-by: Marco <marco@nanoweb.ch>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de/
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de_CH/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1178 of 1178 strings)
Translated using Weblate (Slovak)
Currently translated at 100.0% (1174 of 1174 strings)
Translated using Weblate (Slovak)
Currently translated at 100.0% (1172 of 1172 strings)
Co-authored-by: Jozef Gaal <preklady@mayday.sk>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/sk/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1178 of 1178 strings)
Translated using Weblate (French)
Currently translated at 100.0% (1174 of 1174 strings)
Translated using Weblate (French)
Currently translated at 100.0% (1172 of 1172 strings)
Co-authored-by: Cyril59310 <archas.cyril@hotmail.fr>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/fr/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1161 of 1161 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1161 of 1161 strings)
Translated using Weblate (German)
Currently translated at 99.9% (1160 of 1161 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 99.9% (1160 of 1161 strings)
Co-authored-by: Marco <marco@nanoweb.ch>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de/
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de_CH/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1160 of 1160 strings)
Translated using Weblate (Italian)
Currently translated at 100.0% (1154 of 1154 strings)
Translated using Weblate (Italian)
Currently translated at 100.0% (1154 of 1154 strings)
Co-authored-by: Gringo <ita.translations@tiscali.it>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/it/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1160 of 1160 strings)
Translated using Weblate (French)
Currently translated at 100.0% (1154 of 1154 strings)
Translated using Weblate (French)
Currently translated at 100.0% (1143 of 1143 strings)
Co-authored-by: Cyril59310 <archas.cyril@hotmail.fr>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/fr/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1160 of 1160 strings)
Translated using Weblate (Bulgarian)
Currently translated at 100.0% (1154 of 1154 strings)
Translated using Weblate (Bulgarian)
Currently translated at 100.0% (1143 of 1143 strings)
Co-authored-by: MrEddX <mreddx@chatrix.one>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/bg/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1160 of 1160 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1160 of 1160 strings)
Translated using Weblate (German)
Currently translated at 100.0% (1154 of 1154 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1154 of 1154 strings)
Translated using Weblate (German)
Currently translated at 100.0% (1143 of 1143 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1143 of 1143 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1139 of 1139 strings)
Co-authored-by: Marco <marco@nanoweb.ch>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de/
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de_CH/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 96.5% (1100 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 95.9% (1093 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 92.2% (1051 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 91.5% (1043 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 82.7% (942 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 82.2% (937 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 78.3% (892 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 77.4% (882 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 76.4% (871 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 75.5% (860 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 75.5% (860 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 73.6% (839 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 70.6% (805 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 66.1% (754 of 1139 strings)
Translated using Weblate (Slovak)
Currently translated at 65.8% (750 of 1139 strings)
Co-authored-by: Jozef Gaal <preklady@mayday.sk>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/sk/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1160 of 1160 strings)
Translated using Weblate (Chinese (Simplified))
Currently translated at 100.0% (1154 of 1154 strings)
Translated using Weblate (Chinese (Simplified))
Currently translated at 100.0% (1139 of 1139 strings)
Co-authored-by: AnnAngela <naganjue@vip.qq.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/zh_Hans/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1160 of 1160 strings)
Translated using Weblate (Portuguese (Brazil))
Currently translated at 100.0% (1154 of 1154 strings)
Translated using Weblate (Portuguese (Brazil))
Currently translated at 100.0% (1143 of 1143 strings)
Translated using Weblate (Portuguese (Brazil))
Currently translated at 100.0% (1139 of 1139 strings)
Co-authored-by: Aluisio <aluisiodeavila@hotmail.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/pt_BR/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1154 of 1154 strings)
Translated using Weblate (Croatian)
Currently translated at 100.0% (1143 of 1143 strings)
Translated using Weblate (Croatian)
Currently translated at 100.0% (1139 of 1139 strings)
Co-authored-by: Ivan Bratović <ivanbratovic4@gmail.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/hr/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1139 of 1139 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1139 of 1139 strings)
Translated using Weblate (German)
Currently translated at 100.0% (1134 of 1134 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1134 of 1134 strings)
Co-authored-by: Marco <marco@nanoweb.ch>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de/
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de_CH/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 99.0% (1121 of 1132 strings)
Translated using Weblate (Spanish)
Currently translated at 98.4% (1115 of 1132 strings)
Translated using Weblate (Spanish)
Currently translated at 96.5% (1093 of 1132 strings)
Co-authored-by: Àlex <ladiv12@pm.me>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/es/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1127 of 1127 strings)
Translated using Weblate (Croatian)
Currently translated at 100.0% (1125 of 1125 strings)
Translated using Weblate (Croatian)
Currently translated at 100.0% (1124 of 1124 strings)
Co-authored-by: Ivan Bratović <ivanbratovic4@gmail.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/hr/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1127 of 1127 strings)
Translated using Weblate (Ukrainian)
Currently translated at 100.0% (1125 of 1125 strings)
Translated using Weblate (Ukrainian)
Currently translated at 100.0% (1121 of 1121 strings)
Translated using Weblate (Ukrainian)
Currently translated at 96.4% (1074 of 1113 strings)
Co-authored-by: stanol <stanol777@gmail.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/uk/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1127 of 1127 strings)
Translated using Weblate (Portuguese (Brazil))
Currently translated at 100.0% (1125 of 1125 strings)
Translated using Weblate (Portuguese (Brazil))
Currently translated at 100.0% (1121 of 1121 strings)
Translated using Weblate (Portuguese (Brazil))
Currently translated at 100.0% (1113 of 1113 strings)
Translated using Weblate (Portuguese (Brazil))
Currently translated at 100.0% (1111 of 1111 strings)
Co-authored-by: Aluisio <aluisiodeavila@hotmail.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/pt_BR/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1125 of 1125 strings)
Translated using Weblate (Persian)
Currently translated at 100.0% (1125 of 1125 strings)
Translated using Weblate (Persian)
Currently translated at 100.0% (1121 of 1121 strings)
Translated using Weblate (Persian)
Currently translated at 100.0% (1121 of 1121 strings)
Translated using Weblate (Persian)
Currently translated at 100.0% (1111 of 1111 strings)
Co-authored-by: Alex Javadi <15309978+aljvdi@users.noreply.github.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/fa/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1127 of 1127 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1127 of 1127 strings)
Translated using Weblate (German)
Currently translated at 100.0% (1125 of 1125 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1125 of 1125 strings)
Translated using Weblate (German)
Currently translated at 100.0% (1125 of 1125 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1125 of 1125 strings)
Translated using Weblate (German)
Currently translated at 100.0% (1111 of 1111 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1111 of 1111 strings)
Co-authored-by: Marco <marco@nanoweb.ch>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de/
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de_CH/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1127 of 1127 strings)
Translated using Weblate (Bulgarian)
Currently translated at 100.0% (1125 of 1125 strings)
Translated using Weblate (Bulgarian)
Currently translated at 100.0% (1121 of 1121 strings)
Translated using Weblate (Bulgarian)
Currently translated at 100.0% (1113 of 1113 strings)
Translated using Weblate (Bulgarian)
Currently translated at 100.0% (1111 of 1111 strings)
Co-authored-by: MrEddX <mreddx@chatrix.one>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/bg/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1127 of 1127 strings)
Translated using Weblate (French)
Currently translated at 100.0% (1125 of 1125 strings)
Translated using Weblate (French)
Currently translated at 100.0% (1121 of 1121 strings)
Translated using Weblate (French)
Currently translated at 100.0% (1113 of 1113 strings)
Translated using Weblate (French)
Currently translated at 100.0% (1111 of 1111 strings)
Co-authored-by: Cyril59310 <archas.cyril@hotmail.fr>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/fr/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1069 of 1069 strings)
Translated using Weblate (Lithuanian)
Currently translated at 100.0% (1069 of 1069 strings)
Translated using Weblate (Lithuanian)
Currently translated at 100.0% (1069 of 1069 strings)
Translated using Weblate (Lithuanian)
Currently translated at 89.5% (957 of 1069 strings)
Translated using Weblate (Lithuanian)
Currently translated at 88.4% (945 of 1069 strings)
Co-authored-by: mantak <mantaksam@gmail.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/lt/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1069 of 1069 strings)
Translated using Weblate (Ukrainian)
Currently translated at 100.0% (1067 of 1067 strings)
Translated using Weblate (Ukrainian)
Currently translated at 100.0% (1061 of 1061 strings)
Co-authored-by: stanol <stanol777@gmail.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/uk/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1069 of 1069 strings)
Translated using Weblate (French)
Currently translated at 100.0% (1067 of 1067 strings)
Translated using Weblate (French)
Currently translated at 100.0% (1061 of 1061 strings)
Co-authored-by: Cyril59310 <archas.cyril@hotmail.fr>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/fr/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1069 of 1069 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1069 of 1069 strings)
Translated using Weblate (German)
Currently translated at 100.0% (1067 of 1067 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1067 of 1067 strings)
Translated using Weblate (German)
Currently translated at 100.0% (1061 of 1061 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1061 of 1061 strings)
Co-authored-by: Marco <marco@nanoweb.ch>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de/
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de_CH/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1069 of 1069 strings)
Translated using Weblate (Bulgarian)
Currently translated at 100.0% (1067 of 1067 strings)
Translated using Weblate (Bulgarian)
Currently translated at 100.0% (1061 of 1061 strings)
Translated using Weblate (Bulgarian)
Currently translated at 100.0% (1055 of 1055 strings)
Co-authored-by: MrEddX <mreddx@chatrix.one>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/bg/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 62.8% (662 of 1053 strings)
Translated using Weblate (Basque)
Currently translated at 62.0% (653 of 1053 strings)
Translated using Weblate (Basque)
Currently translated at 61.9% (652 of 1053 strings)
Translated using Weblate (Basque)
Currently translated at 59.1% (623 of 1053 strings)
Co-authored-by: Unai Tolosa Pontesta <utolosa002@gmail.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/eu/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1053 of 1053 strings)
Translated using Weblate (Japanese)
Currently translated at 100.0% (1053 of 1053 strings)
Translated using Weblate (Japanese)
Currently translated at 100.0% (1053 of 1053 strings)
Co-authored-by: KEINOS <github@keinos.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/ja/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1053 of 1053 strings)
Translated using Weblate (French)
Currently translated at 100.0% (1053 of 1053 strings)
Translated using Weblate (French)
Currently translated at 100.0% (1053 of 1053 strings)
Co-authored-by: Cyril59310 <archas.cyril@hotmail.fr>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/fr/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1053 of 1053 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1053 of 1053 strings)
Translated using Weblate (German)
Currently translated at 100.0% (1062 of 1062 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (1062 of 1062 strings)
Co-authored-by: Marco <marco@nanoweb.ch>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de/
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de_CH/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (1016 of 1016 strings)
Translated using Weblate (Indonesian)
Currently translated at 95.1% (967 of 1016 strings)
Co-authored-by: Harry Suryapambagya <harsxv@gmail.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/id/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 94.5% (904 of 956 strings)
Translated using Weblate (Chinese (Traditional))
Currently translated at 94.3% (902 of 956 strings)
Translated using Weblate (Chinese (Traditional))
Currently translated at 91.9% (879 of 956 strings)
Co-authored-by: Max <max.tsai@alfred.camera>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/zh_Hant/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 69.9% (660 of 944 strings)
Translated using Weblate (Japanese)
Currently translated at 67.9% (641 of 944 strings)
Translated using Weblate (Japanese)
Currently translated at 67.7% (640 of 944 strings)
Co-authored-by: KEINOS <github@keinos.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/ja/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 99.5% (953 of 957 strings)
Translated using Weblate (Czech)
Currently translated at 100.0% (944 of 944 strings)
Translated using Weblate (Czech)
Currently translated at 100.0% (944 of 944 strings)
Co-authored-by: Michal <black23@gmail.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/cs/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (957 of 957 strings)
Translated using Weblate (Finnish)
Currently translated at 100.0% (956 of 956 strings)
Translated using Weblate (Finnish)
Currently translated at 100.0% (944 of 944 strings)
Co-authored-by: Ilkka Myller <ilkka.myller@nodefield.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/fi/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (957 of 957 strings)
Translated using Weblate (Swedish)
Currently translated at 100.0% (956 of 956 strings)
Translated using Weblate (Swedish)
Currently translated at 100.0% (944 of 944 strings)
Co-authored-by: Gunnar Norin <gunnar.norin@gmail.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/sv/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (957 of 957 strings)
Translated using Weblate (Romanian)
Currently translated at 100.0% (956 of 956 strings)
Translated using Weblate (Romanian)
Currently translated at 100.0% (944 of 944 strings)
Translated using Weblate (Romanian)
Currently translated at 99.8% (944 of 945 strings)
Co-authored-by: kindercat <156439718+kindercat@users.noreply.github.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/ro/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (957 of 957 strings)
Translated using Weblate (Ukrainian)
Currently translated at 100.0% (956 of 956 strings)
Translated using Weblate (Ukrainian)
Currently translated at 100.0% (945 of 945 strings)
Co-authored-by: stanol <stanol777@gmail.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/uk/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (957 of 957 strings)
Translated using Weblate (Turkish)
Currently translated at 100.0% (956 of 956 strings)
Translated using Weblate (Turkish)
Currently translated at 100.0% (944 of 944 strings)
Translated using Weblate (Turkish)
Currently translated at 100.0% (945 of 945 strings)
Co-authored-by: Ömer Faruk Genç <omer@farukgenc.com>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/tr/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (957 of 957 strings)
Translated using Weblate (French)
Currently translated at 100.0% (956 of 956 strings)
Translated using Weblate (French)
Currently translated at 100.0% (945 of 945 strings)
Co-authored-by: Cyril59310 <archas.cyril@hotmail.fr>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/fr/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (957 of 957 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (957 of 957 strings)
Translated using Weblate (German)
Currently translated at 100.0% (956 of 956 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (956 of 956 strings)
Translated using Weblate (German)
Currently translated at 100.0% (945 of 945 strings)
Translated using Weblate (German (Switzerland))
Currently translated at 100.0% (945 of 945 strings)
Co-authored-by: Marco <marco@nanoweb.ch>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de/
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/de_CH/
Translation: Uptime Kuma/Uptime Kuma
Currently translated at 100.0% (957 of 957 strings)
Translated using Weblate (Bulgarian)
Currently translated at 100.0% (956 of 956 strings)
Translated using Weblate (Bulgarian)
Currently translated at 99.8% (943 of 944 strings)
Translated using Weblate (Bulgarian)
Currently translated at 100.0% (945 of 945 strings)
Co-authored-by: MrEddX <mreddx@chatrix.one>
Translate-URL: https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/bg/
Translation: Uptime Kuma/Uptime Kuma
- show PORT (cloned switchcase from discord,squadcast,servenio)
- show monitorName in the first row to get on point also from messagge preview notification
- avoid duplication of monitorName and monitorName in the message content
There are a lot of changes here:
-Fixed a lot of issues encountered during my testing
-JSON path is evaluated BEFORE making comparisons (this was the true intended behavior by @chakflying)
-Variable name changes (cosmetic)
-Added != operator
-Changed jsonQueryDescription (again)
Further testing of SNMP feat, however I'm running into the issue `Error in SNMP check: RequestTimedOutError: Request timed out` when the check function is called. I am unsure as to why since my local SNMP script works great with very similar code.
This commit introduces a new SNMP monitor feature to the application, allowing users to monitor devices using SNMP (Simple Network Management Protocol).
🚫 **We kindly ask you to refrain from pinging maintainers unless absolutely necessary. Pings are reserved for critical/urgent issues that require immediate attention.**
**Why**: Reserving pings for urgent matters ensures maintainers can prioritize critical tasks effectively
- type:checkboxes
id:no-duplicate-question
attributes:
label:⚠️ Please verify that your question has not already been reported
description:|
To avoid duplicate reports, please search for any existing issues before submitting a new one. You can find the list of existing issues **[HERE](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue%20sort%3Acreated-desc%20)**.
options:
- label:|
I have searched the [existing issues](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue%20sort%3Acreated-desc%20) and found no similar reports.
required:true
- type:checkboxes
id:security-policy
attributes:
label:🛡️ Security Policy
description:|
Please review and acknowledge the Security Policy before reporting any security-related issues or bugs. You can find the full Security Policy **[HERE](https://github.com/louislam/uptime-kuma/security/policy)**.
options:
- label:|
I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy).
required:true
- type:textarea
id:steps-to-reproduce
validations:
required:true
attributes:
label:📝 Describe your problem
description:|
Please walk us through it step by step. Include all important details and add screenshots where appropriate
placeholder:|
Describe what are you asking for ...
- type:textarea
id:error-msg
attributes:
label:📝 Error Message(s) or Log
description:|
Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
render:bash session
validations:
required:false
- type:input
id:uptime-kuma-version
attributes:
label:🐻 Uptime-Kuma Version
description:|
What version of Uptime-Kuma are you running? Please do not provide Docker tags like `latest` or `1`.
placeholder:|
e.g., 1.23.16 or 2.0.0-beta.2
validations:
required:true
- type:input
id:operating-system
attributes:
label:💻 Operating System and Arch
description:|
Which OS is your server/device running on? (For Replit, please do not report this bug)
placeholder:|
e.g., Ubuntu Server 24.04.2 LTS (GNU/Linux 6.8.0-55-generic x86_64)
validations:
required:true
- type:input
id:browser-vendor
attributes:
label:🌐 Browser
description:|
Which browser are you running on? (For Replit, please do not report this bug)
placeholder:|
e.g., Google Chrome 134.0.6998.183 (Official Build) (64-bit)
validations:
required:true
- type:textarea
id:deployment-info
attributes:
label:🖥️ Deployment Environment
description:|
Provide details about the deployment environment, including runtime components, databases, and storage configurations. This will
help assess the infrastructure and identify any potential compatibility requirements.
**Remove any fields that do not apply to your setup.**
value:|
- **Runtime Environment**:
- Docker: Version `X.X.X` (Build `Y.Y.Y`)
- Docker Compose: Version `X.X.X`
- Portainer (BE/CE): Version `X.X.X` (LTS: Yes/No)
- MariaDB: Version `X.X.X` (LTS: Yes/No)
- Node.js: Version `X.X.X` (LTS: Yes/No)
- Kubernetes (K3S/K8S): Version `X.X.X` (LTS: Yes/No, via `[method/tool]`)
description:"Submit a bug report to help us improve"
#title: "[Bug] "
labels:[bug]
body:
- type:textarea
id:related-issues
validations:
required:true
attributes:
label:"📑 I have found these related issues/pull requests"
description:"Search related issues by clicking [HERE](https://github.com/louislam/uptime-kuma/issues?q=) and explain what the difference between them or explain that you are unable to find any related issues"
placeholder:"Related to #1 by also touching the ... system. They should not be merged because ..."
- type:checkboxes
attributes:
label:"🛡️ Security Policy"
description:Please review the security policy before reporting security related issues/bugs.
options:
- label:I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy)
required:true
- type:textarea
id:description
validations:
required:false
attributes:
label:"Description"
description:"You could also upload screenshots"
- type:textarea
id:steps-to-reproduce
validations:
required:true
attributes:
label:"👟 Reproduction steps"
description:"How do you trigger this bug? Please walk us through it step by step. Include all important details and add screenshots where appropriate"
placeholder:"..."
- type:textarea
id:expected-behavior
validations:
required:true
attributes:
label:"👀 Expected behavior"
description:"What did you think would happen?"
placeholder:"..."
- type:textarea
id:actual-behavior
validations:
required:true
attributes:
label:"😓 Actual Behavior"
description:"What actually happen?"
placeholder:"..."
- type:input
id:uptime-kuma-version
attributes:
label:"🐻 Uptime-Kuma Version"
description:"Which version of Uptime-Kuma are you running? Please do NOT provide the docker tag such as latest or 1"
placeholder:"Ex. 1.10.0"
validations:
required:true
- type:input
id:operating-system
attributes:
label:"💻 Operating System and Arch"
description:"Which OS is your server/device running on? (For Replit, please do not report this bug)"
🚫 **We kindly ask you to refrain from pinging maintainers unless absolutely necessary. Pings are reserved for critical/urgent issues that require immediate attention.**
**Why**: Reserving pings for urgent matters ensures maintainers can prioritize critical tasks effectively
- type:textarea
id:related-issues
validations:
required:true
attributes:
label:📑 I have found these related issues/pull requests
description:|
Please search for related **[ISSUES](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue%20sort%3Acreated-desc)**
and **[PULL REQUESTS](https://github.com/louislam/uptime-kuma/pulls?q=is%3Apr+sort%3Acreated-desc+)**.
Explain the differences between them or clarify if you were unable to find any related issues/pull requests.
placeholder:|
Example: This relates to issue #1, which also affects the ... system. It should not be merged because ...
- type:checkboxes
id:security-policy
attributes:
label:🛡️ Security Policy
description:|
Please review and acknowledge the Security Policy before reporting any security-related issues or bugs. You can find the full Security Policy **[HERE](https://github.com/louislam/uptime-kuma/security/policy)**.
options:
- label:|
I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy).
required:true
- type:textarea
id:description
validations:
required:false
attributes:
label:📝 Description
description:|
You could also upload screenshots
- type:textarea
id:steps-to-reproduce
validations:
required:true
attributes:
label:👟 Reproduction steps
description:|
How do you trigger this bug? Please walk us through it step by step. Include all important details and add screenshots where appropriate
placeholder:|
...
- type:textarea
id:expected-behavior
validations:
required:true
attributes:
label:👀 Expected behavior
description:|
What did you think would happen?
placeholder:|
...
- type:textarea
id:actual-behavior
validations:
required:true
attributes:
label:😓 Actual Behavior
description:|
What actually happen?
placeholder:|
...
- type:input
id:uptime-kuma-version
attributes:
label:🐻 Uptime-Kuma Version
description:|
What version of Uptime-Kuma are you running? Please do not provide Docker tags like `latest` or `1`.
placeholder:|
e.g., 1.23.16 or 2.0.0-beta.2
validations:
required:true
- type:input
id:operating-system
attributes:
label:💻 Operating System and Arch
description:|
Which OS is your server/device running on? (For Replit, please do not
report this bug)
placeholder:|
e.g., Ubuntu Server 24.04.2 LTS (GNU/Linux 6.8.0-55-generic x86_64)
validations:
required:true
- type:input
id:browser-vendor
attributes:
label:🌐 Browser
description:|
Which browser are you running on?
placeholder:|
e.g., Google Chrome 134.0.6998.183 (Official Build) (64-bit)
validations:
required:true
- type:textarea
id:deployment-info
attributes:
label:🖥️ Deployment Environment
description:|
Provide details about the deployment environment, including runtime components, databases, and storage configurations. This will
help assess the infrastructure and identify any potential compatibility requirements.
**Remove any fields that do not apply to your setup.**
value:|
- **Runtime Environment**:
- Docker: Version `X.X.X` (Build `Y.Y.Y`)
- Docker Compose: Version `X.X.X`
- Portainer (BE/CE): Version `X.X.X` (LTS: Yes/No)
- MariaDB: Version `X.X.X` (LTS: Yes/No)
- Node.js: Version `X.X.X` (LTS: Yes/No)
- Kubernetes (K3S/K8S): Version `X.X.X` (LTS: Yes/No, via `[method/tool]`)
- **Database**:
- SQLite: Embedded
- MariaDB: Embedded/External
- **Database Storage**:
- **Filesystem**:
- Linux: ext4/XFS/Btrfs/ZFS/F2FS
- macOS: APFS/ HFS+
- Windows: NTFS/ReFS
- **Storage Medium**: HDD/eMMC/SSD/NVMe
- **Uptime Kuma Setup**:
- Number of monitors: `X`
validations:
required:true
- type:textarea
id:logs
attributes:
label:📝 Relevant log output
description:|
Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
label:"📑 I have found these related issues/pull requests"
description:"Search related issues by clicking [HERE](https://github.com/louislam/uptime-kuma/issues?q=) and explain what the difference between them or explain that you are unable to find any related issues"
placeholder:"Related to #1 by also touching the ... system. They should not be merged because ..."
- type:dropdown
id:feature-area
attributes:
label:"🏷️ Feature Request Type"
description:"What kind of feature request is this?"
multiple:true
options:
- API / automation options
- New notification-provider
- Change to existing notification-provider
- New monitor
- Change to existing monitor
- Dashboard
- Status-page
- Maintenance
- Deployment
- Certificate expiry
- Settings
- Other
validations:
required:true
- type:textarea
id:feature-description
validations:
required:true
attributes:
label:"🔖 Feature description"
description:"A clear and concise description of what the feature request is."
placeholder:"You should add ..."
- type:textarea
id:solution
validations:
required:true
attributes:
label:"✔️ Solution"
description:"A clear and concise description of what you want to happen."
placeholder:"In my use-case, ..."
- type:textarea
id:alternatives
validations:
required:false
attributes:
label:"❓ Alternatives"
description:"A clear and concise description of any alternative solutions or features you've considered."
placeholder:"I have considered ..."
- type:textarea
id:additional-context
validations:
required:false
attributes:
label:"📝 Additional Context"
description:"Add any other context or screenshots about the feature request here."
Notify Louis Lam about a security concern. Please do NOT include any sensitive details in this issue.
# title: "Security Issue"
labels:["security"]
assignees:[louislam]
body:
- type:markdown
attributes:
value:|
## ❗ IMPORTANT: DO NOT SHARE VULNERABILITY DETAILS HERE
### ⚠️ Report a Security Vulnerability
**If you have discovered a security vulnerability, please report it securely using the GitHub Security Advisory.**
**Note**: This issue is only for notifying the maintainers of the repository, as the GitHub Security Advisory does not automatically send notifications.
- **Confidentiality**: The information you provide in the GitHub Security Advisory will initially remain confidential. However, once the vulnerability is addressed, the advisory will be publicly disclosed on GitHub.
- **Access and Visibility**: Until the advisory is published, it will only be visible to the maintainers of the repository and invited collaborators.
- **Credit**: You will be automatically credited as a contributor for identifying and reporting the vulnerability. Your contribution will be reflected in the MITRE Credit System.
- **Important Reminder**: **Do not include any sensitive or detailed vulnerability information in this issue.** This issue is only for sharing the advisory URL to notify the maintainers of the repository, not for discussing the vulnerability itself.
**Thank you for helping us keep Uptime Kuma secure!**
## **Step 1: Submit a GitHub Security Advisory**
Right-click the link below and select `Open link in new tab` to access the page. This will keep the security issue open, allowing you to easily return and paste the Advisory URL here later.
➡️ [Create a New Security Advisory](https://github.com/louislam/uptime-kuma/security/advisories/new)
## **Step 2: Share the Advisory URL**
Once you've created your advisory, please share the URL below. This will notify Louis Lam and enable them to take the appropriate action.
- type:textarea
id:github-advisory-url
validations:
required:true
attributes:
label:GitHub Advisory URL for @louislam
placeholder:|
Please paste the GitHub Advisory URL here. Only the URL is required.
- [ ] I have read and understand the pull request rules.
<details><summary>Click here for more details:</summary>
</p>
# Description
**⚠️ Please Note: We do not accept all types of pull requests, and we want to ensure we don’t waste your time. Before submitting, make sure you have read our pull request guidelines: [Pull Request Rules](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma)**
Fixes #(issue)
### 🚫 Please Avoid Unnecessary Pinging of Maintainers
## Type of change
We kindly ask you to refrain from pinging maintainers unless absolutely necessary. Pings are for critical/urgent pull requests that require immediate attention.
Please delete any options that are not relevant.
</p>
</details>
- Bug fix (non-breaking change which fixes an issue)
- User interface (UI)
- New feature (non-breaking change which adds functionality)
- Breaking change (a fix or feature that would cause existing functionality to not work as expected)
- Other
- This change requires a documentation update
## 📋 Overview
## Checklist
<!-- Provide a clear summary of the purpose and scope of this pull request:-->
-[ ] My code follows the style guidelines of this project
- [ ] I ran ESLint and other linters for modified files
-[ ] I have performed a self-review of my own code and tested it
- [ ] I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
- [ ] My changes generates no new warnings
- [ ] My code needed automated testing. I have added them (this is optional task)
- **What problem does this pull request address?**
- Please provide a detailed explanation here.
- **What features or functionality does this pull request introduce or enhance?**
- Please provide a detailed explanation here.
## Screenshots (if any)
<!--
Please link any GitHub issues or tasks that this pull request addresses.
Use the appropriate issue numbers or links to enable auto-closing.
-->
Please do not use any external image service. Instead, just paste in or drag and drop the image here, and it will be uploaded automatically.
- Relates to #issue-number
- Resolves #issue-number
## 🛠️ Type of change
<!-- Please select all options that apply -->
- [ ] 🐛 Bugfix (a non-breaking change that resolves an issue)
- [ ] ✨ New feature (a non-breaking change that adds new functionality)
- [ ] ⚠️ Breaking change (a fix or feature that alters existing functionality in a way that could cause issues)
- [ ] 🎨 User Interface (UI) updates
- [ ] 📄 New Documentation (addition of new documentation)
- [ ] 📄 Documentation Update (modification of existing documentation)
- [ ] 📄 Documentation Update Required (the change requires updates to related documentation)
- [ ] 🔧 Other (please specify):
- Provide additional details here.
## 📄 Checklist
<!-- Please select all options that apply -->
- [ ] 🔍 My code adheres to the style guidelines of this project.
- [ ] 🦿 I have indicated where (if any) I used an LLM for the contributions
- [ ] ✅ I ran ESLint and other code linters for modified files.
- [ ] 🛠️ I have reviewed and tested my code.
- [ ] 📝 I have commented my code, especially in hard-to-understand areas (e.g., using JSDoc for methods).
- [ ] ⚠️ My changes generate no new warnings.
- [ ] 🤖 My code needed automated testing. I have added them (this is an optional task).
- [ ] 📄 Documentation updates are included (if applicable).
- [ ] 🔒 I have considered potential security impacts and mitigated risks.
- [ ] 🧰 Dependency updates are listed and explained.
- [ ] 📚 I have read and understood the [Pull Request guidelines](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#recommended-pull-request-guideline).
## 📷 Screenshots or Visual Changes
<!--
If this pull request introduces visual changes, please provide the following details.
If not, remove this section.
Please upload the image directly here by pasting it or dragging and dropping.
Avoid using external image services as the image will be uploaded automatically.
-->
- **UI Modifications**: Highlight any changes made to the user interface.
- **Before & After**: Include screenshots or comparisons (if applicable).
**Uptime Kuma** is a self-hosted monitoring tool for HTTP(s), TCP, DNS, Docker, etc. Built with Vue 3 (frontend) and Node.js/Express (backend), using Socket.IO for real-time communication.
Different types of pull requests (PRs) may have different guidelines, so be sure
to review the appropriate one for your contribution.
- <details><summary><b>Security Fixes</b> (click to expand)</summary>
<p>
Submitting security fixes is something that may put the community at risk.
Please read through our [security policy](SECURITY.md) and submit vulnerabilities via an [advisory](https://github.com/louislam/uptime-kuma/security/advisories/new) + [issue](https://github.com/louislam/uptime-kuma/issues/new?assignees=&labels=help&template=security.md) instead.
We encourage you to submit how to fix a vulnerability if you know how to, this is not required.
Following the security policy allows us to properly test, fix bugs.
This review allows us to notice, if there are any changes necessary to unrelated parts like the documentation.
Please read through our [security policy](SECURITY.md) and submit
vulnerabilities via an [advisory] + [issue] instead. We encourage you to
submit how to fix a vulnerability if you know how to, this is not required.
Following the security policy allows us to properly test, fix bugs. This
review allows us to notice, if there are any changes necessary to unrelated
parts like the documentation.
[**PLEASE SEE OUR SECURITY POLICY.**](SECURITY.md)
To set up a new notification provider these files need to be modified/created:
-`server/notification-providers/PROVIDER_NAME.js` is where the heart of the notification provider lives.
- Both `monitorJSON` and `heartbeatJSON` can be `null` for some events.
If both are `null`, this is a general testing message, but if just `heartbeatJSON` is `null` this is a certificate expiry.
- Please wrap the axios call into a
```js
try {
let result = await axios.post(...);
if (result.status === ...) ...
} catch (error) {
this.throwGeneralAxiosError(error);
}
```
- `server/notification.js` is where the backend of the notification provider needs to be registered.
*If you have an idea how we can skip this step, we would love to hear about it ^^*
- `src/components/NotificationDialog.vue` you need to decide if the provider is a regional or a global one and add it with a name to the respective list
- `src/components/notifications/PROVIDER_NAME.vue` is where the frontend of each provider lives.
Please make sure that you have:
- used `HiddenInput` for secret credentials
- included all the necessary helptexts/placeholder/.. to make sure the notification provider is simple to setup for new users.
- include all translations (`{{ $t("Translation key") }}`, [`i18n-t keypath="Translation key">`](https://vue-i18n.intlify.dev/guide/advanced/component.html)) in `src/lang/en.json` to enable our translators to translate this
- `src/components/notifications/index.js` is where the frontend of the provider needs to be registered.
*If you have an idea how we can skip this step, we would love to hear about it ^^*
Offering notifications is close to the core of what we are as an uptime monitor.
Therefore, making sure that they work is also really important.
Because testing notification providers is quite time intensive, we mostly offload this onto the person contributing a notification provider.
To make shure you have tested the notification provider, please include screenshots of the following events in the pull-request description:
- `UP`/`DOWN`
- Certificate Expiry via https://expired.badssl.com/
- Testing (the test button on the notification provider setup page)
Using the following way to format this is encouraged:
- <details><summary><b>New Monitoring Types</b> (click to expand)</summary>
<p>
To set up a new notification provider these files need to be modified/created:
- `server/monitor-types/MONITORING_TYPE.js` is the core of each monitor.
the `async check(...)`-function should:
- throw an error for each fault that is detected with an actionable error message
- in the happy-path, you should set `heartbeat.msg` to a successfull message and set `heartbeat.status = UP`
- `server/uptime-kuma-server.js` is where the monitoring backend needs to be registered.
*If you have an idea how we can skip this step, we would love to hear about it ^^*
- `server/monitor-types/MONITORING_TYPE.js` is the core of each monitor. the
`async check(...)`-function should:
- throw an error for each fault that is detected with an actionable error
message - in the happy-path, you should set `heartbeat.msg` to a successful
message and set `heartbeat.status = UP`
- `server/uptime-kuma-server.js` is where the monitoring backend needs to be
registered. _If you have an idea how we can skip this step, we would love to
hear about it ^^_
- `src/pages/EditMonitor.vue` is the shared frontend users interact with.
Please make sure that you have:
- used `HiddenInput` for secret credentials
- included all the necessary helptexts/placeholder/.. to make sure the notification provider is simple to setup for new users.
- include all translations (`{{ $t("Translation key") }}`, [`i18n-t keypath="Translation key">`](https://vue-i18n.intlify.dev/guide/advanced/component.html)) in `src/lang/en.json` to enable our translators to translate this
-
Please make sure that you have: - used `HiddenInput` for secret
credentials - included all the necessary helptexts/placeholder/.. to make
sure the notification provider is simple to setup for new users. - include
10. **When publishing your PR, set it as a** `Draft pull request` **to allow
for review and prevent automatic merging.**
11. **Maintainers will assign relevant labels** (e.g., `A:maintenance`,
`A:notifications`).
12. **Complete the PR checklist**, ensuring that:
- Documentation is updated if necessary.
- Tests are written or updated.
- CI/CD checks pass successfully.
13. **Request feedback** from team members to refine your changes before the
final review.
## When Can You Change the PR Status to "Ready for Review"?
A PR should remain in **draft status** until all tasks are completed. Only
change the status to **Ready for Review** when:
- You have implemented all planned changes.
- You have addressed all feedback.
- Your code is fully tested and ready for integration.
- You have updated or created the necessary tests.
- You have verified that CI/CD checks pass successfully.
<br />
A **work-in-progress (WIP) PR** must stay in **draft status** until everything
is finalized.
<sub>Since maintainer time is valuable, junior maintainers may merge
uncontroversial PRs.</sub>
</p>
</details>
## The following rules are essential for making your PR mergable
- Merging multiple issues by a huge PR is more difficult to review and causes
conflicts with other PRs. Please
- (if possible) **create one PR for one issue** or
- (if not possible) **explain which issues a PR addresses and why this PR should not be broken apart**
- Make sure your **PR passes our continuous integration**.
PRs will not be merged unless all CI-Checks are green.
- **Breaking changes** (unless for a good reason and discussed beforehand) will not get merged / not get merged quickly.
Such changes require a major version release.
- **Test your code** before submitting a PR.
Buggy PRs will not be merged.
- (if not possible) **explain which issues a PR addresses and why this PR
should not be broken apart**
- Make sure your **PR passes our continuous integration**. PRs will not be
merged unless all CI-Checks are green.
- **Breaking changes** (unless for a good reason and discussed beforehand) will
not get merged / not get merged quickly. Such changes require a major version
release.
- **Test your code** before submitting a PR. Buggy PRs will not be merged.
- Make sure the **UI/UX is close to Uptime Kuma**.
- **Think about the maintainability**:
Don't add functionality that is completely **out of scope**.
Keep in mind that we need to be able to maintain the functionality.
- **Think about the maintainability**: Don't add functionality that is
completely **out of scope**. Keep in mind that we need to be able to maintain
the functionality.
- Don't modify or delete existing logic without a valid reason.
- Don't convert existing code into other programming languages for no reason.
I ([@louislam](https://github.com/louislam)) have the final say.
If your pull request does not meet my expectations, I will reject it, no matter how much time you spent on it.
Therefore, it is essential to have a discussion beforehand.
I ([@louislam](https://github.com/louislam)) have the final say. If your pull
request does not meet my expectations, I will reject it, no matter how much time
you spent on it. Therefore, it is essential to have a discussion beforehand.
I will assign your pull request to a [milestone](https://github.com/louislam/uptime-kuma/milestones), if I plan to review and merge it.
I will assign your pull request to a [milestone], if I plan to review and merge
it.
Please don't rush or ask for an ETA.
We have to understand the pull request, make sure it has no breaking changes and stick to the vision of this project, especially for large pull requests.
Please don't rush or ask for an ETA. We have to understand the pull request,
make sure it has no breaking changes and stick to the vision of this project,
especially for large pull requests.
## I'd like to work on an issue. How do I do that?
## I'd Like to Work on an Issue. How Do I Do That?
We have found that assigning people to issues is management-overhead that we don't need.
A short comment that you want to try your hand at this issue is appreciated to save other devs time.
If you come across any problem during development, feel free to leave a comment with what you are stuck on.
We have found that assigning people to issues is unnecessary management
overhead. Instead, a short comment stating that you want to work on an issue is
appreciated, as it saves time for other developers. If you encounter any
problems during development, feel free to leave a comment describing what you
are stuck on.
### Recommended Pull Request Guideline
Before diving deep into coding, having a discussion first by creating an empty pull request for discussion is preferred.
The rationale behind this is that we can align the direction and scope of the feature to eliminate any conflicts with existing and planned work, and can help by pointing out any potential pitfalls.
Before jumping into coding, it's recommended to initiate a discussion by
creating an empty pull request. This approach allows us to align on the
direction and scope of the feature, ensuring it doesn't conflict with existing
or planned work. It also provides an opportunity to identify potential pitfalls
Both frontend and backend share the same `package.json`.
However, the frontend dependencies are eventually not used in the production environment, because it is usually also baked into `dist` files. So:
Both frontend and backend share the same `package.json`. However, the frontend
dependencies are eventually not used in the production environment, because it
is usually also baked into `dist` files. So:
- Frontend dependencies = "devDependencies"
- Examples: `vue`, `chart.js`
- Examples: - `vue`, `chart.js`
- Backend dependencies = "dependencies"
- Examples: `socket.io`, `sqlite3`
- Development dependencies = "devDependencies"
@@ -346,31 +597,41 @@ However, the frontend dependencies are eventually not used in the production env
### Update Dependencies
Since previously updating Vite 2.5.10 to 2.6.0 broke the application completely, from now on, it should update the patch release version only.
Since previously updating Vite 2.5.10 to 2.6.0 broke the application completely,
from now on, it should update the patch release version only.
Patch release = the third digit ([Semantic Versioning](https://semver.org/))
If for security / bug / other reasons, a library must be updated, breaking changes need to be checked by the person proposing the change.
If for security / bug / other reasons, a library must be updated, breaking
changes need to be checked by the person proposing the change.
## Translations
Please add **all** the strings which are translatable to `src/lang/en.json` (if translation keys are omitted, they can not be translated.)
Please add **all** the strings which are translatable to `src/lang/en.json` (if
translation keys are omitted, they can not be translated.)
**Don't include any other languages in your initial pull request** (even if this is your mother tongue), to avoid merge-conflicts between weblate and `master`.
The translations can then (after merging a PR into `master`) be translated by awesome people donating their language skills.
**Don't include any other languages in your initial pull request** (even if this
is your mother tongue), to avoid merge-conflicts between weblate and `master`.
The translations can then (after merging a PR into `master`) be translated by
awesome people donating their language skills.
If you want to help by translating Uptime Kuma into your language, please visit the [instructions on how to translate using weblate](https://github.com/louislam/uptime-kuma/blob/master/src/lang/README.md).
If you want to help by translating Uptime Kuma into your language, please visit
the [instructions on how to translate using weblate].
@@ -17,7 +17,7 @@ Uptime Kuma is an easy-to-use self-hosted monitoring tool.
Try it!
Demo Server (Location: Frankfurt - Germany): https://demo.kuma.pet/start-demo
Demo Server (Location: Frankfurt - Germany): <https://demo.kuma.pet/start-demo>
It is a temporary live demo, all data will be deleted after 10 minutes. Sponsored by [Uptime Kuma Sponsors](https://github.com/louislam/uptime-kuma#%EF%B8%8F-sponsors).
@@ -37,34 +37,44 @@ It is a temporary live demo, all data will be deleted after 10 minutes. Sponsore
Uptime Kuma is now running on <http://0.0.0.0:3001>.
Uptime Kuma is now running on all network interfaces (e.g. http://localhost:3001 or http://your-ip:3001).
> [!WARNING]
> File Systems like **NFS** (Network File System) are **NOT** supported. Please map to a local directory or volume.
> [!NOTE]
> If you want to limit exposure to localhost (without exposing port for other users or to use a [reverse proxy](https://github.com/louislam/uptime-kuma/wiki/Reverse-Proxy)), you can expose the port like this:
1. Please report security issues to https://github.com/louislam/uptime-kuma/security/advisories/new.
2. Please also create an empty security issue to alert me, as GitHub Advisories do not send a notification, I probably will miss it without this. https://github.com/louislam/uptime-kuma/issues/new?assignees=&labels=help&template=security.md
Do not use the public issue tracker or discuss it in public as it will cause more damage.
Do not use the public issue tracker or discuss it in public as it will cause
more damage.
## Do you accept other 3rd-party bug bounty platforms?
At this moment, I DO NOT accept other bug bounty platforms, because I am not familiar with these platforms and someone has tried to send a phishing link to me by doing this already. To minimize my own risk, please report through GitHub Advisories only. I will ignore all 3rd-party bug bounty platforms emails.
At this moment, I DO NOT accept other bug bounty platforms, because I am not
familiar with these platforms and someone has tried to send a phishing link to
me by doing this already. To minimize my own risk, please report through GitHub
Advisories only. I will ignore all 3rd-party bug bounty platforms emails.
## Supported Versions
### Uptime Kuma Versions
You should use or upgrade to the latest version of Uptime Kuma. All `1.X.X` versions are upgradable to the latest version.
You should use or upgrade to the latest version of Uptime Kuma.
All versions are upgradable to the latest version.
body:`@${username}: Hello! :wave:\n\nThis issue is being automatically closed because it does not follow the issue template. Please **DO NOT open blank issues and use our [issue-templates](https://github.com/louislam/uptime-kuma/issues/new/choose) instead**.\nBlank Issues do not contain the context nessesary for a good discussions.`
body:`@${username}: Hello! :wave:\n\nThis issue is being automatically closed because it does not follow the issue template. Please **DO NOT open blank issues and use our [issue-templates](https://github.com/louislam/uptime-kuma/issues/new/choose) instead**.\nBlank Issues do not contain the context necessary for a good discussions.`
<xs:documentation>A list of assembly names to exclude from the default action of "embed all Copy Local references", delimited with line breaks</xs:documentation>
<xs:documentation>A list of assembly names to include from the default action of "embed all Copy Local references", delimited with line breaks.</xs:documentation>
<xs:documentation>A list of runtime assembly names to exclude from the default action of "embed all Copy Local references", delimited with line breaks</xs:documentation>
<xs:documentation>A list of runtime assembly names to include from the default action of "embed all Copy Local references", delimited with line breaks.</xs:documentation>
<xs:documentation>This will copy embedded files to disk before loading them into memory. This is helpful for some scenarios that expected an assembly to be loaded from a physical file.</xs:documentation>
<xs:documentation>Embedded assemblies are compressed by default, and uncompressed when they are loaded. You can turn compression off with this option.</xs:documentation>
<xs:documentation>As part of Costura, embedded assemblies are no longer included as part of the build. This cleanup can be turned off.</xs:documentation>
<xs:documentation>Costura by default will load as part of the module initialization. This flag disables that behavior. Make sure you call CosturaUtility.Initialize() somewhere in your code.</xs:documentation>
<xs:documentation>Costura will by default use assemblies with a name like 'resources.dll' as a satellite resource and prepend the output path. This flag disables that behavior.</xs:documentation>
<xs:documentation>A list of assembly names to exclude from the default action of "embed all Copy Local references", delimited with |</xs:documentation>
<xs:documentation>A list of assembly names to include from the default action of "embed all Copy Local references", delimited with |.</xs:documentation>
<xs:documentation>A list of runtime assembly names to exclude from the default action of "embed all Copy Local references", delimited with |</xs:documentation>
<xs:documentation>A list of runtime assembly names to include from the default action of "embed all Copy Local references", delimited with |.</xs:documentation>
Console.WriteLine("The --intranet argument was provided, so we will not try to access the internet. The first time this application runs you'll need to run it without the --intranet param or copy the result from another machine to the intranet server.");
varresult=MessageBox.Show("A new version is available. Do you want to update?","Update",MessageBoxButtons.YesNo);
if(result==DialogResult.Yes){
// Create a empty file `update`, so the app will download the core files again at startup
File.Create("update").Close();
trayIcon.Visible=false;
process?.Kill();
// Restart the app, it will download the core files again at startup
Application.Restart();
}
}else{
MessageBox.Show("You are using the latest version.");
}
}
}
voidVisitGitHub(objectsender,EventArgse){
if(intranetOnly){
MessageBox.Show("You have parsed in --intranet so we will not try to access the internet or visit github.com, please go to https://github.com/louislam/uptime-kuma if you want to visit github.");
<ErrorText>This project references NuGet package(s) that are missing on this computer. Enable NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105.The missing file is {0}.</ErrorText>
* to avoid the runtime deprecation warning triggered for using `fs.rmdirSync` with `{ recursive: true }` in Node.js v16,
* or the `recursive` property removing completely in the future Node.js version.
* See the link below.
* @todo Once we drop the support for Node.js v14 (or at least versions before v14.14.0), we can safely replace this function with `fs.rmSync`, since `fs.rmSync` was add in Node.js v14.14.0 and currently we supports all the Node.js v14 versions that include the versions before the v14.14.0, and this function have almost the same signature with `fs.rmSync`.
* @link https://nodejs.org/docs/latest-v16.x/api/deprecations.html#dep0147-fsrmdirpath--recursive-true- the deprecation information of `fs.rmdirSync`
* @link https://nodejs.org/docs/latest-v16.x/api/fs.html#fsrmsyncpath-options the document of `fs.rmSync`
* @param {fs.PathLike} path Valid types for path values in "fs".
* @param {fs.RmDirOptions} options options for `fs.rmdirSync`, if `fs.rmSync` is available and property `recursive` is true, it will automatically have property `force` with value `true`.
LLM Task: Please help to put above PRs into the following sections based on their content. If a PR fits multiple sections, choose the most relevant one. If a PR doesn't fit any section, place it in "Others". If there are grammatical errors in the PR titles, please correct them. Don't change the PR numbers and authors, and keep the format. Output as markdown.
Changelog:
### 🆕 New Features
### 💇♀️ Improvements
### 🐞 Bug Fixes
### ⬆️ Security Fixes
### 🦎 Translation Contributions
### Others
- Other small changes, code refactoring and comment/doc updates in this repo:
`;
awaitmain();
/**
* Main Function
* @returns {Promise<void>}
*/
asyncfunctionmain(){
constpreviousVersion=process.argv[2];
if(!previousVersion){
console.error("Please provide the previous version as the first argument.");
process.exit(1);
}
console.log(`Generating changelog since version ${previousVersion}...`);
// If host is omitted, the server will accept connections on the unspecified IPv6 address (::) when IPv6 is available and the unspecified IPv4 address (0.0.0.0) otherwise.
// Dual-stack support for (::)
lethostname=process.env.UPTIME_KUMA_HOST;
// Also read HOST if not *BSD, as HOST is a system environment variable in FreeBSD
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.