url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://git-scm.com/book/uk/v2/Git-%d0%bd%d0%b0-%d1%81%d0%b5%d1%80%d0%b2%d0%b5%d1%80%d1%96-%d0%a0%d0%be%d0%b7%d1%83%d0%bc%d0%bd%d0%b8%d0%b9-HTTP | Git - Розумний HTTP About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Вступ 1.1 Про систему контролю версій 1.2 Коротка історія Git 1.3 Основи Git 1.4 Git, зазвичай, тільки додає дані 1.5 Три стани 1.6 Командний рядок 1.7 Інсталяція Git 1.8 Початкове налаштування Git 1.9 Отримання допомоги 1.10 Підсумок 2. Основи Git 2.1 Створення Git-сховища 2.2 Запис змін до репозиторія 2.3 Перегляд історії комітів 2.4 Скасування речей 2.5 Взаємодія з віддаленими сховищами 2.6 Теґування 2.7 Псевдоніми Git 2.8 Підсумок 3. Галуження в git 3.1 Гілки у кількох словах 3.2 Основи галуження та зливання 3.3 Управління гілками 3.4 Процеси роботи з гілками 3.5 Віддалені гілки 3.6 Перебазовування 3.7 Підсумок 4. Git на сервері 4.1 Протоколи 4.2 Отримання Git на сервері 4.3 Генерація вашого публічного ключа SSH 4.4 Налаштування Серверу 4.5 Демон Git 4.6 Розумний HTTP 4.7 GitWeb 4.8 GitLab 4.9 Варіанти стороннього хостингу 4.10 Підсумок 5. Розподілений Git 5.1 Розподілені процеси роботи 5.2 Внесення змін до проекту 5.3 Супроводжування проекту 5.4 Підсумок 6. GitHub 6.1 Створення та налаштування облікового запису 6.2 Як зробити внесок до проекту 6.3 Супроводжування проєкту 6.4 Керування організацією 6.5 Скриптування GitHub 6.6 Підсумок 7. Інструменти Git 7.1 Вибір ревізій 7.2 Інтерактивне індексування 7.3 Ховання та чищення 7.4 Підписання праці 7.5 Пошук 7.6 Переписування історії 7.7 Усвідомлення скидання (reset) 7.8 Складне злиття 7.9 Rerere 7.10 Зневадження з Git 7.11 Підмодулі 7.12 Пакування 7.13 Заміна 7.14 Збереження посвідчення (credential) 7.15 Підсумок 8. Налаштування Git 8.1 Конфігурація Git 8.2 Атрибути Git 8.3 Гаки (hooks) Git 8.4 Приклад політики користування виконуваної Git-ом 8.5 Підсумок 9. Git and Other Systems 9.1 Git як клієнт 9.2 Міграція на Git 9.3 Підсумок 10. Git зсередини 10.1 Кухонні та парадні команди 10.2 Об’єкти Git 10.3 Посилання Git 10.4 Файли пакунки 10.5 Специфікація посилань (refspec) 10.6 Протоколи передачі 10.7 Супроводження та відновлення даних 10.8 Змінні середовища 10.9 Підсумок A1. Додаток A: Git в інших середовищах A1.1 Графічні інтерфейси A1.2 Git у Visual Studio A1.3 Git в Eclipse A1.4 Git у Bash A1.5 Git у Zsh A1.6 Git у Powershell A1.7 Підсумок A2. Додаток B: Вбудовування Git у ваші застосунки A2.1 Git з командного рядка A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. Додаток C: Команди Git A3.1 Налаштування та конфігурація A3.2 Отримання та створення проектів A3.3 Базове збереження відбитків A3.4 Галуження та зливання A3.5 Поширення й оновлення проектів A3.6 Огляд та порівняння A3.7 Зневаджування A3.8 Латання (patching) A3.9 Електронна пошта A3.10 Зовнішні системи A3.11 Адміністрування A3.12 Кухонні команди 2nd Edition 4.6 Git на сервері - Розумний HTTP Розумний HTTP Ми вже маємо авторизований доступ через SSH та неавторизований через git:// , проте існує ще протокол, котрий може працювати в обох варіантах одночасно. Налаштування Розумного HTTP потрибує лише ввімкнути CGI скрипт, що входить в пакет Git під назвою git-http-backent , на вашому сервері. Цей CGI буде читати шлях та заголовки, що їх відправили git fetch чи git push до HTTP URL та визначати, чи клієнт в змозі спілкуватися через HTTP (що є правдою для будь-якого клієнту після версії 1.6.6). Якщо CGI визначив, що клієнт розумний, він буде з ним спілкуватися розумно, інакше доведеться використовувати тупу поведінку (отже він зворотно сумісний для читання зі старіших клієнтів). Давайте покроково розглянемо дуже просту схему налаштування. Ми використаємо Apache в якості CGI серверу. Якщо у вас немає Apache, ви можете його встановити на Linux машині приблизно так: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env Ця команда також вмикає модулі mod_cgi , mod_alias і mod_env . Вони всі необхідні для правильної роботи розумного HTTP. Вам також треба встановити групу Unix теки /srv/git у значення www-data , щоб веб сервер мав доступ на читання й запис до сховища, оскільки процес APache, що виконує CGI скрипт, буде типово виконуватись від цього користувача: $ chgrp -R www-data /srv/git Далі нам треба додати дещо до конфігурації Apache, щоб git-http-backend обробник для будь-якого шляху на вашому веб сервері, що закінчується на /git . SetEnv GIT_PROJECT_ROOT /srv/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/lib/git-core/git-http-backend/ Якщо ви пропустите змінну середовища GIT_HTTP_EXPORT_ALL, Git погодиться роздавати неавторизованим користувачам тільки сховища з файлом `git-daemon-export-ok , як робить і демон Git. Нарешті, вам варто сказати Apache дозволяти запити до git-http-backend і якимось чином зробити записи авторизованими, можливо за допомогою блоку Auth ось так: <Files "git-http-backend"> AuthType Basic AuthName "Git Access" AuthUserFile /srv/git/.htpasswd Require expr !(%{QUERY_STRING} -strmatch '*service=git-receive-pack*' || %{REQUEST_URI} =~ m#/git-receive-pack$#) Require valid-user </Files> Щоб це працювало необхідно створити файл .htpasswd з паролями дозволених користувачів. Ось приклад того, як можна додати користувача ``schacon'' до цього файлу: $ htpasswd -c /srv/git/.htpasswd schacon Існує безліч методів авторизації в Apache, вам доведеться вибрати та використати один з них. У цій секції ми навели найпростіший приклад, який тільки могли вигадати. Також ви безсумнівно захочете налаштувати шифрування даних через SSL. Ми не бажаємо занадто багато розглядати конфігурацію Apache, адже цілком можливо, що ви будете використовувати інший сервер, чи у вас інші потреби авторизації. Суть в тому, що Git поставляє CGI скрипт git-http-backent , який може відправляти та приймати дані Git через HTTP. Він не реалізує авторизацію сам, проте авторизацію легко контролювати на рівні веб серверу, що його викликає. Це дозволяє майже кожен веб сервер, що підтримує CGI, отже використовуйте той, що ви найкраще знаєте. Зауваження За докладнішою інформацією щодо конфігурації авторизації в Apache, дивіться документацію Apache за адресою: http://httpd.apache.org/docs/current/howto/auth.html prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:19 |
http://www.trello.com/pricing | Which Trello Plan Is Best for You? Our Pricing Guide Can Help | Trello Skip to main content Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Use case: Task management Track progress of tasks in one convenient place with a visual layout that adds ‘ta-da’ to your to-do’s. Use case: Resource hub Save hours when you give teams a well-designed hub to find information easily and quickly. Use case: Project management Keep projects organized, deadlines on track, and teammates aligned with Trello. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Back Navigation Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Read though our use cases to make the most of Trello on your team. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Helping teams work better, together Discover Trello use cases, productivity tips, best practices for team collaboration, and expert remote work advice. Check out the Trello blog Trello your way. Trusted by millions, Trello powers teams all around the world. Explore which option is right for you. Free $ 0 USD Free for up to 10 collaborators per Workspace Capture your to-dos, get organized, and get sh*t done. See what's included Included in Free: Unlimited cards Up to 10 boards per Workspace Quickly capture to-dos from email, Slack, and Teams Inbox Unlimited Power-Ups per board Unlimited storage (10MB/file) 250 Workspace command runs per month Custom backgrounds & stickers Unlimited activity log Assignee and due dates iOS and Android mobile apps 2-factor authentication Standard $ 5 USD Per user/month if billed annually ($6 billed monthly) Get more stuff done with unlimited boards, card mirroring, and more automation. See what's included Everything in Free, plus: Unlimited boards Quickly capture to-dos from email, Slack, and Teams — powered by AI Planner Advanced checklists Card mirroring Custom Fields List colors Collapsible lists Unlimited storage (250MB/file) 1,000 Workspace command runs per month Single board guests Saved searches Learn more about Standard Premium $ 10 USD Per user/month if billed annually ($12.50 billed monthly) Add AI to your boards and admin controls to your toolkit. Plus, get more perspective with views. See what's included Everything in Standard, plus: AI Views: Calendar, Timeline, Table, Dashboard, and Map Workspace views: Table and Calendar Unlimited Workspace command runs Admin and security features Workspace-level templates Collections Observers Simple data export Learn more about Premium Enterprise $ 17.50 USD Per user/month - billed annually ($210.00 annual price per user) Add enterprise-grade security and controls. This plan includes Atlassian Guard Standard and 24/7 Enterprise Admin support. Est. cost for users See what's included Everything in Premium, plus: Unlimited Workspaces Organization-wide permissions Organization-visible boards Public board management Multi-board guests Attachment permissions Power-Up administration Free SSO and user provisioning with Atlassian Guard Learn more about Enterprise Compare our plans Features Free Standard Premium Enterprise Unlimited cards True True True True Quick capture Instantly capture to-dos, notes, and messages, from email, Slack, and Microsoft Teams. True True True True Inbox Gather messages and to-dos in this personal space before organizing them into your boards. True True True True Planner (view-only) View your scheduled cards on a calendar and synchronize events from your favorite tools. True True True True Quick Capture powered by AI Instantly capture to-dos, notes, and messages from email, Slack, and Microsoft Teams using AI. False True True True Planner (full access) Drag and drop cards on a calendar to block any available time. Sync with more events in your favorite tools. False True True True Card mirroring Keep your to-dos aligned across boards. Mirror a single card to multiple boards to view and edit it from anywhere. False True True True Built-in automation Powerful no-code automation is built into every Trello board. Start automating True True True True Assignee and due dates True True True True iOS and Android mobile apps Download mobile apps True True True True Desktop app Download desktop app True True True True Unlimited activity logs True True True True Trello templates Give your team a blueprint for success with tried-and-true templates from the Trello community. Try a template True True True True 2-factor authentication True True True True Mobile device management Enforce security controls on mobile app usage through built-in mobile device management (MDM) support for iOS and Android. True True True True Unlimited power-ups Integrate with more than 200+ apps and tools your team depends on like Slack, Google Drive, Salesforce, and more directly into your Trello boards. (Note: Some Power-Ups by our partners require an additional subscription fee.) Learn more True True True True Unlimited Workspace collaborators Up to 10 collaborators True True True Unlimited boards Create as many Trello boards as your team sees fit; from onboarding new hires, to sprint planning, and every team meeting agenda in between. False True True True Advanced checklists Break down projects into byte-sized tasks and get granular by assigning members and due dates to individual tasks. False True True True Custom fields Bring process and formality to your workflow by structuring information on Trello cards to the task at hand with Custom Fields. False True True True Collapsible lists Keep your Trello boards tidy and focus on what matters by easily hiding and revealing list details. Learn more False True True True List colors Brighten up your boards by using list colors to easily spot priorities and keep your to-dos organized and on track. Learn more False True True True AI Enhance Trello card descriptions and comments effortlessly with AI-driven content generation, grammar correction, and brainstorming. Learn more False False True True Dashboard view Trello’s reporting tool lets you access real-time insights and communicate your team’s progress in a visual and meaningful way. Learn more False False True True Map view Plan an offsite, scout new office locations, or manage product distribution points by adding locations to your cards and visualizing them geographically on a map. Learn more False False True True Timeline view Plan your project, stay on top of every sprint, and see how all of the moving parts fit together over time with Timeline. Learn more False False True True Table View Bring a clearer perspective to all the work happening across a single board in a list format where you can create and edit cards in just a few clicks. Learn more False False True True Calendar view Calendar displays start dates, due dates, and advanced checklist items so you can see what lies ahead for your project and stay on top of today’s to-dos. Learn more False False True True Workspace table view See your projects and tasks across Workspaces and boards in a spreadsheet-style list that can be sorted and filtered to drill down to exactly the cards you need to see. Learn more False False True True Workspace calendar view Workspace calendar displays items with start dates and due dates across your projects and boards, so you can see what lies ahead for all your teamwork. Learn more False False True True Workspace-level templates False False True True Command run administration Premium or Enterprise administrators can disable commands on behalf of other users, and perform other command maintenance. False False True True Board collections Premium and Enterprise teams can use Board Collections to easily group boards together whether by Workspace, department, or major project. False False True True Observers Observers are a Premium security setting that limit a user’s actions within a board. False False True True Domain-restricted invites False False True True Deactivate members False False True True Simple data export False False True True Unlimited command runs False False True True SAML SSO via Atlassian Guard Atlassian Guard is a separate subscription that your company can enable across all your Atlassian products and starts at $4/month/user. Learn more Available Available Available True Unlimited workspaces False False False True Power-up administration False False False True Attachment restrictions False False False True Organization wide permissions False False False True Organization visible boards False False False True Public board management False False False True Support Learn more Community Support Local Business Hours 24/5 Premium Support 24/7 Enterprise Admin Support Didn’t find what you were looking for? Make a suggestion Frequently asked questions + Does Trello offer a Premium free trial? We sure do. All users can enroll their Workspace in a free trial of Trello Premium . With that trial your Workspace will get access to create unlimited Trello boards, automate as much as you’d like, take advantage of Timeline, Dashboard, and other new views, and much more! + Do you offer any discounted plans? Yes! Trello offers both a non-profit community discount as well as an education discount . + What payment methods do you accept? You can purchase a monthly or annual Trello Standard or Premium subscription with any major credit card. We offer more options for Enterprise customers, if you’re interested in learning more about Trello Enterprise contact our sales team. + How do I cancel my Trello Standard or Premium subscription? If you aren’t 100% satisfied with Trello Standard or Premium you may downgrade at any time. When a team downgrades from Standard or Premium, it retains its Standard or Premium features and unlimited boards until the end of its prepaid service period. At the end of its prepaid service period, it becomes a free Trello Workspace that can hold 10 boards. Learn more about canceling your Standard or Premium subscription here. + How are users counted towards billing? A Trello user who is added as a member to a Workspace—either as a normal member or as a team admin—is considered a billable team member that is included in the cost of Trello Standard or Premium. Any Guest that is on more than one board within the Workspace is considered a Multi-Board Guest and is billed at the same rate as Standard or Premium Workspace members. See this page for more information on Multi-Board Guests. + Is there an on-premises version of Trello? Trello is proudly a cloud-only product. We offer access via the web, desktop, and our awesome mobile apps . + Can I have Trello Standard or Premium just for my own account? Trello Standard and Premium are designed for all teams—even teams of one! To upgrade to Standard or Premium you’ll need to create a Workspace and then upgrade that Workspace. + How secure is Trello? Trello, Inc. (“we”, “us” or “our”) is SOC2 Type 2 certified—we receive and review our data hosting providers’ SOC1 and SOC2 reports every 6 months under NDA. Trello is ISO/IEC 27001 certified which validates our information security management system (ISMS) and the implementation of our security controls. More information is available on the Atlassian Trust Management System. Trello is PCI-DSS certified. Learn more about Trello’s security protocols here . Best-in-class security and centralized administration with Atlassian Guard SAML single sign-on Enforced 2FA Atlassian Guard is a separate subscription that your company can enable across all your Atlassian products and starts at $4/month/user. Trello is an Atlassian product. Learn more Log In About Trello What’s behind the boards. Jobs Learn about open roles on the Trello team. Apps Download the Trello App for your Desktop or Mobile devices. Contact us Need anything? Get in touch and we can help. Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Privacy Policy Terms Copyright © 2024 Atlassian | 2026-01-13T09:29:19 |
http://www.trello.com?trk=products_details_guest_secondary_call_to_action#skip-target | Capture, organize, and tackle your to-dos from anywhere | Trello Skip to main content Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Use case: Task management Track progress of tasks in one convenient place with a visual layout that adds ‘ta-da’ to your to-do’s. Use case: Resource hub Save hours when you give teams a well-designed hub to find information easily and quickly. Use case: Project management Keep projects organized, deadlines on track, and teammates aligned with Trello. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Back Navigation Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Read though our use cases to make the most of Trello on your team. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Helping teams work better, together Discover Trello use cases, productivity tips, best practices for team collaboration, and expert remote work advice. Check out the Trello blog Accelerate your teams' work with AI features 🤖 now available for all Premium and Enterprise! Learn more. Capture, organize, and tackle your to-dos from anywhere. Escape the clutter and chaos—unleash your productivity with Trello. Sign up - it’s free! By entering my email, I acknowledge the Atlassian Privacy Policy Watch video Hero Trello 101 Your productivity powerhouse Stay organized and efficient with Inbox, Boards, and Planner. Every to-do, idea, or responsibility—no matter how small—finds its place, keeping you at the top of your game. Inbox When it’s on your mind, it goes in your Inbox. Capture your to-dos from anywhere, anytime. Boards Your to-do list may be long, but it can be manageable! Keep tabs on everything from "to-dos to tackle" to "mission accomplished!” Planner Drag, drop, get it done. Snap your top tasks into your calendar and make time for what truly matters. Inbox When it’s on your mind, it goes in your Inbox. Capture your to-dos from anywhere, anytime. Boards Your to-do list may be long, but it can be manageable! Keep tabs on everything from "to-dos to tackle" to "mission accomplished!” Planner Drag, drop, get it done. Snap your top tasks into your calendar and make time for what truly matters. From message to action Quickly turn communication from your favorite apps into to-dos, keeping all your discussions and tasks organized in one place. EMAIL MAGIC Easily turn your emails into to-dos! Just forward them to your Trello Inbox, and they’ll be transformed by AI into organized to-dos with all the links you need. MESSAGE APP SORCERY Need to follow up on a message from Slack or Microsoft Teams? Send it directly to your Trello board! Your favorite app interface lets you save messages that appear in your Trello Inbox with AI-generated summaries and links. WORK SMARTER Do more with Trello Customize the way you organize with easy integrations, automation, and mirroring of your to-dos across multiple locations. Integrations Connect the apps you are already using into your Trello workflow or add a Power-Up to fine-tune your specific needs. Browse Integrations Automation No-code automation is built into every Trello board. Focus on the work that matters most and let the robots do the rest. Get to know Automation Card mirroring View all your to-dos from multiple boards in one place. Mirror a card to keep track of work wherever you need it! Compare plans [Trello is] great for simplifying complex processes. As a manager, I can chunk [processes] down into bite-sized pieces for my team and then delegate that out, but still keep a bird's-eye view. Joey Rosenberg Global Leadership Director at Women Who Code Read the story 75% of organizations report that Trello delivers value to their business within 30 days. Trello TechValidate Survey Whether someone is in the office, working from home, or working on-site with a client, everyone can share context and information through Trello. Sumeet Moghe Product Manager at ThoughtWorks Read the story 81% of customers chose Trello for its ease of use. Trello TechValidate Survey We used Trello to provide clarity on steps, requirements, and procedures. This was exceptional when communicating with teams that had deep cultural and language differences. Jefferson Scomacao Development Manager at IKEA/PTC Read the story 74% of customers say Trello has improved communication with their co-workers and teams. Trello TechValidate Survey Join a community of millions of users globally who are using Trello to get more done. Join a community of millions of users globally who are using Trello to get more done. Get started with Trello today Sign up - it’s free! By entering my email, I acknowledge the Atlassian Privacy Policy Log In About Trello What’s behind the boards. Jobs Learn about open roles on the Trello team. Apps Download the Trello App for your Desktop or Mobile devices. Contact us Need anything? Get in touch and we can help. Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Privacy Policy Terms Copyright © 2024 Atlassian | 2026-01-13T09:29:19 |
https://sre.google/mobaa/2022/ | Google SRE - Museum of Borgmon Abstract Art Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content 2022 Gallery Page Ding Dong Galloping Gertie Latency Waterfall Technicolor Hills Wave Interference For The Love of Abstract Art Alignment Wheat In a Heavy Wind Ghost of Batman Ding Dong Galloping Gertie Latency Waterfall Technicolor Hills Wave Interference For The Love of Abstract Art Alignment Wheat In a Heavy Wind Ghost of Batman Interested in joining SRE? Google strives to cultivate an inclusive workplace. We believe diversity of perspectives and ideas leads to better discussions, decisions, and outcomes for everyone. Explore SRE opportunities at Google Follow us About Google Google products Privacy Terms Help | 2026-01-13T09:29:19 |
https://www.linkedin.com/products/netscout-arbor-sightline/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_full-click | Arbor Sightline | LinkedIn Skip to main content LinkedIn NETSCOUT in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Arbor Sightline Network Monitoring Software by NETSCOUT See who's skilled in this Add as skill Learn more Report this product About The network is the business. Operators must optimize resources, reduce service availability threats and thus save money. Arbor Sightline provides robust capabilities from network-wide capacity planning, to identifying and managing the mitigation of threats to the network. This pervasive network data can also be leveraged to make routing and peering design decisions, lower transit costs, eliminate network threats and provide your business with new revenue-generating services. Arbor’s DDoS attack protection solutions are based upon industry-leading technology. NETSCOUT offers a comprehensive portfolio of fully integrated, in‑cloud and on-premise DDoS protection products and services; all backed by continuous global threat intelligence. Media Products media viewer No more previous content Detecting and Mitigation a DDoS Attack Utilizing Arbor Sightline and TMS Learn how to detect and mitigate a DDoS Attack using NETSCOUT Arbor Sightline and TMS on a large enterprise or service provider network. Here, we demonstrate how DDoS Mitigation can be carried out by first detecting the attack and then automatically beginning mitigation using Arbor TMS. Multi-vector DDoS attacks are threats to all networks. In this example, NETSCOUT shows how Arbor Sightline and TMS can be used to detect and protect against an attack on a server farm. Threat Detection Through proactive detection of network or service availability threats, Sightline can quickly diagnose and manage DDoS attacks. Network Capacity Management You can employ Sightline to monitor the capacity of network infrastructure, which allows you to avoid saturation and re-engineer network traffic for more efficient utilization. Network Peering Analysis Your network delivers value to customers and users when it connects to other networks. Peering analysis helps determine what traffic can transfer off of expensive transit links to either free peering or even become revenue-generating as a new customer. Arbor Sightline Infrastructure No more next content Similar products NMS NMS Network Monitoring Software Network Operations Center (NOC) Network Operations Center (NOC) Network Monitoring Software TEMS™ Suite TEMS™ Suite Network Monitoring Software Progress Flowmon Progress Flowmon Network Monitoring Software ASM ASM Network Monitoring Software ONES (Open Networking Enterprise Suite) ONES (Open Networking Enterprise Suite) Network Monitoring Software Sign in to see more Show more Show less NETSCOUT products Arbor Edge Defense Arbor Edge Defense DDoS Protection Software Arbor Cloud DDoS Protection Arbor Cloud DDoS Protection DDoS Protection Software Arbor Threat Mitigation System (TMS) Arbor Threat Mitigation System (TMS) DDoS Protection Software InfiniStreamNG (ISNG) InfiniStreamNG (ISNG) Business Continuity Software nGenius Business Analytics nGenius Business Analytics Business Intelligence (BI) Software nGeniusONE nGeniusONE Application Performance Monitoring (APM) Software nGeniusPULSE nGeniusPULSE Network Management Software Omnis Threat Horizon Omnis Threat Horizon DDoS Protection Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:19 |
https://sre.google/resources/practices-and-processes/no-heroes/ | Why heroism is bad, and what we can do to stop it Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content Why Heroism Is Bad And What We Can Do To Stop It What is heroism? Why is "the Hero" a bad role to have on a team? In this article, learn about how to build your team to avoid heroism, and when heroics can indeed be useful. by Alexander Malmberg Use arrow keys to move to the next page Swipe to move to the next page What is heroism? When there's a systemic problem or gap in a system, and an individual decides to fill that gap. General pattern We have a system: a service, a team, a process, a piece of automation, some combination of the above... We want the system to have some nice property: often but not always an SLO of some kind. The system does not have this property. The Hero decides that, despite this, they will uphold this property, no matter what. No matter what No matter what includes: No matter how many hours they need to work. No matter that they need to work evenings and weekends. Often also: No matter what they're told about not doing this. No matter whether this property is actually important or not. No matter whether the team has "officially" decided to uphold this property. Example #1 Team has a ticket queue, and a ticket rotation, with one person assigned to tickets every week. They have a ticket SLO: all tickets will be handled within 24 hours. Ticket arrival rate is so high that, most days, the tickets arriving in one day cannot be handled in a normal 8-hour working day. Our Hero is on the case, though: They start working 12-, 14-, 16-hour days to make sure the ticket SLO is upheld. Example #2 Team has a production service and associated automation, tooling, and on-call rotation. They have an SLO for the service: 99.99% availability. But the service effectively does not run at 99.99% availability, due to inherent properties of the service, how it degrades, the team's release process, alerting thresholds, etc. Enter the Hero: Every day (including weekends), they look at the monitoring; they spot-check graphs. They roll back bad canaries by hand, they spot memory-use increases before alerts fire and submit CLs to fix the issues, and they spot outlier tasks and restart them to limit the damage, etc., etc. Example #3 Team has a launch process: Follow checklists, calculate resource requirements, submit changes, run automation to push out changes. There's explicit pressure to make launches happen quickly — after all, the launch is good for users, or might increase revenue. We don't want SREs slowing the launches down. But the process is full of manual work, and is very time consuming. The automation is flaky and needs hand-holding. Have no fear, Hero is here: They'll work 12-hour days to get everything in place, and then hand-hold the automation over the weekend to make sure we're ready to ramp up Monday morning. But wait... heroism has saved us before! Sometimes acts of heroism really are appreciated and necessary — we've all run into situations where we had a blind spot when planning, or experienced a major outage, or something weird and unexpected happened. But heroism shouldn't be something you plan for or rely on in the long term. If you're committing to an SLO, you should be able to meet the SLO without any heroes. Is firefighting heroism? Not necessarily. Heroism often comes in the form of firefighting or toil. However, if you have a proper, structured approach to firefighting, with realistic expectations, no heroism is required. On-call, when done right, does not require constant heroism. Heroism is bad for the system Because heroism masks systemic problems, the systemic problems are never fixed: The team never has proper discussions about a realistic SLO. The team doesn't realize that it needs to work on long-term systemic fixes that enable the system to behave the way it wants it to. The system is broken, and because the team doesn't realize that it's broken, the system never improves. Heroism is bad for the team Heroism cultivates a culture that reinforces unrealistic expectations about the amount of work and the type of work expected from team members, and about the behavior expected from our systems. Heroism is bad for the individual The individual performs vast quantities of uninteresting, low-impact work. They are likely to burn out. No matter what volume of rote work an engineer does, it's unlikely they will get promoted. Why is it hard to discourage? Heroism is low risk, and easy to do. A hero knows they can do and complete the work. (This can be a huge temptation for anyone with any form of impostor syndrome.) As a hero, you may receive immediate rewards: You complete a task, you feel that it's important, you often get praise from other members of your team or of a team that you helped, and you get peer bonuses . It "feels" really important, and after all, aren't we supposed to own and care deeply about the systems we run? How to discourage heroism Explain why the behavior is bad for the individual, the team, and the system. Tell the teammates engaging in heroism to let the system break. Explain why the behavior isn't constructive Help the Hero figure out what they should do instead. Often, they have a really good feel for where the pain points and problems in a system are, and have good but "raw" ideas about how to fix them. Push them to work on the long-term fixes. Let it break This sounds scary, but normally it isn't. Some common patterns here: The Hero really thinks the consequences of them not saving the system will be disastrous, but they really usually aren't. Sometimes the Hero is upholding some property that really isn't important, and the team (and Tech Leads, Managers, client teams, etc.) have decided that we really don't need to uphold the property—it isn't worth the cost. But the Hero won't let it go. Let it break If we have SLOs, we also have an error budget. A signal that a system is broken is a really valuable signal. It's worth spending some error budget to obtain that signal, and it's worth pointing this out (especially if the Hero thinks the world will end if they stop being a hero, but nobody else does). 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Follow us About Google Google products Privacy Terms Help | 2026-01-13T09:29:19 |
https://scholar.google.com/citations?view_op=metrics_intro&hl=ko&oe=KSC | Google 학술 검색 통계 로드 중... 현재 시스템이 작동되지 않습니다. 나중에 다시 시도해 주세요. 죄송합니다. 현재 Internet Explorer 버전에서는 일부 기능이 작동하지 않을 수 있습니다. 최적의 상태로 사용하려면 Chrome 또는 Mozilla Firefox 를 사용해 주세요. 내 프로필 내 서재 통계 알리미 설정 로그인 Google 학술 검색 통계 로그인 통계 상위 저작물 지난 5년간 최다 인용 저작물 자세히 알아보기 발행처 h5-색인 h5-중앙값 1. Nature 490 784 2. IEEE/CVF Conference on Computer Vision and Pattern Recognition 450 702 3. The New England Journal of Medicine 441 854 4. Science 415 653 5. Nature Communications 399 509 6. The Lancet 375 712 7. Neural Information Processing Systems 371 637 8. International Conference on Learning Representations 362 652 9. Advanced Materials 330 440 10. Cell 317 528 모두 보기 공공 접근 의무제출 연구비 지원 기관을 위한 요약 통계 자세히 알아보기 재정 지원 기관 공개 자료 1. National Natural Science Foundation of China - 캐시된 페이지 50% 2. US National Institutes of Health - 캐시된 페이지 74% 3. European Commission - 캐시된 페이지 88% 4. US National Science Foundation - 캐시된 페이지 64% 5. German Research Foundation - 캐시된 페이지 61% 6. Government of Spain - 캐시된 페이지 81% 7. US Department of Energy - 캐시된 페이지 73% 8. Natural Sciences and Engineering Research Council of Canada - 캐시된 페이지 56% 9. Department of Science & Technology, India - 캐시된 페이지 56% 모두 보기 개인정보처리방침 약관 도움말 학술검색 정보 검색 도움말 | 2026-01-13T09:29:19 |
https://git-scm.com/book/sv/v2/Git-p%c3%a5-servern-Smart-HTTP | Git - Smart HTTP About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Kom igång 1.1 Om versionshantering 1.2 En kort historik av Git 1.3 Vad är Git? 1.4 Kommandoraden 1.5 Installera Git 1.6 Använda Git för första gången 1.7 Få hjälp 1.8 Sammanfattning 2. Grunder i Git 2.1 Skaffa ett Git-förvar 2.2 Spara ändringar till förvaret 2.3 Visa historiken 2.4 Ångra saker 2.5 Jobba med fjärrförvar 2.6 Taggning 2.7 Git alias 2.8 Sammanfattning 3. Git förgreningar 3.1 Grenar i ett nötskal 3.2 Grundläggande förgrening och sammanslagning 3.3 Hantera grenar 3.4 Arbetsflöde med grenar 3.5 Fjärrgrenar 3.6 Grenflytt 3.7 Sammanfattning 4. Git på servern 4.1 Protokollen 4.2 Skaffa Git på en server 4.3 Generera din publika SSH-nyckel 4.4 Konvigurera servern 4.5 Git Daemonen 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Alternativ tillhandahållna av tredje part 4.10 Sammanfattning 5. Distribuerade Git 5.1 Distribuerade arbetsflöden 5.2 Medverka i ett projekt 5.3 Underhålla ett projekt 5.4 Sammanfattning 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Bilaga A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in PowerShell A1.7 Summary A2. Bilaga B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Bilaga C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.6 Git på servern - Smart HTTP Smart HTTP Vi har nu autentiserad åtkomst genom SSH och icke-autentiserad åtkomst genom git:// men det fins också protokoll som kan göra båda saker samtidigt. Att konfigurera Smart HTTP är praktiskt taget bara att tillåta ett CGI-skript som tillhandahålls tillsammans med Git som heter git-http-backend på servern. Detta CGI kommer läsa sökvägen och headers som skickas av git fetch eller git push till en HTTP URL och avgöra om klienten kan kommuniocera över HTTP (vilket stämmer för alla klienter sedan version 1.6.6). Om CGI ser att klienten är smart, kommer den att kommunicera smart med den, annars kommer den falla tillbaka till det dumma beteendet (så den är bakåtkompatibel för läsning med äldre klienter). Låt oss gå igenom en väldigt grundläggande konfiguration. Vi kommer att konfigurera detta med Apache som CGI-server. Om du inte har Apache så kan du installera det på en Linuxburk genom nåt liknande detta: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env Detta aktiverar även modulerna mod_cgi , mod_alias , och mod_env som behövs för att detta skall fungera ordentligt. DU kommer också behöva konfigurera Unixanvändargruppen för katalogerna /srv/git till www-data så att din webserver kan läsa och skriva till repona, eftersom Apacheinstansen som kör CGI-skriptet kommer (normalt) köras som den användaren: $ chgrp -R www-data /srv/git Nu behöver vi lägga till några rader i Apaches konfiguration för att köra git-http-backend som hanterare för något som inkommer till /git -sökvägen på webservern. SetEnv GIT_PROJECT_ROOT /srv/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/lib/git-core/git-http-backend/ Om du utelämnar miljövariabeln GIT_HTTP_EXPORT_ALL kommer Git bara tillhandahålla repon med git-daemon-export-ok -filen till icke-autentiserade klienter, precis som Gitdaemoenen gjorde. Slutligen behöver du tala om för Apache att tillåta anrop till git-http-backend och göra skrivningar autentiserade på något sätt, möjligtvis genom ett Auth-block som här: <Files "git-http-backend"> AuthType Basic AuthName "Git Access" AuthUserFile /srv/git/.htpasswd Require expr !(%{QUERY_STRING} -strmatch '*service=git-receive-pack*' || %{REQUEST_URI} =~ m#/git-receive-pack$#) Require valid-user </Files> Det kommer kräva att du skapar en .htpasswd -fil som innehåller lösenorden av alla giltiga användare. Här är ett exempel med att lägga till användaren “schacon” till filen: $ htpasswd -c /srv/git/.htpasswd schacon Det finns en mängd sätt att få Apache att autentisera användare, du måste välja och implementera en av dem. Detta är det enklaste exemplet vi kom på. Du kommer också med säkerhet vilja konfigurera SSL så att all data är krypterad. Vi dyker inte så långt ner i kaninhålet när det kommer till specifika Apachekonfigurationer, eftersom du mycket väl kan använda en annan server eller ha andra autentiseringsbehov. Iden är att Git kommer med ett CGI kallat git-http-backend som, när det anrpoas, gör all förhandling för att skicka och ta emot data över HTTP. Den implementerar inte själva autentiseringen, men det kan lätt kontrolleras av webbserverlagret som anropar den. Du kan göra detta med nästan alla CGI-kapabla webservrar, så använd den som du känner till bäst. Notera För mer information om konfigurering av autentisering av Apache, läs Apachedokumentationen här:http://httpd.apache.org/docs/current/howto/auth.html[] prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:19 |
http://www.trello.com/teams/marketing | Trello for Marketing Teams | Trello Skip to main content Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Use case: Task management Track progress of tasks in one convenient place with a visual layout that adds ‘ta-da’ to your to-do’s. Use case: Resource hub Save hours when you give teams a well-designed hub to find information easily and quickly. Use case: Project management Keep projects organized, deadlines on track, and teammates aligned with Trello. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Back Navigation Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Read though our use cases to make the most of Trello on your team. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Helping teams work better, together Discover Trello use cases, productivity tips, best practices for team collaboration, and expert remote work advice. Check out the Trello blog < Go back to Team Solutions Trello For Marketing Teams Whether launching a new product, campaign, or creating content, experience how Trello helps marketing teams around the world organize, plan, and get more done. Trello’s boards, lists, and cards enable teams to go from ideas to action in seconds. Visual and easy-to-use, Trello helps teams bring projects to life and keep them moving forward. Join over 2,000,000 teams worldwide who are using Trello to get more done. Your team’s workspace for marketing success All marketers have one thing in common: they wear a lot of (unique) hats. Organize all of your marketing processes, projects, and initiatives in one place with Trello. See all of our Marketing templates EDITORIAL CALENDAR Seamlessly coordinate content creation, editing, and production with the entire team, while keeping an eye on the publishing calendar and distribution strategy. GO-TO-MARKET CAMPAIGNS Seamlessly coordinate cross-team, go-to-market brand and product launches with a single Trello board, and ditch the browser tab tango of trying to collaborate across multiple apps. EMAIL WORKFLOW There’s one secret to keeping the moving pieces together: a bulletproof process with seamless cross-team collaboration. Litmus shares their workflow for email marketing success. EDITORIAL CALENDAR Seamlessly coordinate content creation, editing, and production with the entire team, while keeping an eye on the publishing calendar and distribution strategy. GO-TO-MARKET CAMPAIGNS Seamlessly coordinate cross-team, go-to-market brand and product launches with a single Trello board, and ditch the browser tab tango of trying to collaborate across multiple apps. EMAIL WORKFLOW There’s one secret to keeping the moving pieces together: a bulletproof process with seamless cross-team collaboration. Litmus shares their workflow for email marketing success. Visualize your work from the right angle. Power your Marketing team with Calendar View and ensure campaign launches are cool, calm, and collected—instead of chaotic. Learn more about Trello views Power-Up Your Marketing Team’s Productivity Simple, adaptable, customizable. Make Trello your marketing hub with Power-Ups. Connect your favorite apps and integrations to Trello and gather all of the information you need to get things done under one roof. Explore 150+ Power-Ups Move Work Forward, Auto-magically Trello’s built-in automation makes it easy to automate the repetitive, everyday tasks that keep your team from focusing on the work that matters most. Let the robots do the work Resources To Up Your Marketing Game Everything you need to improve your marketing department workflow with Trello, from industry leaders and the Trello team. HOW TO PLAN A SUCCESSFUL MARKETING CAMPAIGN IN TRELLO [Ebook] In this ebook, we’ll show you how to optimize your marketing campaign process with Trello, and establish a productive workflow for getting from start to finish that keeps your whole team involved and on track. READ MORE HOW TO CREATE YOUR PERFECT EDITORIAL CALENDAR WITH TRELLO [Blog Post] Follow this guide to create your own custom editorial calendar in a few easy steps so you can take any idea from potential pitch to successful, published blog post in style. READ MORE HOW TO VISUALLY PLAN YOUR EMAIL CALENDAR WITH TRELLO [Blog Post] This may come as a complete surprise, but we use Trello at Trello to manage our email process. Let's talk about why it’s a great tool for email calendar planning. READ MORE NOW AVAILABLE A 14 Day Free Trial of Premium! Get unlimited boards, Trello views, and limitless automation, plus a ton more. Try it today SwagUp: Scale Any Business With Trello BC “Not only did [Trello] unify our process and help everyone understand their role, but we were able to automate essential steps of the process so we could move a lot faster and grow to a multi-million dollar company with a team of ten.” –Founder, SwagUp Learn More Instinct Dog Training “As you scale, you need visibility, accountability, and organization. Trello has provided that for us.” –Brian Burton, Founder, Instinct Dog Training Learn More Desk Plants “We chose Trello because it is well-designed—it’s beautifully designed—intuitive, and really hit the nail on the head with what we needed to solve.” –Lawrence Hanley, founder of Desk Plants Learn More Scan2Cad “We use Trello because our data becomes alive. A bullet point list turns into real tasks that are assigned to real people with due dates and connections to our other apps. The power in that is fantastic.” –Luke Kennedy, CEO, Scan2Cad Learn More Palace Law “People have generally been happier since we started using Trello. It has made our lives a lot easier. People are less stressed.” -Jordan Couch, attorney at Palace Law Learn More Trello Your Way Ready to get your team up and running? Try the business tool so easy to use, your team can’t help but collaborate. Learn more about our pricing and plans Free $ 0 USD Free for up to 10 collaborators per Workspace Capture your to-dos, get organized, and get sh*t done. Standard $ 5 USD Per user/month if billed annually ($6 billed monthly) Get more stuff done with unlimited boards, card mirroring, and more automation. Learn more about Standard Premium $ 10 USD Per user/month if billed annually ($12.50 billed monthly) Add AI to your boards and admin controls to your toolkit. Plus, get more perspective with views. Learn more about Premium Enterprise $ 17.50 USD Per user/month - billed annually ($210.00 annual price per user) Add enterprise-grade security and controls. This plan includes Atlassian Guard Standard and 24/7 Enterprise Admin support. Est. cost for users Learn more about Enterprise Well, what are you waiting for? Head over to your boards and start getting things done! Log In About Trello What’s behind the boards. Jobs Learn about open roles on the Trello team. Apps Download the Trello App for your Desktop or Mobile devices. Contact us Need anything? Get in touch and we can help. Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Privacy Policy Terms Copyright © 2024 Atlassian | 2026-01-13T09:29:19 |
https://www.linkedin.com/products/netscout-arbor-cloud-ddos-protection?similarProducts=true&trk=products_details_guest_similar_products_section_sign_in | Arbor Cloud DDoS Protection | LinkedIn Skip to main content LinkedIn NETSCOUT in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Arbor Cloud DDoS Protection DDoS Protection Software by NETSCOUT See who's skilled in this Add as skill Learn more Report this product About Arbor Cloud combines on-premise DDoS defense with cloud-based traffic scrubbing services that are tightly integrated via an automated cloud signal. This multi-layered, adaptive DDoS protection approach is a proven industry best practice and is the only way to mitigate today's full spectrum of DDoS threats for both Service Providers and Enterprises, all from a single cloud DDoS protection provider. This product is intended for Cyber Security Engineer Chief Executive Officer Chief Information Officer Network Operations Center Head of Information Technology Network Security Engineer Security Engineer Director of Security Information Technology Specialist Director of Information Technology Media Products media viewer No more previous content Arbor Cloud Interface Arbor Cloud Arbor Cloud Infrastructure No more next content Similar products Cloudflare DDoS Protection Cloudflare DDoS Protection DDoS Protection Software Cloudflare Spectrum Cloudflare Spectrum DDoS Protection Software Akamai Prolexic Routed Akamai Prolexic Routed DDoS Protection Software OVHcloud Anti-DDoS Protection OVHcloud Anti-DDoS Protection DDoS Protection Software Kona DDoS Defender Kona DDoS Defender DDoS Protection Software Kaspersky DDoS Protection Kaspersky DDoS Protection DDoS Protection Software Sign in to see more Show more Show less NETSCOUT products Arbor Edge Defense Arbor Edge Defense DDoS Protection Software Arbor Sightline Arbor Sightline Network Monitoring Software Arbor Threat Mitigation System (TMS) Arbor Threat Mitigation System (TMS) DDoS Protection Software InfiniStreamNG (ISNG) InfiniStreamNG (ISNG) Business Continuity Software nGenius Business Analytics nGenius Business Analytics Business Intelligence (BI) Software nGeniusONE nGeniusONE Application Performance Monitoring (APM) Software nGeniusPULSE nGeniusPULSE Network Management Software Omnis Threat Horizon Omnis Threat Horizon DDoS Protection Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:19 |
https://git-scm.com/book/es/v2/GitHub-Gesti%c3%b3n-de-una-organizaci%c3%b3n | Git - Gestión de una organización About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Inicio - Sobre el Control de Versiones 1.1 Acerca del Control de Versiones 1.2 Una breve historia de Git 1.3 Fundamentos de Git 1.4 La Línea de Comandos 1.5 Instalación de Git 1.6 Configurando Git por primera vez 1.7 ¿Cómo obtener ayuda? 1.8 Resumen 2. Fundamentos de Git 2.1 Obteniendo un repositorio Git 2.2 Guardando cambios en el Repositorio 2.3 Ver el Historial de Confirmaciones 2.4 Deshacer Cosas 2.5 Trabajar con Remotos 2.6 Etiquetado 2.7 Alias de Git 2.8 Resumen 3. Ramificaciones en Git 3.1 ¿Qué es una rama? 3.2 Procedimientos Básicos para Ramificar y Fusionar 3.3 Gestión de Ramas 3.4 Flujos de Trabajo Ramificados 3.5 Ramas Remotas 3.6 Reorganizar el Trabajo Realizado 3.7 Recapitulación 4. Git en el Servidor 4.1 Los Protocolos 4.2 Configurando Git en un servidor 4.3 Generando tu clave pública SSH 4.4 Configurando el servidor 4.5 El demonio Git 4.6 HTTP Inteligente 4.7 GitWeb 4.8 GitLab 4.9 Git en un alojamiento externo 4.10 Resumen 5. Git en entornos distribuidos 5.1 Flujos de trabajo distribuidos 5.2 Contribuyendo a un Proyecto 5.3 Manteniendo un proyecto 5.4 Resumen 6. GitHub 6.1 Creación y configuración de la cuenta 6.2 Participando en Proyectos 6.3 Mantenimiento de un proyecto 6.4 Gestión de una organización 6.5 Scripting en GitHub 6.6 Resumen 7. Herramientas de Git 7.1 Revisión por selección 7.2 Organización interactiva 7.3 Guardado rápido y Limpieza 7.4 Firmando tu trabajo 7.5 Buscando 7.6 Reescribiendo la Historia 7.7 Reiniciar Desmitificado 7.8 Fusión Avanzada 7.9 Rerere 7.10 Haciendo debug con Git 7.11 Submódulos 7.12 Agrupaciones 7.13 Replace 7.14 Almacenamiento de credenciales 7.15 Resumen 8. Personalización de Git 8.1 Configuración de Git 8.2 Git Attributes 8.3 Puntos de enganche en Git 8.4 Un ejemplo de implantación de una determinada política en Git 8.5 Recapitulación 9. Git y Otros Sistemas 9.1 Git como Cliente 9.2 Migración a Git 9.3 Resumen 10. Los entresijos internos de Git 10.1 Fontanería y porcelana 10.2 Los objetos Git 10.3 Referencias Git 10.4 Archivos empaquetadores 10.5 Las especificaciones para hacer referencia a… (refspec) 10.6 Protocolos de transferencia 10.7 Mantenimiento y recuperación de datos 10.8 Variables de entorno 10.9 Recapitulación A1. Apéndice A: Git en otros entornos A1.1 Interfaces gráficas A1.2 Git en Visual Studio A1.3 Git en Eclipse A1.4 Git con Bash A1.5 Git en Zsh A1.6 Git en Powershell A1.7 Resumen A2. Apéndice B: Integrando Git en tus Aplicaciones A2.1 Git mediante Línea de Comandos A2.2 Libgit2 A2.3 JGit A3. Apéndice C: Comandos de Git A3.1 Configuración A3.2 Obtener y Crear Proyectos A3.3 Seguimiento Básico A3.4 Ramificar y Fusionar A3.5 Compartir y Actualizar Proyectos A3.6 Inspección y Comparación A3.7 Depuración A3.8 Parcheo A3.9 Correo Electrónico A3.10 Sistemas Externos A3.11 Administración A3.12 Comandos de Fontanería 2nd Edition 6.4 GitHub - Gestión de una organización Gestión de una organización Además de las cuentas de usuario, GitHub tiene Organizaciones. Al igual que las cuentas de usuario, las cuentas de organización tienen un espacio donde se guardarán los proyectos, pero en otras cosas son diferentes. Estas cuentas representan un grupo de gente que comparte la propiedad de los proyectos, y además se pueden gestionar estos miembros en subgrupos. Normalmente, estas cuentas se usan en equipos de desarrollo de código abierto (por ejemplo, un grupo para “perl” o para “rails) o empresas (como sería ``google” o “twitter”). Conceptos básicos Crear una organización es muy fácil: simplemente pulsa en el icono “+” en el lado superior derecho y selecciona “New organization”. Figura 126. El menú “New organization”. En primer lugar tienes que decidir el nombre de la organización y una dirección de correo que será el punto principal de contacto del grupo. A continuación puedes invitar a otros usuarios a que se unan como co-propietarios de la cuenta. Sigue estos pasos y serás propietario de un grupo nuevo. A diferencia las cuentas personales, las organizaciones son gratuitas siempre que los repositorios sean de código abierto (y por tanto, públicos). Como propietario de la organización, cuando bifurcas un repositorio podrás hacerlo a tu elección en el espacio de la organización. Cuando creas nuevos repositorios puedes también elegir el espacio donde se crearán: la organización o tu cuenta personal. Automáticamente, además, quedarás como vigilante (watcher) de los repositorios que crees en la organización. Al igual que en Tu icono , puedes subir un icono para personalizar un poco la organización, que aparecerá entre otros sitios en la página principal de la misma, que lista todos los repositorios y puede ser vista por cualquiera. Vamos a ver algunas cosas que son diferentes cuando se hacen con una cuenta de organización. Equipos Las organizaciones se asocian con individuos mediante los equipos, que son simplemente agrupaciones de cuentas de usuario y repositorios dentro de la organización, y qué accesos tienen esas personas sobre cada repositorio. Por ejemplo, si tu empresa tiene tres repositorios: frontend , backend y deployscripts'; y quieres que los desarrolladores de web tengan acceso a `frontend y tal vez a backend , y las personas de operaciones tengan acceso a backend y deployscripts . Los equipos hacen fácil esta organización, sin tener que gestionar los colaboradores en cada repositorio individual. La página de la organización te mostrará un panel simple con todos los repositorios, usuarios y equipos que se encuentran en ella. Figura 127. Página de la organización. Para gestionar tus equipos, puedes pulsar en la barra “Teams” del lado derecho en la página Página de la organización. . Esto te llevará a una página en la que puedes añadir los miembros del equipo, añadir repositorios al equipo o gestionar los ajustes y niveles de acceso del mismo. Cada equipo puede tener acceso de solo lectura, de escritura o administrativo al repositorio. Puedes cambiar el nivel pulsando en el botón “Settings” en Página de equipos. . Figura 128. Página de equipos. Cuando invitas a alguien a un equipo, recibirá un correo con una invitación. Además, hay menciones de equipo (por ejemplo, @acmecorp/frontend ) que servirán para que todos los miembros de ese equipo sean suscritos al hilo. Esto resulta útil si quieres involucrar a un equipo en algo al no tener claro a quién en concreto preguntar. Un usuario puede pertenecer a cuantos equipos desee, por lo que no uses equipos solamente para temas de control de acceso a repositorios, sino que puedes usarlos para formar equipos especializados y dispares como ux , css , refactoring , legal , etc. Auditorías Las organizaciones pueden también dar a los propietarios acceso a toda la información sobre la misma. Puedes incluso ir a la opción Audit Log y ver los eventos que han sucedido, quién hizo qué y dónde. Figura 129. Log de auditoría. También puedes filtrar por tipo de evento, por lugares o por personas concretas. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:19 |
https://git-scm.com/book/it/v2/Git-on-the-Server-Smart-HTTP | Git - Smart HTTP About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Per Iniziare 1.1 Il Controllo di Versione 1.2 Una Breve Storia di Git 1.3 Cos’é Git? 1.4 La riga di comando 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Chiedere aiuto 1.8 Sommario 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Sommario 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendice A: Git in altri contesti A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Riassunto A2. Appendice B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendice C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.6 Git on the Server - Smart HTTP Smart HTTP We now have authenticated access though SSH and unauthenticated access through git:// , but there is also a protocol that can do both at the same time. Setting up Smart HTTP is basically just enabling a CGI script that is provided with Git called git-http-backend on the server.git commands, "http-backend" This CGI will read the path and headers sent by a git fetch or git push to an HTTP URL and determine if the client can communicate over HTTP (which is true for any client since version 1.6.6). If the CGI sees that the client is smart, it will communicate smartly with it, otherwise it will fall back to the dumb behavior (so it is backward compatible for reads with older clients). Let’s walk though a very basic setup. We’ll set this up with Apache as the CGI server. If you don’t have Apache setup, you can do so on a Linux box with something like this: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env This also enables the mod_cgi , mod_alias , and mod_env modules, which are all needed for this to work properly. Next we need to add some things to the Apache configuration to run the git http-backend as the handler for anything coming into the /git path of your web server. SetEnv GIT_PROJECT_ROOT /opt/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/libexec/git-core/git-http-backend/ If you leave out GIT_HTTP_EXPORT_ALL environment variable, then Git will only serve to unauthenticated clients the repositories with the git-daemon-export-ok file in them, just like the Git daemon did. Then you’ll have to tell Apache to allow requests to that path with something like this: <Directory "/usr/lib/git-core*"> Options ExecCGI Indexes Order allow,deny Allow from all Require all granted </Directory> Finally you’ll want to make writes be authenticated somehow, possibly with an Auth block like this: <LocationMatch "^/git/.*/git-receive-pack$"> AuthType Basic AuthName "Git Access" AuthUserFile /opt/git/.htpasswd Require valid-user </LocationMatch> That will require you to create a .htaccess file containing the passwords of all the valid users. Here is an example of adding a “schacon” user to the file: $ htdigest -c /opt/git/.htpasswd "Git Access" schacon There are tons of ways to have Apache authenticate users, you’ll have to choose and implement one of them. This is just the simplest example we could come up with. You’ll also almost certainly want to set this up over SSL so all this data is encrypted. We don’t want to go too far down the rabbit hole of Apache configuration specifics, since you could well be using a different server or have different authenication needs. The idea is that Git comes with a CGI called git http-backend that when invoked will do all the negotiation to send and receive data over HTTP. It does not implement any authentication itself, but that can easily be controlled at the layer of the web server that invokes it. You can do this with nearly any CGI-capable web server, so go with the one that you know best. Nota For more information on configuring authentication in Apache, check out the Apache docs here: http://httpd.apache.org/docs/current/howto/auth.html prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:19 |
https://git-scm.com/book/ko/v2/Git-%ec%84%9c%eb%b2%84-%ec%8a%a4%eb%a7%88%ed%8a%b8-HTTP | Git - 스마트 HTTP About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 시작하기 1.1 버전 관리란? 1.2 짧게 보는 Git의 역사 1.3 Git 기초 1.4 CLI 1.5 Git 설치 1.6 Git 최초 설정 1.7 도움말 보기 1.8 요약 2. Git의 기초 2.1 Git 저장소 만들기 2.2 수정하고 저장소에 저장하기 2.3 커밋 히스토리 조회하기 2.4 되돌리기 2.5 리모트 저장소 2.6 태그 2.7 Git Alias 2.8 요약 3. Git 브랜치 3.1 브랜치란 무엇인가 3.2 브랜치와 Merge 의 기초 3.3 브랜치 관리 3.4 브랜치 워크플로 3.5 리모트 브랜치 3.6 Rebase 하기 3.7 요약 4. Git 서버 4.1 프로토콜 4.2 서버에 Git 설치하기 4.3 SSH 공개키 만들기 4.4 서버 설정하기 4.5 Git 데몬 4.6 스마트 HTTP 4.7 GitWeb 4.8 GitLab 4.9 또 다른 선택지, 호스팅 4.10 요약 5. 분산 환경에서의 Git 5.1 분산 환경에서의 워크플로 5.2 프로젝트에 기여하기 5.3 프로젝트 관리하기 5.4 요약 6. GitHub 6.1 계정 만들고 설정하기 6.2 GitHub 프로젝트에 기여하기 6.3 GitHub 프로젝트 관리하기 6.4 Organization 관리하기 6.5 GitHub 스크립팅 6.6 요약 7. Git 도구 7.1 리비전 조회하기 7.2 대화형 명령 7.3 Stashing과 Cleaning 7.4 내 작업에 서명하기 7.5 검색 7.6 히스토리 단장하기 7.7 Reset 명확히 알고 가기 7.8 고급 Merge 7.9 Rerere 7.10 Git으로 버그 찾기 7.11 서브모듈 7.12 Bundle 7.13 Replace 7.14 Credential 저장소 7.15 요약 8. Git맞춤 8.1 Git 설정하기 8.2 Git Attributes 8.3 Git Hooks 8.4 정책 구현하기 8.5 요약 9. Git과 여타 버전 관리 시스템 9.1 Git: 범용 Client 9.2 Git으로 옮기기 9.3 요약 10. Git의 내부 10.1 Plumbing 명령과 Porcelain 명령 10.2 Git 개체 10.3 Git Refs 10.4 Packfile 10.5 Refspec 10.6 데이터 전송 프로토콜 10.7 운영 및 데이터 복구 10.8 환경변수 10.9 요약 A1. 부록 A: 다양한 환경에서 Git 사용하기 A1.1 GUI A1.2 Visual Studio A1.3 Eclipse A1.4 Bash A1.5 Zsh A1.6 Git in Powershell A1.7 요약 A2. 부록 B: 애플리케이션에 Git 넣기 A2.1 Git 명령어 A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. 부록 C: Git 명령어 A3.1 설치와 설정 A3.2 프로젝트 가져오기와 생성하기 A3.3 스냅샷 다루기 A3.4 Branch와 Merge A3.5 공유하고 업데이트하기 A3.6 보기와 비교 A3.7 Debugging A3.8 Patch 하기 A3.9 Email A3.10 다른 버전 관리 시스템 A3.11 관리 A3.12 Plumbing 명령어 2nd Edition 4.6 Git 서버 - 스마트 HTTP 스마트 HTTP 지금까지 인증 기능을 갖춘 SSH와 인증 기능이 없는 git 프로토콜을 배웠다. 이제는 이 두 기능을 한꺼번에 가진 프로토콜을 알아보자. 서버에서 git-http-backend 명령어를 이용해 일단 기본적인 스마트 HTTP를 지원하는 Git 서버를 실행한다. Git 클라이언트에서 git fetch 나 git push 를 실행하면 서버로 HTTP 요청을 보낸다. 서버는 그 요청을 보고 경로와 헤더를 읽어 클라이언트가 HTTP로 통신하려 하는지 감지한다. 이는 1.6.6 버전 이상의 클라이언트에서 동작한다. 서버는 클라이언트가 스마트 HTTP 프로토콜을 지원한다고 판단되면 스마트 HTTP 프로토콜을 사용하고 아니면 멍청한 프로토콜을 계속 사용한다. 덕분에 하위 호환성이 잘 유지된다. 이제 설정해보자. CGI 서버로 Apache를 사용한다. Apache가 없다면 Linux에서는 아래와 같이 Apache를 설치할 수 있다. $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env 이 명령어 한 방이면 mod_cgi , mod_alias , mod_env 도 사용할 수 있다. 다 앞으로 사용할 모듈들이다. /srv/git 디렉토리의 Unix 사용자 그룹도 www-data 로 설정해야 한다. 그래야 웹 서버가 저장소를 읽고 쓸 수 있다. Apache 인스턴스는 CGI 스크립트를 이 사용자로 실행시킨다(기본 설정이다). $ chgrp -R www-data /srv/git 그리고 Apache 설정 파일을 수정한다. 그러면 git http-backend 를 실행했을 때 모든 요청을 /git 경로로 받을 수 있다. SetEnv GIT_PROJECT_ROOT /srv/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/lib/git-core/git-http-backend/ GIT_HTTP_EXPORT_ALL 환경 변수를 설정하지 않으면 git-daemon-export-ok 파일이 있는 저장소에는 아무나 다 접근할 수 있게 된다. 그냥 Git 데몬의 동작과 똑같다. 마지막으로 Apache가 git-http-backend 에 요청하는 것을 허용하고 쓰기 접근 시 인증하게 한다. <Files "git-http-backend"> AuthType Basic AuthName "Git Access" AuthUserFile /srv/git/.htpasswd Require expr !(%{QUERY_STRING} -strmatch '*service=git-receive-pack*' || %{REQUEST_URI} =~ m#/git-receive-pack$#) Require valid-user </Files> .htpasswd 파일에는 접근을 허가하려는 사용자의 암호가 들어가 있어야 한다. 아래는 “schacon” 이란 사용자를 추가하는 방법이다. $ htpasswd -c /srv/git/.htpasswd schacon Apache에는 사용자 인증 방법이 많다. 그중 하나를 골라 사용해야 하는데 위에 설명한 방법이 가장 간단한 방법의 하나다. 그리고 이렇게 사용자 인증 설정을 할 때는 보안을 위해 SSL로 접속해 작업하는 것이 좋다. 웹 서버는 Apache 말고도 다른 서버를 사용할 수도 있고, 인증 방식도 다르므로 Apache 설정에 대해서 길게 이야기하지 않는다. 대신 이것만 알아두었으면 한다. HTTP를 이용한 모든 통신에서는 git http-backend 와 Git을 함께 사용한다는 것이다. Git 그 자체로는 인증 기능을 가지고 있지 않다. 하지만 웹 서버의 인증 레이어와 손쉽게 연동할 수 있다. CGI를 실행할 수 있는 웹 서버라면 어떤 서버든지 붙일 수 있다. 가장 좋아하는 서버를 사용하길 바란다. 노트 Apache 웹 서버에서 인증 설정에 대해 더 자세히 알아보려면 Apache 문서를 참고하길 바란다.( http://httpd.apache.org/docs/current/howto/auth.html ) prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:19 |
https://bsky.app/profile/w3techs.com | @w3techs.com on Bluesky JavaScript Required This is a heavily interactive web application, and JavaScript is required. Simple HTML interfaces are possible, but that is not what this is. Learn more about Bluesky at bsky.social and atproto.com . Profile W3Techs w3techs.com did:plc:e3abkzebuven347lwqci7lg4 W3Techs.com provides web technology surveys | 2026-01-13T09:29:20 |
https://git-scm.com/book/be/v2/Git-on-the-Server-Smart-HTTP | Git - Smart HTTP About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Першыя крокі 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Падсумаваньне 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Дадатак A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Дадатак B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Дадатак C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.6 Git on the Server - Smart HTTP Smart HTTP We now have authenticated access through SSH and unauthenticated access through git:// , but there is also a protocol that can do both at the same time. Setting up Smart HTTP is basically just enabling a CGI script that is provided with Git called git-http-backend on the server. This CGI will read the path and headers sent by a git fetch or git push to an HTTP URL and determine if the client can communicate over HTTP (which is true for any client since version 1.6.6). If the CGI sees that the client is smart, it will communicate smartly with it; otherwise it will fall back to the dumb behavior (so it is backward compatible for reads with older clients). Let’s walk through a very basic setup. We’ll set this up with Apache as the CGI server. If you don’t have Apache setup, you can do so on a Linux box with something like this: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env This also enables the mod_cgi , mod_alias , and mod_env modules, which are all needed for this to work properly. You’ll also need to set the Unix user group of the /srv/git directories to www-data so your web server can read- and write-access the repositories, because the Apache instance running the CGI script will (by default) be running as that user: $ chgrp -R www-data /srv/git Next we need to add some things to the Apache configuration to run the git-http-backend as the handler for anything coming into the /git path of your web server. SetEnv GIT_PROJECT_ROOT /srv/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/lib/git-core/git-http-backend/ If you leave out GIT_HTTP_EXPORT_ALL environment variable, then Git will only serve to unauthenticated clients the repositories with the git-daemon-export-ok file in them, just like the Git daemon did. Finally you’ll want to tell Apache to allow requests to git-http-backend and make writes be authenticated somehow, possibly with an Auth block like this: <Files "git-http-backend"> AuthType Basic AuthName "Git Access" AuthUserFile /srv/git/.htpasswd Require expr !(%{QUERY_STRING} -strmatch '*service=git-receive-pack*' || %{REQUEST_URI} =~ m#/git-receive-pack$#) Require valid-user </Files> That will require you to create a .htpasswd file containing the passwords of all the valid users. Here is an example of adding a “schacon” user to the file: $ htpasswd -c /srv/git/.htpasswd schacon There are tons of ways to have Apache authenticate users, you’ll have to choose and implement one of them. This is just the simplest example we could come up with. You’ll also almost certainly want to set this up over SSL so all this data is encrypted. We don’t want to go too far down the rabbit hole of Apache configuration specifics, since you could well be using a different server or have different authentication needs. The idea is that Git comes with a CGI called git-http-backend that when invoked will do all the negotiation to send and receive data over HTTP. It does not implement any authentication itself, but that can easily be controlled at the layer of the web server that invokes it. You can do this with nearly any CGI-capable web server, so go with the one that you know best. Заўвага For more information on configuring authentication in Apache, check out the Apache docs here: https://httpd.apache.org/docs/current/howto/auth.html prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/uz/v2/Git-%d1%81%d0%b5%d1%80%d0%b2%d0%b5%d1%80%d0%b4%d0%b0-Smart-HTTP | Git - Smart HTTP About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Иш бошланиши 1.1 Талқинларни бошқариш ҳақида 1.2 Git нинг қисқача тарихи 1.3 Git асоси 1.4 Командалар сатри 1.5 Git ни ўрнатиш 1.6 Git да биринчи созлашлар 1.7 Қандай ёрдам олиш мумкин? 1.8 Хулосалар 2. Git асослари 2.1 Git омборини яратиш 2.2 Ўзгаришларни омборга ёзиш 2.3 Фиксирлашлар тарихини кўриш 2.4 Ўзгаришларни бекор қилиш 2.5 Узоқ масофадаги омборлар билан ишлаш 2.6 Тамғалаш 2.7 Git да таҳаллуслар 2.8 Хулоса 3. Git да тармоқланиш 3.1 Тармоқланиш ҳақида икки оғиз сўз 3.2 Тармоқланиш ва бирлашиш асослари 3.3 Тармоқларни бошқариш 3.4 Иш жараёнларини тармоқлаш 3.5 Узоқ масофадаги тармоқлар 3.6 Қайта асосланиш 3.7 Хулосалар 4. Git серверда 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Sizning SSH ochiq (public) kalitingizni generatsiyalash 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Хулосалар 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Qism modullar (Submodule) 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.6 Git серверда - Smart HTTP Smart HTTP We now have authenticated access though SSH and unauthenticated access through git:// , but there is also a protocol that can do both at the same time. Setting up Smart HTTP is basically just enabling a CGI script that is provided with Git called git-http-backend on the server. This CGI will read the path and headers sent by a git fetch or git push to an HTTP URL and determine if the client can communicate over HTTP (which is true for any client since version 1.6.6). If the CGI sees that the client is smart, it will communicate smartly with it, otherwise it will fall back to the dumb behavior (so it is backward compatible for reads with older clients). Let’s walk through a very basic setup. We’ll set this up with Apache as the CGI server. If you don’t have Apache setup, you can do so on a Linux box with something like this: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env This also enables the mod_cgi , mod_alias , and mod_env modules, which are all needed for this to work properly. Next we need to add some things to the Apache configuration to run the git-http-backend as the handler for anything coming into the /git path of your web server. SetEnv GIT_PROJECT_ROOT /opt/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/libexec/git-core/git-http-backend/ If you leave out GIT_HTTP_EXPORT_ALL environment variable, then Git will only serve to unauthenticated clients the repositories with the git-daemon-export-ok file in them, just like the Git daemon did. Then you’ll have to tell Apache to allow requests to that path with something like this: <Directory "/usr/lib/git-core*"> Options ExecCGI Indexes Order allow,deny Allow from all Require all granted </Directory> Finally you’ll want to make writes be authenticated somehow, possibly with an Auth block like this: <LocationMatch "^/git/.*/git-receive-pack$"> AuthType Basic AuthName "Git Access" AuthUserFile /opt/git/.htpasswd Require valid-user </LocationMatch> That will require you to create a .htaccess file containing the passwords of all the valid users. Here is an example of adding a “schacon” user to the file: $ htdigest -c /opt/git/.htpasswd "Git Access" schacon There are tons of ways to have Apache authenticate users, you’ll have to choose and implement one of them. This is just the simplest example we could come up with. You’ll also almost certainly want to set this up over SSL so all this data is encrypted. We don’t want to go too far down the rabbit hole of Apache configuration specifics, since you could well be using a different server or have different authentication needs. The idea is that Git comes with a CGI called git-http-backend that when invoked will do all the negotiation to send and receive data over HTTP. It does not implement any authentication itself, but that can easily be controlled at the layer of the web server that invokes it. You can do this with nearly any CGI-capable web server, so go with the one that you know best. Note For more information on configuring authentication in Apache, check out the Apache docs here: http://httpd.apache.org/docs/current/howto/auth.html prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/ru/v2/Git-%d0%bd%d0%b0-%d1%81%d0%b5%d1%80%d0%b2%d0%b5%d1%80%d0%b5-%d0%a3%d0%bc%d0%bd%d1%8b%d0%b9-HTTP | Git - Умный HTTP About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Введение 1.1 О системе контроля версий 1.2 Краткая история Git 1.3 Что такое Git? 1.4 Командная строка 1.5 Установка Git 1.6 Первоначальная настройка Git 1.7 Как получить помощь? 1.8 Заключение 2. Основы Git 2.1 Создание Git-репозитория 2.2 Запись изменений в репозиторий 2.3 Просмотр истории коммитов 2.4 Операции отмены 2.5 Работа с удалёнными репозиториями 2.6 Работа с тегами 2.7 Псевдонимы в Git 2.8 Заключение 3. Ветвление в Git 3.1 О ветвлении в двух словах 3.2 Основы ветвления и слияния 3.3 Управление ветками 3.4 Работа с ветками 3.5 Удалённые ветки 3.6 Перебазирование 3.7 Заключение 4. Git на сервере 4.1 Протоколы 4.2 Установка Git на сервер 4.3 Генерация открытого SSH ключа 4.4 Настраиваем сервер 4.5 Git-демон 4.6 Умный HTTP 4.7 GitWeb 4.8 GitLab 4.9 Git-хостинг 4.10 Заключение 5. Распределённый Git 5.1 Распределённый рабочий процесс 5.2 Участие в проекте 5.3 Сопровождение проекта 5.4 Заключение 6. GitHub 6.1 Настройка и конфигурация учётной записи 6.2 Внесение собственного вклада в проекты 6.3 Сопровождение проекта 6.4 Управление организацией 6.5 Создание сценариев GitHub 6.6 Заключение 7. Инструменты Git 7.1 Выбор ревизии 7.2 Интерактивное индексирование 7.3 Припрятывание и очистка 7.4 Подпись 7.5 Поиск 7.6 Перезапись истории 7.7 Раскрытие тайн reset 7.8 Продвинутое слияние 7.9 Rerere 7.10 Обнаружение ошибок с помощью Git 7.11 Подмодули 7.12 Создание пакетов 7.13 Замена 7.14 Хранилище учётных данных 7.15 Заключение 8. Настройка Git 8.1 Конфигурация Git 8.2 Атрибуты Git 8.3 Хуки в Git 8.4 Пример принудительной политики Git 8.5 Заключение 9. Git и другие системы контроля версий 9.1 Git как клиент 9.2 Переход на Git 9.3 Заключение 10. Git изнутри 10.1 Сантехника и Фарфор 10.2 Объекты Git 10.3 Ссылки в Git 10.4 Pack-файлы 10.5 Спецификации ссылок 10.6 Протоколы передачи данных 10.7 Обслуживание репозитория и восстановление данных 10.8 Переменные окружения 10.9 Заключение A1. Приложение A: Git в других окружениях A1.1 Графические интерфейсы A1.2 Git в Visual Studio A1.3 Git в Visual Studio Code A1.4 Git в Eclipse A1.5 Git в IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.6 Git в Sublime Text A1.7 Git в Bash A1.8 Git в Zsh A1.9 Git в PowerShell A1.10 Заключение A2. Приложение B: Встраивание Git в ваши приложения A2.1 Git из командной строки A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Приложение C: Команды Git A3.1 Настройка и конфигурация A3.2 Клонирование и создание репозиториев A3.3 Основные команды A3.4 Ветвление и слияния A3.5 Совместная работа и обновление проектов A3.6 Осмотр и сравнение A3.7 Отладка A3.8 Внесение исправлений A3.9 Работа с помощью электронной почты A3.10 Внешние системы A3.11 Администрирование A3.12 Низкоуровневые команды 2nd Edition 4.6 Git на сервере - Умный HTTP Умный HTTP Теперь у нас есть доступ с аутентификацией через SSH и неаутентифицированный доступ через git:// , но есть ещё протокол, который может делать и то и другое. Настройка умного HTTP — это просто установка на сервер CGI-скрипта git-http-backend , поставляемого вместе с Git. Этот CGI-скрипт будет читать путь и заголовки, посылаемые git fetch или git push в URL и определять, может ли клиент работать через HTTP (это верно для любого клиента, начиная с версии 1.6.6). Если CGI-скрипт видит, что клиент умный, то и общаться с ним будет по-умному, иначе откатится на простое поведение (что делает операции чтения обратно совместимыми со старыми клиентами). Давайте пройдёмся по самой базовой установке. Мы настроим Apache как сервер CGI. Если у вас не установлен Apache, вы можете сделать это на Linux-машине примерно так: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env Это также включит необходимые для корректной работы модули mod_cgi , mod_alias и mod_env . Так же необходимо установить Unix пользователя и группу для каталога /srv/git в значение www-data , чтобы позволить веб-серверу читать из и писать в репозитории, потому что процесс Apache, запускающий CGI скрипт, работает от имени этого пользователя: $ chgrp -R www-data /srv/git Затем добавим некоторые настройки в конфигурационный файл Apache, чтобы запускать git-http-backend как обработчик для всех запросов, содержащих /git . SetEnv GIT_PROJECT_ROOT /srv/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/lib/git-core/git-http-backend/ Если пропустить переменную окружения GIT_HTTP_EXPORT_ALL , тогда Git будет отдавать только неаутентифицированным клиентам репозитории с файлом git-daemon-export-ok внутри, также как это делает Git-демон. Наконец, нужно разрешить Apache обрабатывать запросы к git-http-backend , при этом запросы на запись должны быть авторизованы, для этого можно использовать вот такой блок конфигурации: <Files "git-http-backend"> AuthType Basic AuthName "Git Access" AuthUserFile /srv/git/.htpasswd Require expr !(%{QUERY_STRING} -strmatch '*service=git-receive-pack*' || %{REQUEST_URI} =~ m#/git-receive-pack$#) Require valid-user </Files> Это потребует создания файла .htpasswd , содержащего пароли всех пользователей. Например, добавление пользователя «schacon» в этот файл делается так: $ htpasswd -c /srv/git/.htpasswd schacon Существует множество способов аутентифицировать пользователей в Apache, вам нужно выбрать и применить хотя бы один из них. Мы привели простейший пример. Скорее всего вы ещё захотите настроить SSL для шифрования трафика. Мы не хотим погружаться слишком глубоко в бездну настроек Apache, так как у вас может быть другой сервер или другие требования к аутентификации. Идея в том, что Git идёт с CGI-скриптом git-http-backend , который берёт на себя согласование передачи и приёма данных по HTTP. Сам по себе, он не реализует аутентификации, но это легко настраивается на уровне веб-сервера, который его запускает. Вы можете сделать это практически на любом веб-сервере с поддержкой CGI, так что используйте тот, который знаете лучше всего. Примечание За дополнительной информацией по настройке аутентификации в Apache обратитесь к документации: https://httpd.apache.org/docs/current/howto/auth.html prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://sre.google/local/ | Google SRE Events Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content Google SRE Events Google SRE invites the community to join us at our local events and meetups, taking place in the following locations. The events offer a chance to share knowledge and to meet folks from SRE and related fields. Munich New York Pittsburgh Sunnyvale Munich https://muc.sre.xyz/ New York https://www.meetup.com/new-york-site-reliability-engineering-tech-talks/ Pittsburgh https://www.meetup.com/pittsburgh-site-reliability-engineering/ Sunnyvale https://www.meetup.com/google-bay-area-sre-engagement/ Note: These are not recruiting events, and no recruiters from Google or other companies participate. Follow us About Google Google products Privacy Terms Help | 2026-01-13T09:29:20 |
https://sre.google/resources/practices-and-processes/art-of-slos/ | Google SRE - Art of slo | customer reliability engineering Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content The Art of SLOs This page is also available in 日本語 Introduction The Art of SLOs is a workshop developed by Google's Customer Reliability Engineering team. The goal of the workshop is to introduce participants to the way Google measures service reliability—in terms of Service Level Indicators (SLIs) and Service Level Objectives (SLOs) —and give them some hands-on experience with creating these measures in practice. These are important, fundamental concepts: it is far easier to have a meaningful conversation about the reliability of a service when you have an objective way of measuring that reliability. In the theoretical part of the workshop, participants learn how setting a target that describes the desired reliability of their services can resolve the organizational tension that so often arises between development and operations teams. They are shown how SLOs and Error Budgets can be used to measure and manage the reliability of a service in a data-driven, objective and user-focused manner. The workshop takes a technical turn as participants are given a brief introduction to the qualities that make for good SLIs. Finally, the session wraps up with an application of the four-step process for developing SLIs to a simple interaction users have with the server-side infrastructure of a fictional mobile game. The practical part of the workshop asks participants to apply what they've learned to more complex interactions between the users of the game and its infrastructure. Each interaction has a particular twist that challenges them to think hard about what the user expects, and how to find a good proxy measure for how well the service meets those expectations. Finally, they're given example answers, which they can compare to their own progress and reasoning. Target Audience The workshop content is relatively technical and primarily aimed at development and operations engineers and their immediate management. However, you'll have the best results if you can include technically-minded product people and business leaders as well. SLO targets need to be set with your users in mind, and error budgets can only resolve organizational tensions if the consequences for exceeding them have executive backing. If you don't have a whole team to educate, you might be interested in our Measuring and Managing Reliability course on Coursera , which is a more thorough, self-paced dive into the world of SLIs, SLOs and error budgets. Workshop Materials The Art of SLOs – Slides The presentation and the backbone of the workshop. It contains the training content that prepares participants for the practical exercises. There are detailed speaker notes for presenters that make it possible to deliver the workshop with minimum preparation. PDF version of these slides, without speaker notes The Art of SLOs – Participant Resources A 28-page printable handbook to give to each workshop participant on the day of training. It contains reference material that is useful both during the workshop and more generally when creating SLOs for services, as well as the backstory and technical details of the fictional mobile game necessary for the practical exercises. Handbook-A4 Handbook-Letter Handbook-A5 Handbook-Half-Letter SLO Worksheet SLO Worksheet A4 SLO Worksheet Letter SLO Cheatsheet The Art of SLOs – Facilitator Resources The facilitator’s handbook for planning and running an Art of SLOs workshop. It contains—spoiler alert!—long-form example SLOs, with detailed rationales for the decisions made, for two of the more complex and challenging interactions participants are asked to develop SLOs for. Handbook A4 Handbook Letter Handbook A5 Handbook Half-Letter Licensing The four documents above are released under the Creative Commons CC-BY-4.0 license for anyone to use and reuse—as long as Google is credited as the original author. If you want to suggest improvements , have any problems with the content , or just want to ask a question please create a bug in our issue tracker component . Follow us About Google Google products Privacy Terms Help English 日本語 (日本) | 2026-01-13T09:29:20 |
https://git-scm.com/book/es/v2/Git-en-el-Servidor-El-demonio-Git | Git - El demonio Git About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Inicio - Sobre el Control de Versiones 1.1 Acerca del Control de Versiones 1.2 Una breve historia de Git 1.3 Fundamentos de Git 1.4 La Línea de Comandos 1.5 Instalación de Git 1.6 Configurando Git por primera vez 1.7 ¿Cómo obtener ayuda? 1.8 Resumen 2. Fundamentos de Git 2.1 Obteniendo un repositorio Git 2.2 Guardando cambios en el Repositorio 2.3 Ver el Historial de Confirmaciones 2.4 Deshacer Cosas 2.5 Trabajar con Remotos 2.6 Etiquetado 2.7 Alias de Git 2.8 Resumen 3. Ramificaciones en Git 3.1 ¿Qué es una rama? 3.2 Procedimientos Básicos para Ramificar y Fusionar 3.3 Gestión de Ramas 3.4 Flujos de Trabajo Ramificados 3.5 Ramas Remotas 3.6 Reorganizar el Trabajo Realizado 3.7 Recapitulación 4. Git en el Servidor 4.1 Los Protocolos 4.2 Configurando Git en un servidor 4.3 Generando tu clave pública SSH 4.4 Configurando el servidor 4.5 El demonio Git 4.6 HTTP Inteligente 4.7 GitWeb 4.8 GitLab 4.9 Git en un alojamiento externo 4.10 Resumen 5. Git en entornos distribuidos 5.1 Flujos de trabajo distribuidos 5.2 Contribuyendo a un Proyecto 5.3 Manteniendo un proyecto 5.4 Resumen 6. GitHub 6.1 Creación y configuración de la cuenta 6.2 Participando en Proyectos 6.3 Mantenimiento de un proyecto 6.4 Gestión de una organización 6.5 Scripting en GitHub 6.6 Resumen 7. Herramientas de Git 7.1 Revisión por selección 7.2 Organización interactiva 7.3 Guardado rápido y Limpieza 7.4 Firmando tu trabajo 7.5 Buscando 7.6 Reescribiendo la Historia 7.7 Reiniciar Desmitificado 7.8 Fusión Avanzada 7.9 Rerere 7.10 Haciendo debug con Git 7.11 Submódulos 7.12 Agrupaciones 7.13 Replace 7.14 Almacenamiento de credenciales 7.15 Resumen 8. Personalización de Git 8.1 Configuración de Git 8.2 Git Attributes 8.3 Puntos de enganche en Git 8.4 Un ejemplo de implantación de una determinada política en Git 8.5 Recapitulación 9. Git y Otros Sistemas 9.1 Git como Cliente 9.2 Migración a Git 9.3 Resumen 10. Los entresijos internos de Git 10.1 Fontanería y porcelana 10.2 Los objetos Git 10.3 Referencias Git 10.4 Archivos empaquetadores 10.5 Las especificaciones para hacer referencia a… (refspec) 10.6 Protocolos de transferencia 10.7 Mantenimiento y recuperación de datos 10.8 Variables de entorno 10.9 Recapitulación A1. Apéndice A: Git en otros entornos A1.1 Interfaces gráficas A1.2 Git en Visual Studio A1.3 Git en Eclipse A1.4 Git con Bash A1.5 Git en Zsh A1.6 Git en Powershell A1.7 Resumen A2. Apéndice B: Integrando Git en tus Aplicaciones A2.1 Git mediante Línea de Comandos A2.2 Libgit2 A2.3 JGit A3. Apéndice C: Comandos de Git A3.1 Configuración A3.2 Obtener y Crear Proyectos A3.3 Seguimiento Básico A3.4 Ramificar y Fusionar A3.5 Compartir y Actualizar Proyectos A3.6 Inspección y Comparación A3.7 Depuración A3.8 Parcheo A3.9 Correo Electrónico A3.10 Sistemas Externos A3.11 Administración A3.12 Comandos de Fontanería 2nd Edition 4.5 Git en el Servidor - El demonio Git El demonio Git Ahora vamos a configurar un “demonio” sirviendo repositorios mediante el protocolo “Git”. Es la forma más común para dar acceso anónimo, pero rápido, a los repositorios. Recuerda: puesto que es un acceso no autentificado, todo lo que sirvas mediante este protocolo será público en la red. Si activas el protocolo en un servidor más allá del cortafuegos, lo debes usar únicamente en proyectos que deban ser visibles a todo el mundo. Si el servidor está detrás de un cortafuegos, puedes usarlo en proyectos a los que un gran número de personas o de computadores (por ejemplo, servidores de integración continua o de compilación) tengan acceso de sólo lectura y no necesiten establecer una clave SSH para cada uno de ellos. El protocolo Git es relativamente fácil de configurar. Básicamente, necesitas ejecutar el comando con la variante “demonio” (daemon): git daemon --reuseaddr --base-path=/opt/git/ /opt/git/ El parámetro --reuseaddr permite al servidor reiniciarse sin esperar a que se liberen viejas conexiones; el parámetro --base-path permite a los usuarios clonar proyectos sin necesidad de indicar su camino completo; y el camino indicado al final del comando mostrará al “demonio” Git, dónde buscar los repositorios a exportar. Si tienes un cortafuegos activo, necesitarás abrir el puerto 9418 para la máquina donde estás configurando el “demonio” Git. Este proceso se puede demonizar de diferentes maneras, dependiendo del sistema operativo con el que trabajas. En una máquina Ubuntu, puedes usar un script de arranque. Poniendo en el siguiente archivo: /etc/event.d/local-git-daemon un script tal como: start on startup stop on shutdown exec /usr/bin/git daemon \ --user=git --group=git \ --reuseaddr \ --base-path=/opt/git/ \ /opt/git/ respawn Por razones de seguridad, es recomendable lanzar este “demonio” con un usuario que tenga únicamente permisos de lectura en los repositorios (Lo puedes hacer creando un nuevo usuario git-ro y lanzando el “demonio” con él). Para simplificar, en estos ejemplos vamos a lanzar el “demonio” Git bajo el mismo usuario git que se usa con git-shell . Tras reiniciar tu máquina, el “demonio” Git arrancará automáticamente y se reiniciará cuando se caiga. Para arrancarlo sin necesidad de reiniciar la máquina, puedes utilizar el comando: initctl start local-git-daemon En otros sistemas operativos, puedes utilizar xinetd , un script en el sistema sysvinit , o alguna otra manera (siempre y cuando demonizes el comando y puedas monitorizarlo). A continuación, has de indicar a Git a cuales de tus repositorios ha de permitir acceso sin autentificar. Lo puedes hacer creando en cada repositorio un archivo llamado git-daemon-export-ok . $ cd /path/to/project.git $ touch git-daemon-export-ok La presencia de este archivo dice a Git que este proyecto se puede servir sin problema sin necesidad de autentificación de usuarios. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/nl/v2/Git-op-de-server-Samenvatting | Git - Samenvatting About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Aan de slag 1.1 Over versiebeheer 1.2 Een kort historisch overzicht van Git 1.3 Wat is Git? 1.4 De commando-regel 1.5 Git installeren 1.6 Git klaarmaken voor eerste gebruik 1.7 Hulp krijgen 1.8 Samenvatting 2. Git Basics 2.1 Een Git repository verkrijgen 2.2 Wijzigingen aan de repository vastleggen 2.3 De commit geschiedenis bekijken 2.4 Dingen ongedaan maken 2.5 Werken met remotes 2.6 Taggen (Labelen) 2.7 Git aliassen 2.8 Samenvatting 3. Branchen in Git 3.1 Branches in vogelvlucht 3.2 Eenvoudig branchen en mergen 3.3 Branch-beheer 3.4 Branch workflows 3.5 Branches op afstand (Remote branches) 3.6 Rebasen 3.7 Samenvatting 4. Git op de server 4.1 De protocollen 4.2 Git op een server krijgen 4.3 Je publieke SSH sleutel genereren 4.4 De server opzetten 4.5 Git Daemon 4.6 Slimme HTTP 4.7 GitWeb 4.8 GitLab 4.9 Hosting oplossingen van derden 4.10 Samenvatting 5. Gedistribueerd Git 5.1 Gedistribueerde workflows 5.2 Bijdragen aan een project 5.3 Het beheren van een project 5.4 Samenvatting 6. GitHub 6.1 Account setup en configuratie 6.2 Aan een project bijdragen 6.3 Een project onderhouden 6.4 Een organisatie beheren 6.5 GitHub Scripten 6.6 Samenvatting 7. Git Tools 7.1 Revisie Selectie 7.2 Interactief stagen 7.3 Stashen en opschonen 7.4 Je werk tekenen 7.5 Zoeken 7.6 Geschiedenis herschrijven 7.7 Reset ontrafeld 7.8 Mergen voor gevorderden 7.9 Rerere 7.10 Debuggen met Git 7.11 Submodules 7.12 Bundelen 7.13 Vervangen 7.14 Het opslaan van inloggegevens 7.15 Samenvatting 8. Git aanpassen 8.1 Git configuratie 8.2 Git attributen 8.3 Git Hooks 8.4 Een voorbeeld van Git-afgedwongen beleid 8.5 Samenvatting 9. Git en andere systemen 9.1 Git als een client 9.2 Migreren naar Git 9.3 Samenvatting 10. Git Binnenwerk 10.1 Binnenwerk en koetswerk (plumbing and porcelain) 10.2 Git objecten 10.3 Git Referenties 10.4 Packfiles 10.5 De Refspec 10.6 Uitwisseling protocollen 10.7 Onderhoud en gegevensherstel 10.8 Omgevingsvariabelen 10.9 Samenvatting A1. Bijlage A: Git in andere omgevingen A1.1 Grafische interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in Eclipse A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Samenvatting A2. Bijlage B: Git in je applicaties inbouwen A2.1 Commando-regel Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Bijlage C: Git Commando’s A3.1 Setup en configuratie A3.2 Projecten ophalen en maken A3.3 Basic Snapshotten A3.4 Branchen en mergen A3.5 Projecten delen en bijwerken A3.6 Inspectie en vergelijking A3.7 Debuggen A3.8 Patchen A3.9 Email A3.10 Externe systemen A3.11 Beheer A3.12 Binnenwerk commando’s (plumbing commando’s) 2nd Edition 4.10 Git op de server - Samenvatting Samenvatting Je hebt meerdere opties om een remote Git repository werkend te krijgen zodat je kunt samenwerken met anderen of je werk kunt delen. Je eigen server draaien geeft je veel controle en stelt je in staat om de server binnen je firewall te draaien, maar zo’n server vraagt over het algemeen een behoorlijke hoeveelheid tijd om in te stellen en te onderhouden. Als je je gegevens op een beheerde server plaatst, is het eenvoudig in te stellen en te onderhouden; maar je moet wel willen dat je code op de server van een derde opgeslagen is, en sommige organisaties staan dit niet toe. Het zou redelijk eenvoudig moeten zijn om te bepalen welke oplossing of combinatie van oplossingen van toepassing is op jou en jouw organisatie. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://www.netscout.com/product/arbor-threat-mitigation-system | DDoS Mitigator - DDoS Threat Mitigation System Skip to main content myNETSCOUT Login Solutions ← Back Enterprise Communication Service Provider By Industry Technology Partners Enterprise Observability nGenius Solutions for Observability Network Performance Management Application Performance Management Remote Site Observability Cloud Performance Monitoring VPN/VDI SaaS AIOps AIOps for Enterprises Collaboration UC&C and UCaaS Contact Centers Cybersecurity Network Detection and Response NetOps and SecOps Collaboration DDoS Protection Adaptive DDoS Protection Cybersecurity Stack Optimization DNS Infrastructure Protection 5G Transformation 5G for Enterprise Private 4G/5G Communication Service Provider AIOps AIOps for Communication Service Providers GeoMarketing Mobile Networks 5G 5G Fixed Wireless Access LTE/VoLTE/VoWi-Fi RAN Planning, Optimization, and Automation Cybersecurity & DDoS Protection Arbor DDoS Protection Carpet Bombing DDoS Protection DNS Infrastructure Protection Mobile Network Security Network Detection and Response Cloud and Digital Transformation Cloud Visibility Internet of Things (IoT) Network Function Virtualization (NFV) OTT Visibility Cable/MSO and Fixed Networks Cable/MSO and Fixed Networks Fiber (FTTx) and DAA Monitoring Analytics Automated Analytics Business Analytics By Industry Banking Capital Markets Education Government Healthcare Insurance Manufacturing Pharmaceutical Retail Telecommunications Transportation Utilities Featured Industry: Healthcare Optimize productivity, enhance the patient care experience, and improve bottom-line with powerful healthcare IT solutions. Learn more Technology Partners AWS Cisco Systems Citrix Dell Technologies F5 Google Cloud Microsoft Oracle Palo Alto Networks Red Hat ServiceNow Splunk VMware Products ← Back Enterprise Network Security Arbor DDoS Protection Communication Service Provider AIOps Enterprise nGeniusONE for Enterprise Enable real-time visibility into any enterprise network infrastructure environment to improve performance and user experience. InfiniStreamNG Capture, store, and analyze packet-level data in real-time to help troubleshoot issues and optimize performance across IT infrastructures. nGenius Edge Sensor Help improve user experience at remote sites and other network edges to achieve holistically strong network and application performance. vSTREAM Improve visibility into virtualized and cloud environments with deep packet inspection to further performance management and security. nGeniusPULSE Continuously test and track the performance of applications, network services, and user experience across all IT infrastructures. nGenius Packet Switches Packet flow switch architectures can combine with other NETSCOUT solutions to enable pervasive visibility across network environments. Network Security Omnis Cyber Intelligence NDR Leverage packet-level insights to power network detection and response (NDR) solutions and cyber threat hunting. Omnis CyberStream Detect, investigate, and respond to cyberthreats in real-time by leveraging packet-level data to identify suspicious activity across IT environments. nGenius Decryption Appliance Decrypt SSL and TLS-encrypted traffic to enable visibility into hidden threats within network traffic. Arbor DDoS Protection Arbor Sightline Leverage network intelligence to detect, analyze, and respond to DDoS threats across the most complex service provider and enterprise networks. Arbor Sightline Mobile Safeguard mobile services and ensure network performance and security with a DDoS protection solution specifically designed for mobile networks. Arbor Threat Mitigation System Detect, mitigate, and prevent DDoS attacks with real-time traffic analysis and automated attack mitigation. Arbor Edge Defense (AED) Powerful AI & ML powered DDoS protection backed by unmatched actionable threat intelligence maintains availability to critical services and applications. Arbor Global DDoS Threat Intelligence NETSCOUT global DDoS threat intelligence provides insights into the most current cyberthreats and their tactics, enhancing products and solutions. Arbor Cloud Cloud DDoS protection that defends against large-scale, volumetric attacks. Arbor Managed Services Round-the-clock support and assistance from Arbor product experts is available with managed services. Communication Service Provider nGenius Business Analytics Drive better business decisions at scale with efficient data collection, enrichment, and third-party application feeds. nGenius Session Analyzer Isolate and resolve congestion and interference problems contributing to 70% of all subscriber issues. nGeniusONE for Carrier Assure a premium user experience with end-to-end visibility across network domains, service enablers, and devices. InfiniStreamNG Access real-time views of RAN control plane for end-to-end visibility across physical and virtual network environments. ISNG-RAN Prioritize the mobile subscriber experience with scalable, cost-effective and cloud-ready RAN network monitoring. Omnis RAN Stay ahead of capacity and mobility targets with distinct automation modules to address growing RAN complexities. TrueCall Improve your understanding of network capacity and complexity with true user performance insights. AIOps Omnis AI Sensor Unparalleled telemetry insights at enterprise speed and scale across your entire IT ecosystem. Omnis AI Streamer Build data pipelines that sift through the noise to improve the efficiency, reliability, and scalability of IT operations and AI/ML workflows. Support & Resources ← Back Blogs, Resources, & Webinars Intelligence & Reports Support & Training Blogs, Resources, & Webinars Blog Stay updated with the latest insights, tips, and news on our blog. Resource Library Explore the latest case studies, whitepapers, eBooks, and more to discover real-world applications of our products and solutions. Learning Center Quickly learn the definitions of key phrases in networking, security, and DDoS. Webinars Gain insights from product and industry experts through our live & on-demand webinars. NETSCOUT Blog Whether you're a seasoned network performance professional or a novice in the industry, you're guaranteed to learn something new from the NETSCOUT blog. Read the blog Intelligence & Reports ASERT Threat Intelligence Team Meet the ASERT team, the leading experts on DDoS and cyber threat intelligence. DDoS Threat Intelligence Report Learn about the latest DDoS trends and statistics powered by NETSCOUT’s industry-leading global internet traffic visibility. Cyber Threat Horizon Look at live DDoS attack maps to discover what attacks are occurring in real-time. DDoS Threat Intelligence Report NETSCOUT’s latest DDoS Threat Intelligence dives into the most recent trends in DDoS adversarial tactics. Get the report Support & Training Overview Get support for your products and solutions to maximize the value of your investment. My.NETSCOUT Existing customers, log in to MyNETSCOUT to access additional assets, resources, and support channels. NETSCOUT University Our mission is to help you and your team to successfully implement NETSCOUT’s solutions so that your network functions seamlessly and effectively. NO LATENCY Explore tech tips, use cases, and more in our NO LATENCY newsletter. MasterCare Support NETSCOUT's award-winning global support service. Learn more Company ← Back About Us News & Events Partners About Us About Us Board of Directors Careers Customer Reviews Environmental, Social, and Governance Executive Team Industry Analyst Perspectives Investor Relations The Future of Intelligence The quality of your AI outcomes hinges on the data available. With NETSCOUT's Smart Data, ensure you have the network visibility you need to overcome the challenges of tomorrow. NETSCOUT provides the Data that Drives You. Watch the video News & Events Events Newsroom Press Releases Read the latest NETSCOUT news to stay informed on the latest updates, press, and more. Read the latest news Partners Partner Portal Become a Partner Learn about our NETSCOUT Connect 360 partner program. Search Under Attack? Contact Us Under Attack? Home Products Arbor Threat Mitigation System for DDoS Attacks Arbor Threat Mitigation System for DDoS Attacks Adaptive mitigation protects your customers and ensures service availability and performance Overview Overview Benefits Key Features Testimonials Resources Related Pages Video Arbor DDoS Protection for Carrier Service Providers - by NETSCOUT Watch Video Protect the Network and Keep Your Business Flowing. Internet Service Providers (ISPs), Cloud Providers and Enterprises face a common problem. Distributed Denial of Service (DDoS) attacks are a major risk to service availability. The power, sophistication and frequency of DDoS attacks continue to increase. Data center operators and network providers need a defense that is adaptable, effective, cost-efficient and easily managed. Arbor Threat Mitigation System (TMS) is the acknowledged leader in DDoS protection . More Service Providers, Cloud Providers, and large Enterprises use Arbor TMS for DDoS mitigation than any other solution. Working in conjunction with our Arbor Sightline solution, which provides visibility and threat detection, the Arbor Threat Mitigation System (TMS) adapts to attacks as they change, surgically removing DDoS attack traffic from your network without disrupting key network services. DDoS Threat Mitigation System Benefits Detect and Mitigate DDoS Threats Automatically Establishes proven countermeasures to remove DDoS attack traffic while enabling the flow of legitimate traffic Diverse Models and Capacity Configurations to Meet Any Size Deployment Provides up to 500 Gbps of mitigation in a single TMS appliance and up to 50Tbps of mitigation capacity in a single deployment Immobilize Mobile Threats Stops DDoS attacks through misbehaving mobile applications, and other IoT devices connecting to the network Click to enlarge image Flexible Deployment Options for any Network Our solution integrates network-wide intelligence and anomaly detection with carrier-class threat management to help identify and stop volumetric, TCP state exhaustion and application-layer DDoS attacks. Arbor TMS provides enterprise-level cloud and edge protection and comes in a variety of mitigation platforms and capacities, including both physical and virtual appliances with mitigation capabilities up to 500Gbps per device and total mitigation capacity up to 50Tbps. Solution Brief Why NETSCOUT’s Arbor DDoS Attack Protection Solution is Better Arbor has the industry’s broadest portfolio of DDoS attack protection products and services that enable organizations of any size to customize a solution to meet their technical and financial requirements of today – and the future. Learn more Features Advanced Detection and Mitigation Arbor Threat Mitigation System surgically removes up to 50Tbps of DDoS attack traffic in a single deployment, while enabling the flow of legitimate traffic—without interrupting your network services. A Flexible and Scalable Solution With a choice of platforms and configurations to meet diverse deployment needs, Arbor's DDoS Threat Mitigation System can address DDoS attacks of all sizes while optimizing your investments to capacity to ensure that you have the right amount of protection needed. Virtualized Attack Mitigation The entire Arbor Sightline & DDoS Threat Mitigation System deployment can be 100% virtualized, enabling organizations to take advantage of the agility and cost savings of SDN/NFV from the industry leader in DDoS threat mitigation. Build a DDoS Service Offering for Your Customers For Service Providers, Offering a DDoS Service to your customers can help them ensure the availability of their networks and applications. With the Arbor Threat Mitigation System, you can extend protection to your network of customers and monetize the investment. Arbor Threat Mitigation System surgically removes up to 40Tbps of DDoS attack traffic in a single deployment, while enabling the flow of legitimate traffic—without interrupting your network services. Advanced Detection and Mitigation Arbor Threat Mitigation System surgically removes up to 50Tbps of DDoS attack traffic in a single deployment, while enabling the flow of legitimate traffic—without interrupting your network services. With a choice of platforms and configurations to meet diverse deployment needs, Arbor Threat Mitigation System can address DDoS attacks of all sizes while optimizing your investments to capacity to ensure that you have right amount of protection needed without having to over-purchase. A Flexible and Scalable Solution With a choice of platforms and configurations to meet diverse deployment needs, Arbor's DDoS Threat Mitigation System can address DDoS attacks of all sizes while optimizing your investments to capacity to ensure that you have the right amount of protection needed. The entire Arbor Sightline & DDoS Threat Mitigation System deployment can be 100% virtualized, enabling organizations to take advantage of the agility and cost savings of SDN/NFV from an industry leading DDoS mitigator. Virtualized Attack Mitigation The entire Arbor Sightline & DDoS Threat Mitigation System deployment can be 100% virtualized, enabling organizations to take advantage of the agility and cost savings of SDN/NFV from the industry leader in DDoS threat mitigation. For Service Providers, Offering a DDoS Service to your customers can help them ensure the availability of their networks and applications. With the Arbor Threat Mitigation System, you can extend protection to your network of customers and monetize the investment. Build a DDoS Service Offering for Your Customers For Service Providers, Offering a DDoS Service to your customers can help them ensure the availability of their networks and applications. With the Arbor Threat Mitigation System, you can extend protection to your network of customers and monetize the investment. Why Arbor Threat Mitigation System? Let our customers tell you. "Best defense against DDoS attacks" Darren G. Read the full review "The Gold Standard in mitigation" Daniel J. Read the full review "Arbor TMS makes it easy to defend against DDoS attacks" Verified User in Internet Read the full review "Better Network Resiliency through real-time DDoS Threat Detection and Mitigation capabilities" William I. Read the full review Read more reviews Data Sheet Arbor Threat Mitigation System Proven, Comprehensive Threat Protection and Service Enablement Learn more Featured Resources Case Study Globe Telecom Protects Critical Infrastructure and Customer Experience with NETSCOUT Arbor DDoS Attack Protection Globe Telecom struggled with DDoS attacks due to a lack of real-time systems for detection and prevention. This caused multiple issues for the company. Report SPARK Matrix for Distributed Denial of Service (DDoS) Mitigation, Q3 2025 NETSCOUT Named both a Technology Leader and Ace Performer in DDoS Mitigation for 2025 Case Study Arelion Employs NETSCOUT Arbor DDoS Protection Products This Ensures Its Global Customers With Secure Access to Arelion’s #1 Ranked Global Internet Backbone Quick Look Healthcare Organizations are Increasingly Targets of DDoS Attacks Healthcare Organization Uses NETSCOUT Solution To Solve Cybersecurity Challenges by Stopping DDoS Attacks Impacting Availability of Services Solution Brief On-Premise Protection is the Best First Step Against DDoS and Cyberattacks for Academic Institutions Due to the complexity of DDoS attacks, Educational Institutions need to understand the risk reduction that on-premise edge protection can provide to their on line learning... Case Study CDN’s Add-On DDoS Protection Falls Short for Major Financial Institution CDN’s Add-On DDoS Protection Falls Short for Major Financial Institution Case Study Large Gaming Organization Employs Out-of-Band Traffic Analysis and Surgical Mitigation to Battle Newest DDoS Attacks The real concern for most of the gaming industry is the attacks designed to evade upstream protections and navigate through the network looking for targets. Use Case Defending Government Agencies Against High-Volume Multi-Vector DDoS Attacks Attacks are often waged against national security infrastructure. NETSCOUT has observed a massive increase from the previous half year in attacks against the US national security... View more resources Related Pages Product ATLAS Intelligence Feed (AIF) ATLAS Intelligence Feed (AIF) provides up-to-date threat intelligence on the latest DDoS threats to our DDoS protection products. Automate defenses against trending attacks with AIF. Learn more Product Arbor Sightline DDoS Attack Detection Solution Whether you are a service provider or have a complex enterprise network, Arbor Sightline helps monitor and identify networking and security issues at any network scale with AI and ML-powered insights. Learn more Product Arbor Managed DDoS Protection Services Arbor Managed Services provides expert management of DDoS protection, backed by 24x7 worldwide expert help and continuous threat intelligence from leading experts. Learn more Product Arbor Cloud DDoS Protection Services Arbor Cloud provides industry-leading scrubbing capacity to enable powerful cloud-based DDoS protection to keep your applications up and running. Learn more Contact NETSCOUT Today To learn more about how NETSCOUT can help your company, speak to one of our highly experienced subject matter experts. Contact Us Guardians of the Connected World ® Discover Our Data Observability Solutions Service Provider Service Assurance AIOps Omnis Network Security Arbor DDoS Protection All Solutions All Products Learn Blog Resource Library Learning Center MyNETSCOUT Events Webinars About About Us Careers Environmental, Social, and Governance For Investors Newsroom Partners Connect 1-888-357-7667 Contact Us Under DDoS Attack? © 2026 NETSCOUT Terms & Conditions Website Terms of Use Data Privacy and Trust Center Transparency in Supply Chains Privacy Policy Vendor Portal Do Not Sell or Share My Personal Information California Privacy Notice UK Disclosure | 2026-01-13T09:29:20 |
https://sre.google/20/ | Google SRE: What is SRE? 20 Years of SRE at Google Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content Twenty Years of Site Reliability Engineering at Google Celebrate Twenty Years of Site Reliability Engineering, learn about the history and future of SRE Jessica McCarthy Director, Site Reliability Engineering Watch video Dermot Duffy Engineering Director Watch video Chris Jones Site Reliability Engineer Watch video Des Keane Engineering Director Watch video Michelle Brush Engineering Director, Site Reliability Engineering Watch video Dan "danrl" Luedtke Site Reliability Engineer Watch video Vidhya Narayanan Engineering Director, Site Reliability Engineering Watch video Jennifer Petoff Director, GCP/TI Education Team (GET) Watch video JC Van Winkel Site Reliability Educator Watch video Jennifer Mace Site Reliability Engineer Watch video Betsy Beyer Senior Program Manager Watch video Benjamin Treynor Sloss VP, 24x7 Watch video Laura Lamb Systems Engineer, Site Reliability Engineering Watch video Trisha Weir Site Reliability Engineering Manager
- Traffic Dataplane Infrastructure Watch video Matt Zelesko Vice President, Engineering Watch video Nicolas Fischbach Senior Director - Security, Privacy, Resilience and Cloud AI SRE Watch video Salim Virji Site Reliability Engineer Watch video Svetlana Gites Engineering Manager SRE Watch video Thais Melo Cloud SRE UTL Watch video Follow us About Google Google products Privacy Terms Help | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/freshworks-inc-freshmarketer/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_image-click | Freshmarketer | LinkedIn Skip to main content LinkedIn Freshworks in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Freshmarketer Marketing Automation Software by Freshworks See who's skilled in this Add as skill Get started Report this product About Freshmarketer provides a personalized marketing automation solution for businesses of all sizes. We do this by taking a fresh approach to building and delivering predictive marketing software that is scalable and collaborates with sales—empowering marketers to engage, retain, and delight customers across their entire journey. This product is intended for Chief Marketing Officer Vice President Marketing Head of Marketing Head of Digital Marketing Head of Growth Marketing Manager Marketing Specialist Email Marketing Manager Demand Generation Specialist Social Media Marketing Specialist Media Products media viewer No more previous content Meet Freshworks for Marketers Freshworks lets D2C and eCommerce organizations manage marketing and customer support with a single solution. Share customized messages on the platforms your customers like to use and use AI functionality to anticipate customer needs, chat in real time, and get them to check out, all in one ridiculously easy solution. Purpose-built marketing CRM for your e-commerce businesses Message sharper, convert faster, and delight better with a unified marketing automation platform. Drive personalized multichannel engagement Engage with buyers wherever they are and provide consistent multichannel experiences across email, WhatsApp, SMS, live chat, social media, and more using a single solution. Segment buyers and engage them with targeted promotions Create or refine your target audience based on their purchases, behavior, and preferences, or use pre-built segments such as new or returning customers, one-time purchases, abandoned carts, and more to send personalized messages that drive conversions. Automate workflows to sell while you sleep Save time and effort with our ready-to-use cross-channel campaigns to automate your tasks at scale. Choose from 20+ e-commerce journey templates, 150+ customizable email templates, and chatbot templates for WISMO, FAQs, checkout, and discounts. No more next content Featured customers of Freshmarketer JLA Group Facilities Services 19,986 followers Evans México Machinery Manufacturing 1,578 followers Dunzo Technology, Information and Internet 356,114 followers Exotel Telecommunications 67,107 followers Sify Technologies Limited. Information Technology & Services 107,192 followers PharmEasy Health, Wellness & Fitness 273,281 followers Blue Nile Retail 33,285 followers Descartes Peoplevox IT Services and IT Consulting 3,164 followers Show more Show less Similar products Marketing Cloud Marketing Cloud Marketing Automation Software Zoho Campaigns Zoho Campaigns Marketing Automation Software HCL Unica HCL Unica Marketing Automation Software Brevo (formerly Sendinblue) Brevo (formerly Sendinblue) Marketing Automation Software RD Station Marketing RD Station Marketing Marketing Automation Software Adobe Marketo Adobe Marketo Marketing Automation Software Sign in to see more Show more Show less Freshworks products Freshchat Freshchat Live Chat Software Freshdesk Freshdesk Help Desk Software Freshdesk Omni Freshdesk Omni Help Desk Software Freshsales Freshsales Customer Relationship Management (CRM) Software Freshservice Freshservice Service Desk Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
http://www.trello.com/planner | Trello Planner: Focus and flourish | Trello Skip to main content Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Use case: Task management Track progress of tasks in one convenient place with a visual layout that adds ‘ta-da’ to your to-do’s. Use case: Resource hub Save hours when you give teams a well-designed hub to find information easily and quickly. Use case: Project management Keep projects organized, deadlines on track, and teammates aligned with Trello. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Back Navigation Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Read though our use cases to make the most of Trello on your team. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Helping teams work better, together Discover Trello use cases, productivity tips, best practices for team collaboration, and expert remote work advice. Check out the Trello blog Trello Planner Plan, stay focused, and get more [sh*t] done Planner is your ultimate planning companion to unlock the power of staying in the zone and getting more done. Get started Learn more about Trello’s plans and pricing. Plan anytime, anywhere Focus and make time for what truly matters. Say goodbye to scattered schedules and missed deadlines! Trello Planner is your go-to tool for capturing and organizing your plans, whether you're at your desk or on the go. Effortless scheduling Never miss a beat! Schedule tasks and events directly from your favorite tools, like Google Calendar and Outlook, ensuring you stay on top of everything. Intuitive organization Ready to lock in your plans? Simply drag and drop your tasks into the right boards, making organization a breeze. Stay on track Got quick tasks? Mark them "Done" straight from the Planner and keep your productivity flowing! Join the Trello Planner revolution! We’re excited to introduce Trello Planner, and we want your feedback to make it even better! Try it out, share your thoughts, and help us shape the future of planning. Get started Log In About Trello What’s behind the boards. Jobs Learn about open roles on the Trello team. Apps Download the Trello App for your Desktop or Mobile devices. Contact us Need anything? Get in touch and we can help. Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Privacy Policy Terms Copyright © 2024 Atlassian | 2026-01-13T09:29:20 |
https://git-scm.com/book/sl/v2/Git-na-stre%c5%beniku-Pametni-HTTP | Git - Pametni HTTP About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Začetek 1.1 O nadzoru različic 1.2 Kratka zgodovina Gita 1.3 Kaj je Git? 1.4 Ukazna vrstica 1.5 Namestitev Gita 1.6 Prva nastavitev Gita 1.7 Pridobivanje pomoči 1.8 Povzetek 2. Osnove Git 2.1 Pridobivanje repozitorija Git 2.2 Snemanje sprememb v repozitorij 2.3 Pregled zgodovine potrditev 2.4 Razveljavljanje stvari 2.5 Delo z daljavami 2.6 Označevanje 2.7 Aliasi Git 2.8 Povzetek 3. Veje Git 3.1 Veje na kratko 3.2 Osnove vej in združevanja 3.3 Upravljanje vej 3.4 Poteki dela z vejami 3.5 Oddaljene veje 3.6 Ponovno baziranje 3.7 Povzetek 4. Git na strežniku 4.1 Protokoli 4.2 Pridobitev Gita na strežniku 4.3 Generiranje vaših javnih ključev SSH 4.4 Nastavitev strežnika 4.5 Prikriti proces Git 4.6 Pametni HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti gostovanja pri tretjih ponudnikih 4.10 Povzetek 5. Porazdeljeni Git 5.1 Porazdeljeni poteki dela 5.2 Prispevek k projektu 5.3 Vzdrževanje projekta 5.4 Povzetek 6. GitHub 6.1 Namestitev in konfiguracija računa 6.2 Prispevek k projektu 6.3 Vzdrževanje projekta 6.4 Upravljanje organizacije 6.5 Skriptni GitHub 6.6 Povzetek 7. Orodja Git 7.1 Izbira revizije 7.2 Interaktivno pripravljanje 7.3 Shranjevanje na varno (angl. stashing) in čiščenje 7.4 Podpisovanje vašega dela 7.5 Iskanje 7.6 Prepisovanje zgodovine 7.7 Demistifikacija ponastavitve 7.8 Napredno združevanje 7.9 Rerere 7.10 Razhroščevanje z Gitom 7.11 Podmoduli 7.12 Povezovanje v pakete 7.13 Zamenjava 7.14 Shramba poverilnic 7.15 Povzetek 8. Prilagoditev Gita 8.1 Konfiguracija Git 8.2 Atributi Git 8.3 Kljuke Git 8.4 Primer pravilnika, ki ga uveljavlja Git 8.5 Povzetek 9. Git in ostali sistemi 9.1 Git kot odjemalec 9.2 Migracija na Git 9.3 Povzetek 10. Notranjost Gita 10.1 Napeljava in keramika 10.2 Objekti Git 10.3 Reference Git 10.4 Packfiles (datoteke zmanjšanih podatkov) 10.5 Refspec 10.6 Protokoli prenosa 10.7 Vzdrževanje in obnovitev podatkov 10.8 Spremenljivke okolja 10.9 Povzetek A1. Dodatek A: Git v drugih okoljih A1.1 Grafični vmesniki A1.2 Git v Visual Studio A1.3 Git v Visual Studio Code A1.4 Git v IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git v Sublime Text A1.6 Git v Bashu A1.7 Git v Zsh A1.8 Git v Powershellu A1.9 Povzetek A2. Dodatek B: Vdelava Gita v vašo aplikacijo A2.1 Git v ukazni vrstici A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Dodatek C: Ukazi Git A3.1 Nastavitev in konfiguracija A3.2 Pridobivanje in ustvarjanje projektov A3.3 Osnove posnetkov A3.4 Veje in združevanje A3.5 Deljenje in posodabljanje projektov A3.6 Pregled in primerjava A3.7 Razhroščevanje A3.8 Popravljanje A3.9 E-pošta A3.10 Zunanji sistemi A3.11 Administracija A3.12 Orodja za sisteme napeljave 2nd Edition 4.6 Git na strežniku - Pametni HTTP Pametni HTTP Sedaj imamo overjen dostop preko SSH in neoverjen dostop preko git:// , vendar obstaja tudi protokol, ki lahko naredi oboje istočasno. Nastavitev pametnega HTTP (angl. Smart HTTP ) je v osnovi samo omogočenje skripta CGI, ki je ponujen z Gitom imenovanim git-http-backend na strežniku. Ta CGI bo prebral pot in glave, ki jih pošlje git fetch ali git push k HTTP URL in določa, ali lahko odjemalec komunicira preko HTTP (kar velja za kateregakoli odjemalca od različice 1.6.6). Če CGI vidi, da je odjemalec pameten, bo z njim komuniciral pametno; drugače se bo vrnil k neumnemu (angl. dumb ) obnašanju (tako, da je združljiv za nazaj za branje s starejšimi odjemalci). Pojdimo skozi zelo osnovno nastavitev. To bomo nastavili z Apachejem kot strežnikom CGI. Če nimate nastavljenega Apacheja, lahko to naredite na napravi Linux nekako takole: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env To omogoči tudi module mod_cgi , mod_alias in mod_env , ki so obvezni, da to ustrezno deluje. Morali boste nastaviti uporabniško skupino Unix za direktorije /srv/git na www-data , da bo vaš spletni strežnik lahko dostopal do repozitorijev z branjem in pisanjem, saj se bo instanca Apache, ki poganja skripto CGI (privzeto), poganjala kot ta uporabnik: $ chgrp -R www-data /srv/git Naslednje moramo dodati nekaj stvari k Apache nastavitvi, da poženemo git-http-backend kot krmilnik za karkoli, kar pride v pot /git vašega spletnega strežnika. SetEnv GIT_PROJECT_ROOT /srv/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/lib/git-core/git-http-backend/ Če izpustite spremenljivko okolja GIT_HTTP_EXPORT_ALL , bo Git stregel repozitorije samo neoverjenim odjemalcem z datoteko git-daemon-export-ok v njih, tako kot to dela prikriti proces Git (angl. daemon ). Na koncu boste želeli povedati Apacheju, da dovoli zahtevke na git-http-backend , in narediti pisanje nekako overjeno, verjetno z blokom Auth nekako takole: <Files "git-http-backend"> AuthType Basic AuthName "Git Access" AuthUserFile /srv/git/.htpasswd Require expr !(%{QUERY_STRING} -strmatch '*service=git-receive-pack*' || %{REQUEST_URI} =~ m#/git-receive-pack$#) Require valid-user </Files> To bo zahtevalo, da ustvarite datoteko .htaccess , ki vsebuje gesla za vse veljavne uporabnike. Tu je primer dodajanja uporabnika »schacon« k datoteki: $ htpasswd -c /srv/git/.htpasswd schacon Na voljo je tona načinov, kako narediti, da Apache overi uporabnike, izbrati in implementirati pa boste morali enega od njih. To je samo enostaven primer, ki nam ga uspe prikazati. Skoraj zagotovo boste tudi to nastavili preko SSL, da so vsi podatki šifrirani. Ne želimo iti predaleč po zajčevi luknji nastavitvenih posebnosti Apache, ker lahko boste uporabljali drugačni strežnik ali pa imeli drugačne overitvene potrebe. Ideja je, da Git prihaja s CGI-jem imenovanim git-http-backend , kateri bo, ko je sklican, naredil vsa pogajanja, da pošilja in prejema podatke preko HTTP. Sam po sebi ne implementira nikakršnega overjanja, vendar to je lahko enostavno krmiljeno na nivoju spletnega strežnika, ki ga prikliče. To lahko naredite s skoraj katerimkoli spletnim strežnikom, ki zmore CGI, torej uporabite tistega, ki ga najbolj poznate. Opomba Za več informacij o nastavitvah overjanja v Apacheju, preverite dokumentacijo Apache tu: https://httpd.apache.org/docs/current/howto/auth.html . prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
http://www.trello.com/templates | Trello Your browser was unable to load all of Trello's resources. They may have been blocked by your firewall, proxy or browser configuration. Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again and if that doesn't work, check out our troubleshooting guide . To use Trello, please enable JavaScript. | 2026-01-13T09:29:20 |
http://www.trello.com/use-cases/task-management | Manage Tasks in One Shared Space | Trello Skip to main content Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Use case: Task management Track progress of tasks in one convenient place with a visual layout that adds ‘ta-da’ to your to-do’s. Use case: Resource hub Save hours when you give teams a well-designed hub to find information easily and quickly. Use case: Project management Keep projects organized, deadlines on track, and teammates aligned with Trello. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Back Navigation Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Read though our use cases to make the most of Trello on your team. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Helping teams work better, together Discover Trello use cases, productivity tips, best practices for team collaboration, and expert remote work advice. Check out the Trello blog Manage tasks in one shared space Say goodbye to sticky notes and to-do lists: Trello allows teams of any size to easily manage tasks and hit deadlines - all without ever leaving the app. Get started with Trello Trello is better than your best to-do list Trello makes it easy to organize and track individual or team tasks in one place Assign tasks and manage deadlines Trello’s advanced checklists give you the power to add more context to your tasks by assigning team members and due dates to checklist items, increasing visibility and keeping your team accountable. Check out advanced checklists Prioritize tasks and keep your team aligned Prioritize with labels to identify what is high, medium, or low priority and bring an extra layer of shared understanding to your tasks. You can even filter by a certain label to only view cards associated with the label you want to view. Learn how to label Bring a fresh perspective to the task at hand (pun intended) with Calendar View Visualize checklist items and cards with due dates in Calendar View, showing what tasks are due in the days and weeks ahead. Cards will be arranged according to their due date and will display any labels, members, or checklists added to them. Learn about Views Trello for Task Management Trello + your favorite tools Trello has 200+ integrations with the tools you know and love. Integrate the tools your team already uses with Trello to keep your work organized and in one place. Try a Trello Power-Up to connect all of your team’s (other) favorite apps to your boards. Go to Power-Ups gallery Slack Automation Keep your communication and collaboration apps connected. Google Drive File management Search Google Drive right from Trello and attach relevant files and folders. Figma Integration Embed Figma files on Trello cards that update in real-time to keep teams in sync. Jira Developer Tools Connect Jira and Trello to help all your teams work better together. Zapier Automation Set up time-saving automations to get things done between all your favorite apps. Card Aging Board Utilities Inactive cards will fade, showing you which tasks need a status update. No need to start from scratch. Use one of our customizable templates. Jumpstart your board with a well-proven template designed by our team. Customize it for yours. Eisenhower Matrix Task Board The Eisenhower Matrix Template is a powerful method to organize your daily/weekly tasks. Get organized Team Tasks - 5 Things Workflow Keep team status updates transparent and succinct with this template. It’s simple: add two things that are being worked on, two tasks that will be worked on next, one thing that is not being worked on. Improve your workflow Join a community of millions of users globally who are using Trello to get more done. Join a community of millions of users globally who are using Trello to get more done. Are sticky notes and to-do lists taking over your day? Let Trello Help. Read the Trello blog to find ways to improve efficiency, productivity, and collaboration. 12 Power-ups to transform Trello into a powerful task management software Learn the best Power-Ups, integrations, and features to help you and your team move tasks along effortlessly. Read more 8 Ways to track important tasks in Trello Deadlines tend to creep up faster than anticipated. With Trello, you'll be able to gain better control over pending tasks, visualize priorities, and become a more collaborative and efficient team member. Read more Top Trello tips to keep your busy team on track Struggling to decide which tasks to tackle first? Learn how to keep all members of your team (and their tasks) moving forward at a steady pace. Read more How to prioritize tasks as a team when everything seems important When there’s no structure or process to your team’s work, every task can seem more important than the last. Use these tactics to effectively prioritize when everything is competing for your effort and energy. Read more Log In About Trello What’s behind the boards. Jobs Learn about open roles on the Trello team. Apps Download the Trello App for your Desktop or Mobile devices. Contact us Need anything? Get in touch and we can help. Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Privacy Policy Terms Copyright © 2024 Atlassian | 2026-01-13T09:29:20 |
https://git-scm.com/book/zh-tw/v2/%e4%bc%ba%e6%9c%8d%e5%99%a8%e4%b8%8a%e7%9a%84-Git-Smart-HTTP | Git - Smart HTTP About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 開始 1.1 關於版本控制 1.2 Git 的簡史 1.3 Git 基礎要點 1.4 命令列 1.5 Git 安裝教學 1.6 初次設定 Git 1.7 取得說明文件 1.8 摘要 2. Git 基礎 2.1 取得一個 Git 倉儲 2.2 紀錄變更到版本庫中 2.3 檢視提交的歷史記錄 2.4 復原 2.5 與遠端協同工作 2.6 標籤 2.7 Git Aliases 2.8 總結 3. 使用 Git 分支 3.1 簡述分支 3.2 分支和合併的基本用法 3.3 分支管理 3.4 分支工作流程 3.5 遠端分支 3.6 衍合 3.7 總結 4. 伺服器上的 Git 4.1 通訊協定 4.2 在伺服器上佈署 Git 4.3 產生你的 SSH 公鑰 4.4 設定伺服器 4.5 Git 常駐程式 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第3方 Git 託管方案 4.10 總結 5. 分散式的 Git 5.1 分散式工作流程 5.2 對專案進行貢獻 5.3 維護一個專案 5.4 Summary 6. GitHub 6.1 建立帳戶及設定 6.2 參與一個專案 6.3 維護專案 6.4 Managing an organization 6.5 Scripting GitHub 6.6 總結 7. Git 工具 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 總結 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. 附錄 A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. 附錄 B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. 附錄 C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.6 伺服器上的 Git - Smart HTTP Smart HTTP We now have authenticated access though SSH and unauthenticated access through git:// , but there is also a protocol that can do both at the same time. Setting up Smart HTTP is basically just enabling a CGI script that is provided with Git called git-http-backend on the server. This CGI will read the path and headers sent by a git fetch or git push to an HTTP URL and determine if the client can communicate over HTTP (which is true for any client since version 1.6.6). If the CGI sees that the client is smart, it will communicate smartly with it, otherwise it will fall back to the dumb behavior (so it is backward compatible for reads with older clients). Let’s walk through a very basic setup. We’ll set this up with Apache as the CGI server. If you don’t have Apache setup, you can do so on a Linux box with something like this: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env rewrite This also enables the mod_cgi , mod_alias , mod_env , and mod_rewrite modules, which are all needed for this to work properly. You’ll also need to set the Unix user group of the /opt/git directories to www-data so your web server can read- and write-access the repositories, because the Apache instance running the CGI script will (by default) be running as that user: $ chgrp -R www-data /opt/git Next we need to add some things to the Apache configuration to run the git-http-backend as the handler for anything coming into the /git path of your web server. SetEnv GIT_PROJECT_ROOT /opt/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/lib/git-core/git-http-backend/ If you leave out GIT_HTTP_EXPORT_ALL environment variable, then Git will only serve to unauthenticated clients the repositories with the git-daemon-export-ok file in them, just like the Git daemon did. Finally you’ll want to tell Apache to allow requests to git-http-backend and make writes be authenticated somehow, possibly with an Auth block like this: RewriteEngine On RewriteCond %{QUERY_STRING} service=git-receive-pack [OR] RewriteCond %{REQUEST_URI} /git-receive-pack$ RewriteRule ^/git/ - [E=AUTHREQUIRED] <Files "git-http-backend"> AuthType Basic AuthName "Git Access" AuthUserFile /opt/git/.htpasswd Require valid-user Order deny,allow Deny from env=AUTHREQUIRED Satisfy any </Files> That will require you to create a .htpasswd file containing the passwords of all the valid users. Here is an example of adding a “schacon” user to the file: $ htpasswd -c /opt/git/.htpasswd schacon There are tons of ways to have Apache authenticate users, you’ll have to choose and implement one of them. This is just the simplest example we could come up with. You’ll also almost certainly want to set this up over SSL so all this data is encrypted. We don’t want to go too far down the rabbit hole of Apache configuration specifics, since you could well be using a different server or have different authentication needs. The idea is that Git comes with a CGI called git-http-backend that when invoked will do all the negotiation to send and receive data over HTTP. It does not implement any authentication itself, but that can easily be controlled at the layer of the web server that invokes it. You can do this with nearly any CGI-capable web server, so go with the one that you know best. 筆記 For more information on configuring authentication in Apache, check out the Apache docs here: http://httpd.apache.org/docs/current/howto/auth.html prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/tr/v2/Bir-Sunucuda-Git-Kurma-Ak%c4%b1ll%c4%b1-HTTP | Git - Akıllı HTTP About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Başlangıç 1.1 Sürüm Denetimi 1.2 Git’in Kısa Tarihçesi 1.3 Git Nedir? 1.4 Komut Satırı 1.5 Git’i Yüklemek 1.6 Git’i İlk Defa Kurmak 1.7 Yardım Almak 1.8 Özet 2. Git Temelleri 2.1 Bir Git Reposu Oluşturma/Kopyalama 2.2 Değişikliklerin Repoya Kaydedilmesi 2.3 Katkı Geçmişini Görüntüleme 2.4 Değişiklikleri Geri Alma 2.5 Uzak Repo ile Çalışmak 2.6 Etiketleme 2.7 Komut Kısayolu (Alias) Ayarlama 2.8 Özet 3. Git Dalları 3.1 Dallar 3.2 Kısaca Dallandırma ve Birleştirme Temelleri 3.3 Dal Yönetimi 3.4 İş Akışı Dallandırması 3.5 Uzak Dallar 3.6 Yeniden Temelleme (rebase) 3.7 Özet 4. Bir Sunucuda Git Kurma 4.1 İletişim Kuralları (Protocols) 4.2 Bir Sunucuda Git Kurma 4.3 SSH Ortak Anahtarınızı Oluşturma 4.4 Sunucu Kurma 4.5 Git Cini (Daemon) 4.6 Akıllı HTTP 4.7 GitWeb 4.8 GitLab 4.9 Üçüncü Taraf Barındırma (Hosting) Seçenekleri 4.10 Özet 5. Dağıtık Git 5.1 Dağıtık İş Akışları 5.2 Projenin Gelişiminde Rol Almak 5.3 Bir Projeyi Yürütme 5.4 Özet 6. GitHub 6.1 Bir Projeye Katkıda Bulunmak 6.2 Proje Bakımı 6.3 Kurumsal Yönetim 6.4 GitHub’ı otomatikleştirme 6.5 Özet 7. Git Araçları 7.1 Düzeltme Seçimi 7.2 Etkileşimli İzlemleme (Staging) 7.3 Saklama ve Silme 7.4 Çalışmanızı İmzalama 7.5 Arama 7.6 Geçmişi Yeniden Yazma 7.7 Reset Komutunun Gizemleri 7.8 İleri Seviye Birleştirme 7.9 Rerere 7.10 Git’le Hata Ayıklama 7.11 Alt Modüller 7.12 Demetleme (Bundling) 7.13 Git Nesnesini Değiştirme 7.14 Kimlik Bilgisi Depolama 7.15 Özet 8. Git’i Özelleştirmek 8.1 Git Yapılandırması 8.2 Git Nitelikleri 8.3 Git Kancaları (Hooks) 8.4 Bir Örnek: Mecburi Git Politikası 8.5 Özet 9. Git ve Diğer Sistemler 9.1 İstemci Olarak Git 9.2 Git’e Geçiş 9.3 Özet 10. Dahili Git Ögeleri 10.1 Tesisat ve Döşeme (Plumbing ve Porcelain) 10.2 Git Nesneleri 10.3 Git Referansları 10.4 Packfiles 10.5 Refspec 10.6 Transfer Protokolleri 10.7 Bakım ve Veri Kurtarma 10.8 Ortam Değişkenleri 10.9 Özet A1. Ek bölüm A: Diğer Ortamlarda Git A1.1 Görsel Arayüzler A1.2 Visual Studio ile Git A1.3 Visual Studio Code ile Git A1.4 Eclipse ile Git A1.5 Sublime Text ile Git A1.6 Bash ile Git A1.7 Zsh ile Git A1.8 PowerShell ile Git A1.9 Özet A2. Ek bölüm B: Git’i Uygulamalarınıza Gömmek A2.1 Git Komut Satırı A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Ek bölüm C: Git Komutları A3.1 Kurulum ve Yapılandırma Komutları A3.2 Proje Oluşturma Komutları A3.3 Kısaca Poz (Snapshot) Alma A3.4 Dallandırma ve Birleştirme Komutları A3.5 Projeleri Paylaşma ve Güncelleme Komutları A3.6 İnceleme ve Karşılaştırma Komutları A3.7 Hata Ayıklama (Debugging) Komutları A3.8 Yamalama (Patching) A3.9 E-Posta Komutları A3.10 Harici Sistemler A3.11 Yönetim A3.12 Tesisat (Plumbing) Komutları 2nd Edition 4.6 Bir Sunucuda Git Kurma - Akıllı HTTP Akıllı HTTP Şimdi hem SSH üzerinden kimlik doğrulamalı erişim hem de git:// üzerinden kimlik doğrulamasız erişimimiz var, ancak aynı anda her ikisini de yapabilen bir protokol de bulunmaktadır. Akıllı HTTP’yi kurmak temel olarak sunucuda Git ile birlikte gelen git-http-backend adlı bir CGI betiğini etkinleştirmektir. Bu CGI bir git fetch veya git push 'un bir HTTP URL’sine gönderdiği dizin ve başlıkları okur ve istemcinin HTTP üzerinden iletişim kurup kuramayacağını belirler (1.6.6 sürümünden itibaren tüm istemciler için doğrudur). CGI istemcinin akıllı olduğunu görürse onunla akıllı iletişim kurar, aksi takdirde (daha eski istemcilerle geriye dönük uyumluluk için) aptal davranışa geri döner. Hadi şimdi çok temel bir kurulumu inceleyelim. Bunu Apache’yi CGI sunucusu olarak kullanarak yapacağız. Eğer Apache kurulumunuz yoksa, Linux üzerinde şöyle bir şey yapabilirsiniz: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env Bu aynı zamanda bunun düzgün çalışabilmesi için gereken mod_cgi , mod_alias ve mod_env modüllerini de etkinleştirir. Ayrıca, /srv/git dizinlerinin Unix kullanıcı grubunu www-data olarak ayarlamanız gerekecektir. Böylece web sunucunuz repoları okuma ve yazma erişimine sahip olabilir, çünkü CGI betiğini çalıştıran Apache örneği (varsayılan olarak) bu kullanıcı olarak çalışacaktır: $ chgrp -R www-data /srv/git Şimdi, Apache yapılandırmasına bazı şeyler ekleyelim ki git-http-backend 'i web sunucunuzun /git dizinine gelen her şey için işleyici olarak çalıştırsın. SetEnv GIT_PROJECT_ROOT /srv/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/lib/git-core/git-http-backend/ Eğer GIT_HTTP_EXPORT_ALL ortam değişkenini çıkartırsanız, Git (tam olarak Git daemon’ın yaptığı gibi) yalnızca git-daemon-export-ok dosyasına sahip olan repoları kimlik doğrulamasız istemcilere sunacaktır. Son olarak, Apache’ye git-http-backend 'e olan isteklere izin vermesini ve yazma işlemlerinin bir şekilde kimlik doğrulanmasını yapmasını isteyeceksiniz, muhtemelen şu şekilde bir Auth bloğu ile: <Files "git-http-backend"> AuthType Basic AuthName "Git Access" AuthUserFile /srv/git/.htpasswd Require expr !(%{QUERY_STRING} -strmatch '*service=git-receive-pack*' || %{REQUEST_URI} =~ m#/git-receive-pack$#) Require valid-user </Files> Bu geçerli tüm kullanıcıların şifrelerini içeren bir .htpasswd dosyası oluşturmanızı gerektirecektir. İşte dosyaya bir ``schacon`` kullanıcısı eklemenin bir örneği: $ htpasswd -c /srv/git/.htpasswd schacon Apache’in kullanıcıların kimliğini doğrulaması için birçok yöntemi bulunmaktadır, bunlardan birini seçip uygulamanız gerekecektir. Bulabildiğimiz en basit örnek budur. Ayrıca muhtemelen tüm bu verilerin şifrelenmesi için bunu SSL üzerinden kurmak isteyeceksiniz. Apache yapılandırma detaylarına fazla girmek istemiyoruz, çünkü muhtemelen farklı bir sunucu kullanıyor olabilirsiniz veya farklı kimlik doğrulama ihtiyacınız olabilir. Fikir, Git’in çağrıldığında HTTP üzerinden veri gönderme ve alma işlemlerini yürütecek git-http-backend adlı bir CGI ile birlikte gelmesidir. Kendi başına kimlik sormaz, ancak kendini çağıran web sunucu katmanında kolayca kontrol edilebilir. Bu neredeyse CGI yetenekli her web sunucusuyla yapılabilir, bu nedenle en iyi bildiğiniz sunucu ile devam edin. Not Apache’de kimlik doğrulama yapılandırması hakkında daha fazla bilgi için Apache kılavuzunu buradan kontrol edebilirsiniz: https://httpd.apache.org/docs/current/howto/auth.html prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/bg/v2/%d0%9e%d1%81%d0%bd%d0%be%d0%b2%d0%b8-%d0%bd%d0%b0-Git-%d0%9f%d1%80%d0%b5%d0%b3%d0%bb%d0%b5%d0%b4-%d0%bd%d0%b0-%d0%b8%d1%81%d1%82%d0%be%d1%80%d0%b8%d1%8f%d1%82%d0%b0-%d0%bd%d0%b0-%d0%b4%d0%b5%d0%b9%d1%81%d1%82%d0%b2%d0%b8%d1%8f%d1%82%d0%b0 | Git - Преглед на историята на действията About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 2.3 Основи на Git - Преглед на историята на действията Преглед на историята на действията След като сте създали няколко къмита, или ако сте клонирали хранилище с налични такива - може да пожелаете да погледнете назад за да видите как се е развивал проекта. Най-простият, но и мощен инструмент за това е командата git log . Тези примери използват много прост проект наречен “simplegit”. За да го изтеглите, изпълнете: $ git clone https://github.com/schacon/simplegit-progit След като пуснете git log в този проект, трябва да видите изход подобен на следния: $ git log commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 Change version number commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 16:40:33 2008 -0700 Remove unnecessary test commit a11bef06a3f659402fe7563abf99ad00de2209e6 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 10:31:28 2008 -0700 Initial commit По подразбиране, без аргументи, git log показва промените направени в хранилището в обратен хронологичен ред, най-новите се показват най-горе. Както можете да видите, командата показва всеки къмит с неговата SHA-1 чексума, името и имейла на автора, датата и съобщението на къмита. Самата команда git log разполага с голям брой различни опции, които да ви помогнат да намерите точно необходимата информация. Ще покажем някои от най-популярните. Един от най-полезните аргументи е -p или --patch , който показва разликите ( patch изхода) настъпили с всеки къмит. Можете да използвате също и -2 , което ще ограничи изхода само до последните два къмита: $ git log -p -2 commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 Change version number diff --git a/Rakefile b/Rakefile index a874b73..8f94139 100644 --- a/Rakefile +++ b/Rakefile @@ -5,7 +5,7 @@ require 'rake/gempackagetask' spec = Gem::Specification.new do |s| s.platform = Gem::Platform::RUBY s.name = "simplegit" - s.version = "0.1.0" + s.version = "0.1.1" s.author = "Scott Chacon" s.email = "schacon@gee-mail.com" s.summary = "A simple gem for using Git in Ruby code." commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 16:40:33 2008 -0700 Remove unnecessary test diff --git a/lib/simplegit.rb b/lib/simplegit.rb index a0a60ae..47c6340 100644 --- a/lib/simplegit.rb +++ b/lib/simplegit.rb @@ -18,8 +18,3 @@ class SimpleGit end end - -if $0 == __FILE__ - git = SimpleGit.new - puts git.show -end Тази команда показва същата информация, но с разликите директно след всеки елемент от историята. Това е много полезно за преглед на код или за набързо разглеждане на промените настъпили в серия къмити от даден сътрудник. Можете да използвате и серия от статистически параметри с git log . Например, ако искате да видите съкратена статистика за всеки къмит, ползвайте параметъра --stat : $ git log --stat commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 Change version number Rakefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 16:40:33 2008 -0700 Remove unnecessary test lib/simplegit.rb | 5 ----- 1 file changed, 5 deletions(-) commit a11bef06a3f659402fe7563abf99ad00de2209e6 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 10:31:28 2008 -0700 Initial commit README | 6 ++++++ Rakefile | 23 +++++++++++++++++++++++ lib/simplegit.rb | 25 +++++++++++++++++++++++++ 3 files changed, 54 insertions(+) Както се вижда, параметърът --stat отпечатва след всеки къмит списък на модифицираните файлове, колко от тях са променени и колко редове в тях са добавени и изтрити. Отпечатва се и сумарна информация в края. Друга наистина полезна опция е --pretty . Това форматира изхода по начин различен от подразбиращия се. Разполагате с няколко избора за ползване. Стойността oneline печата всеки къмит на единичен ред, което е полезно ако търсите в множество къмити. В допълнение, стойностите на аргумента short , full , и fuller показват изхода в почти същия формат, но с по-малко или повече информация съответно: $ git log --pretty=oneline ca82a6dff817ec66f44342007202690a93763949 Change version number 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Remove unnecessary test a11bef06a3f659402fe7563abf99ad00de2209e6 Initial commit Най-интересната стойност на параметъра е format , която ви позволява сами да укажете формата на изхода. Това е особено полезно, ако се налага да генерирате изход за последваща машинна обработка, защото можете изрично да укажете формата и да сте сигурни, че той ще си остане същия докато версиите на Git се обновяват: $ git log --pretty=format:"%h - %an, %ar : %s" ca82a6d - Scott Chacon, 6 years ago : Change version number 085bb3b - Scott Chacon, 6 years ago : Remove unnecessary test a11bef0 - Scott Chacon, 6 years ago : Initial commit Полезни опции за git log --pretty=format показва някои от най-популярните флагове, които format разбира. Таблица 1. Полезни опции за git log --pretty=format Флаг Описание %H Хеш на къмита %h Съкратен хеш на къмита %T Tree хеш %t Съкратен Tree хеш %P Родителски хешове %p Съкратени родителски хешове %an Име на автора %ae Имейл на автора %ad Дата на author къмит (форматът взема предвид --date=option) %ar Релативна дата на author къмит %cn Име на committer %ce Имейл на committer %cd Дата на committer-къмит %cr Релативна дата на committer-къмит %s Съобщение Може да се запитате каква е разликата между author и committer . Авторът е лицето, което първоначално е писало нещо по дадена задача, докато committer е лицето, което последно е допринесло в нея. Така, ако вие изпратите даден пач към проект и някой от сътрудниците го приложи към проекта, и двамата правите принос — вие като автор и въпросния сътрудник като committer. Ще разгледаме по-подробно това разделение в [ch05-distributed-git] . Аргументите oneline и format са особено полезни в съчетание с друг аргумент, --graph . Това добавя забавна малка ASCII графика, показваща клона и историята на сливанията: $ git log --pretty=format:"%h %s" --graph * 2d3acf9 Ignore errors from SIGCHLD on trap * 5e3ee11 Merge branch 'master' of git://github.com/dustin/grit |\ | * 420eac9 Add method for getting the current branch * | 30e367c Timeout code and tests * | 5a09431 Add timeout protection to grit * | e1193f8 Support for heads with slashes in them |/ * d6016bc Require time for xmlschema * 11d191e Merge branch 'defunkt' into local Този тип изход става по-интересен, когато навлезем в материята на клоновете (branching) и сливането (merging) в следващата глава. Но това са само някои прости опции за форматиране на изхода на git log — съществуват и много други. Common options to git log изброява опциите, които вече разгледахме плюс някои други полезни такива, променящи изхода на командата log. Таблица 2. Common options to git log Опция Описание -p Показва пача за всеки къмит. --stat Показва статистики за файловете променени във всеки къмит. --shortstat Показва само changed/insertions/deletions реда от --stat варианта. --name-only Показва списък на променените файлове след информацията за къмита. --name-status Показва списък на засегнатите файлове ведно с added/modified/deleted детайлите. --abbrev-commit Показва само първите няколко символа на SHA-1 чексумата, вместо всичките 40. --relative-date Показва датата в релативен формат (например, “2 weeks ago”) вместо в пълния ѝ формат. --graph Показва ASCII графика на branch и merge историята до изхода. --pretty Показва къмитите в алтернативен формат. Стойностите включват oneline, short, full, fuller, и format (където указвате собствен формат на изхода). --oneline Съкращение за --pretty=oneline --abbrev-commit използвани заедно. Ограничаване на изхода В допълнение към опциите за формат на изхода, git log поддържа и полезни средства за лимитиране, с които да показвате само част от къмитите. Вече видяхте едно от тях под формата на параметър -2 , показващ само последните два къмита. В действителност, можете да ползвате -<n> , където n е произволно число, за да покажете колкото от тях желаете. Практически обаче, това рядко се налага, защото Git по подразбиране странира изхода си, така че да виждате само по един екран в даден момент. Обаче, опциите за ограничаване по време, като --since и --until , са много полезни. Например, тази команда показва списък от къмитите направени в последните две седмици: $ git log --since=2.weeks Тази команда работи с множество формати — можете да укажете специфична дата като "2008-01-15" , или релативен период като "2 years 1 day 3 minutes ago" . Можете също да филтрирате списъка с къмити, които съответстват на определен критерий за търсене. Опцията --author позволява да търсите по определен автор и --grep опцията ви позволява да търсите по ключови думи в съобщенията на къмитите. (Отбележете, че ако искате да използвате едновременно и двете опции, трябва да добавите --all-match , иначе командата ще показва резултат ако дори и само единият критерий съвпада) Забележка Можете да укажете повече от една инстанция за --author и --grep критериите, което ще ограничи показваните къмити до всеки , който отговаря на --author и всеки , който отговаря на --grep маските; обаче, добавянето на --all-match опцията допълнително ограничава изхода до само тези, които отговарят на всички --grep маски. Друг полезен филтър е опцията -S (позната още като “pickaxe” опцията на Git), която приема стринг и показва само тези къмити, които са променили броя на срещанията на този стринг. Ако примерно желаете да намерите последния къмит, който е добавил или премахнал обръщение към специфична функция, можете да изпълните: $ git log -S function_name Последната доста полезна опция, която можете да пратите като филтър към git log е път към файл/директория. Ако укажете име на директория или файл, можете да ограничите изхода до къмитите, в които са правени промени по тези специфични файлове. Това винаги трябва да е последен параметър към командата и обикновено се слага префикс от две тирета ( -- ) за разделяне на пътищата от другите параметри: $ git log -- path/to/file В таблицата Опции за ограничаване на изхода на git log разглеждаме тези и някои други опции. Таблица 3. Опции за ограничаване на изхода на git log Опция Описание -<n> Показва само последните n на брой къмита --since , --after Показва само къмитите направени след указаната дата. --until , --before Показва само къмитите направени преди указаната дата. --author Показва само къмитите, в които авторът съответства на подадения стринг. --committer Показва само къмитите, в които committer-ът съответства на подадения стринг. --grep Позволява търсене по стринг в commit-съобщението -S Позволява търсене по стринг в промените в кода Например, ако искате да видите кои къмити променили тестови файлове в сорс кода на Git са направени от Junio Hamano през октомври 2008 и това не са merge-къмити, можете да изпълните нещо подобно: $ git log --pretty="%h - %s" --author='Junio C Hamano' --since="2008-10-01" \ --before="2008-11-01" --no-merges -- t/ 5610e3b - Fix testcase failure when extended attributes are in use acd3b9e - Enhance hold_lock_file_for_{update,append}() API f563754 - demonstrate breakage of detached checkout with symbolic link HEAD d1a43f2 - reset --hard/read-tree --reset -u: remove unmerged new paths 51a94af - Fix "checkout --track -b newbranch" on detached HEAD b0ad11e - pull: allow "git pull origin $something:$current_branch" into an unborn branch Тази команда филтрира близо 40 хиляди къмита от историята на сорс кода на Git и показва само 6-те, които отговарят на критерия. Подсказка Пропускане на показването на merge къмити В зависимост от работната последователност, която се използва във вашето хранилище, възможно е голям процент от къмитите в историята да са просто merge къмити, които обикновено не са много информативни. За да забраните показването им, и да опростите историята, просто подайте аргумента --no-merges . prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
http://www.trello.com/use-cases | Work Management Use Cases | Trello Skip to main content Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Use case: Task management Track progress of tasks in one convenient place with a visual layout that adds ‘ta-da’ to your to-do’s. Use case: Resource hub Save hours when you give teams a well-designed hub to find information easily and quickly. Use case: Project management Keep projects organized, deadlines on track, and teammates aligned with Trello. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Back Navigation Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Read though our use cases to make the most of Trello on your team. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Helping teams work better, together Discover Trello use cases, productivity tips, best practices for team collaboration, and expert remote work advice. Check out the Trello blog See Trello in action Explore all the ways Trello can power team productivity. Brainstorming Unleash your team’s creativity and keep ideas visible, collaborative, and actionable. CRM Customize your CRM to help your sales team manage their leads and accounts effectively. Editorial calendar Use Trello as your team’s go-to command center for content curation, revisions, handoff, and publishing. Finance Trello streamlines finance team operations for more transparency and less missed deadlines. Health and wellness Save time with one system for managing health & wellness clients, time-tracking, appointments, and more. Information technology (IT) Get from “intake” to “done” in record time with a flexible system for setting up queues and projects your way. Meetings Empower your team meetings to be more productive, empowering, and dare we say—fun. Onboarding Onboarding to a new company or project is a snap with Trello’s visual layout of to-do’s, resources, and progress tracking. Process tracking View progress to completion at a glance and quickly identify blockers in any process. Professional services Juggle multiple clients and competing priorities with ease using Trello’s automation and advanced Timeline view. Project management Keep tasks in order, deadlines on track, and team members aligned with Trello. Project status dashboard Get a customizable overview of all major work across your organization in one place. Resource hub Save time with a well-designed hub that helps teams find information easily and quickly. Task management Use Trello to track, manage, complete, and bring tasks together like the pieces of a puzzle, and make your team’s projects a cohesive success every time. Nonprofits Manage programs, coordinate volunteers and create more social impact with Trello. Log In About Trello What’s behind the boards. Jobs Learn about open roles on the Trello team. Apps Download the Trello App for your Desktop or Mobile devices. Contact us Need anything? Get in touch and we can help. Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Privacy Policy Terms Copyright © 2024 Atlassian | 2026-01-13T09:29:20 |
https://git-scm.com/book/id/v2/Git-di-Server-Smart-HTTP | Git - Smart HTTP About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Memulai 1.1 Tentang Version Control 1.2 Sejarah Singkat Git 1.3 Dasar-dasar Git 1.4 Command Line 1.5 Memasang Git 1.6 Pengaturan Awal Git 1.7 Mendapatkan Bantuan 1.8 Kesimpulan 2. Git Basics 2.1 Mendapatkan Repository Git 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Alias Git 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git di Server 4.1 Protokol 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Ringkasan 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pengaturan dan Konfigurasi Akun 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Mengelola Organization 6.5 Scripting GitHub 6.6 Ringkasan 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Kostumisasi Git 8.1 Konfigurasi Git 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Ringkasan 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.6 Git di Server - Smart HTTP Smart HTTP We now have authenticated access though SSH and unauthenticated access through git:// , but there is also a protocol that can do both at the same time. Setting up Smart HTTP is basically just enabling a CGI script that is provided with Git called git-http-backend on the server.git commands, "http-backend" This CGI will read the path and headers sent by a git fetch or git push to an HTTP URL and determine if the client can communicate over HTTP (which is true for any client since version 1.6.6). If the CGI sees that the client is smart, it will communicate smartly with it, otherwise it will fall back to the dumb behavior (so it is backward compatible for reads with older clients). Let’s walk though a very basic setup. We’ll set this up with Apache as the CGI server. If you don’t have Apache setup, you can do so on a Linux box with something like this: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env This also enables the mod_cgi , mod_alias , and mod_env modules, which are all needed for this to work properly. Next we need to add some things to the Apache configuration to run the git http-backend as the handler for anything coming into the /git path of your web server. SetEnv GIT_PROJECT_ROOT /opt/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/libexec/git-core/git-http-backend/ If you leave out GIT_HTTP_EXPORT_ALL environment variable, then Git will only serve to unauthenticated clients the repositories with the git-daemon-export-ok file in them, just like the Git daemon did. Then you’ll have to tell Apache to allow requests to that path with something like this: <Directory "/usr/lib/git-core*"> Options ExecCGI Indexes Order allow,deny Allow from all Require all granted </Directory> Finally you’ll want to make writes be authenticated somehow, possibly with an Auth block like this: <LocationMatch "^/git/.*/git-receive-pack$"> AuthType Basic AuthName "Git Access" AuthUserFile /opt/git/.htpasswd Require valid-user </LocationMatch> That will require you to create a .htaccess file containing the passwords of all the valid users. Here is an example of adding a “schacon” user to the file: $ htdigest -c /opt/git/.htpasswd "Git Access" schacon There are tons of ways to have Apache authenticate users, you’ll have to choose and implement one of them. This is just the simplest example we could come up with. You’ll also almost certainly want to set this up over SSL so all this data is encrypted. We don’t want to go too far down the rabbit hole of Apache configuration specifics, since you could well be using a different server or have different authenication needs. The idea is that Git comes with a CGI called git http-backend that when invoked will do all the negotiation to send and receive data over HTTP. It does not implement any authentication itself, but that can easily be controlled at the layer of the web server that invokes it. You can do this with nearly any CGI-capable web server, so go with the one that you know best. Note For more information on configuring authentication in Apache, check out the Apache docs here: http://httpd.apache.org/docs/current/howto/auth.html prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
http://www.trello.com/tour | What is Trello: Learn Features, Uses & More | Trello Skip to main content Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Use case: Task management Track progress of tasks in one convenient place with a visual layout that adds ‘ta-da’ to your to-do’s. Use case: Resource hub Save hours when you give teams a well-designed hub to find information easily and quickly. Use case: Project management Keep projects organized, deadlines on track, and teammates aligned with Trello. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Back Navigation Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Read though our use cases to make the most of Trello on your team. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Helping teams work better, together Discover Trello use cases, productivity tips, best practices for team collaboration, and expert remote work advice. Check out the Trello blog Your productivity powerhouse Welcome to Trello, the ultimate tool for getting things done. Whether you're managing daily to-dos, setting personal goals, or organizing your life, Trello helps you focus on what matters most and always stay on top of your game. Sign up—it’s free! Join a community of millions of users globally who are using Trello to get more done. Your to-dos, organized Stay organized and efficient with Inbox, Boards, and Planner. Every to-do, idea, or responsibility—no matter how small—finds its place, keeping you at the top of your game. Inbox When it’s on your mind, it goes in your Inbox. Capture your to-dos from anywhere, anytime. Boards Your to-do list may be long, but it can be manageable! Keep tabs on everything from "to-dos to tackle" to "mission accomplished!” Planner Drag, drop, get it done. Snap your top tasks into your calendar and make time for what truly matters. Inbox When it’s on your mind, it goes in your Inbox. Capture your to-dos from anywhere, anytime. Boards Your to-do list may be long, but it can be manageable! Keep tabs on everything from "to-dos to tackle" to "mission accomplished!” Planner Drag, drop, get it done. Snap your top tasks into your calendar and make time for what truly matters. Simplify your to-do list Trello cards keep all of your important information organized and accessible in one place. Add due dates, attach files, and mark to-do’s as “Done” when completed. Plus, AI helps you refine your text for a polished finish! Due dates Due dates go hand-in-hand with staying organized. In Trello, they’re easy to set, hard to miss (with reminders!), and oh-so-satisfying to mark as “done.” Attachments No more digging through endless email chains to find attachments. Just drag and drop them onto a card so the right files stay with the right tasks. Checklists Your best tool to overpower overwhelming asks. Break big tasks into small ones, check things off the list, and watch that status bar go to 100% complete. Powered by AI Harness the power of AI. Brainstorm new ideas, organize action items, and condense lengthy texts instantly with AI INTEGRATIONS Simplify your workflow and stay on top of your to-dos effortlessly! Integrate seamlessly with the apps and services your team relies on like Slack, Microsoft Teams, Outlook, Gmail, Confluence, and hundreds more. And if you use Jira, you can seamlessly sync and manage your tasks right within Trello using Jira Lists. Learn more > Unlock your potential with Trello Experience a new level of efficiency and productivity with Trello. Your work, your way Need to structure information on Trello cards specific to the task at hand? Custom Fields lets you do all that and more— providing process and formality to your workflow to meet your unique needs. Automate your workflow Create a foolproof process for moving work forward with Trello’s built-in automation system. Run commands and set automated rules for almost any action in Trello so that you can focus on what matters most. Learn more > Get peace of mind Easily manage users in real-time and control content-management permissions with just a few clicks. With 99.99% uptime YoY and industry-leading compliance certifications, you can rest assured we’ll never leave you hanging. Try Premium free for 14 days Supercharge your productivity with AI and unlimited automation Sign up By entering my email, I acknowledge the Atlassian Privacy Policy Log In About Trello What’s behind the boards. Jobs Learn about open roles on the Trello team. Apps Download the Trello App for your Desktop or Mobile devices. Contact us Need anything? Get in touch and we can help. Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Privacy Policy Terms Copyright © 2024 Atlassian | 2026-01-13T09:29:20 |
https://git-scm.com/book/es/v2/Git-en-el-Servidor-HTTP-Inteligente | Git - HTTP Inteligente About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Inicio - Sobre el Control de Versiones 1.1 Acerca del Control de Versiones 1.2 Una breve historia de Git 1.3 Fundamentos de Git 1.4 La Línea de Comandos 1.5 Instalación de Git 1.6 Configurando Git por primera vez 1.7 ¿Cómo obtener ayuda? 1.8 Resumen 2. Fundamentos de Git 2.1 Obteniendo un repositorio Git 2.2 Guardando cambios en el Repositorio 2.3 Ver el Historial de Confirmaciones 2.4 Deshacer Cosas 2.5 Trabajar con Remotos 2.6 Etiquetado 2.7 Alias de Git 2.8 Resumen 3. Ramificaciones en Git 3.1 ¿Qué es una rama? 3.2 Procedimientos Básicos para Ramificar y Fusionar 3.3 Gestión de Ramas 3.4 Flujos de Trabajo Ramificados 3.5 Ramas Remotas 3.6 Reorganizar el Trabajo Realizado 3.7 Recapitulación 4. Git en el Servidor 4.1 Los Protocolos 4.2 Configurando Git en un servidor 4.3 Generando tu clave pública SSH 4.4 Configurando el servidor 4.5 El demonio Git 4.6 HTTP Inteligente 4.7 GitWeb 4.8 GitLab 4.9 Git en un alojamiento externo 4.10 Resumen 5. Git en entornos distribuidos 5.1 Flujos de trabajo distribuidos 5.2 Contribuyendo a un Proyecto 5.3 Manteniendo un proyecto 5.4 Resumen 6. GitHub 6.1 Creación y configuración de la cuenta 6.2 Participando en Proyectos 6.3 Mantenimiento de un proyecto 6.4 Gestión de una organización 6.5 Scripting en GitHub 6.6 Resumen 7. Herramientas de Git 7.1 Revisión por selección 7.2 Organización interactiva 7.3 Guardado rápido y Limpieza 7.4 Firmando tu trabajo 7.5 Buscando 7.6 Reescribiendo la Historia 7.7 Reiniciar Desmitificado 7.8 Fusión Avanzada 7.9 Rerere 7.10 Haciendo debug con Git 7.11 Submódulos 7.12 Agrupaciones 7.13 Replace 7.14 Almacenamiento de credenciales 7.15 Resumen 8. Personalización de Git 8.1 Configuración de Git 8.2 Git Attributes 8.3 Puntos de enganche en Git 8.4 Un ejemplo de implantación de una determinada política en Git 8.5 Recapitulación 9. Git y Otros Sistemas 9.1 Git como Cliente 9.2 Migración a Git 9.3 Resumen 10. Los entresijos internos de Git 10.1 Fontanería y porcelana 10.2 Los objetos Git 10.3 Referencias Git 10.4 Archivos empaquetadores 10.5 Las especificaciones para hacer referencia a… (refspec) 10.6 Protocolos de transferencia 10.7 Mantenimiento y recuperación de datos 10.8 Variables de entorno 10.9 Recapitulación A1. Apéndice A: Git en otros entornos A1.1 Interfaces gráficas A1.2 Git en Visual Studio A1.3 Git en Eclipse A1.4 Git con Bash A1.5 Git en Zsh A1.6 Git en Powershell A1.7 Resumen A2. Apéndice B: Integrando Git en tus Aplicaciones A2.1 Git mediante Línea de Comandos A2.2 Libgit2 A2.3 JGit A3. Apéndice C: Comandos de Git A3.1 Configuración A3.2 Obtener y Crear Proyectos A3.3 Seguimiento Básico A3.4 Ramificar y Fusionar A3.5 Compartir y Actualizar Proyectos A3.6 Inspección y Comparación A3.7 Depuración A3.8 Parcheo A3.9 Correo Electrónico A3.10 Sistemas Externos A3.11 Administración A3.12 Comandos de Fontanería 2nd Edition 4.6 Git en el Servidor - HTTP Inteligente HTTP Inteligente Ahora ya tenemos acceso autentificado mediante SSH y anónimo mediante git:// , pero hay también otro protocolo que permite tener ambos accesos a la vez. Configurar HTTP inteligente consiste, básicamente, en activar en el servidor web un script CGI que viene con Git, llamado git-http-backend . Este CGI leerá la ruta y las cabeceras enviadas por los comandos git fetch o git push a una URL de HTTP y determinará si el cliente puede comunicar con HTTP (lo que será cierto para cualquier cliente a partir de la versión 1.6.6). Si el CGI comprueba que el cliente es inteligente, se comunicará inteligentemente con él; en otro caso pasará a usar el comportamiento tonto (es decir, es compatible con versiones más antiguas del cliente). Revisemos una configuración básica. Pondremos Apache como servidor de CGI. Si no tienes Apache configurado, lo puedes instalar en un Linux con un comando similar a este: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env Esto además activa los módulos mod_cgi , mod_alias , y mod_env , que van a hacer falta para que todo esto funcione. A continuación tenemos que añadir algunas cosas a la configuración de Apache para que se utilice git-http-backend para cualquier cosa que haya bajo la carpeta virtual /git . SetEnv GIT_PROJECT_ROOT /opt/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/libexec/git-core/git-http-backend/ Si dejas sin definir la variable de entorno GIT_HTTP_EXPORT_ALL , Git solo servirá a los clientes anónimos aquellos repositorios que contengan el archivo daemon-export-ok , igual que hace el “demonio” Git. Ahora tienes que decirle a Apache que acepte peticiones en esta ruta con algo similar a esto: <Directory "/usr/lib/git-core*"> Options ExecCGI Indexes Order allow,deny Allow from all Require all granted </Directory> Finalmente, si quieres que los clientes autentificados tengan acceso de escritura, tendrás que crear un bloque Auth similar a este: <LocationMatch "^/git/.*/git-receive-pack$"> AuthType Basic AuthName "Git Access" AuthUserFile /opt/git/.htpasswd Require valid-user </LocationMatch> Esto requiere que hagas un archivo .htaccess que contenga las contraseñas cifradas de todos los usuarios válidos. Por ejemplo, para añadir el usuario “schacon” a este archivo: $ htdigest -c /opt/git/.htpasswd "Git Access" schacon Hay un montón de maneras de dar acceso autentificado a los usuarios con Apache, y tienes que elegir una. Esta es la forma más simple de hacerlo. Probablemente también te interese hacerlo todo con SSL para que todos los datos vayan cifrados. No queremos profundizar en los detalles de la configuración de Apache, ya que puedes tener diferentes necesidades de autentificación o querer utilizar un servidor diferente. La idea es que Git trae un CGI llamado git-http-backend que cuando es llamado, hace toda la negociación y envío o recepción de datos a través de HTTP. Por sí mismo no implementa autentificación de ningún tipo, pero puede controlarse desde el servidor web que lo utiliza. Puedes configurar esto en casi cualquier servidor web que pueda trabajar con CGI, el que más te guste. Nota Para más información sobre cómo configurar Apache, mira la documentación: http://httpd.apache.org/docs/current/howto/auth.html prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
http://www.trello.com/power-ups | Trello Your browser was unable to load all of Trello's resources. They may have been blocked by your firewall, proxy or browser configuration. Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again and if that doesn't work, check out our troubleshooting guide . To use Trello, please enable JavaScript. | 2026-01-13T09:29:20 |
https://sre.google/resources/practices-and-processes/incident-management-guide/#page-content | Google SRE - Learn sre incident management and response Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content Google Site Reliability Engineering: Incident Management Guide Written by Adam Crume, Alex Cepoi, Chelsea Granados, Roxana Loza, Steve McGhee, Svetlana Gites, Trevor Mattson-Hamilton, and Vrai Stacey Introduction Outages are inevitable in any sufficiently complex system. When an outage happens, it is essential to have a process in place to know how to manage and respond effectively. A well-defined plan helps teams minimize the impact on users and customers, coordinate their response to mitigate the incident faster , and learn from it so that it can be prevented from happening again. Google has a long-standing, well-documented incident response process that has been developed and refined over the years. Here we present a primer of the end-to-end process. Prepare for incidents Effective incident response begins with preparation, which includes having in place a reliable alerting mechanism and well-defined oncall process. Alerts are an efficient way to detect system issues and notify the on-call team so they can be addressed. Here are some of the key attributes of a good alerting mechanism: Alert in a timely manner: Minimize the user impact prior to incident response beginning. Cover all key user facing functionality Alert based on symptoms, not causes: Alerts should be based on end-to-end measures of customer/client experience, not based on a system's internal behavior. Be actionable: Alerts that cannot be acted upon by an on-caller generate noise. Alerting based on SLOs (Service Level Objectives for particular functionality) is a good way to achieve the first three attributes. Some preventive alerts based on internal metrics may be required, such as protecting against an imminent failure due to approaching a hard resource quota, as failures of this nature can cause a system to instantaneously transition from 0% failure to 100% failure. However, the general rule is to avoid alerting on a system's internal behavior as these alerts don't accurately map to user impact, and are fragile due to being closely bound to a service's implementation at the time the alert is defined. Once you have an alerting mechanism ready, you need to ensure your oncall team is ready to respond to the alerts. As with any activity, being oncall can be made much easier with proper preparation. Having up to date playbooks with instructions on how to debug and mitigate issues can speed up incident response significantly. Note that oncallers need to be aware of the playbooks, and other training material , for it to be effective. Regular practice through activities such as "Wheel of Misfortune" exercises can keep this knowledge up to date, as well as providing an opportunity for less experienced oncallers to develop their skills in a safe environment. Where possible, automating elements of incident response will free the oncallers to focus on problem solving. This can include automation of common tasks, automated analysis of key impact information (severity, affected services/locations, etc), root cause analysis, and intelligent suggestion of mitigating actions the oncaller can take. Respond and manage incidents Google's incident response system, known as IMAG, is based on the Incident Command System (ICS), a US standard for responding to emergencies, such as wildfires or earthquakes. These systems focus on the "three Cs" (3Cs) of incident management: coordinate, communicate, and control. IMAG organizes the incident response by establishing a hierarchical structure with clear roles, tasks, and communication channels. The main roles in Google's IMAG are Incident Commander (IC), Communications Lead (CL), and Operations Lead (OL). The IC coordinates the overall incident response. The CL provides regular updates to stakeholders and acts as a point of contact for incoming communications. This allows the OL to focus on mitigating the issue, minimize user impact, and resolving the problem. This helps balance multiple ongoing needs. As suggested by the name, these leads may delegate certain tasks to other responders. Incident roles do not follow reporting chains and instead are based on knowledge and incident context. Good incident response, like many things, is user-centric. Fixing the problem is only part of what's needed; it's just as important to ensure that your users, stakeholders, and leaders are updated about what's affected, how bad it is, what workarounds may be possible, and when the incident may be mitigated and resolved. Communicating consistently and with an appropriate level of detail for the reader builds trust and transparency. These are just as important as technical mitigations. Google has various Incident Response Teams (IRTs) which can also be activated for additional support during major incidents. The services provided by each IRT vary, but may include coordinating multiple team-level efforts, providing hands-on assistance, identifying and contacting teams that are (or should be) involved, gathering resources, assisting in escalations, activating other IRTs, and broad internal and/or external communications. Effective response means treating it as a project in its own right. This includes planning ahead, deciding who needs to be involved, and documenting what has been done. Chaos will naturally prevail unless it is actively managed. Remediate and learn from incidents One of Google's core tenets of effective incident response is to learn from outages and improve our systems to prevent similar incidents from happening in the future. When not possible, we strive to minimize the duration and impact of unavoidable/unanticipated outages. Left unchecked, outages tend to regularly resurface and accumulate over time. This increases the operational toil for the team and can lead to expended error budgets, eroded user trust, and impacted revenue. The most effective tool we have found for achieving that is through open and blameless postmortem writing . After the incident is resolved, a write-up of the incident is immediately started, seeking to fully understand and document how the incident unfolded, its impact, as well as things that went well or could be improved. It is important to look at a broad range of aspects of the incident response, not just at fixing the immediate problem or preventing it from recurring; looking at effective ways to improve detection, mitigation, coordination, or communication across teams and to impacted users is equally important. One of the core tenets of SRE's culture is that postmortems should be blameless. It's important to remember that everyone involved in the incident had good intentions. Blaming individuals for unintended consequences during the response, does not aid the learning process so instead, we focus on how we can improve our systems, procedures, and training to make them more resilient. An honest and timely postmortem write-up reviewed by stakeholders and shared broadly with the entire organization is key to identifying the most effective corrective action items to prevent similar incidents from happening again. Once SLOs for completion of action items are agreed with stakeholders, these feed back into the team's backlog. Teams balance these action items against feature work and prioritize informed by overall reliability. Once a postmortem writing culture is established, aggregating structured data collected across a large number of postmortems to identify trends and organizational areas needing larger investments becomes a great opportunity in a larger organization. Further reading SRE Book, Chapter 9: https://sre.google/workbook/incident-response/ "Preparing for your next incident" discussion (audio): https://www.oreilly.com/content/taming-chaos-preparing-for-your-next-incident/ How Lowe's reduced its MTTR by over 80 percent: https://cloud.google.com/blog/products/devops-sre/how-lowes-improved-incident-response-processes-with-sre Shrinking the impact of production incidents: https://cloud.google.com/blog/products/devops-sre/shrinking-the-impact-of-production-incidents-using-sre-principles-cre-life-lessons ProdEx - Google's Production Excellence Program: https://videos.itrevolution.com/watch/762364173/ Download as PDF Follow us About Google Google products Privacy Terms Help | 2026-01-13T09:29:20 |
https://git-scm.com/book/gr/v2/%ce%a4%ce%bf-Git-%cf%83%cf%84%ce%bf%ce%bd-%ce%b4%ce%b9%ce%b1%ce%ba%ce%bf%ce%bc%ce%b9%cf%83%cf%84%ce%ae-%ce%88%ce%be%cf%85%cf%80%ce%bd%ce%bf-HTTP | Git - Έξυπνο HTTP About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Ξεκινώντας με το Git 1.1 Σχετικά με τον έλεγχο εκδόσεων 1.2 Σύντομο ιστορικό του Git 1.3 Τι είναι το Git; 1.4 Η γραμμή εντολών 1.5 Εγκατάσταση του Git 1.6 Ρύθμιση του Git για πρώτη φορά 1.7 Χρησιμοποιώντας τη βοήθεια 1.8 Ανακεφαλαίωση 2. Τα θεμελιώδη στοιχεία του Git 2.1 Απόκτηση αποθετηρίου Git 2.2 Καταγραφή αλλαγών στο αποθετήριο 2.3 Χρησιμοποιώντας το ιστορικό υποβολών 2.4 Αναιρέσεις (undoing) 2.5 Δουλεύοντας με απομακρυσμένα αποθετήρια 2.6 Ετικέτες 2.7 Συντομεύεσεις στο Git 2.8 Ανακεφαλαίωση 3. Διακλαδώσεις στο Git 3.1 Οι κλάδοι με λίγα λόγια 3.2 Βασικές έννοιες διακλαδώσεων και συγχωνεύσεων 3.3 Διαχείριση κλάδων 3.4 Ροές εργασίας με διακλαδώσεις 3.5 Απομακρυσμένοι κλάδοι 3.6 Αλλαγή βάσης (rebasing) 3.7 Ανακεφαλαίωση 4. Το Git στον διακομιστή 4.1 Τα πρωτόκολλα 4.2 Εγκατάσταση του Git σε διακομιστή 4.3 Δημιουργία δημόσιου κλειδιού SSH 4.4 Στήσιμο του διακομιστή 4.5 Δαίμονες του Git 4.6 Έξυπνο HTTP 4.7 GitWeb 4.8 GitLab 4.9 Επιλογές φιλοξενίας από τρίτους 4.10 Ανακεφαλαίωση 5. Κατανεμημένο Git 5.1 Κατανεμημένες ροές εργασίας 5.2 Συνεισφέροντας σε ένα έργο 5.3 Συντήρηση ενός έργου 5.4 Ανακεφαλαίωση 6. GitHub 6.1 Δημιουργία λογαριασμού και ρύθμισή του 6.2 Συνεισφορά σε έργο 6.3 Συντήρηση ενός έργου 6.4 Διαχείριση οργανισμώνν 6.5 Συγγραφή script στο GitHub 6.6 Ανακεφαλαίωση 7. Εργαλεία του Git 7.1 Επιλογή αναθεώρησης 7.2 Διαδραστική εργασία με το στάδιο καταχώρισης 7.3 Αποθέματα και Καθαρισμός 7.4 Υπογραφή της δουλειάς μας 7.5 Αναζήτηση 7.6 Η ιστορία ξαναγράφεται 7.7 Απομυθοποίηση της reset 7.8 Προχωρημένη Συγχώνευση 7.9 Rerere 7.10 Αποσφαλμάτωση με το Git 7.11 Υπομονάδες 7.12 Δεμάτιασμα δεδομένων 7.13 Replace 7.14 Αποθήκευση διαπιστευτηρίων 7.15 Ανακεφαλαίωση 8. Εξατομίκευση του Git 8.1 Διαμόρφωση Git 8.2 Γνωρίσματα του Git 8.3 Τα άγκιστρα του Git 8.4 Ένα παράδειγμα επιβολής πολιτικής από το Git 8.5 Ανακεφαλαίωση 9. Το Git και άλλα συστήματα 9.1 Το Git ως πελάτης 9.2 Μετανάστευση στο Git 9.3 Ανακεφαλαίωση 10. Εσωτερική λειτουργία του Git 10.1 Διοχετεύσεις και πορσελάνες 10.2 Αντικείμενα του Git 10.3 Αναφορές του Git 10.4 Πακετάρισμα αρχείων 10.5 Τα refspec 10.6 Πρωτόκολλα μεταφοράς 10.7 Διατήρηση και ανάκτηση δεδομένων 10.8 Μεταβλητές περιβάλλοντος 10.9 Ανακεφαλαίωση A1. Appendix A: Το Git σε άλλα περιβάλλοντα A1.1 Γραφικές διεπαφές A1.2 Το Git στο Visual Studio A1.3 Git στο Visual Studio Code A1.4 Git στο IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git στο Sublime Text A1.6 Το Git στο Bash A1.7 Το Git στο Zsh A1.8 Το Git στο Powershell A1.9 Ανακεφαλαίωση A2. Appendix B: Ενσωμάτωση του Git στις εφαρμογές μας A2.1 Γραμμή εντολών Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Εντολές Git A3.1 Ρύθμιση και διαμόρφωση A3.2 Λήψη και δημιουργία έργων A3.3 Βασική λήψη στιγμιοτύπων A3.4 Διακλάδωση και συγχώνευση A3.5 Κοινή χρήση και ενημέρωση έργων A3.6 Επιθεώρηση και σύγκριση A3.7 Αποσφαλμάτωση A3.8 Επιθέματα A3.9 Ηλεκτρονικό ταχυδρομείο A3.10 Εξωτερικά Συστήματα A3.11 Διοίκηση A3.12 Εντολές διοχέτευσης 2nd Edition 4.6 Το Git στον διακομιστή - Έξυπνο HTTP Έξυπνο HTTP Έχουμε πλέον ταυτοποιημένη πρόσβαση μέσω SSH και μη-ταυτοποιημένη πρόσβαση μέσω του git:// , αλλά υπάρχει και ένα πρωτόκολλο που μπορεί να κάνει και τα δύο ταυτόχρονα. Η εγκατάσταση του Έξυπνου HTTP βασικά απλά ενεργοποιεί ένα script CGI, που παρέχεται με τον Git και ονομάζεται git-http-backend , στον διακομιστή. Αυτό το CGI θα διαβάσει τη διαδρομή και τις κεφαλίδες που θα σταλούν με git fetch ή git push σε μια διεύθυνση URL HTTP και θα καθορίσει εάν ο πελάτης μπορεί να επικοινωνήσει μέσω HTTP (κάτι που ισχύει για όλους τους πελάτες από την έκδοση 1.6.6 και μετά). Αν το CGI διαπιστώσει ότι ο πελάτης είναι έξυπνος, θα επικοινωνήσει μαζί του έξυπνα, αλλιώς θα επανέλθει στη χαζή συμπεριφορά (συνεπώς έχει προς-τα-πίσω συμβατότητα για ανάγνωσεις με τους παλαιότερους πελάτες). Ας δούμε αναλυτικά μία πολύ βασική ρύθμιση. Θα υποθέσουμε ότι ο διακομιστής CGI είναι ο Apache. Αν δεν έχουμε Apache, μπορούμε να το κάνουμε σε ένα κουτί Linux με κάτι σαν αυτό: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env Αυτό ενεργοποιεί επίσης τις λειτουργικές μονάδες (modules) mod_cgi , mod_alias και mod_env , που είναι απαραίτητες για να λειτουργήσει σωστά όλο αυτό. Θα πρέπει επίσης να ορίσουμε την ομάδα χρηστών Unix φακέλων /srv/git σε www-data , ώστε ο web server να έχει πρόσβαση ανάγνωσης και εγγραφής στα αποθετήρια, διότι ο Apache που τρέχει το script CGA θα τρέχει εξ ορισμού ως ο χρήστης: $ chgrp -R www-data /srv/git Στη συνέχεια πρέπει να προσθέσουμε κάποια πράγματα στην παραμετροποίηση του Apache για να εκτελέσουμε το git-http-backend ως τον handler για οτιδήποτε μπαίνει στη διαδρομή /git του web server μας. SetEnv GIT_PROJECT_ROOT /srv/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/lib/git-core/git-http-backend/ Εάν παραλείψουμε τη μεταβλητή περιβάλλοντος (environment variable) GIT_HTTP_EXPORT_ALL , τότε το Git θα εξυπηρετεί σε μη-ταυτοποιημένους πελάτες μόνο τα αποθετήρια που περιέχουν το αρχείο git-daemon-export-ok , ακριβώς όπως έκανε και ο δαίμονας Git. Στη συνέχεια θα πρέπει να πούμε στο Apache να επιτρέψει αιτήματα στο git-http-backend και να ταυτοποιεί με κάποιον τρόπο τις εγγραφές με ένα μπλοκ Auth σαν αυτό: <Files "git-http-backend"> AuthType Basic AuthName "Git Access" AuthUserFile /srv/git/.htpasswd Require expr !(%{QUERY_STRING} -strmatch '*service=git-receive-pack*' || %{REQUEST_URI} =~ m#/git-receive-pack$#) Require valid-user </Files> Αυτό προϋποθέτει την ύπαρξη ενος αρχείου .htpasswd που περιέχει τους κωδικούς πρόσβασης όλων των έγκυρων χρηστών. Να ένα παράδειγμα προσθήκης του χρήστη “schacon” στο αρχείο : $ htpasswd -c /srv/git/.htpasswd schacon Υπάρχουν πάρα πολλοί τρόποι με τους οποίους μπορούμε να ζητήσουμε από τον Apache να ταυτοποιεί χρήστες, θα πρέπει να επιλέξουμε έναν και να τον υλοποιήσουμε. Αυτό είναι το απλούστερο παράδειγμα που μπορέσαμε να σκεφτούμε. Είναι σχεδόν βέβαιο ότι θα θέλήσουμε να το εγκαταστήσουμε πάνω από SSL, ώστε όλα αυτά τα δεδομένα να είναι κρυπτογραφημένα. Δεν θέλουμε να μπούμε πολύ βαθιά στις ρυθμίσεις του Apache, καθώς ενδεχομένως μπορεί να χρησιμοποιούμε διαφορετικό διακομιστή ή να έχουμε διαφορετικές ανάγκες ταυτοποίησης. Η βασική ιδέα είναι ότι το Git έρχεται με ένα CGI που ονομάζεται git-http-backend που όταν καλείται θα κάνει όλες τις διαπραγματεύσεις για αποστολή και λήψη δεδομένων μέσω HTTP. Δεν υλοποιεί το ίδιο την ταυτοποίηση, αλλά αυτό μπορεί εύκολα να ελεγχθεί στο επίπεδο του web server που τον καλεί. Μπορούμε να κάνουμε τα παραπάνω με σχεδόν οποιοδήποτε web server με δυνατότητα CGI, οπότε χρησιμοποιούμε αυτόν που γνωρίζουμε καλύτερα. Note Περισσότερες πληροφορίες σχετικά με την παραμετροποίηση της ταυτοποίησης στον Apache, υπάρχουν στην τεκμηρίωση του Apache εδώ: https://httpd.apache.org/docs/current/howto/auth.html . prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
http://www.trello.com/use-cases/resource-hub | Create a Resource Hub Your Team Will Actually Use | Trello Skip to main content Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Use case: Task management Track progress of tasks in one convenient place with a visual layout that adds ‘ta-da’ to your to-do’s. Use case: Resource hub Save hours when you give teams a well-designed hub to find information easily and quickly. Use case: Project management Keep projects organized, deadlines on track, and teammates aligned with Trello. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Back Navigation Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Read though our use cases to make the most of Trello on your team. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Helping teams work better, together Discover Trello use cases, productivity tips, best practices for team collaboration, and expert remote work advice. Check out the Trello blog Keep information organized and accessible with Trello Knowledge is power – but only if it’s accurate, accessible, and used correctly. Give teams a reliable hub from which to contribute, manage, and find relevant information quickly with Trello. Then, watch their productivity skyrocket! Try it free Ditch outdated spreadsheets and folders for something better Trello for knowledge and information management Collaborate with peace of mind. Trello provides a variety of permissions options and enterprise-grade security to make information easy to share when you want to and easy to gate when you don’t. Automate clean up Never wonder again whether the information you’re looking at is still relevant. Trello automates repeatable processes like setting due dates to update resources or archiving items past a certain date. Spot things faster with visual cues Preview YouTube videos, Miro files, Jira issues, and more in one place by simply pasting their URLs onto your Trello board. Use colorful labels or GIPHY stickers to quickly identify projects by goals and filter to view only cards associated with a specific label. Finding content has never been faster! Switch it up as often you need Toggle between views to see team vacation plans and projects laid out in Timeline, Calendar, Table views, and more to identify risks and resourcing gaps. Trello makes it easy to add, delete, and restructure your Trello resource hub as your team grows and needs change. Trello for Resource hubs Trello works with the tools you love Trello Power-Ups connect your favorite apps directly to Trello for a single source of truth with zero additional effort. Want more niche features in Trello? You can add those, too. With our gallery of 200+ Power-Ups , building a bespoke resource hub is effortless. See more Trello Power-Ups Slack Communication & collaboration Attach Slack conversations to Trello cards or automatically send Trello updates to Slack channels and direct messages. Google Drive File management Browse Google Drive from within Trello to quickly attach relevant files to corresponding Trello cards. Confluence Communication & collaboration Create new Confluence pages or add existing pages to Trello cards for knowledge documentation. Jira Developer tools Connect Jira and Trello to help all your teams work better together. Microsoft Teams Communication & collaboration Receive Trello notifications or view and interact with Trello boards within Microsoft Teams. Miro Product & design Embed and access Miro boards from within Trello. Changes made in one tool are reflected in the other. There’s a template for that Why start from scratch when there’s expertise you can trust? Trello templates get you going quickly with pre-built Trello boards that you can customize for your needs. You’ll also find Trello templates for everything from Team Management to Personal Productivity . Team Organization Central From team birthdays to the company vacation policy, use this Trello board to store essential team resources, schedules, project summaries, updates, and more. Marketing Content Catalog Centralize all the content your team creates so that it’s easily searchable – and usable. Join a community of millions of users globally who are using Trello to get more done. Join a community of millions of users globally who are using Trello to get more done. Teamwork and information management tips from the pros Read the Trello blog to learn ways you can improve team health, productivity, and collaboration. Why your enterprise needs an internal knowledge base Learn how to build an accurate, self-sustaining knowledge base for your company. 5 powerful automation tricks with Trello Custom Fields Employees waste three hours a day on tasks that can be automated – let’s fix that. How to build an adaptable employee manual with Trello Easy ways to build an effective company handbook that employees will actually use. Using Trello and Confluence to streamline business processes Learn what inefficiencies are screwing up your processes and how to fix them. Log In About Trello What’s behind the boards. Jobs Learn about open roles on the Trello team. Apps Download the Trello App for your Desktop or Mobile devices. Contact us Need anything? Get in touch and we can help. Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Privacy Policy Terms Copyright © 2024 Atlassian | 2026-01-13T09:29:20 |
https://git-scm.com/book/id/v2/Git-di-Server-Git-Daemon | Git - Git Daemon About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Memulai 1.1 Tentang Version Control 1.2 Sejarah Singkat Git 1.3 Dasar-dasar Git 1.4 Command Line 1.5 Memasang Git 1.6 Pengaturan Awal Git 1.7 Mendapatkan Bantuan 1.8 Kesimpulan 2. Git Basics 2.1 Mendapatkan Repository Git 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Alias Git 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git di Server 4.1 Protokol 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Ringkasan 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pengaturan dan Konfigurasi Akun 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Mengelola Organization 6.5 Scripting GitHub 6.6 Ringkasan 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Kostumisasi Git 8.1 Konfigurasi Git 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Ringkasan 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.5 Git di Server - Git Daemon Git Daemon Next we’ll set up a daemon serving repositories over the “Git” protocol. This is common choice for fast, unauthenticated access to your Git data. Remember that since it’s not an authenticated service, anything you serve over this protocol is public within it’s network. If you’re running this on a server outside your firewall, it should only be used for projects that are publicly visible to the world. If the server you’re running it on is inside your firewall, you might use it for projects that a large number of people or computers (continuous integration or build servers) have read-only access to, when you don’t want to have to add an SSH key for each. In any case, the Git protocol is relatively easy to set up. Basically, you need to run this command in a daemonized manner: git daemon --reuseaddr --base-path=/opt/git/ /opt/git/ --reuseaddr allows the server to restart without waiting for old connections to time out, the --base-path option allows people to clone projects without specifying the entire path, and the path at the end tells the Git daemon where to look for repositories to export. If you’re running a firewall, you’ll also need to punch a hole in it at port 9418 on the box you’re setting this up on. You can daemonize this process a number of ways, depending on the operating system you’re running. On an Ubuntu machine, you can use an Upstart script. So, in the following file /etc/event.d/local-git-daemon you put this script: start on startup stop on shutdown exec /usr/bin/git daemon \ --user=git --group=git \ --reuseaddr \ --base-path=/opt/git/ \ /opt/git/ respawn For security reasons, it is strongly encouraged to have this daemon run as a user with read-only permissions to the repositories – you can easily do this by creating a new user git-ro and running the daemon as them. For the sake of simplicity we’ll simply run it as the same git user that Gitosis is running as. When you restart your machine, your Git daemon will start automatically and respawn if it goes down. To get it running without having to reboot, you can run this: initctl start local-git-daemon On other systems, you may want to use xinetd , a script in your sysvinit system, or something else – as long as you get that command daemonized and watched somehow. Next, you have to tell Git which repositories to allow unauthenticated Git server-based access to. You can do this in each repository by creating a file name git-daemon-export-ok . $ cd /path/to/project.git $ touch git-daemon-export-ok The presence of that file tells Git that it’s OK to serve this project without authentication. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://sre.google/ | Google SRE - Site Reliability engineering Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content What is Site Reliability Engineering (SRE)? SRE is what you get when you treat operations as if it’s a software problem. Our mission is to protect, provide for, and progress the software and systems behind all of Google’s public services — Google Search, Ads, Gmail, Android, YouTube, and App Engine, to name just a few — with an ever-watchful eye on their availability, latency, performance, and capacity. SRE Video Gallery Explore SRE topics in depth in our video gallery! Read more SRE Video Gallery Explore SRE topics in depth in our video gallery! Read more Museum of Borgmon Abstract Art Explore more of the beauty that emerges from chaos, in this biennial collection of images from our monitoring systems. Read more Museum of Borgmon Abstract Art Explore more of the beauty that emerges from chaos, in this biennial collection of images from our monitoring systems. Read more SRE Careers Hear from some of our most senior engineers about their role at Google. Read more SRE Careers Hear from some of our most senior engineers about their role at Google. Read more SRE Resources A curated list of Site Reliability and Production Engineering resources. Read more SRE Resources A curated list of Site Reliability and Production Engineering resources. Read more What is SRE? Since 2004, SRE has evolved to become the industry-leading practice for service reliability. Hear from key figures about the history of SRE and what’s next for the SRE community. Watch video What is SRE? Since 2004, SRE has evolved to become the industry-leading practice for service reliability. Hear from key figures about the history of SRE and what’s next for the SRE community. Watch video Product-Focused Reliability for SRE Learn about how a product-focused reliability model can effectively support the overall reliability of a product. Read more Product-Focused Reliability for SRE Learn about how a product-focused reliability model can effectively support the overall reliability of a product. Read more SRE Books Read our SRE books online: Building Secure & Reliable Systems, The SRE Workbook, and the original SRE book. Read online SRE Books Read our SRE books online: Building Secure & Reliable Systems, The SRE Workbook, and the original SRE book. Read online STPA (System Theoretic Process Analysis) at Google Google is using STPA to analyze pure software systems and discover the unknown unknowns. Read more STPA (System Theoretic Process Analysis) at Google Google is using STPA to analyze pure software systems and discover the unknown unknowns. Read more 1 2 3 4 5 6 7 8 What we do as SRE Our job is a combination not found elsewhere in the industry. Like traditional operations groups, we keep important, revenue-critical systems up and running despite hurricanes, bandwidth outages, and configuration errors. How we SRE at Google As SRE, we flip between the fine-grained detail of disk driver IO scheduling to the big picture of continental-level service capacity, across a range of systems and a user population measured in billions. Interested in joining SRE? Google strives to cultivate an inclusive workplace. We believe diversity of perspectives and ideas leads to better discussions, decisions, and outcomes for everyone. Explore SRE opportunities at Google Follow us About Google Google products Privacy Terms Help | 2026-01-13T09:29:20 |
https://sre.google/resources/practices-and-processes/sre-fundamentals-course/ | SRE Fundamentals online course with Google Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content SRE Fundamentals online course Master Site Reliability Engineering with SRE Fundamentals with Google! This course covers essential concepts and practical applications, including Service Level Objectives (SLOs). Learn to identify key metrics, build effective SLOs, and create alerts to maintain performance standards. Dive into Systems Design by developing systems from product specifications, assessing single points of failure, and understanding performance and capacity planning. Ideal for aspiring SREs and seasoned professionals, this course provides foundational knowledge for system reliability and operational excellence. Sign up with our partner, Uplimit. Follow us About Google Google products Privacy Terms Help | 2026-01-13T09:29:20 |
https://git-scm.com/book/fr/v2/Git-sur-le-serveur-D%c3%a9mon-Daemon-Git | Git - Démon (Daemon) Git About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Démarrage rapide 1.1 À propos de la gestion de version 1.2 Une rapide histoire de Git 1.3 Rudiments de Git 1.4 La ligne de commande 1.5 Installation de Git 1.6 Paramétrage à la première utilisation de Git 1.7 Obtenir de l’aide 1.8 Résumé 2. Les bases de Git 2.1 Démarrer un dépôt Git 2.2 Enregistrer des modifications dans le dépôt 2.3 Visualiser l’historique des validations 2.4 Annuler des actions 2.5 Travailler avec des dépôts distants 2.6 Étiquetage 2.7 Les alias Git 2.8 Résumé 3. Les branches avec Git 3.1 Les branches en bref 3.2 Branches et fusions : les bases 3.3 Gestion des branches 3.4 Travailler avec les branches 3.5 Branches de suivi à distance 3.6 Rebaser (Rebasing) 3.7 Résumé 4. Git sur le serveur 4.1 Protocoles 4.2 Installation de Git sur un serveur 4.3 Génération des clés publiques SSH 4.4 Mise en place du serveur 4.5 Démon (Daemon) Git 4.6 HTTP intelligent 4.7 GitWeb 4.8 GitLab 4.9 Git hébergé 4.10 Résumé 5. Git distribué 5.1 Développements distribués 5.2 Contribution à un projet 5.3 Maintenance d’un projet 5.4 Résumé 6. GitHub 6.1 Configuration et paramétrage d’un compte 6.2 Contribution à un projet 6.3 Maintenance d’un projet 6.4 Gestion d’un regroupement 6.5 Écriture de scripts pour GitHub 6.6 Résumé 7. Utilitaires Git 7.1 Sélection des versions 7.2 Indexation interactive 7.3 Remisage et nettoyage 7.4 Signer votre travail 7.5 Recherche 7.6 Réécrire l’historique 7.7 Reset démystifié 7.8 Fusion avancée 7.9 Rerere 7.10 Déboguer avec Git 7.11 Sous-modules 7.12 Empaquetage (bundling) 7.13 Replace 7.14 Stockage des identifiants 7.15 Résumé 8. Personnalisation de Git 8.1 Configuration de Git 8.2 Attributs Git 8.3 Crochets Git 8.4 Exemple de politique gérée par Git 8.5 Résumé 9. Git et les autres systèmes 9.1 Git comme client 9.2 Migration vers Git 9.3 Résumé 10. Les tripes de Git 10.1 Plomberie et porcelaine 10.2 Les objets de Git 10.3 Références Git 10.4 Fichiers groupés 10.5 La refspec 10.6 Les protocoles de transfert 10.7 Maintenance et récupération de données 10.8 Les variables d’environnement 10.9 Résumé A1. Annexe A: Git dans d’autres environnements A1.1 Interfaces graphiques A1.2 Git dans Visual Studio A1.3 Git dans Visual Studio Code A1.4 Git dans IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git dans Sublime Text A1.6 Git dans Bash A1.7 Git dans Zsh A1.8 Git dans PowerShell A1.9 Résumé A2. Annexe B: Embarquer Git dans vos applications A2.1 Git en ligne de commande A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Commandes Git A3.1 Installation et configuration A3.2 Obtention et création des projets A3.3 Capture d’instantané basique A3.4 Création de branches et fusion A3.5 Partage et mise à jour de projets A3.6 Inspection et comparaison A3.7 Débogage A3.8 Patchs A3.9 Courriel A3.10 Systèmes externes A3.11 Administration A3.12 Commandes de plomberie 2nd Edition 4.5 Git sur le serveur - Démon (Daemon) Git Démon ( Daemon ) Git Dans la suite, nous allons configurer un daemon qui servira des dépôts sur le protocole « Git ». C’est un choix répandu pour permettre un accès rapide sans authentification à vos données Git. Souvenez-vous que du fait de l’absence d’authentification, tout ce qui est servi sur ce protocole est public au sein de son réseau. Mis en place sur un serveur à l’extérieur de votre pare-feu, il ne devrait être utilisé que pour des projets qui sont destinés à être visibles publiquement par le monde entier. Si le serveur est derrière le pare-feu, il peut être utilisé pour des projets avec accès en lecture seule pour un grand nombre d’utilisateurs ou des ordinateurs (intégration continue ou serveur de compilation) pour lesquels vous ne souhaitez pas avoir à gérer des clés SSH. En tout cas, le protocole Git est relativement facile à mettre en place. Grossièrement, il suffit de lancer la commande suivante en tant que daemon : git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ --reuseaddr autorise le serveur à redémarrer sans devoir attendre que les anciennes connexions expirent, l’option --base-path autorise les utilisateurs à cloner des projets sans devoir spécifier le chemin complet, et le chemin en fin de ligne indique au daemon Git l’endroit où chercher des dépôts à exporter. Si vous utilisez un pare-feu, il sera nécessaire de rediriger le port 9418 sur la machine hébergeant le serveur. Transformer ce processus en daemon peut s’effectuer de différentes manières qui dépendent du système d’exploitation sur lequel il est lancé. Puisque systemd est le système d’init le plus habituel sur les distributions Linux modernes, vous pouvez l’utiliser pour cela. Placez simplement un fichier /etc/systemd/system/git-daemon.service avec le contenu suivant : [Unit] Description=Start Git Daemon [Service] ExecStart=/usr/bin/git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Restart=always RestartSec=500ms StandardOutput=syslog StandardError=syslog SyslogIdentifier=git-daemon User=git Group=git [Install] WantedBy=multi-user.target Vous aurez noté que ce daemon Git est lancé ici avec comme utilisateur et groupe git . Modifiez-le pour correspondre à vos besoins et assurez-vous que l’utilisateur fourni existe sur le système. Vérifiez aussi que le binaire Git est bien à l’emplacement /usr/bin/git ou changer le chemin si nécessaire. Enfin, lancez systemctl enable git-daemon pour démarrer automatiquement le service au démarrage ; vous pouvez démarrer et arrêter le service avec respectivement systemctl start git-daemon et systemctl stop git-daemon . Sur d’autres systèmes, le choix reste large, allant de xinetd à un script de système sysvinit ou à tout autre moyen — tant que le programme est démonisé et surveillé. Ensuite, il faut spécifier à Git quels dépôts sont autorisés en accès non authentifié au moyen du serveur. Dans chaque dépôt concerné, il suffit de créer un fichier appelé git-daemon-export-ok . $ cd /chemin/au/projet.git $ touch git-daemon-export-ok La présence de ce fichier indique à Git que ce projet peut être servi sans authentification. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/ko/v2/Git-%ec%84%9c%eb%b2%84-Git-%eb%8d%b0%eb%aa%ac | Git - Git 데몬 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 시작하기 1.1 버전 관리란? 1.2 짧게 보는 Git의 역사 1.3 Git 기초 1.4 CLI 1.5 Git 설치 1.6 Git 최초 설정 1.7 도움말 보기 1.8 요약 2. Git의 기초 2.1 Git 저장소 만들기 2.2 수정하고 저장소에 저장하기 2.3 커밋 히스토리 조회하기 2.4 되돌리기 2.5 리모트 저장소 2.6 태그 2.7 Git Alias 2.8 요약 3. Git 브랜치 3.1 브랜치란 무엇인가 3.2 브랜치와 Merge 의 기초 3.3 브랜치 관리 3.4 브랜치 워크플로 3.5 리모트 브랜치 3.6 Rebase 하기 3.7 요약 4. Git 서버 4.1 프로토콜 4.2 서버에 Git 설치하기 4.3 SSH 공개키 만들기 4.4 서버 설정하기 4.5 Git 데몬 4.6 스마트 HTTP 4.7 GitWeb 4.8 GitLab 4.9 또 다른 선택지, 호스팅 4.10 요약 5. 분산 환경에서의 Git 5.1 분산 환경에서의 워크플로 5.2 프로젝트에 기여하기 5.3 프로젝트 관리하기 5.4 요약 6. GitHub 6.1 계정 만들고 설정하기 6.2 GitHub 프로젝트에 기여하기 6.3 GitHub 프로젝트 관리하기 6.4 Organization 관리하기 6.5 GitHub 스크립팅 6.6 요약 7. Git 도구 7.1 리비전 조회하기 7.2 대화형 명령 7.3 Stashing과 Cleaning 7.4 내 작업에 서명하기 7.5 검색 7.6 히스토리 단장하기 7.7 Reset 명확히 알고 가기 7.8 고급 Merge 7.9 Rerere 7.10 Git으로 버그 찾기 7.11 서브모듈 7.12 Bundle 7.13 Replace 7.14 Credential 저장소 7.15 요약 8. Git맞춤 8.1 Git 설정하기 8.2 Git Attributes 8.3 Git Hooks 8.4 정책 구현하기 8.5 요약 9. Git과 여타 버전 관리 시스템 9.1 Git: 범용 Client 9.2 Git으로 옮기기 9.3 요약 10. Git의 내부 10.1 Plumbing 명령과 Porcelain 명령 10.2 Git 개체 10.3 Git Refs 10.4 Packfile 10.5 Refspec 10.6 데이터 전송 프로토콜 10.7 운영 및 데이터 복구 10.8 환경변수 10.9 요약 A1. 부록 A: 다양한 환경에서 Git 사용하기 A1.1 GUI A1.2 Visual Studio A1.3 Eclipse A1.4 Bash A1.5 Zsh A1.6 Git in Powershell A1.7 요약 A2. 부록 B: 애플리케이션에 Git 넣기 A2.1 Git 명령어 A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. 부록 C: Git 명령어 A3.1 설치와 설정 A3.2 프로젝트 가져오기와 생성하기 A3.3 스냅샷 다루기 A3.4 Branch와 Merge A3.5 공유하고 업데이트하기 A3.6 보기와 비교 A3.7 Debugging A3.8 Patch 하기 A3.9 Email A3.10 다른 버전 관리 시스템 A3.11 관리 A3.12 Plumbing 명령어 2nd Edition 4.5 Git 서버 - Git 데몬 Git 데몬 여기선 “Git” 프로토콜로 동작하는 데몬 설정 방법을 알아본다. 이 방법은 인증 기능이 없는 Git 저장소를 만들 수 있는 가장 빠른 방법이다. 다시 한 번 강조하지만, 인증 기능이 없다. 전 세계 누구든지 데이터에 접근할 수 있다는 뜻이다. 만약 서버가 외부에 그냥 노출돼 있다면 우선 방화벽으로 보호하고 프로젝트를 외부에서 접근할 수 있게 만들어야 한다. 그리고 이미 서버를 방화벽으로 보호하고 있어도 사람이나 컴퓨터(CI 서버나 빌드 서버)가 읽기 접근을 할 수 있도록 SSH 키를 일일이 추가하고 싶지 않을 것이다. 어쨌든 Git 프로토콜은 상대적으로 설치하기 쉽다. 그냥 데몬을 실행하면 된다. $ git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ --reuseaddr 는 서버가 기존의 연결이 타임아웃될 때까지 기다리지 말고 바로 재시작하게 하는 옵션이다. --base-path 옵션을 사용하면 사람들이 프로젝트를 Clone 할 때 전체 경로를 사용하지 않아도 된다. 그리고 마지막에 있는 경로는 노출할 저장소의 위치를 Git 데몬에 알려주는 것이다. 마지막으로 방화벽을 사용하고 있으면 9418 포트를 열어서 지금 작업하는 서버의 숨통을 틔워주어야 한다. 운영체제에 따라 Git 데몬을 실행시키는 방법은 다르다. 대개의 리눅스 배포판은 systemd 를 가장 보편적으로 사용하며 이를 이용하는 방법이 가장 일반적이다. 아래의 내용으로 /etc/systemd/system/git-daemon.service 파일을 작성한다. [Unit] Description=Start Git Daemon [Service] ExecStart=/usr/bin/git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Restart=always RestartSec=500ms StandardOutput=syslog StandardError=syslog SyslogIdentifier=git-daemon User=git Group=git [Install] WantedBy=multi-user.target 여기서 주의해서 봐야 할 부분은 git 이라는 사용자와 그룹을 사용하여 Git 데몬이 실행된다는 점이다. 운영하는 환경에 따라 이 부분을 이미 존재하는 사용자나 그룹을 지정해서 사용할 수도 있다. 위의 예제에서는 Git 실행 파일의 위치가 /usr/bin/git 으로 설정되어 있으나 다른곳에 위치해있다면 변경해주어야 한다. 마지막으로 systemctl enable git-daemon 명령을 실행해서 시스템이 부팅될 때 자동으로 서비스가 시작되고, 시스템이 종료될 때 자동으로 서비스도 종료 되도록 설정한다. systemctl start git-daemon , systemctl stop git-daemon 두 명령으로도 설정할 수 있다. 우분투 LTS 14.04 까지는 Upstart 구성을 사용한다. 따라서 14.04 이하의 버전이라면 Upstart 스크립트를 사용한다. 우선 아래와 같이 파일을 만든다. /etc/init/local-git-daemon.conf 아래의 내용을 입력한다. start on startup stop on shutdown exec /usr/bin/git daemon \ --user=git --group=git \ --reuseaddr \ --base-path=/srv/git/ \ /srv/git/ respawn 보안을 위해서 저장소를 읽을 수만 있는 사용자로 데몬을 실행시킬 것을 강력하게 권고한다. git-ro 라는 계정을 새로 만들고 그 계정으로 데몬을 실행시키는 것이 좋다. 하지만 여기에서는 쉽게 설명하려고 git-shell 을 실행하는 동일한 사용자인 git 계정을 사용한다. 서버가 재시작할 때 Git 데몬이 자동으로 실행되고 데몬이 죽어도 자동으로 재시작될 것이다. 서버는 놔두고 Git 데몬만 재시작할 수 있다. $ initctl start local-git-daemon 다른 시스템에서는 sysvinit 시스템의 xinetd 스크립트를 사용하거나 자신만의 방법으로 해야 한다. 아무나 읽을 수 있다는 것을 Git 서버에 알려주어야 한다. 저장소에 git-daemon-export-ok 파일을 만들면 된다. $ cd /path/to/project.git $ touch git-daemon-export-ok 이 파일이 있으면 Git 데몬은 인증 없이 프로젝트를 노출하는 것으로 판단한다. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/gr/v2/%ce%a4%ce%bf-Git-%cf%83%cf%84%ce%bf%ce%bd-%ce%b4%ce%b9%ce%b1%ce%ba%ce%bf%ce%bc%ce%b9%cf%83%cf%84%ce%ae-%ce%94%ce%b1%ce%af%ce%bc%ce%bf%ce%bd%ce%b5%cf%82-%cf%84%ce%bf%cf%85-Git | Git - Δαίμονες του Git About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Ξεκινώντας με το Git 1.1 Σχετικά με τον έλεγχο εκδόσεων 1.2 Σύντομο ιστορικό του Git 1.3 Τι είναι το Git; 1.4 Η γραμμή εντολών 1.5 Εγκατάσταση του Git 1.6 Ρύθμιση του Git για πρώτη φορά 1.7 Χρησιμοποιώντας τη βοήθεια 1.8 Ανακεφαλαίωση 2. Τα θεμελιώδη στοιχεία του Git 2.1 Απόκτηση αποθετηρίου Git 2.2 Καταγραφή αλλαγών στο αποθετήριο 2.3 Χρησιμοποιώντας το ιστορικό υποβολών 2.4 Αναιρέσεις (undoing) 2.5 Δουλεύοντας με απομακρυσμένα αποθετήρια 2.6 Ετικέτες 2.7 Συντομεύεσεις στο Git 2.8 Ανακεφαλαίωση 3. Διακλαδώσεις στο Git 3.1 Οι κλάδοι με λίγα λόγια 3.2 Βασικές έννοιες διακλαδώσεων και συγχωνεύσεων 3.3 Διαχείριση κλάδων 3.4 Ροές εργασίας με διακλαδώσεις 3.5 Απομακρυσμένοι κλάδοι 3.6 Αλλαγή βάσης (rebasing) 3.7 Ανακεφαλαίωση 4. Το Git στον διακομιστή 4.1 Τα πρωτόκολλα 4.2 Εγκατάσταση του Git σε διακομιστή 4.3 Δημιουργία δημόσιου κλειδιού SSH 4.4 Στήσιμο του διακομιστή 4.5 Δαίμονες του Git 4.6 Έξυπνο HTTP 4.7 GitWeb 4.8 GitLab 4.9 Επιλογές φιλοξενίας από τρίτους 4.10 Ανακεφαλαίωση 5. Κατανεμημένο Git 5.1 Κατανεμημένες ροές εργασίας 5.2 Συνεισφέροντας σε ένα έργο 5.3 Συντήρηση ενός έργου 5.4 Ανακεφαλαίωση 6. GitHub 6.1 Δημιουργία λογαριασμού και ρύθμισή του 6.2 Συνεισφορά σε έργο 6.3 Συντήρηση ενός έργου 6.4 Διαχείριση οργανισμώνν 6.5 Συγγραφή script στο GitHub 6.6 Ανακεφαλαίωση 7. Εργαλεία του Git 7.1 Επιλογή αναθεώρησης 7.2 Διαδραστική εργασία με το στάδιο καταχώρισης 7.3 Αποθέματα και Καθαρισμός 7.4 Υπογραφή της δουλειάς μας 7.5 Αναζήτηση 7.6 Η ιστορία ξαναγράφεται 7.7 Απομυθοποίηση της reset 7.8 Προχωρημένη Συγχώνευση 7.9 Rerere 7.10 Αποσφαλμάτωση με το Git 7.11 Υπομονάδες 7.12 Δεμάτιασμα δεδομένων 7.13 Replace 7.14 Αποθήκευση διαπιστευτηρίων 7.15 Ανακεφαλαίωση 8. Εξατομίκευση του Git 8.1 Διαμόρφωση Git 8.2 Γνωρίσματα του Git 8.3 Τα άγκιστρα του Git 8.4 Ένα παράδειγμα επιβολής πολιτικής από το Git 8.5 Ανακεφαλαίωση 9. Το Git και άλλα συστήματα 9.1 Το Git ως πελάτης 9.2 Μετανάστευση στο Git 9.3 Ανακεφαλαίωση 10. Εσωτερική λειτουργία του Git 10.1 Διοχετεύσεις και πορσελάνες 10.2 Αντικείμενα του Git 10.3 Αναφορές του Git 10.4 Πακετάρισμα αρχείων 10.5 Τα refspec 10.6 Πρωτόκολλα μεταφοράς 10.7 Διατήρηση και ανάκτηση δεδομένων 10.8 Μεταβλητές περιβάλλοντος 10.9 Ανακεφαλαίωση A1. Appendix A: Το Git σε άλλα περιβάλλοντα A1.1 Γραφικές διεπαφές A1.2 Το Git στο Visual Studio A1.3 Git στο Visual Studio Code A1.4 Git στο IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git στο Sublime Text A1.6 Το Git στο Bash A1.7 Το Git στο Zsh A1.8 Το Git στο Powershell A1.9 Ανακεφαλαίωση A2. Appendix B: Ενσωμάτωση του Git στις εφαρμογές μας A2.1 Γραμμή εντολών Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Εντολές Git A3.1 Ρύθμιση και διαμόρφωση A3.2 Λήψη και δημιουργία έργων A3.3 Βασική λήψη στιγμιοτύπων A3.4 Διακλάδωση και συγχώνευση A3.5 Κοινή χρήση και ενημέρωση έργων A3.6 Επιθεώρηση και σύγκριση A3.7 Αποσφαλμάτωση A3.8 Επιθέματα A3.9 Ηλεκτρονικό ταχυδρομείο A3.10 Εξωτερικά Συστήματα A3.11 Διοίκηση A3.12 Εντολές διοχέτευσης 2nd Edition 4.5 Το Git στον διακομιστή - Δαίμονες του Git Δαίμονες του Git Στη συνέχεια θα εγκαταστήσουμε έναν δαίμονα που θα εξυπηρετεί αποθετήρια μέσω του πρωτοκόλλου “Git”. Αυτή είναι μια συνήθης επιλογή για γρήγορη και χωρίς ταυτοποίηση πρόσβαση στα δεδομένα μας στο Git. Θυμόμαστε πως δεδομένου ότι πρόκειται για μια υπηρεσία χωρίς ταυτοποίηση, οτιδήποτε παρέχεται πάνω από αυτό το πρωτόκολλο είναι δημόσιο εντός του δικτύου του. Εάν τρέχουμε τον δαίμονα σε έναν διακομιστή εκτός firewall, θα πρέπει να χρησιμοποιείται μόνο για έργα που είναι ορατά σε όλον τον κόσμο. Αν ο διακομιστής στον οποίο τον τρέχουμε είναι εντός firewall, μπορούμε να τον χρησιμοποιήσουμε για έργα στα οποία ένας μεγάλος αριθμός ανθρώπων ή υπολογιστών (continuous integration ή build servers) έχουν πρόσβαση μόνο για ανάγνωση, όταν δεν θέλουμε να προσθέσουμε κλειδί SSH για τον καθένα. Σε κάθε περίπτωση, το πρωτόκολλο Git είναι σχετικά εύκολο στη ρύθμισή του. Βασικά, θα πρέπει να εκτελέσουμε αυτή την εντολή με “δαιμονοποιημένο” τρόπο: $ git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Ο διακόπτης --reuseaddr επιτρέπει στον διακομιστή να επανεκκινήσει χωρίς να αναμένει αποσύνδεση των παλαιών συνδέσεων, ο διακόπτης --base-path επιτρέπει την κλωνοποίηση έργων χωρίς να καθορίζεται ολόκληρη η διαδρομή (path), και η διαδρομή (path) στο τέλος λέει στον δαίμονα Git πού να αναζητήσει αποθετήρια προς εξαγωγή. Εάν τρέχουμε ένα firewall, θα χρειαστεί επίσης να του ανοίξουμε μία τρύπα στη θύρα 9418 στο κουτί που τον εγκαθιστούμε στον διακομιστή. Μπορούμε να “δαιμονοποίησουμε” αυτή τη διαδικασία με διάφορους τρόπους, ανάλογα με το λειτουργικό σύστημα που εκτελούμε. Δεδομένου ότι systemd είναι το πιο συνηθισμένο σύστημα init στις μοντέρνες διανομές Linux, μπορούμε να χρησιμοποιήσουμε αυτό για τον σκοπό αυτό. Απλά βάλτε ένα αρχείο στο /etc/systemd/system/git-daemon.service με αυτά τα περιεχόμενα: [Unit] Description=Start Git Daemon [Service] ExecStart=/usr/bin/git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Restart=always RestartSec=500ms StandardOutput=syslog StandardError=syslog SyslogIdentifier=git-daemon User=git Group=git [Install] WantedBy=multi-user.target Αν προσέξουμε ο δαίμονας του Git daemon ξεκινά εδώ ως git τόσο για την ομάδα (group) όσο και για τον χρήστη (user). Το τροποποιούμε ώστε να το προσαρμόσουμε στις ανάγκες μας και σιγουρευόμαστε ότι ο χρήστης που δίνεται υπάρχει στο σύστημα. Επίσης, ελέγχουμε ότι το εκτελέσιμο αρχείο του Git βρίσκεται πράγματι στο /usr/bin/git αλλιώς αλλάζουμε τη διαδρομή (path) αναλόγως. Τέλος, θα εκτελέσουμε systemctl enable git-daemon ώστε η υπηρεσία να ξεκινά αυτόματα κατά την εκκίνηση του υπολογιστή και μπορούμε να εκκινήσούμε και να σταματήσουμε την υπηρεσία με systemctl start git-daemon και systemctl stop git-daemon αντίστοιχα. Σε άλλα συστήματα, ίσως θελήσουμε να χρησιμοποιήσουμε το xinetd , ένα script στο σύστημά μας sysvinit ή κάτι άλλο — με την προϋπόθεση ότι μπορούμε δαιμονοποιήσουμε αυτή την εντολή και να την παρακολουθούμε με κάποιον τρόπο. Στη συνέχεια, πρέπει να ενημερώσουμε το Git ποια αποθετήρια επιτρέπουν την πρόσβαση σε διακομιστές Git χωρίς ταυτοποίηση. Μπορούμε να το κάνουμε σε κάθε αποθετήριο δημιουργώντας ένα αρχείο που ονομάζεται git-daemon-export-ok . $ cd /path/to/project.git $ touch git-daemon-export-ok Η παρουσία αυτού του αρχείου λέει στο Git ότι επιτρέπεται να εξυπηρετήσει αυτό το έργο χωρίς ταυτοποίηση. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/freshworks-inc-freshservice?similarProducts=true&trk=products_details_guest_similar_products_section_sign_in | Freshservice | LinkedIn Skip to main content LinkedIn Freshworks in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Freshservice Service Desk Software by Freshworks See who's skilled in this Add as skill Get started Report this product About Freshservice is an intelligent, right-sized service management solution for modern businesses of all sizes. Freshservice does this by taking a fresh approach to building and delivering modern employee experiences and unified service management —empowering businesses to achieve efficiency, fast time-to-value, and improved employee satisfaction and productivity. This product is intended for Chief Information Officer Information Technology Manager Information Technology Asset Manager Change Manager Information Technology Operations Manager Chief Technology Officer Vice President Information Technology Head of Information Technology Media Products media viewer No more previous content Freshservice for ITSM Transform IT support into a single, easy-to-use service management solution. With AI-powered tools, automated ticketing, and simple setup, IT teams can finally get back to solving real problems. Freshservice for ITOM Safeguard your business from operational incidents. Track service health, eliminate noise with Freddy AI, automate escalation, & update customers and stakeholders – minus any tool hopping. Freshservice for ITAM Build a backbone for efficient service delivery with complete visibility into your on-premise and cloud infrastructure with IT Asset Management software. Freshservice for Business Teams IT, HR, Facilities, Legal - extending Freshservice across business teams eliminates the need for multiple tools, all while delivering your employees a consistent service environment. No more next content Featured customers of Freshservice EF Education 519,430 followers TaylorMade Golf Company Sporting Goods Manufacturing 172,325 followers HelloFresh Consumer Services 422,334 followers RingCentral Software Development 295,494 followers Chargebee Financial Services 520,368 followers INCAE Business School Higher Education 181,676 followers Payvision Financial Services 14,507 followers VICE Media Media Production 660,568 followers University of Aberdeen Higher Education 155,678 followers NHS Food and Beverage Services 712,120 followers Western Sussex Hospitals NHS Trust Hospitals and Health Care 2,739 followers Addison Lee Transportation, Logistics, Supply Chain and Storage 23,478 followers M+C Saatchi UK Advertising Services 84,163 followers Moneycorp Financial Services 25,699 followers PowerSchool E-Learning Providers 160,054 followers UNiDAYS Advertising Services 18,275 followers Radisson Hotel Group Hospitality 878,390 followers Swinerton Construction 133,048 followers Wake Forest University Higher Education 98,864 followers Trainline Technology, Information and Internet 55,507 followers Show more Show less Similar products Jira Service Management Jira Service Management Service Desk Software Intercom Intercom Service Desk Software Atomicwork Atomicwork Service Desk Software SolarWinds Service Desk SolarWinds Service Desk Service Desk Software Service Desk Service Desk Service Desk Software TOPdesk TOPdesk Service Desk Software Sign in to see more Show more Show less Freshworks products Freshchat Freshchat Live Chat Software Freshdesk Freshdesk Help Desk Software Freshdesk Omni Freshdesk Omni Help Desk Software Freshmarketer Freshmarketer Marketing Automation Software Freshsales Freshsales Customer Relationship Management (CRM) Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://sre.google/resources/practices-and-processes/measuring-reliability/ | Google SRE - SLOs ecosystem to measure reliability Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content Measuring Reliability What got you here won't get you there The SLOs ecosystem is just one tool we can use to measure reliability... This talk is about understanding when your tools apply for answering questions, and building new ones if you need them. Read more Watch video Scroll down to explore more Measuring Reliability ...what got you here won't get you there Štěpán Davidovič, Google for SREcon EMEA 2022, Oct 25th-27th What is "reliability"? It's a fuzzy concept! Lagging Indicator User's perception of how the system worked for them It has already impacted the business, cannot be changed It's user experience, and we should know about it "The system didn't work an hour every day of the last week, that sucks." Leading Indicator Risk property of the system as it stands Not yet realized, can be changed "The system is at 99% of disk usage. It works now, but it might break any minute!" Leading Indicator is important, but out of scope here This slide deck will focus on the ability to measure what has already happened, and draw conclusions from that. Measure reliability? "Define your SLIs/SLOs!" ...let's look at that more! The SLO Model Recap Service Level Indicator (SLI) Time series data which can tell us how good the level of service is. Often from logs or sampled counters. Examples: tuple: {HTTP 500s, all HTTP responses} ratio: responses under 200ms / all responses Service Level Objective (SLO) Predicate on a mathematical function applied on SLI. Has free parameters. Aim is to keep this predicate true. Mathematical example: Organizational example: "We hit/missed our SLO last quarter" Answering our reliability questions When we say " measure reliability ", we want our data to give us some insight. We are answering questions, by using our available data. But there is no single reliability question! An engineer oncall is in a different situation than a CEO strategizing. The purpose of computing is insight, not numbers. - Richard Hamming Our reliability questions? Some illustrative examples: Oncall engineer responds to and mitigates an incident. Did their action help? Team manager holds weekly production review team meetings, are there creeping problems? Customer support asks if a customer has problems? SVP wants to understand customer-perceived reliability of product portfolio before meeting with the customer. CEO wants to know if company's reliability is getting worse. Do we need to pivot? Illustration #1: Oncall Engineer Engineer got paged with the alert " SLI_Suddenly_Awful ". After an hour of debugging, engineer tried a mitigation. How do they know if it helped? If it were me: Wait for a while Look at whether the SLI has recovered to above SLO (or maybe even to previous levels) We built an intuitive, ad-hoc model to answer our question! Illustration #2: CEO wonders Comparing how many SLOs were met month to month CEO is wondering whether reliability of the company's product is getting worse, and new reliability work needs to be prioritized. How do they interpret the reliability data? Maybe they compare how many SLOs were met, month to month? Let's say we have 200 SLOs. Are we getting less reliable? Naive answer: Yes, because 12 (6.0% of total) SLOs not met is (a lot) more than 3 (1.5%) or 4 (2%). Better answer: We can't tell by interpreting this data this way. Illustrating using a binomial model: Let's say probability of not meeting SLO each month is 1/24 Then 95% confidence interval is from 3 to 13 SLOs not met, even if the average reliability doesn't change Naive idea was non-obviously dangerous. The more impactful (=costly) the decisions, the more important to check your methods! This illustration model is very flawed (SLOs typically not IID, etc.). It's only an illustration, prompting going beyond the naive answer. Illustration by Allyssa Jill Olivan SLI/SLO model got us here, but… We need more models. The examples show that SLO model alone isn't sufficient. In practice we build ad-hoc models in our heads, intuitive but sometimes dangerously wrong. The SLI/SLO model helped us make good progress in reliability! But what got us here won't get us there . The illustrations were strawman, but the problem is real. To figure our next steps, let's understand some of the limitations and assumptions of SLIs and SLOs . Illustration by Allyssa Jill Olivan Error Budgets Have Error Margins That's okay! But do you know what yours are? We establish our "error budget" based on acceptable losses 100% availability is fanciful Since we make 1M USD, we set a failure budget 10K USD We set our SLO to correspond to our error budget We make 1M USD/yr, so 10K implies 99% SLO We measure incident impact - but inaccuracy is a problem! Impact assessment may be inaccurate, e.g. order of magnitude! Estimate your inaccuracy: Ask three independent incident reviewers for impact estimate, and observe variance This is a problem even without any black swan events! SLO Model Assumes Linearity ...in time and space! Aggregating upwards hides bad behavior What if your product never works for a handful of users ? For SLI/SLO, it's the same as if it didn't work a little bit for all users! SLIs assume all requests are equal They can have different costs, user utility, or revenue Human-curated SLI grouping helps, e.g. group by API call or location Human-designed grouping is not always possible Example: Free-form SQL queries for a database, or arbitrary input video formats for video encoder SLO model aggregates over time 1000x 1-minute full outages is equal to... ...1x 1000-minute full-outage? ...2x 1000-minute half-outages? To your users and your business, this difference may matter Aggregation to global (or zonal) SLO can hide severe problems! Illustration by Allyssa Jill Olivan SLIs Aren't The Best Data ...they are the easiest data Practical SLIs are often limited to sources which have: High sample rate Low cost to sample (and interpret) Low sampling latency We should integrate other useful sources: Complaints on Twitter Crowdsourced outage reporting Direct customer feedback Valuable signals worth not ignoring! Could we integrate them into our day-to-day reliability management? Know Your Tools This talk isn't to say SLIs or SLOs are bad - or good. The SLOs ecosystem is only a tool. The only question for a tool is if it fits the need. You should understand your needs. They might be answering questions with data, or organizational design, or many more! This talk is about understanding when your tools apply for answering questions, and building new ones if you need them. Illustration by Allyssa Jill Olivan Operationalization " ...defines a fuzzy concept so as to make it clearly distinguishable, measurable , and understandable by empirical observation... " ( Wikipedia , May 2022) Reliability Measurement Models ...operationalization using three "simple" steps Identify your key reliability questions Some are generic (e.g. need to alert), many aren't Be precise, and think of cost of consequent action Build a model for each question This is creative, and hard work Consider how hard it is to agree on a model to answer the question "given this data, should we alert someone?" ML techniques are tempting, but beware their caveats Backtest your models against historical data For boolean questions, you can get a confusion matrix Identify model shortcomings, and iterate Good news: We're doing it already! "SLO alerting" is an example of building a fresh model Input is SLI data, output is a boolean answer Frequent topic of articles and discussions Alerting decision is made frequently Models for identifying unusual behaviors, such as: Anomaly detection in monitoring solutions SRECon'21 talk "Beyond Goldilocks Reliability" But beware: "unusual" is not automatically "bad"! Cost of being wrong drives accuracy requirements However, models for high-level decision are hard Typically very infrequent decisions Not always clear what should've been done, even in hindsight Illustration by Allyssa Jill Olivan Conclusion What got you here won't get you there! SLI/SLO model is a helpful hammer, but not everything is a nail Understand what questions you need answered! Match your tool to that, don't start with a tool Build models, and backtest them (...and publish them?) Start with just three reliability questions Backtesting is sometimes hard, "what should we have done?" not always accurate or available Think of the cost of the answer being wrong, be ready Include new or external data in your reliability day-to-day practice Complaints on Twitter as a regularly measured quantity? :-) Ideally: used as input to your regularly exercised models See also: Incident metrics in SRE (O'Reilly, 2021) The VOID Report (Verica, 2024) ML for Operations (USENIX ;login:, 2020) How to measure Anything (Wiley, 2020) Thanks to : Ben Appleton, Kristina Bennett, Brent Bryan, Brendan Gleason, Paul Holden, Jennifer Mace, Jake McGuire, Niall Richard Murphy, Courtney Nash, Alex Rodriguez, Dylan Vener, Salim Virji For their review and thoughts on this (or preceding) material Illustrations by : Allyssa Jill Olivan (@kleinebean) allyssajillolivan.myportfolio.com See also: Incident metrics in SRE (O'Reilly, 2021) The VOID Report (Verica, 2024) ML for Operations (USENIX ;login:, 2020) How to measure Anything (Wiley, 2020) Illustrations by : Allyssa Jill Olivan (@kleinebean) allyssajillolivan.myportfolio.com 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 / Follow us About Google Google products Privacy Terms Help | 2026-01-13T09:29:20 |
https://sre.google/resources/practices-and-processes/stpa/ | STPA (System Theoretic Process Analysis) at Google Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content STPA (System Theoretic Process Analysis) at Google Google's SRE team pioneered methods to keep failures rare by engineering reliability into every part of the stack—Service Level Objectives (SLOs), error budgets, isolation strategies, thorough postmortems, progressive rollouts, and other techniques. In the face of increasing system complexity and emerging challenges: what's next? How can we continue to push the boundaries of reliability and safety? To address these challenges, Google is using System Theoretic Process Analysis (STPA) to analyze pure software systems and discover the unknown unknowns: risks of which you are unaware and not actively seeking. Learn more about how we're using STPA in the following resources. Mapping a Better Future with STPA talk from SREcon Americas 2025 Learn more STPA for Software Systems -- Illuminate the Unknown Unknowns SREcon EMEA 2025 Learn more The Evolution of SRE at Google by Tim Falzone and Ben Treynor Sloss STPA - Teaching a new way to prevent outages at Google by Garrett Holthaus Listen to the Prodcast: The One With STPA and Jeffrey and Theo Follow us About Google Google products Privacy Terms Help | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/teamviewer-frontline/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_image-click | TeamViewer Frontline | LinkedIn Skip to main content LinkedIn TeamViewer in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in TeamViewer Frontline Workflow Management Software by TeamViewer See who's skilled in this Add as skill Request demo Report this product About Empower your Frontline Workforce with Augmented Reality! Digitalize and streamline processes for frontline employees in desk-free workspaces with AR-guided workflows – seamlessly integrated with wearables and mobile devices. With TeamViewer Frontline you can increase your company’s productivity, efficiency, and quality along the entire value chain. This product is intended for Supply Chain Manager Director of Logistics Vice President Logistics Chief Supply Chain Officer Manufacturing Executive Director Installation Director of Maintenance Director of Field Operations Director Technical Training Operations Manager Media Products media viewer No more previous content TeamViewer Frontline – Empowering Frontline Workers 80 percent of today’s workers globally are working deskless jobs. Frontline workers are often overlooked when companies focus on digitization. TeamViewer Frontline is here to change this. As the world’s first and fully integrated augmented reality (AR) platform for mobile workers, Frontline from TeamViewer enables a truly digitalized industrial workplace, simplifying processes, minimizing error rates, ensuring high-quality output, and increasing productivity along your entire value chain. TeamViewer Frontline xPick & Samsung SDS – How vision picking transforms warehouse operations Easy and hands-free: Step-by-step instructions with xInspec Discover our augmented reality solution xInspect for inspection and maintenance. It provides hands-free and visual instuctions, on-site documentation and instant connection to expert support at any time. The container inspection use case shown here originates from the research project PortForward, which we actively contribute to. Together with our partners we are researching to make the future of European ports more smart, environmentally friendly and interconnected.. Lewis Hamilton trying out augmented reality software by TeamViewer Lewis Hamilton, 7 times Formula 1 world champion, using TeamViewer’s Frontline AR solution to look at his past season’s car in a totally new way! Beyond the racetrack, Frontline improves manual work processes across industries on the basis of the latest wearable computing technologies. How TeamViewer Frontline Supports Deyaar FM's Facility Management Operations Thanks to TeamViewer's Augmented Reality-based solution, TeamViewer Frontline xAssist, Deyaar Facilities Management can remotely support its customers quickly and effectively while avoiding unnecessary travel and reducing its carbon footprint. With the use of smart glasses, its remote expert sees exactly what the on-site technician sees and can provide technical expertise. Find more information about our latest case study here: https://www.teamviewer.com/en-us/success-stories/deyaar-fm/ No more next content Featured customers of TeamViewer Frontline DB Schenker Transportation, Logistics, Supply Chain and Storage 1,063,239 followers AUDI AG Motor Vehicle Manufacturing 2,271,748 followers GlobalFoundries Semiconductor Manufacturing 290,958 followers DHL Supply Chain Transportation, Logistics, Supply Chain and Storage 2,154,574 followers Boehringer Ingelheim Pharmaceutical Manufacturing 2,159,518 followers Samsung SDS IT Services and IT Consulting 203,738 followers BMW Group Motor Vehicle Manufacturing 3,535,364 followers Intel Corporation Semiconductor Manufacturing 4,100,344 followers Ford Motor Company Motor Vehicle Manufacturing 4,288,347 followers Coca-Cola HBC Food and Beverage Services 677,887 followers SIG Group Packaging and Containers Manufacturing 248,926 followers Airbus Aviation and Aerospace Component Manufacturing 2,754,147 followers Lexus Motor Vehicle Manufacturing 137,581 followers AGCO Corporation Machinery Manufacturing 448,087 followers Liebherr Group Industrial Machinery Manufacturing 468,297 followers KEMPER GmbH Industrial Machinery Manufacturing 8,794 followers NSF Public Safety 257,168 followers Toyota Deutschland GmbH Automotive 9,431 followers Show more Show less Similar products n8n n8n Workflow Management Software Automation Engine Automation Engine Workflow Management Software Pipefy Pipefy Workflow Management Software Jotform Workflows Jotform Workflows Workflow Management Software Value Stream Management Value Stream Management Workflow Management Software ApprovalMax ApprovalMax Workflow Management Software Sign in to see more Show more Show less TeamViewer products TeamViewer Remote TeamViewer Remote Remote Desktop Software TeamViewer Tensor TeamViewer Tensor Enterprise Cloud Platforms LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://git-scm.com/book/tr/v2/Bir-Sunucuda-Git-Kurma-Git-Cini-Daemon | Git - Git Cini (Daemon) About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Başlangıç 1.1 Sürüm Denetimi 1.2 Git’in Kısa Tarihçesi 1.3 Git Nedir? 1.4 Komut Satırı 1.5 Git’i Yüklemek 1.6 Git’i İlk Defa Kurmak 1.7 Yardım Almak 1.8 Özet 2. Git Temelleri 2.1 Bir Git Reposu Oluşturma/Kopyalama 2.2 Değişikliklerin Repoya Kaydedilmesi 2.3 Katkı Geçmişini Görüntüleme 2.4 Değişiklikleri Geri Alma 2.5 Uzak Repo ile Çalışmak 2.6 Etiketleme 2.7 Komut Kısayolu (Alias) Ayarlama 2.8 Özet 3. Git Dalları 3.1 Dallar 3.2 Kısaca Dallandırma ve Birleştirme Temelleri 3.3 Dal Yönetimi 3.4 İş Akışı Dallandırması 3.5 Uzak Dallar 3.6 Yeniden Temelleme (rebase) 3.7 Özet 4. Bir Sunucuda Git Kurma 4.1 İletişim Kuralları (Protocols) 4.2 Bir Sunucuda Git Kurma 4.3 SSH Ortak Anahtarınızı Oluşturma 4.4 Sunucu Kurma 4.5 Git Cini (Daemon) 4.6 Akıllı HTTP 4.7 GitWeb 4.8 GitLab 4.9 Üçüncü Taraf Barındırma (Hosting) Seçenekleri 4.10 Özet 5. Dağıtık Git 5.1 Dağıtık İş Akışları 5.2 Projenin Gelişiminde Rol Almak 5.3 Bir Projeyi Yürütme 5.4 Özet 6. GitHub 6.1 Bir Projeye Katkıda Bulunmak 6.2 Proje Bakımı 6.3 Kurumsal Yönetim 6.4 GitHub’ı otomatikleştirme 6.5 Özet 7. Git Araçları 7.1 Düzeltme Seçimi 7.2 Etkileşimli İzlemleme (Staging) 7.3 Saklama ve Silme 7.4 Çalışmanızı İmzalama 7.5 Arama 7.6 Geçmişi Yeniden Yazma 7.7 Reset Komutunun Gizemleri 7.8 İleri Seviye Birleştirme 7.9 Rerere 7.10 Git’le Hata Ayıklama 7.11 Alt Modüller 7.12 Demetleme (Bundling) 7.13 Git Nesnesini Değiştirme 7.14 Kimlik Bilgisi Depolama 7.15 Özet 8. Git’i Özelleştirmek 8.1 Git Yapılandırması 8.2 Git Nitelikleri 8.3 Git Kancaları (Hooks) 8.4 Bir Örnek: Mecburi Git Politikası 8.5 Özet 9. Git ve Diğer Sistemler 9.1 İstemci Olarak Git 9.2 Git’e Geçiş 9.3 Özet 10. Dahili Git Ögeleri 10.1 Tesisat ve Döşeme (Plumbing ve Porcelain) 10.2 Git Nesneleri 10.3 Git Referansları 10.4 Packfiles 10.5 Refspec 10.6 Transfer Protokolleri 10.7 Bakım ve Veri Kurtarma 10.8 Ortam Değişkenleri 10.9 Özet A1. Ek bölüm A: Diğer Ortamlarda Git A1.1 Görsel Arayüzler A1.2 Visual Studio ile Git A1.3 Visual Studio Code ile Git A1.4 Eclipse ile Git A1.5 Sublime Text ile Git A1.6 Bash ile Git A1.7 Zsh ile Git A1.8 PowerShell ile Git A1.9 Özet A2. Ek bölüm B: Git’i Uygulamalarınıza Gömmek A2.1 Git Komut Satırı A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Ek bölüm C: Git Komutları A3.1 Kurulum ve Yapılandırma Komutları A3.2 Proje Oluşturma Komutları A3.3 Kısaca Poz (Snapshot) Alma A3.4 Dallandırma ve Birleştirme Komutları A3.5 Projeleri Paylaşma ve Güncelleme Komutları A3.6 İnceleme ve Karşılaştırma Komutları A3.7 Hata Ayıklama (Debugging) Komutları A3.8 Yamalama (Patching) A3.9 E-Posta Komutları A3.10 Harici Sistemler A3.11 Yönetim A3.12 Tesisat (Plumbing) Komutları 2nd Edition 4.5 Bir Sunucuda Git Kurma - Git Cini (Daemon) Git Cini (Daemon) Şimdi, repoları "Git" protokolünü kullanarak sunan bir daemon kuracağız. Bu, Git verilerinize hızlı, kimlik doğrulamasız erişim için yaygın bir seçenektir. Unutmayın ki bu kimlik doğrulamasız bir servis olduğundan, bu protokol üzerinden sunduğunuz her şey, ağ içindeki herkese açık olacaktır. Eğer bunu güvenlik duvarınızın dışında bir sunucuda çalıştırıyorsanız, yalnızca dünya genelinde herkese açık olan projeler için kullanılmalıdır. Eğer çalıştırdığınız sunucu güvenlik duvarınızın içindeyse, birçok insanın veya bilgisayarın (sürekli entegrasyon veya derleme sunucuları gibi) salt okuma erişimine sahip olduğu projeler için kullanabilirsiniz. Böylece her biri için bir SSH anahtarı eklemek zorunda kalmazsınız. Her durumda, Git protokolü kurulumu nispeten kolaydır. Temel olarak, bu komutu daemon olarak çalıştırmanız gerekmektedir: $ git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ --reuseaddr seçeneği, sunucunun eski bağlantıların zaman aşımını beklemeksizin yeniden başlamasına olanak tanırken, --base-path seçeneği, insanların projeleri tüm yolunu belirtmeden kopyalamasına izin verir. Dizin ise, Git daemon’a dışa aktarılacak repoları nerede bulacağını söyler. Eğer bir güvenlik duvarı kullanıyorsanız, bunu kurduğunuz kutunun 9418 numaralı portunda bir delik açmanız da gerekecektir. Bu işlemi, çalıştırdığınız işletim sistemine bağlı olarak birkaç farklı şekilde demonize edebilirsiniz. systemd modern Linux dağılımları arasında en yaygın init sistemi olduğu için bunu kullanabilirsiniz. Sadece /etc/systemd/system/git-daemon.service dizinine aşağıdaki içeriğe sahip bir dosya yerleştirin: [Unit] Description=Start Git Daemon [Service] ExecStart=/usr/bin/git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Restart=always RestartSec=500ms StandardOutput=syslog StandardError=syslog SyslogIdentifier=git-daemon User=git Group=git [Install] WantedBy=multi-user.target Git daemon’un burada hem grup hem de kullanıcı olarak git ile başlatıldığını farketmiş olabilirsiniz. Bunu kendi ihtiyaçlarınıza uyacak şekilde değiştirin ve sağlanan kullanıcının sistemde var olduğundan emin olun. Ayrıca, Git binary’sinin gerçekten /usr/bin/git dizininde olduğunu kontrol edin ve gerekirse dizini değiştirin. Son olarak, systemctl enable git-daemon komutunu çalıştırarak servisin otomatik olarak başlamasını sağlayabilir, systemctl start git-daemon komutu ile servisi başlatabilir veya systemctl stop git-daemon komutu ile durdurabilirsiniz. Diğer sistemlerde, xinetd ( sysvinit sisteminizde bir betik) veya başka bir şey kullanmak isteyebilirsiniz. Yeter ki o komutu bir şekilde demonize edip izleyin. Sonraki adım olarak, Git’e hangi repoların kimlik doğrulamasız Git sunucu tabanlı erişimine izin vereceğini belirtmelisiniz. git-daemon-export-ok adında bir dosya oluşturarak, her repoda bunu yapabilirsiniz. $ cd /path/to/project.git $ touch git-daemon-export-ok Bu dosyanın varlığı, Git’e bu projenin kimlik doğrulamasız hizmet vermesinin uygun olduğunu söyler. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/uz/v2/Git-%d1%81%d0%b5%d1%80%d0%b2%d0%b5%d1%80%d0%b4%d0%b0-Git-Daemon | Git - Git Daemon About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Иш бошланиши 1.1 Талқинларни бошқариш ҳақида 1.2 Git нинг қисқача тарихи 1.3 Git асоси 1.4 Командалар сатри 1.5 Git ни ўрнатиш 1.6 Git да биринчи созлашлар 1.7 Қандай ёрдам олиш мумкин? 1.8 Хулосалар 2. Git асослари 2.1 Git омборини яратиш 2.2 Ўзгаришларни омборга ёзиш 2.3 Фиксирлашлар тарихини кўриш 2.4 Ўзгаришларни бекор қилиш 2.5 Узоқ масофадаги омборлар билан ишлаш 2.6 Тамғалаш 2.7 Git да таҳаллуслар 2.8 Хулоса 3. Git да тармоқланиш 3.1 Тармоқланиш ҳақида икки оғиз сўз 3.2 Тармоқланиш ва бирлашиш асослари 3.3 Тармоқларни бошқариш 3.4 Иш жараёнларини тармоқлаш 3.5 Узоқ масофадаги тармоқлар 3.6 Қайта асосланиш 3.7 Хулосалар 4. Git серверда 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Sizning SSH ochiq (public) kalitingizni generatsiyalash 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Хулосалар 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Qism modullar (Submodule) 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.5 Git серверда - Git Daemon Git Daemon Next we’ll set up a daemon serving repositories over the “Git” protocol. This is common choice for fast, unauthenticated access to your Git data. Remember that since it’s not an authenticated service, anything you serve over this protocol is public within its network. If you’re running this on a server outside your firewall, it should only be used for projects that are publicly visible to the world. If the server you’re running it on is inside your firewall, you might use it for projects that a large number of people or computers (continuous integration or build servers) have read-only access to, when you don’t want to have to add an SSH key for each. In any case, the Git protocol is relatively easy to set up. Basically, you need to run this command in a daemonized manner: git daemon --reuseaddr --base-path=/opt/git/ /opt/git/ --reuseaddr allows the server to restart without waiting for old connections to time out, the --base-path option allows people to clone projects without specifying the entire path, and the path at the end tells the Git daemon where to look for repositories to export. If you’re running a firewall, you’ll also need to punch a hole in it at port 9418 on the box you’re setting this up on. You can daemonize this process a number of ways, depending on the operating system you’re running. On an Ubuntu machine, you can use an Upstart script. So, in the following file /etc/event.d/local-git-daemon you put this script: start on startup stop on shutdown exec /usr/bin/git daemon \ --user=git --group=git \ --reuseaddr \ --base-path=/opt/git/ \ /opt/git/ respawn For security reasons, it is strongly encouraged to have this daemon run as a user with read-only permissions to the repositories – you can easily do this by creating a new user git-ro and running the daemon as them. For the sake of simplicity we’ll simply run it as the same git user that git-shell is running as. When you restart your machine, your Git daemon will start automatically and respawn if it goes down. To get it running without having to reboot, you can run this: initctl start local-git-daemon On other systems, you may want to use xinetd , a script in your sysvinit system, or something else – as long as you get that command daemonized and watched somehow. Next, you have to tell Git which repositories to allow unauthenticated Git server-based access to. You can do this in each repository by creating a file name git-daemon-export-ok . $ cd /path/to/project.git $ touch git-daemon-export-ok The presence of that file tells Git that it’s OK to serve this project without authentication. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://sre.google/cloud/ | Google SRE - SRE in cloud, leveraging cloud technology Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content SRE in the Cloud Learn how to put SRE principles into practice by leveraging cloud technology. Implement SRE in your organization through tooling, hands-on tutorials, videos, blogs, and other resources. Simplify your SRE journey with cloud native tooling Balance development velocity and reliability Manage reliability and drive alignment between developers and operators with baked-in SRE best practices. Create Service-Level Indicators (SLI), set Service-Level Objectives (SLO), and track errors easily with Service Monitoring . Out-of-the-box metric dashboards are available to help you quickly view and analyze service health. Reduce toil through built-in integrations One integrated view across metrics, uptime monitoring, dashboards, and alerts helps with faster resolution and in context observability. You also get access to metrics, traces, and logs with zero setup. Connect to tools you love like PagerDuty to troubleshoot incidents quickly across hybrid and multicloud environments. Near real-time ingestion latency and terabyte per-second ingestion rate ensures you can perform real-time log management and analysis at scale. Become proactive about observability using open APIs Leverage open observability tooling to instrument your applications. OpenTelemetry is fully integrated with Cloud Operations, so you can collect and export data from cloud-native applications, Specifically, Cloud Trace allows developers to instrument and export applications with OpenTelemetry for faster incident resolution. Leverage Cloud Observability suite Monitor, troubleshoot, and improve application performance on your Google Cloud environment. Cloud Monitoring Gain visibility into the performance, availability, and health of your applications and infrastructure. <clipPath id="clip0_785_5597"> </clipPath> Cloud Logging Securely store, search, analyze, and receive alerts for all of your log data and events in real time with an exabyte-scale, fully managed service. Learn more SRE practices in the cloud Learn SRE Best Practices with resources created by SRE Experts Cloud blog Google Cloud Blog: DevOps & SRE Google Cloud blogs written by SRE subject matter experts across various SRE and DevOps topics such as setting SLOs, getting the right culture, product announcements, customer stories, and more. Learn more White paper Increasing business value with better IT operations: A guide to SRE This paper covers the business benefits of SRE, SRE best practices, what Google Cloud offers for SRE, and how Google's own experience can help customers on their SRE journey. Learn more Learn from real-world case studies Learn how Google Cloud customers are able to leverage SRE practices. Devops & SRE How Lowe's increased their monthly release velocity by 300x View story Devops & SRE How Lowe's SRE reduced its mean time to recovery (MTTR) by over 80 percent View story Devops & SRE How Sabre is using SRE to lead a successful digital transformation View story 1 2 3 2024 State of DevOps Report For over a decade, the DORA Accelerate State of DevOps report has been offering critical insights into the practices and capabilities that fuel the success of high-performing technology organizations. The tenth edition of the DORA report explores how AI is changing work and its impact on overall technology organizations’ performance. Learn more Google Cloud SRE website Visit the Google Cloud SRE website to learn more about leveraging SRE in the Cloud. Get started Follow us About Google Google products Privacy Terms Help | 2026-01-13T09:29:20 |
Buy aboard.exchange – Premium Expired .exchange Domain on GoDaddy | ExpiredDomains.com Search Contact Us Login Search About Us Contact Us Fresh Listings Daily Powerful Domain Insights No Hidden Costs, Or Registration Fees Trusted by Professionals Fresh Listings Daily Powerful Domain Insights No Hidden Costs, Or Registration Fees Trusted by Professionals aboard.exchange Buy Now on GoDaddy GoDaddy As the world’s largest domain registrar with over 20 million customers, GoDaddy manages more than 84 million domains, offering a robust platform with 24/7 customer support and a wide range of TLDs. Its user-friendly interface and comprehensive services, including hosting and website builders, make it ideal for businesses seeking an all-in-one solution. Price 100 USD Auction Type GoDaddy Buy Now Google Status Not blocked Adult Status Not adult Domain Profile for aboard.exchange Name Properties Length 6 TLD exchange Registered in TLD with links 76 Keyword Search Volume 0 Keyword CPC 0 Radio Test Passed Generic Properties WHOIS Birth Date 17/09/2021 Wayback First Year 2021 Wayback Indexed Pages 130 Number of Wayback Crawls 51 Facebook Shares 5 Facebook Reactions 29 SEO Properties MOZ Domain Authority Login to view MOZ Page Authority Login to view Majestic External Backlinks Login to view Majestic Trust Flow Login to view Majestic Citation Flow Login to view Semrush Rank Login to view Related Domains Available Domain Address Price on.exchange 4832 USD Add to Cart on Godaddy captain.exchange 4999 USD Add to Cart on Godaddy armada.exchange 100 USD Buy Now on GoDaddy cargo.exchange 6988 USD Add to Cart on Godaddy cruiseship.holiday 8 USD Bid (Dyna) ship.exchange 19988 USD Add to Cart on Godaddy over.exchange 3488 USD Add to Cart on Godaddy ride.exchange 100 USD Buy Now on GoDaddy onyx.exchange 100 USD Buy Now on GoDaddy ero.exchange 100 USD Buy Now on GoDaddy ★ ★ ★ ★ ★ 4.9 based on Thousands of domain purchaes! Trusted by Thousands of Domain Buyers Hear what our customers had to say below. ★ ★ ★ ★ ★ Honestly didn’t expect it to be this good Saw this recommended on a forum and didn’t expect much, but wow. The amount of data it shows is crazy for a free tool. I use it mostly to look for brandable names and cross-check SEO value. Already registered a couple. Definitely bookmarking this. Anonymous Purchased on 01/03/2025 ★ ★ ★ ★ ★ Good for flipping or just grabbing brand names Been using ExpiredDomains for about a month and I’ve already picked up a few solid names — one of them’s already flipped. The name value and SEO price estimates are really handy. I wish the design was a bit cleaner but functionally, it’s spot on. Anonymous Purchased on 14/03/2025 ★ ★ ★ ★ ★ Great for finding niche domains I run a few small affiliate sites and I’m always looking for expired domains with decent backlink profiles. ExpiredDomains saves me a ton of time. Filters are a bit overwhelming at first but once you figure it out, it’s so much faster than doing it manually. Found 3 great ones last week. Anonymous Purchased on 03/04/2025 ★ ★ ★ ★ ★ Takes a bit to get used to but super helpful Not the fanciest UI in the world, but the data is solid. It took me a bit of clicking around to learn how to get what I need, but once I did, it’s saved me hours. If you’re into SEO or domaining, this is a no-brainer. Anonymous Purchased on 09/04/2025 ★ ★ ★ ★ ★ Free and no login required, love that I hate tools that make you sign up before you can even try them. This one just works. I use it to find domains for client projects — it’s quick, gives Moz and Majestic scores, and some other custom data I’ve not seen elsewhere. Would happily pay for it, but glad I don’t have to! Anonymous Purchased on 19/03/2025 Why choose Expired Domains? Here’s what makes us a better place to start your search. Comprehensive Listings Over 1 million domains across 677+ TLDs — updated daily. Exclusive Data Metrics you won’t find anywhere else, built to highlight true domain value. User-Friendly Interface Quick filtering, clean results, and zero guesswork. Professional Trust Used by SEOs, marketers, and investors all over the world! Why GoDaddy GoDaddy is one of the most popular domain registries and web hosting providers in the world. As of 2023, it's the fifth-largest web host by market share, with over 62 million registered domains. Comprehensive Domain Services GoDaddy is the world’s largest domain registrar, offering a vast selection of domain names and extensions to help you establish your online presence. User-Friendly Website Builder GoDaddy’s intuitive website builder allows users to create professional-looking websites quickly, with customizable templates and integrated marketing tools. Reliable Hosting with 99.9% Uptime GoDaddy provides dependable web hosting services, ensuring your website remains accessible with a 99.9% uptime guarantee and 24/7 customer support. aboard.exchange find other domains Buy Now on GoDaddy ★ ★ ★ ★ ★ Can’t believe this isn’t behind a paywall Honestly I’ve paid for similar tools that do less. This lets you search through expired domains and filter down by authority, keywords, backlink stuff, even what platform they’re being sold on. And it updates constantly. Feels like a cheat code tbh. Anonymous Purchased on 24/03/2025 Frequently Asked Questions Your queries answered What is ExpiredDomains.com? ExpiredDomains.com is a free online platform that helps users find valuable expired and expiring domain names. It aggregates domain data from hundreds of top-level domains (TLDs) and displays them in a searchable, filterable format. Whether you’re seeking domains with SEO authority, existing traffic, or strong brand potential, the platform provides tools and insights to support smarter decisions. Is there a cost to use the platform? No, the platform is completely free to use. You can browse listings, view metrics, and apply filters without needing to sign up or pay any fees. There are no hidden charges or usage restrictions. Can I register domains directly through the site? No, ExpiredDomains.com does not register domains itself. Instead, it connects you to trusted external registrars and marketplaces like GoDaddy. You’ll be directed to complete your purchase or place a bid through their platform. How often is the domain data updated? The domain data is updated daily to ensure you're always seeing the most current listings, prices, and metrics. This includes newly expired domains, auction updates, and fresh insights from third-party tools and proprietary systems. What tools and filters are available on the platform? You can filter domains by TLD, keyword, length, backlink profile, SEO score, traffic estimates, and more. The platform also includes proprietary metrics like Estimated Auction Price, BrandRank, and SEO Price, alongside trusted data from sources like MOZ and Majestic. aboard.exchange Buy Now on GoDaddy GoDaddy As the world’s largest domain registrar with over 20 million customers, GoDaddy manages more than 84 million domains, offering a robust platform with 24/7 customer support and a wide range of TLDs. Its user-friendly interface and comprehensive services, including hosting and website builders, make it ideal for businesses seeking an all-in-one solution. Looking for something different? Search for expired domains below to find the best prices. SOLD Sold for speedforce.com $2425 USD SOLD Sold for gobeast.com $1342 USD SOLD Sold for sirriusblackcafe.com $405 USD SOLD Sold for lungspace.com $600 USD SOLD Sold for webcamcruise.com $610 USD SOLD Sold for speedforce.com $2425 USD SOLD Sold for gobeast.com $1342 USD SOLD Sold for sirriusblackcafe.com $405 USD SOLD Sold for lungspace.com $600 USD SOLD Sold for webcamcruise.com $610 USD Buy Now on GoDaddy FAQ TOS Privacy About Us Knowledge Base Follow us on X Receive updates on hot deals, exclusive platform enhancements, and insider tips Follow @ExpiredDomainHQ © expireddomains 2025 | 2026-01-13T09:29:20 | |
http://www.trello.com/teams/design | Trello for Design Teams | Trello Skip to main content Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Use case: Task management Track progress of tasks in one convenient place with a visual layout that adds ‘ta-da’ to your to-do’s. Use case: Resource hub Save hours when you give teams a well-designed hub to find information easily and quickly. Use case: Project management Keep projects organized, deadlines on track, and teammates aligned with Trello. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Back Navigation Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Read though our use cases to make the most of Trello on your team. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Helping teams work better, together Discover Trello use cases, productivity tips, best practices for team collaboration, and expert remote work advice. Check out the Trello blog < Go back to Team Solutions Trello For Design Teams From creative brainstorms to the final touches, discover how Trello helps your design teams deliver with style. Trello’s boards, lists, and cards enable teams to go from ideas to action in seconds. Visual and easy-to-use, Trello helps teams bring projects to life and keep them moving forward. Join over 2,000,000 teams worldwide who are using Trello to get more done. Your Team’s Workspace These template boards make it easier for creative teams to manage requests, drafts, revisions, cross-functional projects, and focus on what they do best—crafting beautiful designs. Explore all design templates Design Sprint Help your team move from problem to solution by using this template to run a design sprint. Easily ideate on early concepts, test ideas, and hit the ground running. Design Huddle Design critique is a tenet of any good design practice. This design huddle template encourages collaboration, feedback, and better future design decisions. Research Project Use this board to share the work with your team, automate steps, and create a thorough analysis of your project. Design Sprint Help your team move from problem to solution by using this template to run a design sprint. Easily ideate on early concepts, test ideas, and hit the ground running. Design Huddle Design critique is a tenet of any good design practice. This design huddle template encourages collaboration, feedback, and better future design decisions. Research Project Use this board to share the work with your team, automate steps, and create a thorough analysis of your project. Keep the focus on creativity. Keep your Design team on track with the Timeline view, and ensure sure creative projects and assets are delivered before the deadline. Learn more about Trello views Power-Up Your Designs While you’re busy drafting award-winning designs, Power-Ups are busy making your boards even more efficient. With integrations like Miro and Figma you can easily connect your favorite design tools within Trello. Explore 150+ Power-Ups Move Work Forward, Auto-magically Trello’s built-in automation makes it easy to automate the repetitive, everyday tasks that keep your team from focusing on the work that matters most. Let the robots do the work Resources To Make Design Dreams A Reality How Think Company Uses Trello To Manage A Design System [Blog Post] Discover how a successful design firm uses Trello to easily collaborate, store information, and organize a complex but effective design system. READ MORE Huddle Up: The New Way To Create A Safe ‘Critique’ Space For Your Team [Blog Post] Learn best practices for spotting inconsistencies, building skills, and building a positive feedback culture within your design team. READ MORE How Design Teams Are Using Trello: The Ultimate Roundup [Blog Post] Keeping the work of design teams manageable, the culture of the team collaborative, and communication and feedback at the forefront are all essential elements to executing a truly successful product. Trello can help your team do just that–here’s an entire guide to prove it. READ MORE NOW AVAILABLE A 14 Day Free Trial of Premium! Get unlimited boards, Trello views, and limitless automation, plus a ton more. Try it today SwagUp: Scale Any Business With Trello BC “Not only did [Trello] unify our process and help everyone understand their role, but we were able to automate essential steps of the process so we could move a lot faster and grow to a multi-million dollar company with a team of ten.” –Founder, SwagUp Learn More Instinct Dog Training “As you scale, you need visibility, accountability, and organization. Trello has provided that for us.” –Brian Burton, Founder, Instinct Dog Training Learn More Desk Plants “We chose Trello because it is well-designed—it’s beautifully designed—intuitive, and really hit the nail on the head with what we needed to solve.” –Lawrence Hanley, founder of Desk Plants Learn More Scan2Cad “We use Trello because our data becomes alive. A bullet point list turns into real tasks that are assigned to real people with due dates and connections to our other apps. The power in that is fantastic.” –Luke Kennedy, CEO, Scan2Cad Learn More Palace Law “People have generally been happier since we started using Trello. It has made our lives a lot easier. People are less stressed.” -Jordan Couch, attorney at Palace Law Learn More Trello Your Way Ready to get your team up and running? Try the business tool so easy to use, your team can’t help but collaborate. Learn more about our pricing and plans Free $ 0 USD Free for up to 10 collaborators per Workspace Capture your to-dos, get organized, and get sh*t done. Standard $ 5 USD Per user/month if billed annually ($6 billed monthly) Get more stuff done with unlimited boards, card mirroring, and more automation. Learn more about Standard Premium $ 10 USD Per user/month if billed annually ($12.50 billed monthly) Add AI to your boards and admin controls to your toolkit. Plus, get more perspective with views. Learn more about Premium Enterprise $ 17.50 USD Per user/month - billed annually ($210.00 annual price per user) Add enterprise-grade security and controls. This plan includes Atlassian Guard Standard and 24/7 Enterprise Admin support. Est. cost for users Learn more about Enterprise Well, what are you waiting for? Head over to your boards and start getting things done! Log In About Trello What’s behind the boards. Jobs Learn about open roles on the Trello team. Apps Download the Trello App for your Desktop or Mobile devices. Contact us Need anything? Get in touch and we can help. Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Privacy Policy Terms Copyright © 2024 Atlassian | 2026-01-13T09:29:20 |
https://git-scm.com/book/it/v2/Git-on-the-Server-Git-Daemon | Git - Git Daemon About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Per Iniziare 1.1 Il Controllo di Versione 1.2 Una Breve Storia di Git 1.3 Cos’é Git? 1.4 La riga di comando 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Chiedere aiuto 1.8 Sommario 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Sommario 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendice A: Git in altri contesti A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Riassunto A2. Appendice B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendice C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.5 Git on the Server - Git Daemon Git Daemon Next we’ll set up a daemon serving repositories over the “Git” protocol. This is common choice for fast, unauthenticated access to your Git data. Remember that since it’s not an authenticated service, anything you serve over this protocol is public within it’s network. If you’re running this on a server outside your firewall, it should only be used for projects that are publicly visible to the world. If the server you’re running it on is inside your firewall, you might use it for projects that a large number of people or computers (continuous integration or build servers) have read-only access to, when you don’t want to have to add an SSH key for each. In any case, the Git protocol is relatively easy to set up. Basically, you need to run this command in a daemonized manner: git daemon --reuseaddr --base-path=/opt/git/ /opt/git/ --reuseaddr allows the server to restart without waiting for old connections to time out, the --base-path option allows people to clone projects without specifying the entire path, and the path at the end tells the Git daemon where to look for repositories to export. If you’re running a firewall, you’ll also need to punch a hole in it at port 9418 on the box you’re setting this up on. You can daemonize this process a number of ways, depending on the operating system you’re running. On an Ubuntu machine, you can use an Upstart script. So, in the following file /etc/event.d/local-git-daemon you put this script: start on startup stop on shutdown exec /usr/bin/git daemon \ --user=git --group=git \ --reuseaddr \ --base-path=/opt/git/ \ /opt/git/ respawn For security reasons, it is strongly encouraged to have this daemon run as a user with read-only permissions to the repositories – you can easily do this by creating a new user git-ro and running the daemon as them. For the sake of simplicity we’ll simply run it as the same git user that Gitosis is running as. When you restart your machine, your Git daemon will start automatically and respawn if it goes down. To get it running without having to reboot, you can run this: initctl start local-git-daemon On other systems, you may want to use xinetd , a script in your sysvinit system, or something else – as long as you get that command daemonized and watched somehow. Next, you have to tell Git which repositories to allow unauthenticated Git server-based access to. You can do this in each repository by creating a file name git-daemon-export-ok . $ cd /path/to/project.git $ touch git-daemon-export-ok The presence of that file tells Git that it’s OK to serve this project without authentication. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/dataport-a%C3%B6r-dwebservice?similarProducts=true&trk=products_details_guest_similar_products_section_sign_in | dWebService | LinkedIn Skip to main content LinkedIn Dataport AöR in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in dWebService Web Hosting by Dataport AöR See who's skilled in this Add as skill Get started Report this product About Hosting. Webportale. Analysen. Ohne Webseite geht es heute nicht mehr. Dabei unterstützt Sie dWebService: Vom simplen Webspace bis hin zu einem vollständigen Content Management System. Inklusive sicherem Hosting, Barrierefreiheits-Check und smarten Nutzungsanalysen. Auf einen Blick: ✅ Individuelle Beratung und maßgeschneiderte Entwicklung von Webportalen ✅ Hosting im BSI-zertifizierten Twin Data Center ✅ Barrierefreie Webentwicklung ✅ DSGVO-konforme Nutzungsanalysen ✅ Entwicklung und Betreuung von Webportalen mit TYPO3 ✅ Integration von Active Directories und Single-Sign-On This product is intended for Head of Section Resort Manager Department Manager Information Technology Application Manager Information Technology Specialist Mayor Senior Administrative Officer State Secretary Chief Information Security Officer Press Officer Media Products media viewer No more previous content dWebService Schnelles und sicheres Hosting No more next content Similar products IPv4 Address Leasing Service IPv4 Address Leasing Service Web Hosting Pantheon Platform Pantheon Platform Web Hosting Elastic Metal Elastic Metal Web Hosting Web Hosting Web Hosting Web Hosting WooCommerce Hosting WooCommerce Hosting Web Hosting Cloudways Autonomous Cloudways Autonomous Web Hosting Sign in to see more Show more Show less Dataport AöR products data[port]ai data[port]ai Data Science & Machine Learning Platforms Dataport Consulting Dataport Consulting Strategic Planning Software dDataBox dDataBox Managed File Transfer (MFT) Software dMessenger dMessenger Enterprise Messaging Software dProjectTracking dProjectTracking Project Management Software dWorkflow dWorkflow Workflow Management Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://git-scm.com/book/fa/v2/%da%af%db%8c%d8%aa-%d8%b1%d9%88%db%8c-%d8%b3%d8%b1%d9%88%d8%b1-Git-on-the-server-HTTP-%d9%87%d9%88%d8%b4%d9%85%d9%86%d8%af-Smart-HTTP | Git - HTTP هوشمند (Smart HTTP) About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. شروع به کار (getting started) 1.1 درباره ورژن کنترل (About Version Control) 1.2 تاریخچه کوتاهی از گیت (A Short History of Git) 1.3 گیت چیست؟ (What is Git) 1.4 نصب گیت (Installing Git) 1.5 ستاپ اولیه گیت (First-Time Git Setup) 1.6 دریافت کمک (Getting Help) 1.7 خلاصه (summary) 2. مقدمات گیت (git basics chapter) 2.1 گرفتن یک مخزن گیت (Getting a Git Repository) 2.2 ثبت تغییرات در مخزن (Recording Changes to the Repository) 2.3 مشاهده تاریخچه کامیتها (Viewing the Commit History) 2.4 بازگرداندن تغییرات (Undoing Things) 2.5 کار کردن با ریموت ها (Working with Remotes) 2.6 تگ کردن (Tagging) 2.7 نام مستعار گیت (Git Aliases) 2.8 خلاصه (summary) 3. انشعابگیری در گیت (Git Branching) 3.1 شاخهها در یک نگاه (Branches in a Nutshell) 3.2 شاخهبندی و ادغام پایهای (Basic Branching and Merging) 3.3 مدیریت شاخهها (Branch Management) 3.4 روندهای کاری شاخهها (Branching Workflows) 3.5 شاخههای راه دور (Remote Branches) 3.6 بازپایهگذاری (Rebasing) 3.7 خلاصه (Summary) 4. گیت روی سرور (Git on the server) 4.1 پروتکلها (The Protocols) 4.2 راهاندازی گیت روی یک سرور (Getting Git on a Server) 4.3 ایجاد کلید عمومی SSH شما (Generating Your SSH Public Key) 4.4 نصب و راهاندازی سرور (Setting up server) 4.5 سرویسدهنده گیت (Git Daemon) 4.6 HTTP هوشمند (Smart HTTP) 4.7 گیتوب (GitWeb) 4.8 گیتلب (GitLab) 4.9 گزینههای میزبانی شخص ثالث (Third Party Hosted Options) 4.10 خلاصه (Summary) 5. گیت توزیعشده (Distributed git) 5.1 جریانهای کاری توزیعشده (Distributed Workflows) 5.2 مشارکت در یک پروژه (Contributing to a Project) 5.3 نگهداری یک پروژه (Maintaining a Project) 5.4 خلاصه (Summary) 6. گیت هاب (GitHub) 6.1 راهاندازی و پیکربندی حساب کاربری (Account Setup and Configuration) 6.2 مشارکت در یک پروژه (Contributing to a Project) 6.3 نگهداری یک پروژه (Maintaining a Project) 6.4 مدیریت یک سازمان (Managing an organization) 6.5 اسکریپتنویسی در گیتهاب (Scripting GitHub) 6.6 خلاصه (Summary) 7. ابزارهای گیت (Git Tools) 7.1 انتخاب بازبینی (Revision Selection) 7.2 مرحلهبندی تعاملی (Interactive Staging) 7.3 ذخیره موقت و پاکسازی (Stashing and Cleaning) 7.4 امضای کارهای شما (Signing Your Work) 7.5 جستجو (Searching) 7.6 بازنویسی تاریخچه (Rewriting History) 7.7 بازنشانی به زبان ساده (Reset Demystified) 7.8 ادغام پیشرفته (Advanced Merging) 7.9 بازاستفاده خودکار از حل تضادها (Rerere) 7.10 اشکالزدایی با گیت (Debugging with Git) 7.11 سابماژول ها (Submodules) 7.12 بستهبندی (Bundling) 7.13 جایگزینی (Replace) 7.14 ذخیرهسازی اطلاعات ورود (Credential Storage) 7.15 خلاصه (Summary) 8. سفارشیسازی Git (Customizing Git) 8.1 پیکربندی گیت (Git Configuration) 8.2 ویژگیهای گیت (Git Attributes) 8.3 هوکهای گیت (Git Hooks) 8.4 یک نمونه سیاست اعمال شده توسط گیت (An Example Git-Enforced Policy) 8.5 خلاصه (Summary) 9. گیت و سیستمهای دیگر (Git and Other Systems) 9.1 گیت بهعنوان کلاینت (Git as a Client) 9.2 مهاجرت به گیت (Migrating to Git) 9.3 خلاصه (Summary) 10. مباحث درونی گیت (Git Internals) 10.1 ابزارها و دستورات سطح پایین (Plumbing and Porcelain) 10.2 اشیا گیت (Git Objects) 10.3 مراجع گیت (Git References) 10.4 فایلهای بسته (Packfiles) 10.5 نگاشت (The Refspec) 10.6 پروتکلهای انتقال (Transfer Protocols) 10.7 نگهداری و بازیابی دادهها (Maintenance and Data Recovery) 10.8 متغیرهای محیطی (Environment Variables) 10.9 خلاصه (Summary) A1. پیوست A: گیت در محیطهای دیگر (Git in Other Environments) A1.1 رابط های گرافیکی (Graphical Interfaces) A1.2 گیت در ویژوال استودیو (Git in Visual Studio) A1.3 گیت در Visual Studio Code (Git in Visual Studio Code) A1.4 گیت در IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine (Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine) A1.5 گیت در Sublime Text (Git in Sublime Text) A1.6 گیت در بش (Git in Bash) A1.7 گیت در Zsh (Git in Zsh) A1.8 گیت در PowerShell (Git in PowerShell) A1.9 خلاصه (Summary) A2. پیوست B: گنجاندن گیت در برنامههای شما (Embedding Git in your Applications) A2.1 خط فرمان گیت (Command-line Git) A2.2 کتابخانهٔ گیت به زبان سی (Libgit2) A2.3 کتابخانه گیت برای زبان جاوا (JGit) A2.4 کتابخانه گیت برای زبان گو (go-git) A2.5 کتابخانه گیت پایتون (Dulwich) A3. پیوست C: دستورات گیت (Git Commands) A3.1 تنظیم و پیکربندی (Setup and Config) A3.2 گرفتن و ایجاد پروژهها (Getting and Creating Projects) A3.3 نمونهبرداری پایهای (Basic Snapshotting) A3.4 انشعابگیری و ادغام (Branching and Merging) A3.5 بهاشتراکگذاری و بهروزرسانی پروژهها (Sharing and Updating Projects) A3.6 بازرسی و مقایسه (Inspection and Comparison) A3.7 عیبیابی (Debugging) A3.8 اعمال تغییرات به صورت پچ (Patching) A3.9 ایمیل (Email) A3.10 سیستمهای خارجی (External Systems) A3.11 مدیریت (Administration) A3.12 دستورات سطح پایین گیت (Plumbing Commands) 2nd Edition 4.6 گیت روی سرور (Git on the server) - HTTP هوشمند (Smart HTTP) HTTP هوشمند (Smart HTTP) ما اکنون دسترسی احراز هویت شده از طریق SSH و دسترسی بدون احراز هویت از طریق git:// داریم، اما پروتکلی نیز وجود دارد که میتواند هر دو را همزمان انجام دهد. راهاندازی Smart HTTP اساساً فقط فعال کردن یک اسکریپت CGI است که با گیت ارائه میشود و در سرور git-http-backend نام دارد. (دستورات گیت، "http-backend") این CGI مسیر و هدرهای ارسال شده توسط git fetch یا git push به یک URL HTTP را میخواند و تعیین میکند که آیا کلاینت میتواند از طریق HTTP ارتباط برقرار کند (که برای هر کلاینتی از نسخه ۱.۶.۶ به بعد درست است). اگر CGI ببیند که مشتری باهوش است، با او هوشمندانه ارتباط برقرار میکند؛ در غیر این صورت به رفتار سادهلوحانه بازمیگردد (بنابراین برای خواندن با مشتریان قدیمیتر سازگار با نسخههای قبلی است). بیایید یک راهاندازی بسیار ساده را مرور کنیم. ما این را با آپاچی به عنوان سرور CGI راهاندازی خواهیم کرد. اگر آپاچی را راهاندازی نکردهاید، میتوانید این کار را روی یک سرور لینوکس با چیزی شبیه این انجام دهید: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env این همچنین ماژولهای mod_cgi ، mod_alias و mod_env را فعال میکند که همگی برای عملکرد صحیح این کار لازم هستند. همچنین باید گروه کاربری یونیکس دایرکتوریهای /srv/git را روی www-data تنظیم کنید تا سرور وب شما بتواند به مخازن دسترسی خواندن و نوشتن داشته باشد، زیرا نمونه آپاچی که اسکریپت CGI را اجرا میکند (به طور پیشفرض) با آن کاربر اجرا خواهد شد: $ chgrp -R www-data /srv/git بعداً باید چیزهایی به پیکربندی آپاچی اضافه کنیم تا git-http-backend را به عنوان هندلر هر چیزی که به مسیر /git سرور وب شما میآید، اجرا کنیم. SetEnv GIT_PROJECT_ROOT /srv/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/lib/git-core/git-http-backend/ اگر متغیر محیطی GIT_HTTP_EXPORT_ALL را حذف کنید، گیت فقط مخزنهایی را که فایل git-daemon-export-ok در آنها وجود دارد، درست مانند گیت دیمون، به کلاینتهای بدون احراز هویت سرویس میدهد. در نهایت، میخواهید به آپاچی بگویید که درخواستها به git-http-backend را مجاز کند و نوشتنها را به نوعی احراز هویت کند، احتمالاً با یک بلوک Auth مانند این: <Files "git-http-backend"> AuthType Basic AuthName "Git Access" AuthUserFile /srv/git/.htpasswd Require expr !(%{QUERY_STRING} -strmatch '*service=git-receive-pack*' || %{REQUEST_URI} =~ m#/git-receive-pack$#) Require valid-user </Files> این کار مستلزم ایجاد یک فایل .htpasswd است که حاوی رمز عبور تمام کاربران معتبر باشد. در اینجا نمونهای از اضافه کردن کاربر “schacon” به فایل آورده شده است: $ htpasswd -c /srv/git/.htpasswd schacon راههای زیادی برای احراز هویت کاربران توسط آپاچی وجود دارد، شما باید یکی از آنها را انتخاب و پیادهسازی کنید. این فقط سادهترین مثالی بود که توانستیم به آن برسیم. همچنین تقریباً مطمئناً میخواهید این را روی SSL راهاندازی کنید تا تمام این دادهها رمزگذاری شوند. ما نمیخواهیم خیلی وارد جزئیات پیکربندی آپاچی شویم، زیرا ممکن است شما از سرور دیگری استفاده کنید یا نیازهای احراز هویت متفاوتی داشته باشید. ایده این است که گیت همراه با یک CGI به نام git-http-backend ارائه میشود که هنگام فراخوانی، تمام مذاکرات برای ارسال و دریافت دادهها از طریق HTTP را انجام میدهد. خودش هیچ احرازی هویت را پیادهسازی نمیکند، اما این را میتوان به راحتی در لایه وب سروری که آن را فراخوانی میکند، کنترل کرد. شما میتوانید این کار را تقریباً با هر سرور وب دارای قابلیت CGI انجام دهید، بنابراین سروری را انتخاب کنید که بهترین شناخت را از آن دارید. یادداشت برای اطلاعات بیشتر در مورد پیکربندی احراز هویت در آپاچی، مستندات آپاچی را در اینجا بررسی کنید: https://httpd.apache.org/docs/current/howto/auth.html [^]. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/de/v2/Git-auf-dem-Server-Git-Daemon | Git - Git-Daemon About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Erste Schritte 1.1 Was ist Versionsverwaltung? 1.2 Kurzer Überblick über die Historie von Git 1.3 Was ist Git? 1.4 Die Kommandozeile 1.5 Git installieren 1.6 Git Basis-Konfiguration 1.7 Hilfe finden 1.8 Zusammenfassung 2. Git Grundlagen 2.1 Ein Git-Repository anlegen 2.2 Änderungen nachverfolgen und im Repository speichern 2.3 Anzeigen der Commit-Historie 2.4 Ungewollte Änderungen rückgängig machen 2.5 Mit Remotes arbeiten 2.6 Taggen 2.7 Git Aliases 2.8 Zusammenfassung 3. Git Branching 3.1 Branches auf einen Blick 3.2 Einfaches Branching und Merging 3.3 Branch-Management 3.4 Branching-Workflows 3.5 Remote-Branches 3.6 Rebasing 3.7 Zusammenfassung 4. Git auf dem Server 4.1 Die Protokolle 4.2 Git auf einem Server einrichten 4.3 Erstellung eines SSH-Public-Keys 4.4 Einrichten des Servers 4.5 Git-Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Von Drittanbietern gehostete Optionen 4.10 Zusammenfassung 5. Verteiltes Git 5.1 Verteilter Arbeitsablauf 5.2 An einem Projekt mitwirken 5.3 Ein Projekt verwalten 5.4 Zusammenfassung 6. GitHub 6.1 Einrichten und Konfigurieren eines Kontos 6.2 Mitwirken an einem Projekt 6.3 Ein Projekt betreuen 6.4 Verwalten einer Organisation 6.5 Skripte mit GitHub 6.6 Zusammenfassung 7. Git Tools 7.1 Revisions-Auswahl 7.2 Interaktives Stagen 7.3 Stashen und Bereinigen 7.4 Deine Arbeit signieren 7.5 Suchen 7.6 Den Verlauf umschreiben 7.7 Reset entzaubert 7.8 Fortgeschrittenes Merging 7.9 Rerere 7.10 Debuggen mit Git 7.11 Submodule 7.12 Bundling 7.13 Replace (Ersetzen) 7.14 Anmeldeinformationen speichern 7.15 Zusammenfassung 8. Git einrichten 8.1 Git Konfiguration 8.2 Git-Attribute 8.3 Git Hooks 8.4 Beispiel für Git-forcierte Regeln 8.5 Zusammenfassung 9. Git und andere VCS-Systeme 9.1 Git als Client 9.2 Migration zu Git 9.3 Zusammenfassung 10. Git Interna 10.1 Basisbefehle und Standardbefehle (Plumbing and Porcelain) 10.2 Git Objekte 10.3 Git Referenzen 10.4 Packdateien (engl. Packfiles) 10.5 Die Referenzspezifikation (engl. Refspec) 10.6 Transfer Protokolle 10.7 Wartung und Datenwiederherstellung 10.8 Umgebungsvariablen 10.9 Zusammenfassung A1. Anhang A: Git in anderen Umgebungen A1.1 Grafische Schnittstellen A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Zusammenfassung A2. Anhang B: Git in deine Anwendungen einbetten A2.1 Die Git-Kommandozeile A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Anhang C: Git Kommandos A3.1 Setup und Konfiguration A3.2 Projekte importieren und erstellen A3.3 Einfache Snapshot-Funktionen A3.4 Branching und Merging A3.5 Projekte gemeinsam nutzen und aktualisieren A3.6 Kontrollieren und Vergleichen A3.7 Debugging A3.8 Patchen bzw. Fehlerkorrektur A3.9 E-mails A3.10 Externe Systeme A3.11 Administration A3.12 Basisbefehle 2nd Edition 4.5 Git auf dem Server - Git-Daemon Git-Daemon Als Nächstes richten wir einen Daemon ein, der Repositorys mit dem „Git“-Protokoll versorgt. Das ist eine gängige Option für den schnellen, nicht authentifizierten Zugriff auf deine Git-Daten. Denke daran, dass alles, was du über dieses Protokoll bereitstellst, innerhalb deines Netzwerks öffentlich ist, da dies kein authentifizierter Dienst ist. Wenn du dieses auf einem Server außerhalb deiner Firewall ausführst, sollte dies nur für Projekte verwendet werden, die für die Welt öffentlich sichtbar sein dürfen. Wenn sich der genutzte Server, hinter deiner Firewall befindet, kannst du es für Projekte verwenden, auf die eine große Anzahl von Personen oder Computern (Continuous Integration oder Build-Server) nur Lesezugriff haben, wenn du nicht für jeden einen SSH-Schlüssel hinzufügen möchtest. In jedem Fall ist das Git-Protokoll relativ einfach einzurichten. Grundsätzlich solltest du diesen Befehl als Daemon auszuführen: $ git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Mit der --reuseaddr Option kann der Server neu gestartet werden, ohne dass man auf eine Time-Out für alte Verbindungen warten muß. Mit der --base-path Option können Benutzer Projekte klonen, ohne den gesamten Pfad anzugeben. Der abschließende Pfad teilt dem Git-Daemon mit, wo nach zu exportierenden Repositorys gesucht werden soll. Wenn du eine Firewall verwendest, musst du den Port 9418 konfigurieren, um eingehende Verbindungen zuzulassen. Du kannst diesen Prozess auf verschiedene Arten als Daemon betreiben, je nachdem, welches Betriebssystem du verwendest. Das systemd ist das gebräuchlichste Init-System unter modernen Linux-Distributionen. Das könntest du für diesen Zweck verwenden. Lege einfach eine Datei mit folgendem Inhalt in /etc/systemd/system/git-daemon.service ab: [Unit] Description=Start Git Daemon [Service] ExecStart=/usr/bin/git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Restart=always RestartSec=500ms StandardOutput=syslog StandardError=syslog SyslogIdentifier=git-daemon User=git Group=git [Install] WantedBy=multi-user.target Du hast vielleicht bemerkt, dass der Git-Daemon hier mit git als Gruppe und Benutzer gestartet wird. Passe es an deine Bedürfnisse an und stelle sicher, dass der angegebene Benutzer auf dem System vorhanden ist. Überprüfe auch, ob sich die Git-Binärdatei tatsächlich unter /usr/bin/git befindet und ändere gegebenenfalls den Pfad. Abschließend führst du systemctl enable git-daemon aus, um den Dienst beim Booten automatisch zu starten, so dass du den Dienst mit systemctl start git-daemon und systemctl stop git-daemon starten und stoppen kannst. Auf anderen Systemen kannst du xinetd verwenden oder ein Skript in deinem sysvinit System benutzen. Auch andere Lösungen sind möglich, solange der Prozess als Daemon läuft und irgendwie überwacht wird. Als nächstes musst du Git mitteilen, auf welche Repositorys nicht authentifizierter, serverbasierter Zugriffe auf Git möglich sein soll. Du kannst das in den einzelnen Repositorys tun, indem du eine Datei mit dem Namen git-daemon-export-ok erstellst. $ cd /path/to/project.git $ touch git-daemon-export-ok Das Vorhandensein dieser Datei teilt Git mit, dass es in Ordnung ist, dieses Projekt ohne Authentifizierung zur Verfügung zu stellen. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/zh-tw/v2/%e4%bc%ba%e6%9c%8d%e5%99%a8%e4%b8%8a%e7%9a%84-Git-Git-%e5%b8%b8%e9%a7%90%e7%a8%8b%e5%bc%8f | Git - Git 常駐程式 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 開始 1.1 關於版本控制 1.2 Git 的簡史 1.3 Git 基礎要點 1.4 命令列 1.5 Git 安裝教學 1.6 初次設定 Git 1.7 取得說明文件 1.8 摘要 2. Git 基礎 2.1 取得一個 Git 倉儲 2.2 紀錄變更到版本庫中 2.3 檢視提交的歷史記錄 2.4 復原 2.5 與遠端協同工作 2.6 標籤 2.7 Git Aliases 2.8 總結 3. 使用 Git 分支 3.1 簡述分支 3.2 分支和合併的基本用法 3.3 分支管理 3.4 分支工作流程 3.5 遠端分支 3.6 衍合 3.7 總結 4. 伺服器上的 Git 4.1 通訊協定 4.2 在伺服器上佈署 Git 4.3 產生你的 SSH 公鑰 4.4 設定伺服器 4.5 Git 常駐程式 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第3方 Git 託管方案 4.10 總結 5. 分散式的 Git 5.1 分散式工作流程 5.2 對專案進行貢獻 5.3 維護一個專案 5.4 Summary 6. GitHub 6.1 建立帳戶及設定 6.2 參與一個專案 6.3 維護專案 6.4 Managing an organization 6.5 Scripting GitHub 6.6 總結 7. Git 工具 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 總結 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. 附錄 A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. 附錄 B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. 附錄 C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.5 伺服器上的 Git - Git 常駐程式 Git 常駐程式 Next we’ll set up a daemon serving repositories over the “Git” protocol. This is common choice for fast, unauthenticated access to your Git data. Remember that since it’s not an authenticated service, anything you serve over this protocol is public within its network. If you’re running this on a server outside your firewall, it should only be used for projects that are publicly visible to the world. If the server you’re running it on is inside your firewall, you might use it for projects that a large number of people or computers (continuous integration or build servers) have read-only access to, when you don’t want to have to add an SSH key for each. In any case, the Git protocol is relatively easy to set up. Basically, you need to run this command in a daemonized manner: $ git daemon --reuseaddr --base-path=/opt/git/ /opt/git/ --reuseaddr allows the server to restart without waiting for old connections to time out, the --base-path option allows people to clone projects without specifying the entire path, and the path at the end tells the Git daemon where to look for repositories to export. If you’re running a firewall, you’ll also need to punch a hole in it at port 9418 on the box you’re setting this up on. You can daemonize this process a number of ways, depending on the operating system you’re running. On an Ubuntu machine, you can use an Upstart script. So, in the following file /etc/init/local-git-daemon.conf you put this script: start on startup stop on shutdown exec /usr/bin/git daemon \ --user=git --group=git \ --reuseaddr \ --base-path=/opt/git/ \ /opt/git/ respawn For security reasons, it is strongly encouraged to have this daemon run as a user with read-only permissions to the repositories – you can easily do this by creating a new user git-ro and running the daemon as them. For the sake of simplicity we’ll simply run it as the same git user that git-shell is running as. When you restart your machine, your Git daemon will start automatically and respawn if it goes down. To get it running without having to reboot, you can run this: $ initctl start local-git-daemon On other systems, you may want to use xinetd , a script in your sysvinit system, or something else – as long as you get that command daemonized and watched somehow. Next, you have to tell Git which repositories to allow unauthenticated Git server-based access to. You can do this in each repository by creating a file named git-daemon-export-ok . $ cd /path/to/project.git $ touch git-daemon-export-ok The presence of that file tells Git that it’s OK to serve this project without authentication. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/categories/service-desk-software?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_subtitle-click | Best Service Desk Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Information Technology Manager (36) Director of Information Technology (24) Head of Information Technology (17) Chief Technology Officer (15) Chief Information Officer (14) See all products Find top products in Service Desk Software category Software used to organize internal tickets for IT services. - Provide portal for employee hardware and software issues - Manage service requests, incident reports, and knowledge base - Track IT assets in use by department 154 results Jira Service Management Service Desk Software by Atlassian Collaborate at high velocity, respond to business changes, and deliver great customer and employee service experiences fast. View product Freshservice Service Desk Software by Freshworks Freshservice is an intelligent, right-sized service management solution for modern businesses of all sizes. Freshservice does this by taking a fresh approach to building and delivering modern employee experiences and unified service management —empowering businesses to achieve efficiency, fast time-to-value, and improved employee satisfaction and productivity. View product Intercom Service Desk Software by Intercom Intercom is the only complete AI-first customer service platform, enhancing the customer experience, improving operational efficiency, and scaling with your business every step of the way. Our AI-first platform is built on a single AI system, with two major components that will allow you to deliver the remarkable customer service you’ve spent decades striving for: Fin AI Agent: The human-quality AI agent that works with any Helpdesk Intercom Customer Service Platform: The AI-first platform trusted by thousands of support leaders. Founded in 2011 and backed by leading venture capitalists, including Kleiner Perkins, Bessemer Venture Partners and Social Capital, Intercom believes there's a new way to do customer service. View product Atomicwork Service Desk Software by Atomicwork Agentic service management platform to modernize ITSM, ESM and enterprise workflows. View product SolarWinds Service Desk Service Desk Software by SolarWinds An IT service management (ITSM) solution that understands what it takes to successfully manage your employee services. Try Solarwinds Service Desk for free! View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights Service Desk Service Desk Software by Triad Integration Uma operação mais produtiva e responsiva, baseada nas melhores práticas de Information Technology Service Management (ITMS). Os clientes que contam com o suporte técnico insourcing ou outsourcing da Triad têm agilidade e excelência na resolução de problemas, incidentes e requisições. Indicadores operacionais são gerados em tempo real, em formato de dashboards, e apresentam o controle dos SLAs e KPIs quantitativos e qualitativos. Em conjunto, esses dados possibilitam tomadas de decisões mais assertivas e mantém a qualidade da entrega dos produtos e serviços da empresa. View product TOPdesk Service Desk Software by TOPdesk TOPdesk is the only service management solution that combines a ready-to-go tool with dedicated in-house experts. We don’t just create software for consistently great service delivery. We make sure you can achieve your goals, step by step. Whether you want to focus on self-service or automate your ticket routing, our people have loads of best practices to share. Once set up, you can easily adjust the tool yourself, so you can continue to learn and improve in your own time. Need more help? With 25+ years' experience helping organizations like yours, our 900 in-house specialists in 11 countries are rooting for your success and just a phone call away. Let’s make service happen together! View product SysAid AI-powered ITSM Service Desk Software by SysAid Designed to meet the complex needs of IT teams, you can delegate tasks to pre-built AI Agents who intelligently assess issues, make decisions, and take action on your team’s behalf. Complementing your team’s work and helping you scale up your activities—with far less effort. Learn more: https://www.sysaid.com/ai-agent-builder View product Rezolve.ai Service Desk Software by Rezolve AI Rezolve.ai is a GenAI-enabled modern AITSM solution that seamlessly integrates with Microsoft Teams, revolutionizing not only IT but also HR support. This platform streamlines employee assistance through conversational ticketing, conversational automation, and conversational knowledge. This innovative approach elevates your IT and HR support teams to superhero status, with the GenAI SideKick empowering them to deliver unparalleled service in both IT and HR related queries and tasks. View product InvGate Service Management Service Desk Software by InvGate Invgate Service Management is the most flexible no-code, ITIL-aligned ITSM platform designed to help Service Management professionals save time and work faster. SM automates repetitive tasks with a visual workflow builder, gives users AI-powered agents to self-serve answers and a features a flexible UX and data model that makes enterprise service management feel easy. Used by over three million employees across 50 countries, it’s helping companies ranging from Peoples Bank to PwC, from Tulsa Airport to Collins Aerospace, and from Toyota to McDonalds. View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:20 |
https://git-scm.com/book/zh/v2/%e6%9c%8d%e5%8a%a1%e5%99%a8%e4%b8%8a%e7%9a%84-Git-Git-%e5%ae%88%e6%8a%a4%e8%bf%9b%e7%a8%8b | Git - Git 守护进程 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 起步 1.1 关于版本控制 1.2 Git 简史 1.3 Git 是什么？ 1.4 命令行 1.5 安装 Git 1.6 初次运行 Git 前的配置 1.7 获取帮助 1.8 总结 2. Git 基础 2.1 获取 Git 仓库 2.2 记录每次更新到仓库 2.3 查看提交历史 2.4 撤消操作 2.5 远程仓库的使用 2.6 打标签 2.7 Git 别名 2.8 总结 3. Git 分支 3.1 分支简介 3.2 分支的新建与合并 3.3 分支管理 3.4 分支开发工作流 3.5 远程分支 3.6 变基 3.7 总结 4. 服务器上的 Git 4.1 协议 4.2 在服务器上搭建 Git 4.3 生成 SSH 公钥 4.4 配置服务器 4.5 Git 守护进程 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第三方托管的选择 4.10 总结 5. 分布式 Git 5.1 分布式工作流程 5.2 向一个项目贡献 5.3 维护项目 5.4 总结 6. GitHub 6.1 账户的创建和配置 6.2 对项目做出贡献 6.3 维护项目 6.4 管理组织 6.5 脚本 GitHub 6.6 总结 7. Git 工具 7.1 选择修订版本 7.2 交互式暂存 7.3 贮藏与清理 7.4 签署工作 7.5 搜索 7.6 重写历史 7.7 重置揭密 7.8 高级合并 7.9 Rerere 7.10 使用 Git 调试 7.11 子模块 7.12 打包 7.13 替换 7.14 凭证存储 7.15 总结 8. 自定义 Git 8.1 配置 Git 8.2 Git 属性 8.3 Git 钩子 8.4 使用强制策略的一个例子 8.5 总结 9. Git 与其他系统 9.1 作为客户端的 Git 9.2 迁移到 Git 9.3 总结 10. Git 内部原理 10.1 底层命令与上层命令 10.2 Git 对象 10.3 Git 引用 10.4 包文件 10.5 引用规范 10.6 传输协议 10.7 维护与数据恢复 10.8 环境变量 10.9 总结 A1. 附录 A: 在其它环境中使用 Git A1.1 图形界面 A1.2 Visual Studio 中的 Git A1.3 Visual Studio Code 中的 Git A1.4 IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 中的 Git A1.5 Sublime Text 中的 Git A1.6 Bash 中的 Git A1.7 Zsh 中的 Git A1.8 PowerShell 中的 Git A1.9 总结 A2. 附录 B: 在你的应用中嵌入 Git A2.1 命令行 Git 方式 A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. 附录 C: Git 命令 A3.1 设置与配置 A3.2 获取与创建项目 A3.3 快照基础 A3.4 分支与合并 A3.5 项目分享与更新 A3.6 检查与比较 A3.7 调试 A3.8 补丁 A3.9 邮件 A3.10 外部系统 A3.11 管理 A3.12 底层命令 2nd Edition 4.5 服务器上的 Git - Git 守护进程 Git 守护进程 接下来我们将通过 “Git” 协议建立一个基于守护进程的仓库。 对于快速且无需授权的 Git 数据访问，这是一个理想之选。 请注意，因为其不包含授权服务，任何通过该协议管理的内容将在其网络上公开。 如果运行在防火墙之外的服务器上，它应该只对那些公开的只读项目服务。 如果运行在防火墙之内的服务器上，它可用于支撑大量参与人员或自动系统 （用于持续集成或编译的主机）只读访问的项目，这样可以省去逐一配置 SSH 公钥的麻烦。 无论何时，该 Git 协议都是相对容易设定的。 通常，你只需要以守护进程的形式运行该命令： $ git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ --reuseaddr 选项允许服务器在无需等待旧连接超时的情况下重启，而 --base-path 选项允许用户在未完全指定路径的条件下克隆项目， 结尾的路径将告诉 Git 守护进程从何处寻找仓库来导出。 如果有防火墙正在运行，你需要开放端口 9418 的通信权限。 你可以通过许多方式将该进程以守护进程的方式运行，这主要取决于你所使用的操作系统。 由于在现代的 Linux 发行版中， systemd 是最常见的初始化系统，因此你可以用它来达到此目的。 只要在 /etc/systemd/system/git-daemon.service 中放一个文件即可，其内容如下： [Unit] Description=Start Git Daemon [Service] ExecStart=/usr/bin/git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Restart=always RestartSec=500ms StandardOutput=syslog StandardError=syslog SyslogIdentifier=git-daemon User=git Group=git [Install] WantedBy=multi-user.target 你可能会注意这里以 git 启动的 Git 驻留程序同时使用了 Group 和 User 权限。 按需修改它并确保提供的用户在此系统上。此外，请确保 Git 二进制文件位于 /usr/bin/git ，必要时可修改此路径。 最后，你需要运行 systemctl enable git-daemon 以让它在系统启动时自动运行， 这样也能让它通过 systemctl start git-daemon 启动，通过 systemctl stop git-daemon 停止。 在其他系统中，你可以使用 sysvinit 系统中的 xinetd 脚本，或者另外的方式来实现——只要你能够将其命令守护进程化并实现监控。 接下来，你需要告诉 Git 哪些仓库允许基于服务器的无授权访问。 你可以在每个仓库下创建一个名为 git-daemon-export-ok 的文件来实现。 $ cd /path/to/project.git $ touch git-daemon-export-ok 该文件将允许 Git 提供无需授权的项目访问服务。 prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/sv/v2/Git-p%c3%a5-servern-Git-Daemonen | Git - Git Daemonen About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Kom igång 1.1 Om versionshantering 1.2 En kort historik av Git 1.3 Vad är Git? 1.4 Kommandoraden 1.5 Installera Git 1.6 Använda Git för första gången 1.7 Få hjälp 1.8 Sammanfattning 2. Grunder i Git 2.1 Skaffa ett Git-förvar 2.2 Spara ändringar till förvaret 2.3 Visa historiken 2.4 Ångra saker 2.5 Jobba med fjärrförvar 2.6 Taggning 2.7 Git alias 2.8 Sammanfattning 3. Git förgreningar 3.1 Grenar i ett nötskal 3.2 Grundläggande förgrening och sammanslagning 3.3 Hantera grenar 3.4 Arbetsflöde med grenar 3.5 Fjärrgrenar 3.6 Grenflytt 3.7 Sammanfattning 4. Git på servern 4.1 Protokollen 4.2 Skaffa Git på en server 4.3 Generera din publika SSH-nyckel 4.4 Konvigurera servern 4.5 Git Daemonen 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Alternativ tillhandahållna av tredje part 4.10 Sammanfattning 5. Distribuerade Git 5.1 Distribuerade arbetsflöden 5.2 Medverka i ett projekt 5.3 Underhålla ett projekt 5.4 Sammanfattning 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Bilaga A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in PowerShell A1.7 Summary A2. Bilaga B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Bilaga C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.5 Git på servern - Git Daemonen Git Daemonen Nu skall vi konfigurera en daemon som tillhandahåller repon över “Git” protokollet. Det är vanligt för snabb icke-autentiserad åtkomst till din Gitdata. Kom ihåg att, eftersom detta inte är en autentiserad tjänst, kommer allt du skickar över protokollet att vara publikt inom dess nätverk. Om du kör detta på en server utanför din brandvägg, skall det bara användas för projekt som är publikt synliga för hela världen. Om servern du kör på ligger innanför din brandvägg kan du använda den för projekt som ett stort antal människor eller datorer (integrations- eller byggservrar) bara har läsrättigheter till och du inte vill lägga till en separat SSH-nyckel för varje. Oavsett vilket är Gitprotokollet relativt lätt att konfigurera. Du behöver i praktiken bara köra detta kommando som en daemonprocess: $ git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Flaggan --reuseaddr tillåter att servern startar om utan att vänta på att gamla anslutningar dör ut, medan flaggan --base-path tillåter folk att klona projekt utan att specificera hela sökvägen. Sökvägen i slutet talar om för Gitdaemonen var den skall leta efter repon för att exportera. Om du kör en brandvägg, kommer du behöva öppna upp port 9418 på den maskin du konfigurerar detta på. Du kan daemonisera processen på olika sätt, beroende på ditt operativsystem. Eftersom systemd är det vanligatste init-systemet på moderna Linuxdistributioner kan du använda den för ändamålet. Lägg helt enkelt en fil i /etc/systemd/system/git-daemon.service med följande innehåll: [Unit] Description=Start Git Daemon [Service] ExecStart=/usr/bin/git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Restart=always RestartSec=500ms StandardOutput=syslog StandardError=syslog SyslogIdentifier=git-daemon User=git Group=git [Install] WantedBy=multi-user.target Du kanske har noterat att Gitdaemonen startas med git som både grupp och användare. Modifiera dem för att passa dina behov och säkerställ att användaren och gruppen existerar på systemet. Kontrollera också att Gitbinären är tillgänglig på /usr/bin/git och ändra sökvägen om nödvändigt. Slutligen behöver du köra systemctl enable git-daemon för att automatiskt starta tjänsten vid uppstart, och starta och stoppa tjänsten med systemctl start git-daemon respektive systemctl stop git-daemon . Upp till och med LTS 14.04, använde Ubuntu enhetskonfiguration av uppstartstjänster. Därför, på Ubuntu 14.04 och tidigare kan du använda ett uppstartsskript. Så därför, i följande fil /etc/init/local-git-daemon.conf lägger du följande skript: start on startup stop on shutdown exec /usr/bin/git daemon \ --user=git --group=git \ --reuseaddr \ --base-path=/srv/git/ \ /srv/git/ respawn Av säkerhetsskäl är det starkt rekommenderat att denna daemon körs som en användare med enbart läsrättigheter till dina repon — du kan lätt göra detta genom att skapa en ny användare git-ro och köra daemonen som den. För enkelhets skull kommer vi köra den som samma git -användare som git-shell kör som. När du startar om din maskin kommer din Gitdaemon starta automatiskt och återstartas om den stoppas. För att starta den utan att behöva starta om kan du köra: $ initctl start local-git-daemon På andra system kanske du vill använda xinetd , ett skript i ditt sysvinit -system eller något annat — så länge som kommandot är daemoniserat och övervakas på något sätt. Nu behöver du tala om för Git vilka repon som tillåts icke-autentiserad Gitserverbaserad åtkomst till. Du kan göra detta för varje repo genom att skapa en fil som heter git-daemon-export-ok . $ cd /path/to/project.git $ touch git-daemon-export-ok Närvaron av den filen talar om för Git att det är OK att tillhandahålla det projektet utan autentisering. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/uk/v2/Git-%d0%bd%d0%b0-%d1%81%d0%b5%d1%80%d0%b2%d0%b5%d1%80%d1%96-%d0%94%d0%b5%d0%bc%d0%be%d0%bd-Git | Git - Демон Git About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Вступ 1.1 Про систему контролю версій 1.2 Коротка історія Git 1.3 Основи Git 1.4 Git, зазвичай, тільки додає дані 1.5 Три стани 1.6 Командний рядок 1.7 Інсталяція Git 1.8 Початкове налаштування Git 1.9 Отримання допомоги 1.10 Підсумок 2. Основи Git 2.1 Створення Git-сховища 2.2 Запис змін до репозиторія 2.3 Перегляд історії комітів 2.4 Скасування речей 2.5 Взаємодія з віддаленими сховищами 2.6 Теґування 2.7 Псевдоніми Git 2.8 Підсумок 3. Галуження в git 3.1 Гілки у кількох словах 3.2 Основи галуження та зливання 3.3 Управління гілками 3.4 Процеси роботи з гілками 3.5 Віддалені гілки 3.6 Перебазовування 3.7 Підсумок 4. Git на сервері 4.1 Протоколи 4.2 Отримання Git на сервері 4.3 Генерація вашого публічного ключа SSH 4.4 Налаштування Серверу 4.5 Демон Git 4.6 Розумний HTTP 4.7 GitWeb 4.8 GitLab 4.9 Варіанти стороннього хостингу 4.10 Підсумок 5. Розподілений Git 5.1 Розподілені процеси роботи 5.2 Внесення змін до проекту 5.3 Супроводжування проекту 5.4 Підсумок 6. GitHub 6.1 Створення та налаштування облікового запису 6.2 Як зробити внесок до проекту 6.3 Супроводжування проєкту 6.4 Керування організацією 6.5 Скриптування GitHub 6.6 Підсумок 7. Інструменти Git 7.1 Вибір ревізій 7.2 Інтерактивне індексування 7.3 Ховання та чищення 7.4 Підписання праці 7.5 Пошук 7.6 Переписування історії 7.7 Усвідомлення скидання (reset) 7.8 Складне злиття 7.9 Rerere 7.10 Зневадження з Git 7.11 Підмодулі 7.12 Пакування 7.13 Заміна 7.14 Збереження посвідчення (credential) 7.15 Підсумок 8. Налаштування Git 8.1 Конфігурація Git 8.2 Атрибути Git 8.3 Гаки (hooks) Git 8.4 Приклад політики користування виконуваної Git-ом 8.5 Підсумок 9. Git and Other Systems 9.1 Git як клієнт 9.2 Міграція на Git 9.3 Підсумок 10. Git зсередини 10.1 Кухонні та парадні команди 10.2 Об’єкти Git 10.3 Посилання Git 10.4 Файли пакунки 10.5 Специфікація посилань (refspec) 10.6 Протоколи передачі 10.7 Супроводження та відновлення даних 10.8 Змінні середовища 10.9 Підсумок A1. Додаток A: Git в інших середовищах A1.1 Графічні інтерфейси A1.2 Git у Visual Studio A1.3 Git в Eclipse A1.4 Git у Bash A1.5 Git у Zsh A1.6 Git у Powershell A1.7 Підсумок A2. Додаток B: Вбудовування Git у ваші застосунки A2.1 Git з командного рядка A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. Додаток C: Команди Git A3.1 Налаштування та конфігурація A3.2 Отримання та створення проектів A3.3 Базове збереження відбитків A3.4 Галуження та зливання A3.5 Поширення й оновлення проектів A3.6 Огляд та порівняння A3.7 Зневаджування A3.8 Латання (patching) A3.9 Електронна пошта A3.10 Зовнішні системи A3.11 Адміністрування A3.12 Кухонні команди 2nd Edition 4.5 Git на сервері - Демон Git Демон Git Тепер встановимо демон, що надає доступ до сховищ за допомогою протоколу ``Git''. Це поширений вибір для швидкого, неавторизовоного доступу до ваших даних Git. Пам’ятайте, що оскільки він не авторизований, все до чого ви надаєте доступ за допомогою цього протоколу стає загальнодоступним у його мережі. Якщо сервер працює за межами вашого мережевого екрану, він має використовуватись виключно для проектів, що є загальнодоступними для світу. Якщо ж сервер працює в межах мережевого екрану, ви можете використовувати його для проектів, до яких велика кількість людей або комп’ютерів (наприклад сервери компіляції чи інтеграції) мають доступ тільки на читання, але ви не хочете додавати ключ SSH для кожного з них. У будь-якому разі, протокол Git легко налаштувати. Вам просто треба виконати цю команду так, щоби вона працювала як демон: $ git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Опція --reuseaddr дозволяє серверу себе перезапускати без очікування, доки старі з’єднання спливуть (time out), а опція --base-path дозволяє клонувати сховища за допомогою шляху відносно значення цієї опції замість повного шляху. Якщо у вас працює мережевий екран, ви також маєте дозволити передачу через порт 9418 машини з Git сервером. Запустити цю команду як демон можна декількома шляхами, в залежності від вашої операційної системи. Найпоширенішою у сучасних дистрибутивах Linux системою запуску є systemd , отже варто її використати для цього. Просто створіть файл /etc/systemd/system/git-daemon.service з таким вмістом: [Unit] Description=Start Git Daemon [Service] ExecStart=/usr/bin/git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Restart=always RestartSec=500ms StandardOutput=syslog StandardError=syslog SyslogIdentifier=git-daemon User=git Group=git [Install] WantedBy=multi-user.target Можливо, ви помітили, що демон Git запускається під користувачем та групою git . Змініть це згідно ваших потреб. Але вказаний користувач має існувати у вашій системі. Також зверніть увагу на шлях до програми Git — відредагуйте /usr/bin/git , якщо є потреба. Нарешті, треба виконати systemctl enable git-daemon , щоб цей сервіс автоматично запускався під час запуску системи. Також ви можете запустити чи зупинити сервіс за допомогою systemctl start git-daemon та systemctl stop git-daemon відповідно. Ubuntu до версії LTS 14.04 використовувала службу Upstart. Для її конфігурації, треба додати до файлу /etc/init/local-git-daemon.conf такий скрипт: start on startup stop on shutdown exec /usr/bin/git daemon \ --user=git --group=git \ --reuseaddr \ --base-path=/srv/git/ \ /srv/git/ respawn З причин безпеки, ми заохочуємо вас запускати цей демон тільки з користувача, що має доступ тільки на читання сховищ — це легко зробити, створивши нового користувача 'git-ro' та запустивши демон з нього. Для простоти ми просто запустимо його з нашого користувача git , з якого працює і git-shell . Коли ви перезавантажите свою машину, демон Git автоматично запуститься та буде сам перезапускатися, якщо він впаде. Щоб запустити його без перезапуску, ви можете виконати: $ initctl start local-git-daemon На інших системах, ви можете використати xinetd , скрипт у теці системи sysvinit , чи щось інше — головне щоб команда запускалась як демон, та можна було перевіряти її статус. Далі, вам треба сказати Git, до яких сховищ дозволяти неавторизований доступ за допомогою сервера Git. Ви можете зробити це в кожному сховищі за допомогою створення файлу під назвою git-daemon-export-ok . $ cd /path/to/project.git $ touch git-daemon-export-ok Присутність цього файлу каже Git, що він може роздавати цей проект без авторизації. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/pt-br/v2/Git-no-servidor-Git-Daemon | Git - Git Daemon About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Começando 1.1 Sobre Controle de Versão 1.2 Uma Breve História do Git 1.3 O Básico do Git 1.4 A Linha de Comando 1.5 Instalando o Git 1.6 Configuração Inicial do Git 1.7 Pedindo Ajuda 1.8 Sumário 2. Fundamentos de Git 2.1 Obtendo um Repositório Git 2.2 Gravando Alterações em Seu Repositório 2.3 Vendo o histórico de Commits 2.4 Desfazendo coisas 2.5 Trabalhando de Forma Remota 2.6 Criando Tags 2.7 Apelidos Git 2.8 Sumário 3. Branches no Git 3.1 Branches em poucas palavras 3.2 O básico de Ramificação (Branch) e Mesclagem (Merge) 3.3 Gestão de Branches 3.4 Fluxo de Branches 3.5 Branches remotos 3.6 Rebase 3.7 Sumário 4. Git no servidor 4.1 Os Protocolos 4.2 Getting Git on a Server 4.3 Gerando Sua Chave Pública SSH 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Sumário 5. Distributed Git 5.1 Fluxos de Trabalho Distribuídos 5.2 Contribuindo com um Projeto 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Configurando uma conta 6.2 Contribuindo em um projeto 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Funcionamento Interno do Git 10.1 Encanamento e Porcelana 10.2 Objetos do Git 10.3 Referências do Git 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Variáveis de ambiente 10.9 Sumário A1. Appendix A: Git em Outros Ambientes A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Resumo A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.5 Git no servidor - Git Daemon Git Daemon Next we’ll set up a daemon serving repositories over the “Git” protocol. This is common choice for fast, unauthenticated access to your Git data. Remember that since it’s not an authenticated service, anything you serve over this protocol is public within its network. If you’re running this on a server outside your firewall, it should only be used for projects that are publicly visible to the world. If the server you’re running it on is inside your firewall, you might use it for projects that a large number of people or computers (continuous integration or build servers) have read-only access to, when you don’t want to have to add an SSH key for each. In any case, the Git protocol is relatively easy to set up. Basically, you need to run this command in a daemonized manner: $ git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ --reuseaddr allows the server to restart without waiting for old connections to time out, the --base-path option allows people to clone projects without specifying the entire path, and the path at the end tells the Git daemon where to look for repositories to export. If you’re running a firewall, you’ll also need to punch a hole in it at port 9418 on the box you’re setting this up on. You can daemonize this process a number of ways, depending on the operating system you’re running. On an Ubuntu machine, you can use an Upstart script. So, in the following file /etc/init/local-git-daemon.conf you put this script: start on startup stop on shutdown exec /usr/bin/git daemon \ --user=git --group=git \ --reuseaddr \ --base-path=/srv/git/ \ /srv/git/ respawn For security reasons, it is strongly encouraged to have this daemon run as a user with read-only permissions to the repositories – you can easily do this by creating a new user git-ro and running the daemon as them. For the sake of simplicity we’ll simply run it as the same git user that git-shell is running as. When you restart your machine, your Git daemon will start automatically and respawn if it goes down. To get it running without having to reboot, you can run this: $ initctl start local-git-daemon On other systems, you may want to use xinetd , a script in your sysvinit system, or something else – as long as you get that command daemonized and watched somehow. Next, you have to tell Git which repositories to allow unauthenticated Git server-based access to. You can do this in each repository by creating a file named git-daemon-export-ok . $ cd /path/to/project.git $ touch git-daemon-export-ok The presence of that file tells Git that it’s OK to serve this project without authentication. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://sre.google/books/building-secure-reliable-systems/ | Google SRE book- Comprehensive guide to site reliability Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content SRE Books Read online View details Read online View details Book updates Read online View details Building Secure & Reliable Systems By: Heather Adkins, Betsy Beyer, Paul Blankinship, Ana Oprea, Piotr Lewandowski, Adam Stubblefield Can a system be considered truly reliable if it isn't fundamentally secure? Or can it be considered secure if it's unreliable? Security is crucial to the design and operation of scalable systems in production, as it plays an important part in product quality, performance, and availability. In this book, experts from Google share best practices to help your organization design scalable and reliable systems that are fundamentally secure. Buy from Google Books Read online The Site Reliability Workbook Edited by: Betsy Beyer, Niall Richard Murphy, David K. Rensin, Kent Kawahara and Stephen Thorne The Site Reliability Workbook is the hands-on companion to the bestselling Site Reliability Engineering book and uses concrete examples to show how to put SRE principles and practices to work. This book contains practical examples from Google’s experiences and case studies from Google’s Cloud Platform customers. Evernote, The Home Depot, The New York Times, and other companies outline hard-won experiences of what worked for them and what didn’t. Buy from Google Books Read online Site Reliability Engineering Edited by: Betsy Beyer, Chris Jones, Jennifer Petoff and Niall Richard Murphy Members of the SRE team explain how their engagement with the entire software lifecycle has enabled Google to build, deploy, monitor, and maintain some of the largest software systems in the world. Buy from Google Books Read online Interested in joining SRE? Google strives to cultivate an inclusive workplace. We believe diversity of perspectives and ideas leads to better discussions, decisions, and outcomes for everyone. Explore SRE opportunities at Google Follow us About Google Google products Privacy Terms Help | 2026-01-13T09:29:20 |
https://git-scm.com/book/ms/v2/Git-on-the-Server-Git-Daemon | Git - Git Daemon About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Getting Started 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Summary 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.5 Git on the Server - Git Daemon Git Daemon Next we’ll set up a daemon serving repositories using the “Git” protocol. This is a common choice for fast, unauthenticated access to your Git data. Remember that since this is not an authenticated service, anything you serve over this protocol is public within its network. If you’re running this on a server outside your firewall, it should be used only for projects that are publicly visible to the world. If the server you’re running it on is inside your firewall, you might use it for projects that a large number of people or computers (continuous integration or build servers) have read-only access to, when you don’t want to have to add an SSH key for each. In any case, the Git protocol is relatively easy to set up. Basically, you need to run this command in a daemonized manner: $ git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ The --reuseaddr option allows the server to restart without waiting for old connections to time out, while the --base-path option allows people to clone projects without specifying the entire path, and the path at the end tells the Git daemon where to look for repositories to export. If you’re running a firewall, you’ll also need to punch a hole in it at port 9418 on the box you’re setting this up on. You can daemonize this process a number of ways, depending on the operating system you’re running. Since systemd is the most common init system among modern Linux distributions, you can use it for that purpose. Simply place a file in /etc/systemd/system/git-daemon.service with these contents: [Unit] Description=Start Git Daemon [Service] ExecStart=/usr/bin/git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Restart=always RestartSec=500ms StandardOutput=syslog StandardError=syslog SyslogIdentifier=git-daemon User=git Group=git [Install] WantedBy=multi-user.target You might have noticed that Git daemon is started here with git as both group and user. Modify it to fit your needs and make sure the provided user exists on the system. Also, check that the Git binary is indeed located at /usr/bin/git and change the path if necessary. Finally, you’ll run systemctl enable git-daemon to automatically start the service on boot, and can start and stop the service with, respectively, systemctl start git-daemon and systemctl stop git-daemon . On other systems, you may want to use xinetd , a script in your sysvinit system, or something else — as long as you get that command daemonized and watched somehow. Next, you have to tell Git which repositories to allow unauthenticated Git server-based access to. You can do this in each repository by creating a file named git-daemon-export-ok . $ cd /path/to/project.git $ touch git-daemon-export-ok The presence of that file tells Git that it’s OK to serve this project without authentication. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/fa/v2/%d8%a7%d9%86%d8%b4%d8%b9%d8%a7%d8%a8%e2%80%8c%da%af%db%8c%d8%b1%db%8c-%d8%af%d8%b1-%da%af%db%8c%d8%aa-Git-Branching-%d8%a8%d8%a7%d8%b2%d9%be%d8%a7%db%8c%d9%87%e2%80%8c%da%af%d8%b0%d8%a7%d8%b1%db%8c-Rebasing | Git - بازپایهگذاری (Rebasing) About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. شروع به کار (getting started) 1.1 درباره ورژن کنترل (About Version Control) 1.2 تاریخچه کوتاهی از گیت (A Short History of Git) 1.3 گیت چیست؟ (What is Git) 1.4 نصب گیت (Installing Git) 1.5 ستاپ اولیه گیت (First-Time Git Setup) 1.6 دریافت کمک (Getting Help) 1.7 خلاصه (summary) 2. مقدمات گیت (git basics chapter) 2.1 گرفتن یک مخزن گیت (Getting a Git Repository) 2.2 ثبت تغییرات در مخزن (Recording Changes to the Repository) 2.3 مشاهده تاریخچه کامیتها (Viewing the Commit History) 2.4 بازگرداندن تغییرات (Undoing Things) 2.5 کار کردن با ریموت ها (Working with Remotes) 2.6 تگ کردن (Tagging) 2.7 نام مستعار گیت (Git Aliases) 2.8 خلاصه (summary) 3. انشعابگیری در گیت (Git Branching) 3.1 شاخهها در یک نگاه (Branches in a Nutshell) 3.2 شاخهبندی و ادغام پایهای (Basic Branching and Merging) 3.3 مدیریت شاخهها (Branch Management) 3.4 روندهای کاری شاخهها (Branching Workflows) 3.5 شاخههای راه دور (Remote Branches) 3.6 بازپایهگذاری (Rebasing) 3.7 خلاصه (Summary) 4. گیت روی سرور (Git on the server) 4.1 پروتکلها (The Protocols) 4.2 راهاندازی گیت روی یک سرور (Getting Git on a Server) 4.3 ایجاد کلید عمومی SSH شما (Generating Your SSH Public Key) 4.4 نصب و راهاندازی سرور (Setting up server) 4.5 سرویسدهنده گیت (Git Daemon) 4.6 HTTP هوشمند (Smart HTTP) 4.7 گیتوب (GitWeb) 4.8 گیتلب (GitLab) 4.9 گزینههای میزبانی شخص ثالث (Third Party Hosted Options) 4.10 خلاصه (Summary) 5. گیت توزیعشده (Distributed git) 5.1 جریانهای کاری توزیعشده (Distributed Workflows) 5.2 مشارکت در یک پروژه (Contributing to a Project) 5.3 نگهداری یک پروژه (Maintaining a Project) 5.4 خلاصه (Summary) 6. گیت هاب (GitHub) 6.1 راهاندازی و پیکربندی حساب کاربری (Account Setup and Configuration) 6.2 مشارکت در یک پروژه (Contributing to a Project) 6.3 نگهداری یک پروژه (Maintaining a Project) 6.4 مدیریت یک سازمان (Managing an organization) 6.5 اسکریپتنویسی در گیتهاب (Scripting GitHub) 6.6 خلاصه (Summary) 7. ابزارهای گیت (Git Tools) 7.1 انتخاب بازبینی (Revision Selection) 7.2 مرحلهبندی تعاملی (Interactive Staging) 7.3 ذخیره موقت و پاکسازی (Stashing and Cleaning) 7.4 امضای کارهای شما (Signing Your Work) 7.5 جستجو (Searching) 7.6 بازنویسی تاریخچه (Rewriting History) 7.7 بازنشانی به زبان ساده (Reset Demystified) 7.8 ادغام پیشرفته (Advanced Merging) 7.9 بازاستفاده خودکار از حل تضادها (Rerere) 7.10 اشکالزدایی با گیت (Debugging with Git) 7.11 سابماژول ها (Submodules) 7.12 بستهبندی (Bundling) 7.13 جایگزینی (Replace) 7.14 ذخیرهسازی اطلاعات ورود (Credential Storage) 7.15 خلاصه (Summary) 8. سفارشیسازی Git (Customizing Git) 8.1 پیکربندی گیت (Git Configuration) 8.2 ویژگیهای گیت (Git Attributes) 8.3 هوکهای گیت (Git Hooks) 8.4 یک نمونه سیاست اعمال شده توسط گیت (An Example Git-Enforced Policy) 8.5 خلاصه (Summary) 9. گیت و سیستمهای دیگر (Git and Other Systems) 9.1 گیت بهعنوان کلاینت (Git as a Client) 9.2 مهاجرت به گیت (Migrating to Git) 9.3 خلاصه (Summary) 10. مباحث درونی گیت (Git Internals) 10.1 ابزارها و دستورات سطح پایین (Plumbing and Porcelain) 10.2 اشیا گیت (Git Objects) 10.3 مراجع گیت (Git References) 10.4 فایلهای بسته (Packfiles) 10.5 نگاشت (The Refspec) 10.6 پروتکلهای انتقال (Transfer Protocols) 10.7 نگهداری و بازیابی دادهها (Maintenance and Data Recovery) 10.8 متغیرهای محیطی (Environment Variables) 10.9 خلاصه (Summary) A1. پیوست A: گیت در محیطهای دیگر (Git in Other Environments) A1.1 رابط های گرافیکی (Graphical Interfaces) A1.2 گیت در ویژوال استودیو (Git in Visual Studio) A1.3 گیت در Visual Studio Code (Git in Visual Studio Code) A1.4 گیت در IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine (Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine) A1.5 گیت در Sublime Text (Git in Sublime Text) A1.6 گیت در بش (Git in Bash) A1.7 گیت در Zsh (Git in Zsh) A1.8 گیت در PowerShell (Git in PowerShell) A1.9 خلاصه (Summary) A2. پیوست B: گنجاندن گیت در برنامههای شما (Embedding Git in your Applications) A2.1 خط فرمان گیت (Command-line Git) A2.2 کتابخانهٔ گیت به زبان سی (Libgit2) A2.3 کتابخانه گیت برای زبان جاوا (JGit) A2.4 کتابخانه گیت برای زبان گو (go-git) A2.5 کتابخانه گیت پایتون (Dulwich) A3. پیوست C: دستورات گیت (Git Commands) A3.1 تنظیم و پیکربندی (Setup and Config) A3.2 گرفتن و ایجاد پروژهها (Getting and Creating Projects) A3.3 نمونهبرداری پایهای (Basic Snapshotting) A3.4 انشعابگیری و ادغام (Branching and Merging) A3.5 بهاشتراکگذاری و بهروزرسانی پروژهها (Sharing and Updating Projects) A3.6 بازرسی و مقایسه (Inspection and Comparison) A3.7 عیبیابی (Debugging) A3.8 اعمال تغییرات به صورت پچ (Patching) A3.9 ایمیل (Email) A3.10 سیستمهای خارجی (External Systems) A3.11 مدیریت (Administration) A3.12 دستورات سطح پایین گیت (Plumbing Commands) 2nd Edition 3.6 انشعابگیری در گیت (Git Branching) - بازپایهگذاری (Rebasing) بازپایهگذاری (Rebasing) در گیت، دو روش اصلی برای ادغام تغییرات از یک شاخه به شاخه دیگر وجود دارد: دستور merge و دستور rebase . در این بخش خواهید آموخت که بازپایهگذاری چیست، چگونه انجام میشود، چرا این ابزار بسیار کاربردی است و در چه مواردی بهتر است از آن استفاده نکنید. بازپایهگذاری پایه (The Basic Rebase) اگر به مثالی که در بخش ادغام پایهای (Basic Merging) آوردیم رجوع کنید، میبینید که کارتان را از هم جدا کردهاید و تغییراتی را روی دو شاخه متفاوت ایجاد کردهاید. نمودار 35. Simple divergent history سادهترین روش برای ادغام شاخهها، همانطور که پیشتر توضیح دادیم، دستور merge است. این دستور یک ادغام سهطرفه بین دو آخرین تصویر شاخهها ( C3 و C4 ) و آخرین جد مشترک آنها ( C2 ) انجام میدهد و یک تصویر (commit) جدید ایجاد میکند. نمودار 36. Merging to integrate diverged work history اما راه دیگری نیز وجود دارد: میتوانید تغییراتی را که در C4 ایجاد شدهاند برداشته و مجدداً روی C3 اعمال کنید. در گیت به این کار «بازپایهگذاری» گفته میشود. با دستور rebase میتوانید تمام تغییراتی که در یک شاخه ثبت شدهاند را گرفته و دوباره روی شاخهای دیگر اجرا کنید. برای این مثال، ابتدا شاخه experiment را چکاوت میکنید و سپس آن را روی شاخه master بازپایهگذاری میکنید، به این صورت: $ git checkout experiment $ git rebase master First, rewinding head to replay your work on top of it... Applying: added staged command این عملیات با رفتن به جد مشترک دو شاخه (شاخه فعلی و شاخهای که میخواهید بازپایهگذاری کنید)، گرفتن تفاوتهایی که هر کامیت روی شاخه فعلی ایجاد کرده، ذخیره این تفاوتها در فایلهای موقتی، ریست کردن شاخه فعلی به همان کامیتی که شاخه مقصد دارد، و در نهایت اعمال هر تغییر به ترتیب انجام میشود. نمودار 37. Rebasing the change introduced in C4 onto C3 در این مرحله، میتوانید دوباره به شاخه master برگردید و یک ادغام fast-forward انجام دهید. $ git checkout master $ git merge experiment نمودار 38. Fast-forwarding the master branch اکنون تصویری که شاخه C4' به آن اشاره میکند دقیقاً همان است که در the merge example شاخه C5 به آن اشاره داشت. در نهایت محصول ادغام تفاوتی ندارد، اما بازپایهگذاری تاریخچهای تمیزتر و منظمتر ایجاد میکند. اگر لاگ شاخهای که بازپایهگذاری شده را بررسی کنید، تاریخچه به صورت خطی دیده میشود؛ یعنی انگار همه کارها به صورت سری انجام شدهاند، حتی اگر در ابتدا به طور موازی بودند. اغلب این کار را برای اطمینان از اینکه کامیتهای شما بهصورت تمیز روی شاخه ریموت اعمال میشوند انجام میدهید — مثلاً در پروژهای که میخواهید در آن مشارکت کنید اما مسئولیت نگهداری آن را ندارید. در این حالت، کارتان را در یک شاخه انجام میدهید و وقتی آماده ارسال تغییرات به پروژه اصلی شدید، کارتان را روی origin/master بازپایهگذاری میکنید. به این ترتیب، مسئول نگهداری پروژه نیازی به انجام ادغام دستی ندارد — فقط یک fast-forward یا اعمال تمیز تغییرات خواهد بود. توجه داشته باشید که اسنپشاتی که توسط آخرین کامیتی که در نهایت به آن میرسید اشاره میشود، چه آخرین کامیتهای بازبیس شده در یک بازبیس باشند یا کامیت نهایی ادغام بعد از یک مرج، همان اسنپشات است — تنها تاریخچه است که متفاوت است. بازبیس کردن تغییرات را به ترتیبی که معرفی شدهاند، از یک شاخه کاری روی شاخه دیگری بازپخش میکند، در حالی که مرج گرفتن نقاط انتهایی شاخهها را گرفته و آنها را با هم ادغام میکند. بازپایهگذاریهای جالبتر (More Interesting Rebases) شما همچنین میتوانید بازبیس خود را روی چیزی غیر از شاخه هدف بازبیس اجرا کنید. برای مثال، یک تاریخچه مثل A history with a topic branch off another topic branch را در نظر بگیرید. شما یک شاخه موضوعی به نام server ایجاد کردید تا عملکردهای سمت سرور را به پروژهتان اضافه کنید و یک کامیت انجام دادید. سپس، از آن شاخه انشعاب گرفتید تا تغییرات سمت کلاینت ( client ) را ایجاد کنید و چندین بار کامیت کردید. در نهایت، به شاخه server برگشتید و چند کامیت دیگر انجام دادید. نمودار 39. A history with a topic branch off another topic branch فرض کنید تصمیم گرفتهاید تغییرات سمت کلاینت را برای انتشار به شاخه اصلی خود مرج کنید، اما میخواهید تغییرات سمت سرور را تا زمان آزمایش بیشتر نگه دارید. شما میتوانید تغییرات روی شاخه client که روی server نیستند ( C8 و C9 ) را با گزینه --onto در دستور git rebase روی شاخه master بازپخش کنید: $ git rebase --onto master server client این اساساً میگوید: «شاخه client را بگیر، پچهایی را که از زمانی که از شاخه server جدا شدهاند پیدا کن، و این پچها را در شاخه client طوری بازپخش کن که گویی مستقیماً روی شاخه master پایهگذاری شدهاند.» این کمی پیچیده است، اما نتیجه بسیار جالب است. نمودار 40. Rebasing a topic branch off another topic branch حالا میتوانید شاخه master را بهصورت fast-forward جلو ببرید (نگاه کنید به Fast-forwarding your master branch to include the client branch changes ): $ git checkout master $ git merge client نمودار 41. Fast-forwarding your master branch to include the client branch changes فرض کنید تصمیم میگیرید شاخه server را هم وارد کنید. میتوانید شاخه server را بدون نیاز به چکاوت کردن قبلی، روی شاخه master بازبیس کنید با اجرای دستور git rebase <basebranch> <topicbranch> — که شاخه موضوع (در اینجا server ) را برای شما چکاوت میکند و روی شاخه پایه ( master ) بازپخش میکند: $ git rebase master server این کار، تغییرات شاخه server را روی تغییرات شاخه master بازپخش میکند، همانطور که در Rebasing your server branch on top of your master branch نشان داده شده است. نمودار 42. Rebasing your server branch on top of your master branch سپس میتوانید شاخه پایه ( master ) را fast-forward کنید: $ git checkout master $ git merge server میتوانید شاخههای client و server را حذف کنید چون تمام کارها ادغام شده و دیگر به آنها نیازی ندارید، و تاریخچه شما برای کل این فرایند مشابه Final commit history خواهد بود. $ git branch -d client $ git branch -d server نمودار 43. Final commit history خطرات بازپایهگذاری (The Perils of Rebasing) آه، اما لذت بازبیس کردن بدون معایب نیست، که میتوان آن را در یک جمله خلاصه کرد: کامیتهایی را که خارج از مخزن شما وجود دارند و ممکن است دیگران روی آنها کار کرده باشند، بازبیس نکنید. اگر این دستورالعمل را رعایت کنید، مشکلی نخواهید داشت. اگر رعایت نکنید، دیگران از شما متنفر خواهند شد و دوستان و خانواده شما را تحقیر خواهند کرد. هنگامی که بازبیس میکنید، شما کامیتهای موجود را رها کرده و کامیتهای جدیدی میسازید که شبیه آنها اما متفاوت هستند. اگر کامیتهایی را جایی پوش کنید و دیگران آنها را کلون و روی آنها کار کنند، سپس شما با git rebase آن کامیتها را بازنویسی کرده و دوباره پوش کنید، همکاران شما مجبور خواهند بود کارهایشان را دوباره ادغام کنند و وقتی بخواهید تغییراتشان را به کار خودتان برگردانید، اوضاع پیچیده و نامرتب خواهد شد. بیایید مثالی از مشکلات بازبیس کردن تغییراتی که عمومی کردهاید را بررسی کنیم. فرض کنید از یک سرور مرکزی کلون کردهاید و سپس روی آن کارهایی انجام دادهاید. تاریخچه کامیتهای شما به این شکل است: نمودار 44. Clone a repository, and base some work on it حالا، شخص دیگری کار بیشتری انجام میدهد که شامل یک ادغام (merge) است و آن کار را به سرور مرکزی ارسال میکند. شما آن را دریافت میکنید و شاخهی جدید راه دور را با کار خود ادغام میکنید، به طوری که تاریخچهی شما چیزی شبیه به این میشود: نمودار 45. Fetch more commits, and merge them into your work بعداً، همان شخصی که کار ادغامشده را ارسال کرده است تصمیم میگیرد به عقب برگردد و کار خود را مجدداً بازبیس (rebase) کند؛ او با دستور git push --force تاریخچهی سرور را بازنویسی میکند. سپس شما از آن سرور دریافت میکنید و کمیتهای جدید را میآورید. نمودار 46. Someone pushes rebased commits, abandoning commits you’ve based your work on حالا هر دوی شما در وضعیتی دشوار قرار دارید. اگر دستور git pull اجرا کنید، یک کمیت ادغام (merge commit) ایجاد میشود که هر دو خط تاریخچه را شامل میشود و مخزن شما به این شکل در میآید: نمودار 47. You merge in the same work again into a new merge commit اگر وقتی تاریخچهتان به این شکل است دستور git log بزنید، دو کمیت با همان نویسنده، تاریخ و پیام خواهید دید که باعث سردرگمی میشود. علاوه بر این، اگر این تاریخچه را دوباره به سرور بفرستید، تمام کمیتهای بازبیسشده را دوباره به سرور مرکزی وارد میکنید که ممکن است باعث سردرگمی بیشتر شود. به طور منطقی میتوان فرض کرد توسعهدهندهی دیگر نمیخواهد کمیتهای C4 و C6 در تاریخچه باشند؛ به همین دلیل است که ابتدا کارش را بازبیس کرده بود. بازپایهگذاری هنگام بازپایهگذاری (Rebase When You Rebase) اگر در چنین وضعیتی قرار گرفتید، گیت جادوهای دیگری هم دارد که شاید به شما کمک کند. اگر کسی در تیم شما تغییراتی را با force push ارسال کند که کاری را که شما بر اساس آن کار کردهاید بازنویسی کند، چالش شما این است که بفهمید چه چیزی مال شماست و چه چیزی توسط آنها بازنویسی شده است. گیت علاوه بر محاسبهی شناسه SHA-1 کمیت، یک شناسهی دیگری هم بر اساس تغییرات وارد شده در کمیت محاسبه میکند که به آن “patch-id” میگویند. اگر شما کاری را که بازنویسی شده دریافت کنید و آن را روی کمیتهای جدید همتیمیتان بازبیس کنید، گیت اغلب میتواند تشخیص دهد که چه تغییراتی مختص شماست و آنها را دوباره روی شاخه جدید اعمال کند. برای مثال، در سناریوی قبلی، اگر به جای ادغام در مرحلهی Someone pushes rebased commits, abandoning commits you’ve based your work on دستور git rebase teamone/master را اجرا کنیم، گیت این کارها را انجام میدهد: * تشخیص میدهد چه کارهایی منحصر به شاخهی ماست ( C2 ، C3 ، C4 ، C6 ، C7 ) * تشخیص میدهد کدام کمیتها ادغام نیستند ( C2 ، C3 ، C4 ) * تشخیص میدهد کدامها هنوز در شاخهی هدف بازنویسی نشدهاند (فقط C2 و C3 ، چون C4 همان تغییر C4' است) * آن کمیتها را روی رأس teamone/master اعمال میکند پس به جای نتیجهای که در You merge in the same work again into a new merge commit دیدیم، چیزی شبیه به Rebase on top of force-pushed rebase work خواهیم داشت. نمودار 48. Rebase on top of force-pushed rebase work این فقط زمانی جواب میدهد که C4 و C4' که همتیمی شما ساخته تقریباً همان اصلاحات یکسان باشند. در غیر این صورت، بازبیس نمیتواند تشخیص دهد که این یک نسخهی تکراری است و یک تغییر شبیه C4 دیگر اضافه خواهد کرد (که احتمالاً به درستی اعمال نمیشود، چون تغییرات قبلاً تا حدی وجود دارند). شما همچنین میتوانید این کار را با اجرای دستور git pull --rebase به جای git pull معمولی سادهتر کنید. یا میتوانید به صورت دستی ابتدا git fetch بگیرید و سپس دستور git rebase teamone/master را اجرا کنید. اگر میخواهید git pull به طور پیشفرض با گزینه --rebase اجرا شود، میتوانید مقدار pull.rebase را با دستور git config --global pull.rebase true تنظیم کنید. اگر کمیتهایی را بازبیس میکنید که هرگز از کامپیوتر خودتان خارج نشدهاند، هیچ مشکلی نخواهید داشت. اگر کمیتهایی را بازبیس میکنید که قبلاً ارسال شدهاند، اما هیچ کس دیگری بر اساس آنها کار نکرده است، باز هم مشکلی پیش نمیآید. اما اگر کمیتهایی را بازبیس کنید که قبلاً به صورت عمومی ارسال شدهاند و دیگران بر اساس آنها کار کردهاند، ممکن است با مشکلات ناامیدکنندهای روبرو شوید و همکارانتان از شما ناراضی شوند. اگر شما یا همتیمیتان در جایی مجبور شدید این کار را انجام دهید، مطمئن شوید همه میدانند که باید از دستور git pull --rebase استفاده کنند تا دردسرهای بعدی کمی کمتر شود. بازپایهگذاری در مقابل ادغام (Rebase vs. Merge) حالا که بازبیس و ادغام را در عمل دیدهاید، شاید بپرسید کدام بهتر است؟ قبل از پاسخ دادن، کمی عقبتر میرویم و دربارهی مفهوم تاریخچه صحبت میکنیم. یک دیدگاه این است که تاریخچهی کمیتهای مخزن شما، ثبت آنچه واقعاً اتفاق افتاده است. این یک سند تاریخی است که ارزش خاص خود را دارد و نباید دستکاری شود. از این زاویه، تغییر تاریخچهی کمیتها تقریباً یک عمل ناپسند است؛ انگار دربارهی آنچه واقعاً رخ داده دروغ میگویید. پس اگر یک سری کمیت ادغام نامرتب وجود داشته باشد، این همانا همان چیزی است که اتفاق افتاده و مخزن باید این را برای آیندگان حفظ کند. دیدگاه مخالف این است که تاریخچه کامیتها، داستان چگونگی ساخته شدن پروژه شما است. شما اولین پیشنویس یک کتاب را منتشر نمیکنید، پس چرا کار درهموبرهم خود را نشان دهید؟ وقتی روی پروژهای کار میکنید، ممکن است به رکورد تمام اشتباهات و مسیرهای بنبست خود نیاز داشته باشید، اما وقتی زمان نمایش کار به جهان میرسد، شاید بخواهید داستان منسجمتری درباره چگونگی رسیدن از نقطه A به B تعریف کنید. افراد این دسته از ابزارهایی مانند rebase و filter-branch برای بازنویسی کامیتهایشان قبل از ادغام در شاخه اصلی استفاده میکنند. آنها از این ابزارها برای بیان داستان به شکلی که برای خوانندگان آینده بهتر باشد بهره میبرند. حالا درباره این سؤال که ادغام (merge) بهتر است یا بازپایهگذاری (rebase): امیدوارم متوجه شده باشید که پاسخ سادهای ندارد. گیت ابزاری قدرتمند است و به شما امکان انجام کارهای زیادی روی تاریخچه میدهد، اما هر تیم و هر پروژهای متفاوت است. حالا که میدانید هر دو روش چگونه کار میکنند، انتخاب بهترین گزینه برای وضعیت خاص خودتان بر عهده شماست. میتوانید بهترینهای هر دو را داشته باشید: تغییرات محلی را قبل از ارسال با rebase مرتب کنید تا کارتان تمیز شود، اما هرگز چیزی را که جایی ارسال کردهاید دوباره بازپایهگذاری نکنید. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/netscout-arbor-sightline/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_image-click | Arbor Sightline | LinkedIn Skip to main content LinkedIn NETSCOUT in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Arbor Sightline Network Monitoring Software by NETSCOUT See who's skilled in this Add as skill Learn more Report this product About The network is the business. Operators must optimize resources, reduce service availability threats and thus save money. Arbor Sightline provides robust capabilities from network-wide capacity planning, to identifying and managing the mitigation of threats to the network. This pervasive network data can also be leveraged to make routing and peering design decisions, lower transit costs, eliminate network threats and provide your business with new revenue-generating services. Arbor’s DDoS attack protection solutions are based upon industry-leading technology. NETSCOUT offers a comprehensive portfolio of fully integrated, in‑cloud and on-premise DDoS protection products and services; all backed by continuous global threat intelligence. Media Products media viewer No more previous content Detecting and Mitigation a DDoS Attack Utilizing Arbor Sightline and TMS Learn how to detect and mitigate a DDoS Attack using NETSCOUT Arbor Sightline and TMS on a large enterprise or service provider network. Here, we demonstrate how DDoS Mitigation can be carried out by first detecting the attack and then automatically beginning mitigation using Arbor TMS. Multi-vector DDoS attacks are threats to all networks. In this example, NETSCOUT shows how Arbor Sightline and TMS can be used to detect and protect against an attack on a server farm. Threat Detection Through proactive detection of network or service availability threats, Sightline can quickly diagnose and manage DDoS attacks. Network Capacity Management You can employ Sightline to monitor the capacity of network infrastructure, which allows you to avoid saturation and re-engineer network traffic for more efficient utilization. Network Peering Analysis Your network delivers value to customers and users when it connects to other networks. Peering analysis helps determine what traffic can transfer off of expensive transit links to either free peering or even become revenue-generating as a new customer. Arbor Sightline Infrastructure No more next content Similar products NMS NMS Network Monitoring Software Network Operations Center (NOC) Network Operations Center (NOC) Network Monitoring Software TEMS™ Suite TEMS™ Suite Network Monitoring Software Progress Flowmon Progress Flowmon Network Monitoring Software ASM ASM Network Monitoring Software ONES (Open Networking Enterprise Suite) ONES (Open Networking Enterprise Suite) Network Monitoring Software Sign in to see more Show more Show less NETSCOUT products Arbor Edge Defense Arbor Edge Defense DDoS Protection Software Arbor Cloud DDoS Protection Arbor Cloud DDoS Protection DDoS Protection Software Arbor Threat Mitigation System (TMS) Arbor Threat Mitigation System (TMS) DDoS Protection Software InfiniStreamNG (ISNG) InfiniStreamNG (ISNG) Business Continuity Software nGenius Business Analytics nGenius Business Analytics Business Intelligence (BI) Software nGeniusONE nGeniusONE Application Performance Monitoring (APM) Software nGeniusPULSE nGeniusPULSE Network Management Software Omnis Threat Horizon Omnis Threat Horizon DDoS Protection Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/salesforce-agentforce/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_image-click | Agentforce | LinkedIn Skip to main content LinkedIn Salesforce in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Agentforce Product by Salesforce See who's skilled in this Add as skill Learn more Report this product About Build and deploy AI agents at scale on the world's #1 digital labor platform. Agentforce brings digital labor to every employee, department, and business process to augment employees and improve customer experiences. Agentforce works with your existing apps, data, and business logic and can take action across your entire enterprise. And it’s built on the trusted Salesforce platform, so your data always stays safe. Similar products LinkedIn Recruiter LinkedIn Recruiter Recruiting Software LinkedIn Sales Navigator LinkedIn Sales Navigator Sales Intelligence Software Facebook Facebook Social Networking Software LinkedIn Learning AI-powered Coaching LinkedIn Learning AI-powered Coaching AI-Powered Coaching Software LinkedIn Jobs LinkedIn Jobs Job Boards Software LinkedIn Interview Prep AI LinkedIn Interview Prep AI AI-Powered Coaching Software Sign in to see more Show more Show less Salesforce products Commerce Cloud Commerce Cloud E-Commerce Platforms Data Cloud Data Cloud Customer Data Platforms (CDP) Marketing Cloud Marketing Cloud Marketing Automation Software Net Zero Cloud Net Zero Cloud Data Management Platforms (DMP) Sales Cloud Sales Cloud Customer Relationship Management (CRM) Software Salesforce CRM Salesforce CRM Customer Data Platforms (CDP) Salesforce Platform Salesforce Platform Low-Code Development Platforms Slack Slack Cloud Communications Platforms Tableau Tableau Business Intelligence (BI) Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/cloudflare-ddos-protection/?trk=products_seo_search | Cloudflare DDoS Protection | LinkedIn Skip to main content LinkedIn Cloudflare in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Cloudflare DDoS Protection DDoS Protection Software by Cloudflare See who's skilled in this Add as skill Get started Report this product About Comprehensive DDoS Protection Built for anything connected to the Internet Cloudflare DDoS protection secures websites, applications, and entire networks while ensuring the performance of legitimate traffic is not compromised. Cloudflare’s 51 Tbps network blocks an average of 72 billion threats per day, including some of the largest DDoS attacks in history. Media Products media viewer No more previous content DDoS Protection, WAF, CDN and more from Cloudflare Built for anything connected to the Internet Cloudflare offers three DDoS protection solutions designed to protect everything on your cloud and on-premise networks. How Cloudflare protects network infrastructure from DDoS attacks Cloudflare Magic Transit uses our entire anycast network, which spans hundreds of global cities, to detect and mitigate DDoS attacks at the network edge. What Is A DDoS Attack? DDoS attacks represent one of the greatest threats to websites and services. No more next content Featured customers of Cloudflare DDoS Protection Chrono24 Retail Luxury Goods and Jewelry 15,639 followers Upwork Software Development 3,294,409 followers Carousell Group Software Development 129,533 followers Hemnet Real Estate 12,582 followers Trendyol Group Technology, Information and Internet 536,123 followers BookMyShow Entertainment Providers 125,692 followers 早稲田大学 WASEDA University Higher Education 112,057 followers Axios Internet News 75,402 followers Wongnai.com Information Services 5,546 followers Show more Show less Similar products Cloudflare Spectrum Cloudflare Spectrum DDoS Protection Software Akamai Prolexic Routed Akamai Prolexic Routed DDoS Protection Software OVHcloud Anti-DDoS Protection OVHcloud Anti-DDoS Protection DDoS Protection Software Kona DDoS Defender Kona DDoS Defender DDoS Protection Software Kaspersky DDoS Protection Kaspersky DDoS Protection DDoS Protection Software Arbor Cloud DDoS Protection Arbor Cloud DDoS Protection DDoS Protection Software Sign in to see more Show more Show less Cloudflare products Argo Smart Routing Argo Smart Routing Network Management Software Cloudflare DNS Cloudflare DNS Managed DNS Services Software Cloudflare Load Balancing Cloudflare Load Balancing Load Balancing Software Cloudflare Registrar Cloudflare Registrar Managed DNS Services Software Cloudflare Spectrum Cloudflare Spectrum DDoS Protection Software Cloudflare SSL / TLS Cloudflare SSL / TLS SSL Certificates Software Cloudflare WAF Cloudflare WAF Web Application Firewalls (WAF) Cloudflare Web Analytics Cloudflare Web Analytics Digital Analytics Software Cloudflare Workers Cloudflare Workers Server Virtualization Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/scaleway-elastic-metal/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_full-click | Elastic Metal | LinkedIn Skip to main content LinkedIn Scaleway in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Elastic Metal Web Hosting by Scaleway See who's skilled in this Add as skill Get started Report this product About Elastic Metal combines powerful dedicated servers, with flexible pricing, and native integration into Scaleway complete cloud ecosystem. With this range of Bare Metal, you get full control of the resources and applications installed on the server, for maximum performance and security. Elastic Metal servers are available on two different billing plans: hourly or monthly. Media Products media viewer No more previous content Scaleway introduces Elastic Metal The reliability of bare metal meets the flexibility of the public cloud! Elastic Metal Elastic Metal: the reliability of Bare Metal meets the elasticity of the cloud No more next content Similar products IPv4 Address Leasing Service IPv4 Address Leasing Service Web Hosting Pantheon Platform Pantheon Platform Web Hosting Web Hosting Web Hosting Web Hosting WooCommerce Hosting WooCommerce Hosting Web Hosting Cloudways Autonomous Cloudways Autonomous Web Hosting Sites Sites Web Hosting Sign in to see more Show more Show less Scaleway products Kubernetes Kapsule Kubernetes Kapsule Container Management Software Object storage Object storage Object Storage Software LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/cloudflare-spectrum/?trk=products_seo_search | Cloudflare Spectrum | LinkedIn Skip to main content LinkedIn Cloudflare in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Cloudflare Spectrum DDoS Protection Software by Cloudflare See who's skilled in this Add as skill Learn more Report this product About Cloudflare Spectrum increases TCP and UDP security and prevents DDoS attacks for gaming, mail, SSH, and other services. Similar products Cloudflare DDoS Protection Cloudflare DDoS Protection DDoS Protection Software Akamai Prolexic Routed Akamai Prolexic Routed DDoS Protection Software OVHcloud Anti-DDoS Protection OVHcloud Anti-DDoS Protection DDoS Protection Software Kona DDoS Defender Kona DDoS Defender DDoS Protection Software Kaspersky DDoS Protection Kaspersky DDoS Protection DDoS Protection Software Arbor Cloud DDoS Protection Arbor Cloud DDoS Protection DDoS Protection Software Sign in to see more Show more Show less Cloudflare products Argo Smart Routing Argo Smart Routing Network Management Software Cloudflare DDoS Protection Cloudflare DDoS Protection DDoS Protection Software Cloudflare DNS Cloudflare DNS Managed DNS Services Software Cloudflare Load Balancing Cloudflare Load Balancing Load Balancing Software Cloudflare Registrar Cloudflare Registrar Managed DNS Services Software Cloudflare SSL / TLS Cloudflare SSL / TLS SSL Certificates Software Cloudflare WAF Cloudflare WAF Web Application Firewalls (WAF) Cloudflare Web Analytics Cloudflare Web Analytics Digital Analytics Software Cloudflare Workers Cloudflare Workers Server Virtualization Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/categories/managed-file-transfer-software?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_subtitle-click | Best Managed File Transfer (MFT) Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Information Technology Manager (8) System Engineer (3) Technical Architect (3) Compliance Officer (3) Infrastructure Manager (2) See all products Find top products in Managed File Transfer (MFT) Software category Software used to move large volumes of files over established networks with end-to-end security and activity monitoring. - Use built-in security, encryption, and compliance features not included in FTP solutions - Scale delivery between systems, automate file transfer procedures, and support multiple protocols - Control auditing and authentication and receive confirmation of successful transfers 84 results Axway Managed File Transfer Managed File Transfer (MFT) Software by Axway Secure, reliable, and easy-to-manage solution for transferring data between people, partners, businesses, and applications. Manage and control how your organization sends and receives data so you can ensure it stays protected and meets compliance regulations such as HIPAA, PCI, DSS, and GDPR. View product Progress MOVEit Managed File Transfer (MFT) Software by Progress Software Enterprise-grade secure file transfer and automation software for reliable, secure data transfer between partners, customers and systems. View product Serv-U Managed File Transfer Server Managed File Transfer (MFT) Software by SolarWinds Serv-U® Managed File Transfer Server offers comprehensive security, automation, and control over file transfers in and outside your organization. View product JSCAPE by Redwood Managed File Transfer (MFT) Software by Redwood Software Automate your file transfers while staying secure and compliant with JSCAPE by Redwood, able to support any platform, protocol or environment. Easy to use and set up, IT teams are empowered with a single view into all file transfer operations, with real-time notifications and alerts. With a built-in library of 100+ no-code/low-code workflow automation templates, REST APIs and off-the-shelf integrations, your experts have the tools they need to deliver reliable file transfer operations. Experience the power of scalable file transfer with JSCAPE. Experience the power of secure, seamless and scalable file transfer with JSCAPE. Elevate your enterprise's data management capabilities and unlock new levels of productivity and agility today. View product Cerberus by Redwood Managed File Transfer (MFT) Software by Redwood Software Secure file transfer just got easier with Cerberus FTP by Redwood. Since 2001, Cerberus has been simplifying SFTP for small, midsize and enterprise organizations. Known for its ease of use, robust security features and award-winning support, Cerberus is the preferred Windows SFTP solution for IT professionals. Security and compliance features help you meet requirements like HIPAA, GPDR and more, plus regular penetration testing and third-party auditing identifies any potential product weaknesses for remediation. Start sharing your files securely and reliably with Cerberus FTP today. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights MLADU Managed File Transfer (MFT) Software by Dantech Corporation Inc. MLADU redefines data transfer with industry-leading scalability, security, availability, and performance. Designed for businesses of all sizes and across all industries, MLADU effortlessly handles data transfers of any volume, supporting use cases such as acquisitions, clinical trials, omics pipelines, scientific research, enterprise applications, and big data analytics. Its robust features empower you to easily initiate, track, organize, and configure transfers to align perfectly with your business, organizational, and compliance needs. Engineered to overcome the toughest data transfer challenges, MLADU addresses complexities like data corruption, system incompatibility, duplication, and massive data volumes. It also ensures the highest standards of security, regulatory compliance, and data integrity. Whether you're navigating diverse platforms, managing varying formats, or mitigating potential human errors, MLADU is your trusted partner in seamless, reliable data transfer solutions View product dDataBox Managed File Transfer (MFT) Software by Dataport AöR Bei der Kommunikation mit unseren Kolleg*innen und Externen greifen wir täglich auf E-Mails zurück. Für den Versand sehr großer Dateien eignen sie sich allerdings nicht. Zudem bieten E-Mails nicht immer die erforderliche Vertraulichkeit. Mit der dDataBox können Sie Ihren Adressat*innen nun große Dateien sicher bereitstellen. Auf einen Blick: ✅ Ende-zu-Ende Verschlüsselung ✅ Smartphone-App (Android, iOS) ✅ Temporärer Down- und Uploadlink für Externe ✅ Benutzer*innen und Speichervolumen eigenständig verwalten ✅ Betrieb im hochsicheren Twin Data Center ✅ Günstiger Speicher View product LinShare Managed File Transfer (MFT) Software by LINAGORA LinShare is a Private and secure file sharing and cloud storage solution. Fully compliant with GDPR. Made and hosted in the EU. LinShare has been free to use and powered by open-source since 2009. Check us out on GitHub at https://github.com/linagora/linshare LinShare gives you access to features such as notifications whenever your file is opened or downloaded, activity logs and secure uploads. With LinShare you can organize your files conveniently and use them for efficient collaboration with your team. Your privacy is our priority so LinShare uses data encryption, password-safe links and multiple layers of protection. View product AnyShare – Rapid File Transfer Managed File Transfer (MFT) Software by Technozer Solution No. 1 App to transfer APKs, videos and photos to any devices A simple and easy use app to manage files on your android, iOS or PC devices. Avoid using USB cables to transfer files, movies, photos and songs from your device to laptops/PCs/Macs and other android devices without internet. AnyShare sets itself apart from other share apps in the market by offering perks over perks. So, what are you waiting for? Download AnyShare – Rapid File Transfer, Share Files Now. View product Secure File Sharing Managed File Transfer (MFT) Software by Tresorit | Swiss Post Digital Share files securely. Stay in control of your data. Protect your company’s data with zero-knowledge end-to-end encryption when sharing files inside or outside your organization. Keep your files in sight long after they’ve been shared. Data transfers are crucial to running a business in the digital age but this has led to new challenges. The exponential increase in data shared online, an emerging fast-paced working culture, and limitless remote collaboration pose significant risks to companies. Your most valuable data is constantly being exposed to a myriad of security and privacy threats. - Exchange files securely with clients, partners, and other teams using encrypted links. - Ultra-secure share links enable encrypted document and folder sharing with anyone, even if they don’t have a Tresorit account. - Collect files from anyone, anywhere with secure, encrypted file requests. Fully compliant with: - GDPR, CCPA - HIPAA - TISAX(Chapter 5) - ITAR - FINRA View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/akamai-technologies-akamai-prolexic-routed/?trk=products_seo_search | Akamai Prolexic Routed | LinkedIn Skip to main content LinkedIn Akamai Technologies in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Akamai Prolexic Routed DDoS Protection Software by Akamai Technologies See who's skilled in this Add as skill Learn more Report this product About Prolexic solutions provide fully managed DDoS protection for your applications, data centers, and network infrastructure. Similar products Cloudflare DDoS Protection Cloudflare DDoS Protection DDoS Protection Software Cloudflare Spectrum Cloudflare Spectrum DDoS Protection Software OVHcloud Anti-DDoS Protection OVHcloud Anti-DDoS Protection DDoS Protection Software Kona DDoS Defender Kona DDoS Defender DDoS Protection Software Kaspersky DDoS Protection Kaspersky DDoS Protection DDoS Protection Software Arbor Cloud DDoS Protection Arbor Cloud DDoS Protection DDoS Protection Software Sign in to see more Show more Show less Akamai Technologies products Akamai Edge DNS Akamai Edge DNS Managed DNS Services Software Akamai Identity Cloud Akamai Identity Cloud Identity & Access Management (IAM) Software Akamai IoT Edge Connect Akamai IoT Edge Connect Internet of Things (IoT) Software Aura Managed CDN Aura Managed CDN Content Delivery Network (CDN) Software BOCC BOCC Live Streaming Software DNSi AuthServe DNSi AuthServe Managed DNS Services Software DNSi Big Data Connector DNSi Big Data Connector Managed DNS Services Software Enterprise Threat Protector Enterprise Threat Protector Secure Web Gateways Media Services Live Media Services Live Live Streaming Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://sre.google/prodverbs/ | Google SRE - Capture sre beliefs: Prodverbs by Perry Lorier Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content Prodverbs Curated by Perry Lorier, Staff Site Reliability Engineer These "prodverbs" (aka production proverbs) capture general beliefs that SREs have (or, IMHO, should have) that I've collected over the past few years. These prodverbs provide insight into running services in production, and working as an SRE. Each prodverb links to a talk or article that describes the principles in more detail. This is our first collection of prodverbs — look for more here in the coming months! Cascading failures happen, so guard against them. Production is never homogenous. An empty config doesn’t mean you should delete everything. Every single point of failure fails eventually. First mitigate, then diagnose, then fix. If two systems must agree for them to work, someday they will inevitably disagree. Decrease variance, increase mean. Backups are only as good as the last restore. If you have no SLOs, toil is your job. Hope is not a strategy. Scale maintenance sublinearly with the growth of the service. May all your incidents be novel. Share Copy Link × Share Copy Link × Share Copy Link × Share Copy Link × Share Copy Link × Share Copy Link × Share Copy Link × Share Copy Link × Share Copy Link × Share Copy Link × Share Copy Link × Share Copy Link × 1 2 3 4 5 6 7 8 9 10 11 12 Follow us About Google Google products Privacy Terms Help | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/credgenics-chatr/?trk=products_seo_search | ChatR | LinkedIn Skip to main content LinkedIn Credgenics in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in ChatR Live Chat Software by Credgenics See who's skilled in this Add as skill Request demo Report this product About ChatR is a two-way chat solution on WhatsApp that enables debt collections teams of banks, NBFCs and Fintech lenders to engage more effectively with borrowers through verified business accounts. Using ChatR, collection teams can share reminders, payment links and digital notices with borrowers instantly. The borrowers can also respond to these messages, and share payment proofs and other documents digitally with the agent on the lender’s official WhatsApp channel. ● Pre-approved WhatsApp template or free text typing available for the agent to communicate with borrowers ● Chat filters based on the last borrower conversation status and allocation month ● Integration with Credgenics Predictive dialer for Whatsapp Chat access for a Tele-calling agent ● Policy control for contact time limits with WhatsApp message monitoring This product is intended for Collections Manager Operations Manager Operations Lead Caller Customer Service Manager Media Products media viewer No more previous content ChatR No more next content Similar products Freshchat Freshchat Live Chat Software ICE Chat ICE Chat Live Chat Software Webchat Webchat Live Chat Software Microsoft Teams Microsoft Teams Live Chat Software LiveChat LiveChat Live Chat Software Chat Chat Live Chat Software Sign in to see more Show more Show less Credgenics products Billzy Payments Billzy Payments Payment Gateway Software CG Collect - Mobile Based Loan Collections CG Collect - Mobile Based Loan Collections Loan Servicing Software Credgenics Collections Analytics Credgenics Collections Analytics Debt Collection Software Credgenics Litigation Management System Credgenics Litigation Management System Debt Collection Software Credgenics Loan Collections Platform Credgenics Loan Collections Platform Debt Collection Software StarTrack StarTrack Loan Servicing Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://git-scm.com/book/pt-br/v2/Git-no-servidor-GitLab | Git - GitLab About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Começando 1.1 Sobre Controle de Versão 1.2 Uma Breve História do Git 1.3 O Básico do Git 1.4 A Linha de Comando 1.5 Instalando o Git 1.6 Configuração Inicial do Git 1.7 Pedindo Ajuda 1.8 Sumário 2. Fundamentos de Git 2.1 Obtendo um Repositório Git 2.2 Gravando Alterações em Seu Repositório 2.3 Vendo o histórico de Commits 2.4 Desfazendo coisas 2.5 Trabalhando de Forma Remota 2.6 Criando Tags 2.7 Apelidos Git 2.8 Sumário 3. Branches no Git 3.1 Branches em poucas palavras 3.2 O básico de Ramificação (Branch) e Mesclagem (Merge) 3.3 Gestão de Branches 3.4 Fluxo de Branches 3.5 Branches remotos 3.6 Rebase 3.7 Sumário 4. Git no servidor 4.1 Os Protocolos 4.2 Getting Git on a Server 4.3 Gerando Sua Chave Pública SSH 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Sumário 5. Distributed Git 5.1 Fluxos de Trabalho Distribuídos 5.2 Contribuindo com um Projeto 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Configurando uma conta 6.2 Contribuindo em um projeto 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Funcionamento Interno do Git 10.1 Encanamento e Porcelana 10.2 Objetos do Git 10.3 Referências do Git 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Variáveis de ambiente 10.9 Sumário A1. Appendix A: Git em Outros Ambientes A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Resumo A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.8 Git no servidor - GitLab GitLab Embora o GitWeb seja bastante simplista, se você estiver procurando por um servidor Git mais moderno e completo, existem algumas soluções de código aberto lá fora que você pode instalar em vez deste. Como o GitLab é um dos mais populares, vamos cobrir a instalação e usá-lo como um exemplo. Este é um pouco mais complexo do que a opção GitWeb e provavelmente requer mais manutenção, mas é uma opção muito mais completa. Instalação O GitLab é um aplicativo da Web baseado em banco de dados, por isso sua instalação é um pouco mais trabalhosa do que alguns outros servidores Git. Felizmente, este processo é muito bem documentado e apoiado. Existem alguns métodos que você pode seguir para instalar o GitLab. Para obter algo em execução rapidamente, você pode baixar uma imagem de máquina virtual ou um instalador de um clique em https://bitnami.com/stack/gitlab e ajustar a configuração para que corresponda ao seu ambiente particular.. Um toque agradável que Bitnami incluiu é a tela de login (acessada digitando alt-→); Ele informa o endereço IP e o nome de usuário e senha padrão para o GitLab instalado. Figure 50. A tela de login da máquina virtual Bitnami GitLab. Para qualquer outra coisa, siga as orientações no readme do GitLab Community Edition, que pode ser encontrado em https://gitlab.com/gitlab-org/gitlab-ce/tree/master . Lá você encontrará assistência na instalação do GitLab usando receitas do Chef, a máquina virtual no Digital Ocean, e os pacotes RPM e DEB (que, no momento em que este texto foi escrito, estava na versão estável Omnibus, para os sistemas operacionais Ubuntu 14.04, Ubuntu 16.04, Debian 7, Debian 8, CentOS 6, CentOS 7, OpenSUSE 42.1 e Raspberry PI 2 em Raspbian). Há também guias com orientações “não oficiais” para que o GitLab funcione em sistemas operacionais e bancos de dados diferentes dos citados acima, um script para instalação completamente manual e muitos outros tópicos. Administração A interface de administração do GitLab é acessada através da web. Basta apontar o seu navegador para o nome do host ou endereço IP onde o GitLab está instalado e efetuar login como um usuário admin. O nome de usuário padrão é admin@local.host e a senha padrão é 5iveL!fe (que você será solicitado a alterar assim que você entrar nele). Depois de efetuar login, clique no ícone “Área de administração” no menu no canto superior direito. Figure 51. O item “Área de administração” no menu GitLab. Usuários Usuários no GitLab são contas que correspondem a pessoas. As contas de usuário não têm muita complexidade; A conta de usuário é uma coleção de informações pessoais anexadas aos dados de login. Cada conta de usuário vem com um namespace , que é um agrupamento lógico de projetos que pertencem a esse usuário. Se o usuário jane tivesse um projeto chamado project , o URL do projeto seria http://servidor/jane/project . Figure 52. Tela de administração de usuários do GitLab. Remoção de um usuário pode ser feito de duas formas. “Bloquear” um usuário os impede de logar na instância do Gitlab, mas todos os dados sob o namespace do usuário serão preservados, e os commits assinados com o e-mail do usuário ainda irão direcionar para o perfil do mesmo. “Destruir” um usuário, por outro lado, remove o remove completamente do banco de dados e do sistema de arquivos. Todos os projetos e dados no namespace são removidos, e qualquer outro grupo que ele possua também será removido. Isso é obviamente uma ação muito mais permanete e destrutiva, e o uso disso é raro. Grupos Um grupo GitLab é um conjunto de projetos, juntamente com dados sobre como os usuários podem acessar esses projetos. Cada grupo tem um espaço para nome de projeto (da mesma forma que os usuários), então se o grupo training tiver um projeto materials , sua url seria http://servidor/training/materials . Figure 53. Tela de administração de grupos do GitLab. Cada grupo está associado a um número de usuários, cada um com um nível de permissões para os projetos do grupo e para o próprio grupo. Estes variam de “Convidado” (problemas e bate-papo somente) a “Proprietário” (controle total do grupo, seus membros e seus projetos). Os tipos de permissões são muito numerosos para listar aqui, mas o GitLab tem um link útil na tela de administração. Projetos Um projeto GitLab corresponde grosso modo a um único repositório Git. Cada projeto pertence a um único namespace, a um usuário ou a um grupo. Se o projeto pertence a um usuário, o proprietário do projeto tem controle direto sobre quem tem acesso ao projeto; Se o projeto pertence a um grupo, as permissões de nível de usuário do grupo também terão efeito. Cada projeto também tem um nível de visibilidade, que controla quem tem acesso de leitura às páginas desse projeto e ao repositório. Se um projeto for Privado , o proprietário do projeto deve conceder explicitamente acesso a usuários específicos. Um projeto Interno é visível para qualquer usuário logado, e um projeto Público é visível para qualquer pessoa. Observe que isso controla tanto o acesso git fetch quanto o acesso à interface web do usuário a esse projeto. Ganchos (hooks) O GitLab inclui suporte para ganchos (hooks), tanto a nível de projeto como de sistema. Para qualquer um destes, o servidor GitLab executará um HTTP POST com algum JSON descritivo sempre que ocorrerem eventos relevantes. Esta é uma ótima maneira de conectar seus repositórios Git e a instância GitLab ao resto de sua automação de desenvolvimento, como servidores CI, salas de bate-papo ou ferramentas de implantação. Uso Básico A primeira coisa que você vai querer fazer com o GitLab é criar um novo projeto. Isso é feito clicando no ícone “+” na barra de ferramentas. Ser-lhe-á pedido o nome do projecto, a qual namespace ele deverá pertencer e que nível de visibilidade deverá ter. A maior parte do que você especifica aqui não é permanente e pode ser reajustada posteriormente através da interface de configurações. Clique em “Criar projeto” e pronto. Uma vez que o projeto exista, você provavelmente vai querer conectá-lo com um repositório Git local. Cada projeto é acessível através de HTTPS ou SSH, sendo que ambos podem ser usados para configurar um Git remoto. As URLs estão visíveis na parte superior da página inicial do projeto. Para um repositório local existente, este comando criará um remoto chamado gitlab para o local hospedado: $ git remote add gitlab https://servidor/namespace/project.git Se você não tem uma cópia local do repositório, você pode simplesmente fazer isso: $ git clone https://servidor/namespace/project.git A interface do usuário da Web fornece acesso a várias visualizações úteis do próprio repositório. A página inicial de cada projeto mostra as atividades recentes e os links ao longo do topo levam você a exibições dos arquivos do projeto e do log de commits. Trabalhando juntos A maneira mais simples de trabalhar juntos em um projeto GitLab é dar a outro usuário acesso direto de push (envio de commits) ao repositório Git. Você pode adicionar um usuário a um projeto indo para a seção “Membros” das configurações desse projeto e associando o novo usuário com um nível de acesso (os diferentes níveis de acesso estão um pouco descritos em Grupos ). Ao fornecer a um usuário um nível de acesso de “Desenvolvedor” ou superior, esse usuário pode empurrar branches e ramificações diretamente para o repositório. Outra maneira mais dissociada de colaboração é usar solicitações de mesclagem. Esse recurso permite que qualquer usuário que possa ver um projeto contribua para ele de forma controlada. Os usuários com acesso direto podem simplesmente criar uma ramificação, empurrá-la para ele e abrir uma solicitação de mesclagem de seu ramo de volta para master ou qualquer outra ramificação. Os usuários que não têm permissões push para um repositório podem "fork" (criar sua própria cópia), push commit para aquela cópia e abrir uma solicitação de mesclagem de sua bifurcação de volta para o projeto principal. Este modelo permite que o proprietário esteja no controle total do que entra no repositório e quando, embora permita contribuições de usuários não confiáveis. Os pedidos de mesclagem e os problemas são as principais unidades de discussão de longa duração no GitLab. Cada solicitação de mesclagem permite uma discussão linha a linha da alteração proposta (que suporta um tipo leve de revisão de código), bem como um tópico geral de discussão geral. Ambos podem ser atribuídos a usuários ou organizados em marcos. Esta seção é focada principalmente nos recursos relacionados ao Git do GitLab, mas como um projeto maduro, ele fornece muitos outros recursos para ajudar sua equipe a trabalhar em conjunto, como wikis de projeto e ferramentas de manutenção do sistema. Um benefício para o GitLab é que, uma vez que o servidor está configurado e em execução, você raramente precisará ajustar um arquivo de configuração ou acessar o servidor via SSH; A maior parte da administração e o uso geral podem ser realizados através da interface no navegador. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
http://www.trello.com/teams/engineering | Trello for Engineering Teams | Trello Skip to main content Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Use case: Task management Track progress of tasks in one convenient place with a visual layout that adds ‘ta-da’ to your to-do’s. Use case: Resource hub Save hours when you give teams a well-designed hub to find information easily and quickly. Use case: Project management Keep projects organized, deadlines on track, and teammates aligned with Trello. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Back Navigation Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Read though our use cases to make the most of Trello on your team. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Helping teams work better, together Discover Trello use cases, productivity tips, best practices for team collaboration, and expert remote work advice. Check out the Trello blog < Go back to Team Solutions Trello for Engineering Teams Enable your engineering team to be agile, ship more with less stress, and collaborate on product launches and bug fixes seamlessly with Trello. Trello’s boards, lists, and cards enable teams to go from ideas to action in seconds. Visual and easy-to-use, Trello helps teams bring projects to life and keep them moving forward. Join over 2,000,000 teams worldwide who are using Trello to get more done. Your Team’s Workspace For Engineering Excellence Whether the team is planning a new product roadmap, running sprint retrospectives, collaborating on bug fixes, or celebrating a go-live, there’s a Trello board to help with every aspect of an engineer’s day (or all-nighter). Explore all engineering templates SPRINT RETROSPECTIVE Celebrate what went well, what needs improvement, and any action items required to improve communication and collaboration with this template SITE RELIABILITY Manage and maintain system-related improvements, architecture, and development with this template. SOFTWARE DEVELOPMENT A one-stop-shop for software development teams looking to organize, manage tasks, and manage deadlines and features for their IT development projects. SPRINT RETROSPECTIVE Celebrate what went well, what needs improvement, and any action items required to improve communication and collaboration with this template SITE RELIABILITY Manage and maintain system-related improvements, architecture, and development with this template. SOFTWARE DEVELOPMENT A one-stop-shop for software development teams looking to organize, manage tasks, and manage deadlines and features for their IT development projects. Build things better, together, and on time. With Timeline View, your Engineering team can easily sync for sprints and align on project deadlines. Learn more about Trello views Power-Up Your Development Process Simple, adaptable, customizable. Make Trello your official engineering hub with Power-Ups like Github, Jira, Gitlab, and Custom Fields. Connect your favorite apps and integrations to Trello and gather all of the information you need to get things done under one roof. Explore 150+ Power-Ups Move Work Forward, Auto-magically Trello’s built-in automation makes it easy to automate the repetitive, everyday tasks that keep your team from focusing on the work that matters most. Let the robots do the work Resources To Engineer Success Kanban 101: How Any Team Can Be More Agile [Blog Post] By breaking projects down into bite-sized tasks and limiting the work in progress, teams are empowered to quickly understand what’s working and what’s not for a given project. Discover how to kick your team’s productivity levels into high gear. READ MORE Ready, Set, Code: How Engineering Teams Use Trello [Blog Post] Ensure your engineering team is staying on track and prioritizing the right projects by testing out these Trello workflows, and if you find them reliable, commit the changes! READ MORE A Case For The Vital, But Often Avoided, Sprint Retrospective Meeting [Blog Post] The beauty of scrum is incremental improvement. By continuously fixing small items, your team will be happier, more productive, and spend less time dealing with recurring headaches. READ MORE Agile Workflows in Trello [Webinar] Discover how Agile and Scrum techniques can be applied to a workflow in Trello using three key boards for your Sprints, Retrospectives, and Product Roadmaps. Watch Now NOW AVAILABLE A 14 Day Free Trial of Premium! Get unlimited boards, Trello views, and limitless automation, plus a ton more. Try it today SwagUp: Scale Any Business With Trello BC “Not only did [Trello] unify our process and help everyone understand their role, but we were able to automate essential steps of the process so we could move a lot faster and grow to a multi-million dollar company with a team of ten.” –Founder, SwagUp Learn More Instinct Dog Training “As you scale, you need visibility, accountability, and organization. Trello has provided that for us.” –Brian Burton, Founder, Instinct Dog Training Learn More Desk Plants “We chose Trello because it is well-designed—it’s beautifully designed—intuitive, and really hit the nail on the head with what we needed to solve.” –Lawrence Hanley, founder of Desk Plants Learn More Scan2Cad “We use Trello because our data becomes alive. A bullet point list turns into real tasks that are assigned to real people with due dates and connections to our other apps. The power in that is fantastic.” –Luke Kennedy, CEO, Scan2Cad Learn More Palace Law “People have generally been happier since we started using Trello. It has made our lives a lot easier. People are less stressed.” -Jordan Couch, attorney at Palace Law Learn More Trello Your Way Ready to get your team up and running? Try the business tool so easy to use, your team can’t help but collaborate. Learn more about our pricing and plans Free $ 0 USD Free for up to 10 collaborators per Workspace Capture your to-dos, get organized, and get sh*t done. Standard $ 5 USD Per user/month if billed annually ($6 billed monthly) Get more stuff done with unlimited boards, card mirroring, and more automation. Learn more about Standard Premium $ 10 USD Per user/month if billed annually ($12.50 billed monthly) Add AI to your boards and admin controls to your toolkit. Plus, get more perspective with views. Learn more about Premium Enterprise $ 17.50 USD Per user/month - billed annually ($210.00 annual price per user) Add enterprise-grade security and controls. This plan includes Atlassian Guard Standard and 24/7 Enterprise Admin support. Est. cost for users Learn more about Enterprise Well, what are you waiting for? Head over to your boards and start getting things done! Log In About Trello What’s behind the boards. Jobs Learn about open roles on the Trello team. Apps Download the Trello App for your Desktop or Mobile devices. Contact us Need anything? Get in touch and we can help. Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Privacy Policy Terms Copyright © 2024 Atlassian | 2026-01-13T09:29:20 |
https://git-scm.com/book/de/v2/Git-Branching-Rebasing | Git - Rebasing About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Erste Schritte 1.1 Was ist Versionsverwaltung? 1.2 Kurzer Überblick über die Historie von Git 1.3 Was ist Git? 1.4 Die Kommandozeile 1.5 Git installieren 1.6 Git Basis-Konfiguration 1.7 Hilfe finden 1.8 Zusammenfassung 2. Git Grundlagen 2.1 Ein Git-Repository anlegen 2.2 Änderungen nachverfolgen und im Repository speichern 2.3 Anzeigen der Commit-Historie 2.4 Ungewollte Änderungen rückgängig machen 2.5 Mit Remotes arbeiten 2.6 Taggen 2.7 Git Aliases 2.8 Zusammenfassung 3. Git Branching 3.1 Branches auf einen Blick 3.2 Einfaches Branching und Merging 3.3 Branch-Management 3.4 Branching-Workflows 3.5 Remote-Branches 3.6 Rebasing 3.7 Zusammenfassung 4. Git auf dem Server 4.1 Die Protokolle 4.2 Git auf einem Server einrichten 4.3 Erstellung eines SSH-Public-Keys 4.4 Einrichten des Servers 4.5 Git-Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Von Drittanbietern gehostete Optionen 4.10 Zusammenfassung 5. Verteiltes Git 5.1 Verteilter Arbeitsablauf 5.2 An einem Projekt mitwirken 5.3 Ein Projekt verwalten 5.4 Zusammenfassung 6. GitHub 6.1 Einrichten und Konfigurieren eines Kontos 6.2 Mitwirken an einem Projekt 6.3 Ein Projekt betreuen 6.4 Verwalten einer Organisation 6.5 Skripte mit GitHub 6.6 Zusammenfassung 7. Git Tools 7.1 Revisions-Auswahl 7.2 Interaktives Stagen 7.3 Stashen und Bereinigen 7.4 Deine Arbeit signieren 7.5 Suchen 7.6 Den Verlauf umschreiben 7.7 Reset entzaubert 7.8 Fortgeschrittenes Merging 7.9 Rerere 7.10 Debuggen mit Git 7.11 Submodule 7.12 Bundling 7.13 Replace (Ersetzen) 7.14 Anmeldeinformationen speichern 7.15 Zusammenfassung 8. Git einrichten 8.1 Git Konfiguration 8.2 Git-Attribute 8.3 Git Hooks 8.4 Beispiel für Git-forcierte Regeln 8.5 Zusammenfassung 9. Git und andere VCS-Systeme 9.1 Git als Client 9.2 Migration zu Git 9.3 Zusammenfassung 10. Git Interna 10.1 Basisbefehle und Standardbefehle (Plumbing and Porcelain) 10.2 Git Objekte 10.3 Git Referenzen 10.4 Packdateien (engl. Packfiles) 10.5 Die Referenzspezifikation (engl. Refspec) 10.6 Transfer Protokolle 10.7 Wartung und Datenwiederherstellung 10.8 Umgebungsvariablen 10.9 Zusammenfassung A1. Anhang A: Git in anderen Umgebungen A1.1 Grafische Schnittstellen A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Zusammenfassung A2. Anhang B: Git in deine Anwendungen einbetten A2.1 Die Git-Kommandozeile A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Anhang C: Git Kommandos A3.1 Setup und Konfiguration A3.2 Projekte importieren und erstellen A3.3 Einfache Snapshot-Funktionen A3.4 Branching und Merging A3.5 Projekte gemeinsam nutzen und aktualisieren A3.6 Kontrollieren und Vergleichen A3.7 Debugging A3.8 Patchen bzw. Fehlerkorrektur A3.9 E-mails A3.10 Externe Systeme A3.11 Administration A3.12 Basisbefehle 2nd Edition 3.6 Git Branching - Rebasing Rebasing Es gibt bei Git zwei Wege, um Änderungen von einem Branch in einen anderen zu integrieren: merge und rebase . In diesem Abschnitt wirst du erfahren, was Rebasing ist, wie du es anwendest, warum es ein ziemlich erstaunliches Werkzeug ist und bei welchen Gelegenheiten du es besser nicht einsetzen solltest. Einfacher Rebase Wenn du dich noch mal ein früheres Beispiel aus Einfaches Merging anschaust, kannst du sehen, dass du deine Arbeit verzweigt und Commits auf zwei unterschiedlichen Branches erstellt hast. Abbildung 35. Einfacher verzweigter Verlauf Der einfachste Weg, die Branches zu integrieren ist der Befehl merge , wie wir bereits besprochen haben. Er führt einen Drei-Wege-Merge zwischen den beiden letzten Branch-Snapshots ( C3 und C4 ) und dem jüngsten gemeinsamen Vorgänger der beiden ( C2 ) durch und erstellt einen neuen Snapshot (und Commit). Abbildung 36. Zusammenführen (Merging) verzweigter Arbeitsverläufe Allerdings gibt es noch einen anderen Weg: Du kannst den Patch der Änderungen, den wir in C4 eingeführt haben, nehmen und am Ende von C3 erneut anwenden. Dieses Vorgehen nennt man in Git rebasing . Mit dem Befehl rebase kannst du alle Änderungen, die in einem Branch vorgenommen wurden, übernehmen und in einem anderen Branch wiedergeben. Für dieses Beispiel würdest du den Branch experiment auschecken und dann wie folgt auf den master Branch restrukturieren (engl. rebase): $ git checkout experiment $ git rebase master First, rewinding head to replay your work on top of it... Applying: added staged command Dies funktioniert, indem Git zum letzten gemeinsamen Vorgänger der beiden Branches (der, auf dem du arbeitest, und jener, auf den du rebasen möchtest) geht, dann die Informationen zu den Änderungen (diffs) sammelt, welche seitdem bei jedem einzelnen Commit des aktuellen Branches gemacht wurden, diese in temporären Dateien speichert, den aktuellen Branch auf den gleichen Commit setzt wie den Branch, auf den du rebasen möchtest, und dann alle Änderungen erneut durchführt. Abbildung 37. Rebase der in C4 eingeführten Änderung auf C3 An diesem Punkt kannst du zum vorherigen master Branch wechseln und einen fast-forward-Merge durchführen. $ git checkout master $ git merge experiment Abbildung 38. Vorspulen (fast-forwarding) des master Branches Jetzt ist der Schnappschuss, der auf C4' zeigt, exakt derselbe wie derjenige, auf den C5 in dem Merge-Beispiel gezeigt hat. Es gibt keinen Unterschied im Endergebnis der Integration. Das Rebase sorgt jedoch für eine klarere Historie. Wenn man das Protokoll eines rebase Branches betrachtet, sieht es wie eine lineare Historie aus: Es scheint, dass alle Arbeiten sequentiell stattgefunden hätten, auch wenn sie ursprünglich parallel stattgefunden haben. Häufig wirst du das anwenden, damit deine Commits sauber auf einen Remote-Branch angewendet werden – vielleicht in einem Projekt, zu dem du beitragen möchtest, das du aber nicht pflegst. Du würdest deine Änderungen in einem lokalen Branch durchführen und diese im Anschluss mittels rebase zu origin/master dem Hauptprojekt hinzufügen. Auf diese Weise muss der Maintainer keine Integrationsarbeiten durchführen – nur einen „fast-forward“ oder ein einfaches Einbinden deines Patches. Beachte, dass der Snapshot, auf welchen der letzte Commit zeigt, ob es nun der letzte des Rebase-Commits nach einem Rebase oder der finale Merge-Commit nach einem Merge ist, derselbe Schnappschuss ist. Nur der Verlauf ist ein anderer. Rebasing wiederholt die Änderungsschritte von einer Entwicklungslinie auf einer anderen in der Reihenfolge, in der sie entstanden sind. Dagegen werden beim Merge die beiden Endpunkte der Branches genommen und miteinander gemerged. Weitere interessante Rebases Du kannst dein Rebase auch auf einen anderen Branch als den Rebase-Ziel-Branch anwenden. Nimm zum Beispiel einen Verlauf wie im Bild: Ein Verlauf mit einem Feature-Branch neben einem anderen Feature-Branch . Du hast einen Feature-Branch ( server ) angelegt, um ein paar serverseitige Funktionalitäten zu deinem Projekt hinzuzufügen, und hast dann einen Commit gemacht. Anschließend hast du von diesem einen weiteren Branch abgezweigt, um clientseitige Änderungen ( client ) vorzunehmen. Auch hier hast du ein paar Commits durchgeführt. Zum Schluss wechselst du wieder zu deinem vorherigen server Branch und machst weitere Commits. Abbildung 39. Ein Verlauf mit einem Feature-Branch neben einem anderen Feature-Branch Angenommen, du entscheidest dich, dass du für einen Release deine clientseitigen Änderungen mit deiner Hauptentwicklungslinie zusammenführst, während du die serverseitigen Änderungen noch zurückhalten willst, bis diese weiter getestet wurden. Du kannst die Änderungen auf dem client Branch, die nicht auf dem server Branch ( C8 und C9 ) sind, übernehmen und sie in deinem master Branch wiedergeben, indem du die Option --onto von git rebase verwendest: $ git rebase --onto master server client Das bedeutet im Wesentlichen, „Checke den client Branch aus, finde die Patches des gemeinsamen Vorgängers der Branches client und server heraus und wende sie erneut auf den master Branch an.“ Das ist ein wenig komplex, aber das Resultat ist ziemlich toll. Abbildung 40. Rebasing eines Themen-Branches aus einem anderen Themen-Branch Jetzt kannst du deinen Master-Branch vorspulen (engl. fast-forward) (siehe Vorspulen deines master Branches zum Einfügen der Änderungen des client Branches ): $ git checkout master $ git merge client Abbildung 41. Vorspulen deines master Branches zum Einfügen der Änderungen des client Branches Lass uns annehmen, du entscheidest dich dazu, deinen server Branch ebenfalls einzupflegen. Du kannst das Rebase des server Branches auf den master Branch anwenden, ohne diesen vorher auschecken zu müssen, indem du die Anweisung git rebase <Basis-Branch> <Feature-Branch> ausführst, welche für dich den Feature-Branch auscheckt (in diesem Fall server ) und ihn auf dem Basis-Branch ( master ) wiederholt: $ git rebase master server Das wiederholt deine Änderungen aus dem server Branch am Ende des master Branches, wie in Rebase deines server Branches am Ende deines master Branches gezeigt wird. Abbildung 42. Rebase deines server Branches am Ende deines master Branches Dann kannst du den Basis-Branch ( master ) vorspulen (engl. fast-forward): $ git checkout master $ git merge server Du kannst die Branches client und server löschen, da die ganze Arbeit bereits in master integriert wurde und du diese nicht mehr benötigst. Dein Verlauf für diesen gesamten Prozess sieht jetzt wie in Endgültiger Commit-Verlauf aus: $ git branch -d client $ git branch -d server Abbildung 43. Endgültiger Commit-Verlauf Die Gefahren des Rebasing Ahh, aber der ganze Spaß mit dem Rebasen kommt nicht ohne Schattenseiten und Fallstricke, welche in einer einzigen Zeile zusammengefasst werden können: Führe keinen Rebase mit Commits durch, die außerhalb deines Repositorys existieren und auf welche die Arbeit anderer Personen basiert. Wenn du dich an diese Leitlinie hältst, wirst du gut zurechtkommen. Wenn du es nicht tust, werden die Leute dich hassen und du wirst von Freunden und Familie verschmäht werden. Wenn du ein Rebase durchführst, entfernst du bestehende Commits und erstellen stattdessen neue, die zwar ähnlich aber dennoch unterschiedlich sind. Stell dir vor, du lädst diese Commits hoch und andere laden sich diese herunter und nehmen sie als Grundlage für ihre Arbeit. Dann änderst du jedoch ihre commits nochmal und rebasen und pushst sie. Deine Kollegen müssen ihre Änderungen nochmal remergen. Wenn sie nun versuchen diesen remerge bei sich zu pullen, wird das nicht funktionieren und es kommt zu einem heillosen Durcheinander. Schauen wir uns ein Beispiel an, wie ein Rebase von Arbeiten, die du öffentlich gemacht hast, Probleme verursachen kann. Nehmen wir an, du klonst ein Repository von einem zentralen Server und machst ein paar Änderungen. Dein Commit-Verlauf sieht anschließend so aus: Abbildung 44. Klonen eines Repositorys und darauf Arbeit aufbauen Nun macht jemand anderes Änderungen am Code, einschließlich eines Merges und pusht diese dann auf den zentralen Server. Du holst die Änderungen ab und mergst den neuen Remote-Branch mit deiner Arbeit, sodass dein Verlauf wie folgt aussieht. Abbildung 45. Weitere Commits abholen und mergen mit deiner Arbeit Als nächstes entscheidet die Person, welche die gemergte Arbeit hochgeladen hat, diese rückgängig zu machen und stattdessen deine Arbeit mittels Rebase hinzuzufügen. Sie führt dazu die Anweisung git push --force aus, um den Verlauf auf dem Server zu überschreiben. Du holst das Ganze dann von diesem Server ab und lädst die neuen Commits herunter. Abbildung 46. Jemand lädt Commits nach einem Rebase hoch und verwirft damit Commits, auf denen deine Arbeit basiert Jetzt sitzt ihr beide in der Klemme. Wenn du ein git pull durchführst, würdest du einen Merge-Commit erzeugen, welcher beide Entwicklungslinien einschließt und dein Repository würde so aussehen: Abbildung 47. Du lässt die Änderungen nochmals in dieselbe Arbeit einfließen in einen neuen Merge-Commit Falls du ein git log ausführst, wenn dein Verlauf so aussieht, würdest du zwei Commits sehen, bei denen Autor, Datum und Nachricht übereinstimmen, was verwirrend ist. Weiter würdest du, wenn du diesen Verlauf zurück auf den Server pushst, alle diese vom Rebase stammenden Commits auf dem zentralen Server ablegen, was die Kollegen noch weiter durcheinander bringen würde. Man kann ziemlich sicher davon ausgehen, dass der andere Entwickler C4 und C6 nicht im Verlauf haben möchte; das ist der Grund, warum derjenige das Rebase überhaupt gemacht hat. Rebasen, wenn du Rebase durchführst Wenn du dich in einer solchen Situation befindest , hat Git eine weitere magische Funktion, die dir helfen könnte. Falls jemand in deinem Team forcierte Änderungen pusht, die Arbeiten überschreiben, auf denen deine basiert, besteht deine Herausforderung darin, herauszufinden, was dir gehört und was andere überschrieben haben. Es stellt sich heraus, dass Git neben der SHA-1-Prüfsumme eine weitere Prüfsumme berechnet, die nur auf den mit dem Commit eingeführten Änderungen basiert. Diese wird „patch-id“ genannt. Wenn du die neu umgeschriebene Änderungen pullen und ein Rebase auf auf die neuen Commits deines Partners ausführst, kann Git oft erfolgreich herausfinden, was nur von dir ist und kann es entsprechend auf den neuen Branch anwenden. Sobald wir im vorhergehenden Szenario, beispielsweise bei Jemand lädt Commits nach einem Rebase hoch und verwirft damit Commits, auf denen deine Arbeit basiert , die Anweisung git rebase teamone/master ausführen, anstatt ein Merge durchzuführen, dann wird Git: bestimmen, welche Änderungen an unserem Branch einmalig sind ( C2 , C3 , C4 , C6 , C7 ), bestimmen, welche der Commits keine Merge-Commits sind ( C2 , C3 , C4 ), bestimmen, welche Commits nicht neu in den Zielbranch geschrieben wurden (nur C2 und C3 , da C4 der selbe Patch wie C4' ist), und diese Commits am Ende des teamone/master Branches anwenden. Statt des Ergebnisses, welches wir in Du lässt die Änderungen nochmals in dieselbe Arbeit einfließen in einen neuen Merge-Commit sehen, würden wir etwas erhalten, was eher wie Rebase am Ende von Änderungen eines „force-pushed“-Rebase aussieht. Abbildung 48. Rebase am Ende von Änderungen eines „force-pushed“-Rebase Das funktioniert nur, wenn es sich bei C4 und C4' , welche dein Teamkollege erstellt hat, um fast genau denselben Patch handelt. Andernfalls kann das rebase nicht erkennen, dass es sich um ein Duplikat handelt und fügt einen weiteren, dem Patch C4 ähnlichen, hinzu (der wahrscheinlich nicht sauber angewendet werden kann, da die Änderungen bereits vollständig oder zumindest teilweise vorhanden sind). Du kannst das auch vereinfachen, indem du ein git pull --rebase anstelle eines normalen git pull verwendest. Oder du kannst es manuell mit einem git fetch machen, in diesem Fall gefolgt von einem git rebase teamone/master . Wenn du git pull benutzt und --rebase zur Standardeinstellung machen willst, kannst du den pull.rebase Konfigurationswert mit etwas wie git config --global pull.rebase true einstellen. Wenn du nur Commits rebased, die noch nie deinen eigenen Computer verlassen haben, ist alles in Ordnung. Wenn du Commits, die gepusht wurden, aber niemand sonst hat, basierend auf den Commits, rebased, wird auch alles in Ordnung sein. Wenn du Commits rebased, die gepusht wurden, auf denen aber keine Commits von jemand anderen basieren, ist auch alles in Ordnung. Wenn du Commits, die bereits veröffentlicht wurden, rebased und die Arbeit anderer Leute basiert auf diese Commits, dann könntest du Probleme bekommen und von deinen Teamkollegen verhöhnt werden. Wenn du oder ein Partner es irgendwann für unbedingt notwendig halten, stelle sicher, dass jeder weiß, dass er anschließend git pull --rebase laufen lassen muss. So kann man versuchen, den Schaden einzugrenzen, nachdem er passiert ist. Rebase vs. Merge Nachdem du jetzt Rebasing und Merging in Aktion erlebt hast, fragst du dich vielleicht, welches davon besser ist. Bevor wir das beantworten können, lass uns ein klein wenig zurückblicken und darüber reden, was Historie bedeutet. Ein Standpunkt ist, dass der Commit-Verlauf deines Repositorys eine Aufzeichnung davon ist, was wirklich passiert ist . Es ist ein wertvolles Dokument, das nicht manipuliert werden sollte. Aus diesem Blickwinkel ist das Ändern der Commit-Historie fast schon blasphemisch. Man belügt sich über das, was tatsächlich passiert ist. Was wäre, wenn es eine verwirrende Reihe von Merge-Commits gäbe? So ist es nun mal passiert, und das Repository sollte das für die Nachwelt beibehalten. Der entgegengesetzte Standpunkt ist, dass der Commit-Verlauf den Verlauf deines Projekts darstellt. Du würdest den ersten Entwurf eines Buches niemals veröffentlichen, warum also deine unordentliche Arbeit? Wenn du an einem Projekt arbeitest, benötigst du möglicherweise eine Aufzeichnung all deiner Fehltritte und Sackgassen. Wenn es jedoch an der Zeit ist, deine Arbeit der Welt zu zeigen, möchtest du möglicherweise eine kohärentere Geschichte darüber erzählen, wie du von A nach B gekommen bist. Die Leute in diesem Camp verwenden Tools wie Rebase und Filter-Branch, um ihre Commits neu zu schreiben, bevor sie in den Haupt-Branch integriert werden. Sie verwenden Tools wie Rebase und Filter-Branch , um die Geschichte so zu erzählen, wie es für zukünftige Leser am besten ist. Nun zur Frage, ob Mergen oder Rebasen besser ist. Wie so oft, ist diese Frage nicht so leicht zu beantworten. Git ist ein mächtiges Werkzeug und ermöglicht es dir, viele Dinge mit deinem Verlauf anzustellen. Aber jedes Team und jedes Projekt ist anders. Jetzt, da du weißt, wie diese beiden Möglichkeiten funktionieren, liegt es an dir, zu entscheiden, welche für deine Situation die Beste ist. Für gewöhnlich lassen sich die Vorteile von beiden Techniken nutzen: Rebase lokale Änderungen vor einem Push, um deinen Verlauf zu bereinigen, aber rebase niemals etwas, das du bereits gepusht hast. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/categories/calendar-software?trk=products_details_guest_product_category | Best Calendar Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Owner (2) Scheduling Specialist (2) Manager (2) Event Marketing Manager (2) Product Manager (2) See all products Find top products in Calendar Software category Software used to organize tasks and appointments by day, week, month, or year. - Mark important dates and schedule reminders, alerts, meetings, and events - Use features like scheduling assistants, address books, and contact lists - Create group calendars to share and collaborate - Add notes, links, descriptions, and to-do lists 101 results Notion Calendar Calendar Software by Notion All of your commitments, now in one place. Meet the beautifully designed, fully integrated calendar for your work and life. View product Fajr Calendar Calendar Software by Blink22 A calendar built for more — to help you live intentionally, stay focused, and bring meaning to every moment of your day. Fajr Calendar — powered by Blink22. View product CompuLaw Calendar Software by Aderant Protect your practice with rules-based calendaring using Aderant CompuLaw, the number one legal calendar, docket, and matter management solution. Reduce the risk of malpractice exposure from calendar-related errors and reduce potential human errors with rules-based, configurable date calculations. View product Tuta Calendar Calendar Software by Tuta | Secure Email & Calendar Manage your ambitious schedule with the most secure calendar. Control your day, week and month encrypted in Tuta. This way no one can spy on your personal events and business meetings while you are notified with zero-knowledge event reminders. View product Akiflow Calendar Software by Akiflow Akiflow is a task manager and time blocking app that aims to boost individual productivity with better time management. Our app makes the user's daily planning more practical with these core features: - Inbox consolidation. Through smart integrations, you can pull tasks from other productivity and communication tools and create a unified view of all your tasks. - Time blocking. Drag and drop the tasks to pin them into your calendar and block some time for deep focus. - Share availability. Let your teammates know what is your plan for the day and what are the free spots on your schedule. Akiflow is for everyone and anyone who wishes to have a unified view of their tasks, always finding time to get everything done without overwhelming themselves. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights Oktana Calendar (for Salesforce) Calendar Software by Oktana Take your team beyond the default Salesforce Calendar component with Oktana Calendar. Your team will be able to quickly add, edit, delete and even color-code events from within any home page or app page in your org. Based on a responsive design, this calendar keeps up with your busy users (even on the go) and reminds them so they never miss an event. We leverage the Salesforce Calendar, providing additional features to help you manage your time more efficiently. View product Calendars Calendar Software by Readdle Connect all your calendars, manage all your events & tasks, and see everything at a glance. View product Clockwise Calendar Software by Clockwise Clockwise optimizes teams’ calendars to create more time in everyone’s day. Clockwise automatically creates uninterrupted Focus Time in your schedule for deep work. It helps organizations achieve ambitious goals by creating time for important work and preventing employee burnout. The company’s mission is to help people make time for what matters, and over 15,000 organizations run on Clockwise, including Twitter, Atlassian, Uber, and Asana. View product Calendar API Calendar Software by Nylas The Nylas Calendar API is a single point of integration to connect to your users’ calendars and quickly build customizable scheduling workflows in your application. View product Agenda Colaborativa Calendar Software by SULTS Impulsione a produtividade da sua equipe com nossa agenda colaborativa de última geração. Agende reuniões, compartilhe tarefas e gerencie projetos com facilidade, tudo em um único lugar. Aumente a eficiência e mantenha todos na mesma página com visibilidade total das atividades e prazos. Experimente a transformação que nossa ferramenta pode trazer para o seu negócio hoje mesmo! View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/categories/customer-relationship-management-software?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_subtitle-click | Best Customer Relationship Management (CRM) Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Sales Manager (196) Salesperson (149) Sales Specialist (108) Chief Executive Officer (87) Marketing Specialist (85) See all products Find top products in Customer Relationship Management (CRM) Software category Software used to oversee company interaction with current and potential clients. - Manage relationships with customers and improve customer retention - Use a set of sales-related functions and drive sales growth - Compile data from different channels to a single record system 1535 results Sales Cloud Customer Relationship Management (CRM) Software by Salesforce Accelerate growth with your Humans + AI dream team. Ready to elevate every step of your sales cycle, from pipeline to paycheck? Scale your team with AI agents, equip your human sellers with the data and insights they need to win, and drive operational efficiency—all on Sales Cloud, the #1 agentic sales software platform. View product Zoho CRM Customer Relationship Management (CRM) Software by Zoho Zoho CRM is an online customer relationship management software for managing your sales, marketing, support in a single system. Zoho CRM helps businesses of all sizes build excellent customer relationships, with features like an inbuilt AI sales assistant, sales pipeline management, marketing automation, analytics, and more. Zoho CRM empowers a global network of over 150,000 businesses in 180 countries to convert more leads, engage with customers, and grow their revenue. View product Bigin by Zoho CRM Customer Relationship Management (CRM) Software by Zoho Bigin by Zoho CRM is a simplified customer relationship management (CRM) software designed specifically for small businesses, startups and teams! Trusted by 20,000+ businesses, Bigin helps small businesses unify all customer-facing operations— marketing, sales, onboarding, delivery, and support and manage customer relationships effectively. View product Experian DataShare Customer Relationship Management (CRM) Software by Experian Experian DataShare will accelerate new client onboarding and help increase retention through a simplified user experience. The platform integrates with over 100 versions of cloud and on-premise packages to deliver unparalleled accounting connectivity, flexible platform deployment, and instant audit or credit intelligence. It supports 100% of desktop and online accounting packages... including document uploading. Clients get faster decisions and have technical support if they experience any issues during their onboarding journey. Experian DataShare creates a digital pathway that removes the friction associated with the document gathering process. Start your digital journey to collect, format and interpret your client financials today! View product Odoo CRM Customer Relationship Management (CRM) Software by Odoo With over 5 million users, Odoo is the #1 open-source CRM software in the world! Sales teams can easily keep track of top leads and opportunities with just a few clicks. Users can personalize their sales cycle, take control of their statistics/forecasts, and create incredible marketing campaign automation to increase their overall sales performance. With Odoo CRM, sales teams are able to analyze the quality of their leads, make faster decisions, and save valuable time by integrating emails from all contacts directly into this fully-integrated app. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights Freshsales Customer Relationship Management (CRM) Software by Freshworks Freshsales provides a context-driven CRM solution for businesses of all sizes. We do this by taking a fresh approach to building and delivering an AI-driven and cost-effective omnichannel software—empowering sales teams to engage, nurture, and create delighted customers, to drive clear business results. View product Clickup Customer Relationship Management (CRM) Software by ClickUp Save time with the all-in-one productivity platform that brings teams, tasks, and tools together in one place. View product Infor CRM Customer Relationship Management (CRM) Software by Infor Infor CRM software provides a view of every customer touch point across an organization’s sales, marketing, customer service, and support teams. View product Pega Platform Customer Relationship Management (CRM) Software by Pegasystems Pega Platform helps improve business operation by enhancing employee productivity and delivering rapid, personalized service to customers. With enterprise-grade AI, automation, and low code for all users across an organization, Pega Platform enables you to respond to business needs in real time, scale quickly, and evolve as your needs change. Get work done while reducing costs and manual work across your business operations with Pega’s low-code platform for AI-powered decision and workflow automation. View product Zendesk Sell Customer Relationship Management (CRM) Software by Zendesk Zendesk Sell is a modern sales CRM to help you accelerate revenue. It’s a sales tool that’s quick to set up, intuitive, and easy to love. View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/akamai-technologies-kona-ddos-defender/?trk=products_seo_search | Kona DDoS Defender | LinkedIn Skip to main content LinkedIn Akamai Technologies in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Kona DDoS Defender DDoS Protection Software by Akamai Technologies See who's skilled in this Add as skill Learn more Report this product About Always-on, managed DDoS protection service to stop DDoS for critical websites and web applications. HTTP and HTTPS. Similar products Cloudflare DDoS Protection Cloudflare DDoS Protection DDoS Protection Software Cloudflare Spectrum Cloudflare Spectrum DDoS Protection Software Akamai Prolexic Routed Akamai Prolexic Routed DDoS Protection Software OVHcloud Anti-DDoS Protection OVHcloud Anti-DDoS Protection DDoS Protection Software Kaspersky DDoS Protection Kaspersky DDoS Protection DDoS Protection Software Arbor Cloud DDoS Protection Arbor Cloud DDoS Protection DDoS Protection Software Sign in to see more Show more Show less Akamai Technologies products Akamai Edge DNS Akamai Edge DNS Managed DNS Services Software Akamai Identity Cloud Akamai Identity Cloud Identity & Access Management (IAM) Software Akamai IoT Edge Connect Akamai IoT Edge Connect Internet of Things (IoT) Software Akamai Prolexic Routed Akamai Prolexic Routed DDoS Protection Software Aura Managed CDN Aura Managed CDN Content Delivery Network (CDN) Software BOCC BOCC Live Streaming Software DNSi AuthServe DNSi AuthServe Managed DNS Services Software DNSi Big Data Connector DNSi Big Data Connector Managed DNS Services Software Enterprise Threat Protector Enterprise Threat Protector Secure Web Gateways Media Services Live Media Services Live Live Streaming Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://git-scm.com/book/ko/v2/Git%ec%9d%98-%ea%b8%b0%ec%b4%88-Git-%ec%a0%80%ec%9e%a5%ec%86%8c-%eb%a7%8c%eb%93%a4%ea%b8%b0 | Git - Git 저장소 만들기 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 시작하기 1.1 버전 관리란? 1.2 짧게 보는 Git의 역사 1.3 Git 기초 1.4 CLI 1.5 Git 설치 1.6 Git 최초 설정 1.7 도움말 보기 1.8 요약 2. Git의 기초 2.1 Git 저장소 만들기 2.2 수정하고 저장소에 저장하기 2.3 커밋 히스토리 조회하기 2.4 되돌리기 2.5 리모트 저장소 2.6 태그 2.7 Git Alias 2.8 요약 3. Git 브랜치 3.1 브랜치란 무엇인가 3.2 브랜치와 Merge 의 기초 3.3 브랜치 관리 3.4 브랜치 워크플로 3.5 리모트 브랜치 3.6 Rebase 하기 3.7 요약 4. Git 서버 4.1 프로토콜 4.2 서버에 Git 설치하기 4.3 SSH 공개키 만들기 4.4 서버 설정하기 4.5 Git 데몬 4.6 스마트 HTTP 4.7 GitWeb 4.8 GitLab 4.9 또 다른 선택지, 호스팅 4.10 요약 5. 분산 환경에서의 Git 5.1 분산 환경에서의 워크플로 5.2 프로젝트에 기여하기 5.3 프로젝트 관리하기 5.4 요약 6. GitHub 6.1 계정 만들고 설정하기 6.2 GitHub 프로젝트에 기여하기 6.3 GitHub 프로젝트 관리하기 6.4 Organization 관리하기 6.5 GitHub 스크립팅 6.6 요약 7. Git 도구 7.1 리비전 조회하기 7.2 대화형 명령 7.3 Stashing과 Cleaning 7.4 내 작업에 서명하기 7.5 검색 7.6 히스토리 단장하기 7.7 Reset 명확히 알고 가기 7.8 고급 Merge 7.9 Rerere 7.10 Git으로 버그 찾기 7.11 서브모듈 7.12 Bundle 7.13 Replace 7.14 Credential 저장소 7.15 요약 8. Git맞춤 8.1 Git 설정하기 8.2 Git Attributes 8.3 Git Hooks 8.4 정책 구현하기 8.5 요약 9. Git과 여타 버전 관리 시스템 9.1 Git: 범용 Client 9.2 Git으로 옮기기 9.3 요약 10. Git의 내부 10.1 Plumbing 명령과 Porcelain 명령 10.2 Git 개체 10.3 Git Refs 10.4 Packfile 10.5 Refspec 10.6 데이터 전송 프로토콜 10.7 운영 및 데이터 복구 10.8 환경변수 10.9 요약 A1. 부록 A: 다양한 환경에서 Git 사용하기 A1.1 GUI A1.2 Visual Studio A1.3 Eclipse A1.4 Bash A1.5 Zsh A1.6 Git in Powershell A1.7 요약 A2. 부록 B: 애플리케이션에 Git 넣기 A2.1 Git 명령어 A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. 부록 C: Git 명령어 A3.1 설치와 설정 A3.2 프로젝트 가져오기와 생성하기 A3.3 스냅샷 다루기 A3.4 Branch와 Merge A3.5 공유하고 업데이트하기 A3.6 보기와 비교 A3.7 Debugging A3.8 Patch 하기 A3.9 Email A3.10 다른 버전 관리 시스템 A3.11 관리 A3.12 Plumbing 명령어 2nd Edition 2.1 Git의 기초 - Git 저장소 만들기 Git을 사용하는 방법을 알고 싶은데 한 챕터밖에 읽을 시간이 없다면 이번 챕터를 읽어야 한다. Git에서 자주 사용하는 명령어는 모두 2장에 등장한다. 2장을 다 읽으면 저장소를 만들고 설정하는 방법, 파일을 추적하거나(Track) 추적을 그만두는 방법, 변경 내용을 Stage 하고 커밋하는 방법을 알게 된다. 파일이나 파일 패턴을 무시하도록 Git을 설정하는 방법, 실수를 쉽고 빠르게 만회하는 방법, 프로젝트 히스토리를 조회하고 커밋을 비교하는 방법, 리모트 저장소에 Push 하고 Pull 하는 방법을 살펴본다. Git 저장소 만들기 주로 다음 두 가지 중 한 가지 방법으로 Git 저장소를 쓰기 시작한다. 아직 버전관리를 하지 않는 로컬 디렉토리 하나를 선택해서 Git 저장소를 적용하는 방법 다른 어딘가에서 Git 저장소를 Clone 하는 방법 어떤 방법을 사용하든 로컬 디렉토리에 Git 저장소가 준비되면 이제 뭔가 해볼 수 있다. 기존 디렉토리를 Git 저장소로 만들기 버전관리를 하지 아니하는 기존 프로젝트를 Git으로 관리하고 싶은 경우 우선 프로젝트의 디렉토리로 이동한다. 이러한 과정을 처음 해보는 것이라면 시스템마다 조금 다른 점을 주의하자. Linux: $ cd /home/user/my_project Mac: $ cd /Users/user/my_project Windows: $ cd /c/user/my_project 그리고 아래와 같은 명령을 실행한다: $ git init 이 명령은 .git 이라는 하위 디렉토리를 만든다. .git 디렉토리에는 저장소에 필요한 뼈대 파일(Skeleton)이 들어 있다. 이 명령만으로는 아직 프로젝트의 어떤 파일도 관리하지 않는다. ( .git 디렉토리가 막 만들어진 직후에 정확히 어떤 파일이 있는지에 대한 내용은 Git의 내부 에서 다룬다) Git이 파일을 관리하게 하려면 저장소에 파일을 추가하고 커밋해야 한다. git add 명령으로 파일을 추가하고 git commit 명령으로 커밋한다: $ git add *.c $ git add LICENSE $ git commit -m 'initial project version' 명령어 몇 개로 순식간에 Git 저장소를 만들고 파일 버전 관리를 시작했다. 기존 저장소를 Clone 하기 다른 프로젝트에 참여하려거나(Contribute) Git 저장소를 복사하고 싶을 때 git clone 명령을 사용한다. 이미 Subversion 같은 VCS에 익숙한 사용자에게는 "checkout" 이 아니라 "clone" 이라는 점이 도드라져 보일 것이다. Git이 Subversion과 다른 가장 큰 차이점은 서버에 있는 거의 모든 데이터를 복사한다는 것이다. git clone 을 실행하면 프로젝트 히스토리를 전부 받아온다. 실제로 서버의 디스크가 망가져도 클라이언트 저장소 중에서 아무거나 하나 가져다가 복구하면 된다(서버에만 적용했던 설정은 복구하지 못하지만 모든 데이터는 복구된다 - 서버에 Git 설치하기 에서 좀 더 자세히 다룬다). git clone <url> 명령으로 저장소를 Clone 한다. libgit2 라이브러리 소스코드를 Clone 하려면 아래과 같이 실행한다. $ git clone https://github.com/libgit2/libgit2 이 명령은 “libgit2” 라는 디렉토리를 만들고 그 안에 .git 디렉토리를 만든다. 그리고 저장소의 데이터를 모두 가져와서 자동으로 가장 최신 버전을 Checkout 해 놓는다. libgit2 디렉토리로 이동하면 Checkout으로 생성한 파일을 볼 수 있고 당장 하고자 하는 일을 시작할 수 있다. 아래과 같은 명령을 사용하여 저장소를 Clone 하면 libgit2 이 아니라 다른 디렉토리 이름으로 Clone 할 수 있다. $ git clone https://github.com/libgit2/libgit2 mylibgit 디렉토리 이름이 mylibgit 이라는 것만 빼면 이 명령의 결과와 앞선 명령의 결과는 같다. Git은 다양한 프로토콜을 지원한다. 이제까지는 https:// 프로토콜을 사용했지만 git:// 를 사용할 수도 있고 user@server:path/to/repo.git 처럼 SSH 프로토콜을 사용할 수도 있다. 자세한 내용은 서버에 Git 설치하기 에서 다루며 각 프로토콜의 장단점과 Git 저장소에 접근하는 방법을 설명한다. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/netscout-omnis-threat-horizon/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_image-click | Omnis Threat Horizon | LinkedIn Skip to main content LinkedIn NETSCOUT in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Omnis Threat Horizon DDoS Protection Software by NETSCOUT See who's skilled in this Add as skill Try now Report this product About NETSCOUT's Omnis Threat Horizon is a free tool composed of highly curated, real-time global threat data presented in a way that allows you to understand how it impacts your organization. Media Products media viewer No more previous content NETSCOUT Omnis Threat Horizon Omnis Threat Horizon delivers situational awareness across the threat landscape and presents it in a way that organizations can use to understand how it impacts them. Omnis Threat Horizon allows you to view the data however you want to see it, by industry, by vertical, region or country. Our unparalleled visibility allows you to understand what is happening with malicious traffic across the internet that is relevant to your organization. DDoS Attacks During COVID-19 Omnis Threat Horizon provides free insight into the rise in DDoS attacks during the COVID-19 pandemic. Omnis Threat Horizon Real-time global threat intelligence. No more next content Similar products Cloudflare DDoS Protection Cloudflare DDoS Protection DDoS Protection Software Cloudflare Spectrum Cloudflare Spectrum DDoS Protection Software Akamai Prolexic Routed Akamai Prolexic Routed DDoS Protection Software OVHcloud Anti-DDoS Protection OVHcloud Anti-DDoS Protection DDoS Protection Software Kona DDoS Defender Kona DDoS Defender DDoS Protection Software Kaspersky DDoS Protection Kaspersky DDoS Protection DDoS Protection Software Sign in to see more Show more Show less NETSCOUT products Arbor Edge Defense Arbor Edge Defense DDoS Protection Software Arbor Cloud DDoS Protection Arbor Cloud DDoS Protection DDoS Protection Software Arbor Sightline Arbor Sightline Network Monitoring Software Arbor Threat Mitigation System (TMS) Arbor Threat Mitigation System (TMS) DDoS Protection Software InfiniStreamNG (ISNG) InfiniStreamNG (ISNG) Business Continuity Software nGenius Business Analytics nGenius Business Analytics Business Intelligence (BI) Software nGeniusONE nGeniusONE Application Performance Monitoring (APM) Software nGeniusPULSE nGeniusPULSE Network Management Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://www.dataport.de/dworkflow/?mtm_campaign=dworkflow&mtm_source=linkedin&mtm_medium=pp&mtm_content=awareness&mtm_group=rv13&trk=products_details_guest_secondary_call_to_action | dWorkflow – Prozesse einfach transparent | Dataport Ihre Cookie-Einstellungen für diese Webseite Treffen Sie hier Ihre persönlichen Einstellungen Erforderliche Cookies Erforderliche Cookies sind für die Nutzung der Webseite zwingend erforderlich. Die Webseite kann ohne diese Cookies nicht richtig funktionieren. Einzelne Cookies Cookiename: cookiehint; Anbieter: Dataport; Zweck: Dieser Cookie speichert die Einstellung zu Cookies; Laufzeit: 1 Jahr Statistik Diese Cookies helfen uns bei der Analyse des Nutzerverhaltens, um die Qualität unserer Webseite fortlaufend zu verbessern. Einzelne Cookies Cookiename: _pk_id.*; Anbieter: Dataport; Zweck: Erhebung statistischer Daten in Matomo darüber, wie die Webseite von Besucher*innen genutzt wird; Laufzeit: 12 Monate Cookiename: _pk_ref.*; Anbieter: Dataport; Zweck: Erhebung statistischer Daten in Matomo darüber, woher die Besucher*innen dieser Webseite gekommen sind; Laufzeit: 6 Monate Cookiename: _pk_ses.*, _pk_cvar.*; Anbieter: Dataport; Zweck: Erhebung statistischer Daten in Matomo darüber, wie die Webseite von Besucher*innen genutzt wird; Laufzeit: 30 Minuten Weitere Informationen zu Cookies finden Sie in der Datenschutzerklärung Abbrechen Speichern Ihre Daten sind bei uns sicher Als Datenschutzexpert*innen klären wir transparent darüber auf, welche Daten wie und warum verarbeitet werden ( zur Datenschutzerklärung zum Impressum ). Auf dieser Website verwenden wir Cookies. Das sind kleine Dateien, die lokal im Browser gespeichert werden. Einige dieser Cookies sind unbedingt erforderlich, damit Sie diese Website nutzen können und alles richtig funktioniert. Über die Verwendung anderer Cookies entscheiden Sie selbst. Ganz gleich wie Sie sich entscheiden – wir respektieren Ihre Privatsphäre und wir gehen stets verantwortungsvoll mit den Daten um, die Sie uns anvertrauen. Ich entscheide selbst Ich bin einverstanden Ich lehne ab Zur Suche Ansprechpartner*innen finden Störung melden Zu den Jobs Zum Inhalt Menü Unternehmen Dataport Nachhaltigkeit Diversity Digitale Souveränität Geschäftsbericht Organe Partner Services & Produkte Consulting Innovationsmanagement Projektmanagement Rechenzentrum Druckzentrum Software-Entwicklung Weiterbildung Client-Betriebsmodelle IT-Beschaffung SAP-Kompetenzzentrum Fachanwendungen IT-Produkte Unsere Themen Künstliche Intelligenz IT Sicherheit Cloud Onlinezugangsgesetz Open Source Netze Alle Themen Karriere Arbeiten bei Dataport Onboarding Benefits Rund ums Bewerben Qualifizierung Einstieg Aufgabengebiete Veranstaltungen Insights Podcast Jobs Newsroom Übersicht Stories News & Presse Downloads Datareport Support Leichte Sprache Gebärden-sprache English Summary Dialog schließen Ihr direkter Weg zum Ziel Ihr Suchbegriff Suchen Dialog schließen Ansprechpartner*innen Bitte wählen Sie Ihr Anliegen Bitte wählen Pressefragen Karrierefragen Produkte und Vertrieb Internetseite Britta Heinrich Pressesprecherin 040 42846-3047 0171 3342284 E-Mail schreiben Karen Hoffmann-Abraham Stellvertretende Pressesprecherin 040 42846-3736 0176 42860910 E-Mail schreiben Karriereteam E-Mail schreiben Michael Schulz-Heirich Bereichsleiter Vertrieb 040 42846-2881 E-Mail schreiben Online-Redaktion E-Mail schreiben Zentrale: 0431 3295-0 poststelle@dataport.de Mo–Fr: 06:30–18:00 Uhr Dialog schließen Störungsmeldung Region wählen Bitte wählen Hamburg Schleswig-Holstein Bremen Sachsen-Anhalt Kreis Dithmarschen Störungsart wählen Bitte wählen Bei Problemen mit dem BASIS-Standardarbeitsplatz Bei Problemen mit der Schulverwaltungsplattform TUVAS Bei Problemen mit LOGINEO Bei allen anderen IT-Störungen Bei Telefonstörung Bei Mobilfunkproblemen Störungsart wählen Bitte wählen Bei Problemen mit der Plattform ABS Bei Problemen mit dem +1-Arbeitsplatz Bei anderen IT-Störungen Störungsart wählen Bitte wählen Bei Problemen mit dem BASIS-Standardarbeitsplatz Bei Problemen mit dem Fachverfahren MESO Bei allen anderen IT-Störungen Bei Mobilfunkproblemen Störungsart wählen Bitte wählen Bei IT-Problemen mit den StApl-Arbeitsplätzen Bei IT-Problemen aller anderen Kunden Bei IT-Problemen der Polizei ST Störungsart wählen Bitte wählen Bei IT-Störungen Ihre Rufnummer 040 428-333 Ihre Rufnummer 040 42846-3990 Ihre Rufnummer 040 42846-4284 Ihre Rufnummer 040 42846-750 Ihre Rufnummer 040 428-22 Ihre Rufnummer 040 42846-1965 Ihre Rufnummer 0431 3295 7000 Ihre Rufnummer 0431 3295-888 Ihre Rufnummer 0431 3295-444 Ihre Rufnummer 0421 361-55555 Ihre Rufnummer 0421 83558-3559 Ihre Rufnummer 0421 83558-444 Ihre Rufnummer 040 42846-1965 Ihre Rufnummer 0391 6627-1500 Ihre Rufnummer 0391 6627-1545 Ihre Rufnummer 0391-6627-1501 Ihre Rufnummer 0431 3295-3295 Dialog schließen Jobs Zum Jobportal Jetzt Jobalert einrichten Startseite Services & Produkte IT-Produkte dWorkflow dWorkflow – Arbeitsabläufe smart koordiniert Jetzt Demo vereinbaren Kurz erklärt Analoge und pseudo-digitalisierte Arbeitsabläufe sind aufwändig, kosten Zeit und sind intransparent. Deutlich besser geht es digital und ohne Medienbrüche: mit dWorkflow, der Open-Source-Lösung für standardisierte, einfache Arbeitsabläufe! Prozesse transparent abbilden: So funktioniert's Sie können sich dieses YouTube-Video direkt auf unserer Internetseite anschauen. Wir weisen darauf hin, dass dabei personenbezogene Daten (z. B. IP-Adresse) an YouTube übermittelt werden. Datenschutz . Video anschauen Das sagen unsere Kund*innen Mit dWorkflow gehen alle EVB-IT-Verträge mit Dataport an zentraler Stelle ein, und wir haben den Status immer im Blick. Die Durchlaufzeiten zwischen der Angebotsübermittlung und der Vertragsunterzeichnung haben sich dabei erheblich verringert. Und durch den durchgängig digitalisierten Prozess kommen wir heute fast vollständig ohne Papier aus. Nina Lembke Digitalisierung und Zentrales IT-Management, Staatskanzlei des Landes Schleswig-Holstein Das Gesamtsystem empfinde ich als sehr angenehm im Vergleich zur vorherigen Papierarbeitsweise und möchte nicht mehr zurück. Mathias Bergolte Referatsleiter Informations- und Kommunikationstechnik, Freie Hansestadt Bremen Mehr Effizienz und Transparenz in Prozessen Mit dWorkflow ersetzen Sie bisher analoge Abläufe durch digitale Workflows. Damit gehören Unterschriftenmappen und lästige E-Mail-Ketten der Geschichte an. Definieren Sie Workflow-Vorlagen mit festen Bearbeitungsschritten und bei Bedarf mit integrierten Formularen. Stellen Sie diese allen Personen in Ihrer Organisation oder bestimmten Benutzerkreisen zur Verfügung. So standardisieren Sie Ihre Arbeitsabläufe und reduzieren ganz nebenbei Bearbeitungszeiten und Prozesskosten. Schnell und einfach erreichen Sie spürbare Verbesserungen. Ein Workflow kann dabei der Abstimmung und Freigabe eines Dokuments dienen oder der reinen Abarbeitung einzelner Routineaufgaben, wie z.B. beim Onboarding von Mitarbeiter*innen. Alle Vorgänge haben dabei eines gemeinsam: Sie folgen einem stets wiederkehrenden Schema. Besonderer Vorteil: Sämtliche Schritte sind jederzeit für alle am Workflow beteiligten Personen nachvollziehbar. Sie müssen kein To-do mehr im Kopf behalten – ein Blick ins Tool genügt. Zudem ist jederzeit klar, bei wem ein offener Vorgang gerade liegt. Selbst wenn die verantwortliche Person gerade abwesend ist, läuft der Prozess dank Vertretungsregelungen weiter. Rückfragen lassen sich direkt im Workflow stellen und werden mitsamt der übrigen Aktivitäten automatisch revisionssicher protokolliert. Das macht Ihre Prozesse und Entscheidungen auch im Nachhinein nachvollziehbar! Produktvorteile Open Source : Mit dWorkflow sorgen Sie für digitale Souveränität. Strukturiert : Vorlagen standardisieren Ihre Abläufe und optimieren Ihre Prozessqualität. Einfach koordiniert : Sie können Workflows problemlos mit anderen Behörden und Institutionen abarbeiten. Schnell : Ihre Vorgänge werden spürbar beschleunigt und Ihr Arbeitsalltag dank der Übersichtlichkeit erheblich vereinfacht. Transparent : Sie wissen jederzeit, bei wem sich ein Vorgang gerade befindet. Rechtssicher : Jeder Workflow wird revisionssicher dokumentiert und zur Ablage vorbereitet. Effizient : dWorkflow ist dank flexiblem Preismodell individuell skalierbar und eignet sich bereits für kleinste Abstimmungsaufgaben, kann aber auch größere Abläufe systematisieren. Anwendungsbeispiele Auswahl Beschaffungsprozess Unterschriftenmappe Antragsformulare Personal-Onboarding Genehmigungen Interne Bestellprozesse sind oftmals "old fashioned": Formulare müssen ausgefüllt, Genehmigungen eingeholt und Vorgänge per Hauspost an die richtige Stelle geschickt werden. E-Mails sind in diesem Kontext keine wirkliche Alternative. Mit dWorkflow erhält Ihr Beschaffungsprozess einen Turbo. Über integrierte Formulare lösen Sie bisherige Dateien ab. Postumläufe entfallen und der Prozess wird schneller abgearbeitet. Unterschriftenmappen sind heute noch weit verbreitet, transportieren aber auch ein altes Problem: Die Person, bei der die Mappe physikalisch auf dem Schreibtisch liegt, ist die einzige, die sie bearbeiten und weitergeben kann. Abstimmungsprozesse per E-Mail können die Zusammenarbeit zwar beschleunigen. Sie machen Abläufe jedoch oft unübersichtlicher. Mit dWorkflow schaffen Sie Transparenz: Es ist jederzeit ersichtlich, wo der Vorgang gerade liegt und welchen Status er hat. Aufgaben lassen sich gleichzeitig bearbeiten und mit einem Klick weitergeben. Zudem sind Entscheidungsprozesse nachvollziehbar und werden revisionssicher dokumentiert. Integrieren Sie dWorkflow direkt in Ihr Mitarbeiterportal und vereinfachen Sie z.B. mit der Formularfunktion Ihre Antragstellung: Einfach per Klick einen Antrag aufrufen, zum Beispiel einen Dienstreise- oder Urlaubsantrag. Dank des vordefinierten Prozesses weiß dWorkflow, welche Person oder Gruppe zuerst an der Reihe ist und wer darauf folgt. So steuert dWorkflow die gesamte Bearbeitung, vom Ausfüllen des Formulars über die notwendigen Genehmigungen bis hin zur Archivierung des Vorgangs. Ein guter Start ist für neue Mitarbeiter*innen und das Unternehmen gleichermaßen wichtig und sollte nicht dem Zufall überlassen bleiben. Mit dWorkflow können Sie den Prozess des Onboardings in einer Vorlage definieren und beim Start neuer Mitarbeiter*innen immer den gleichen Workflow starten. So behalten Sie stets den Überblick, ob der Onboarding-Prozess reibungslos verläuft. Führungskräfte genehmigen regelmäßig Budgets, Rechnungen und mehr. Mit dWorkflow sorgen Sie dafür, dass diese Anträge in Zukunft schnell und ohne Verzug genehmigt werden. Sie legen den Ablauf des Genehmigungsprozesses fest und organisieren die Vertretungsregeln. Ihre Mitarbeiter*innen wissen jederzeit, welche Führungskraft gerade verantwortlich ist. Jetzt Demo-Termin vereinbaren Welche Prozesse laufen in Ihrer Behörde langwierig per E-Mail oder sogar noch analog ab? Starten Sie mit dWorkflow und entwickeln Sie mit uns gemeinsam Ihre ersten Workflow-Vorlagen für effiziente und transparente Arbeitsabläufe. Jetzt Demotermin vereinbaren Downloads Anwenderbericht: Verträge mit dWorkflow freizeichnen (PDF) 225 KB Produktblatt dWorkflow (PDF) 381 KB Preisblatt dWorkflow (PDF) 91 KB Vereinbaren Sie jetzt einen kostenlosen Demo-Termin. * Pflichtfelder Vorname * Nachname * E-Mail-Adresse * Telefon Behörde/Institution/Firma * Ihre Nachricht Einwilligung für die elektronische Übermittlung * Ich willige in die elektronische Übermittlung meiner Daten gemäß Art. 6 Abs. 1 lit. a DSGVO ein (Opt-In). Eine Weiterverarbeitung der übermittelten Daten erfolgt ggf. auf Basis einer anderen Rechtsgrundlage. Absenden Weitere Informationen finden Sie in der Datenschutzerklärung . Bitte dieses Feld NICHT ausfüllen! Ihr Kontakt Michael Schulz-Heirich Bereichsleiter Vertrieb 040 42846-2881 E-Mail schreiben Team dWorkflow E-Mail schreiben Weiterführende Informationen Bildnachweise Bildnachweise © Dataport © bongkarn - stock.adobe.com © NDABCREATIVITY - stock.adobe.com © Dataport © H_Ko - stock.adobe.com © weyo - stock.adobe.com © C. Daniels/peopleimages.com - stock.adobe.com © Drazen - stock.adobe.com © peopleimages.com - stock.adobe.com © Dataport Schwerpunktthemen Open Source IT Sicherheit Onlinezugangsgesetz Cloud Netze Services & Produkte Consulting Innovationsmanagement Projektmanagement Rechenzentrum Druckzentrum Software-Entwicklung Weiterbildung Client-Betriebsmodelle IT-Beschaffung SAP-Kompetenzzentrum Fachanwendungen IT-Produkte Wir machen digitale Zukunft Starten Sie mit uns durch! Karriere bei Dataport Zu den Stellenangeboten Kontakt Dataport Altenholz Standort (Zentrale) Altenholzer Straße 10-14 24161 Altenholz 0431 3295-0 poststelle@dataport.de Kontakt Zertifizierung Portale Kundenportal Jobportal Weiterbildungsportal Shop Vergabeplattform dataport.kommunal Folgen Sie uns Kontakt Impressum AGB Datenschutz Barrierefreiheit Vergabeverfahren Fördermittelprojekte Sitemap | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/dataport-a%C3%B6r-dwebservice/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_full-click#main-content | dWebService | LinkedIn Skip to main content LinkedIn Dataport AöR in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in dWebService Web Hosting by Dataport AöR See who's skilled in this Add as skill Get started Report this product About Hosting. Webportale. Analysen. Ohne Webseite geht es heute nicht mehr. Dabei unterstützt Sie dWebService: Vom simplen Webspace bis hin zu einem vollständigen Content Management System. Inklusive sicherem Hosting, Barrierefreiheits-Check und smarten Nutzungsanalysen. Auf einen Blick: ✅ Individuelle Beratung und maßgeschneiderte Entwicklung von Webportalen ✅ Hosting im BSI-zertifizierten Twin Data Center ✅ Barrierefreie Webentwicklung ✅ DSGVO-konforme Nutzungsanalysen ✅ Entwicklung und Betreuung von Webportalen mit TYPO3 ✅ Integration von Active Directories und Single-Sign-On This product is intended for Head of Section Resort Manager Department Manager Information Technology Application Manager Information Technology Specialist Mayor Senior Administrative Officer State Secretary Chief Information Security Officer Press Officer Media Products media viewer No more previous content dWebService Schnelles und sicheres Hosting No more next content Similar products IPv4 Address Leasing Service IPv4 Address Leasing Service Web Hosting Pantheon Platform Pantheon Platform Web Hosting Elastic Metal Elastic Metal Web Hosting Web Hosting Web Hosting Web Hosting WooCommerce Hosting WooCommerce Hosting Web Hosting Cloudways Autonomous Cloudways Autonomous Web Hosting Sign in to see more Show more Show less Dataport AöR products data[port]ai data[port]ai Data Science & Machine Learning Platforms Dataport Consulting Dataport Consulting Strategic Planning Software dDataBox dDataBox Managed File Transfer (MFT) Software dMessenger dMessenger Enterprise Messaging Software dProjectTracking dProjectTracking Project Management Software dWorkflow dWorkflow Workflow Management Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://git-scm.com/book/es/v2/Fundamentos-de-Git-Etiquetado | Git - Etiquetado About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Inicio - Sobre el Control de Versiones 1.1 Acerca del Control de Versiones 1.2 Una breve historia de Git 1.3 Fundamentos de Git 1.4 La Línea de Comandos 1.5 Instalación de Git 1.6 Configurando Git por primera vez 1.7 ¿Cómo obtener ayuda? 1.8 Resumen 2. Fundamentos de Git 2.1 Obteniendo un repositorio Git 2.2 Guardando cambios en el Repositorio 2.3 Ver el Historial de Confirmaciones 2.4 Deshacer Cosas 2.5 Trabajar con Remotos 2.6 Etiquetado 2.7 Alias de Git 2.8 Resumen 3. Ramificaciones en Git 3.1 ¿Qué es una rama? 3.2 Procedimientos Básicos para Ramificar y Fusionar 3.3 Gestión de Ramas 3.4 Flujos de Trabajo Ramificados 3.5 Ramas Remotas 3.6 Reorganizar el Trabajo Realizado 3.7 Recapitulación 4. Git en el Servidor 4.1 Los Protocolos 4.2 Configurando Git en un servidor 4.3 Generando tu clave pública SSH 4.4 Configurando el servidor 4.5 El demonio Git 4.6 HTTP Inteligente 4.7 GitWeb 4.8 GitLab 4.9 Git en un alojamiento externo 4.10 Resumen 5. Git en entornos distribuidos 5.1 Flujos de trabajo distribuidos 5.2 Contribuyendo a un Proyecto 5.3 Manteniendo un proyecto 5.4 Resumen 6. GitHub 6.1 Creación y configuración de la cuenta 6.2 Participando en Proyectos 6.3 Mantenimiento de un proyecto 6.4 Gestión de una organización 6.5 Scripting en GitHub 6.6 Resumen 7. Herramientas de Git 7.1 Revisión por selección 7.2 Organización interactiva 7.3 Guardado rápido y Limpieza 7.4 Firmando tu trabajo 7.5 Buscando 7.6 Reescribiendo la Historia 7.7 Reiniciar Desmitificado 7.8 Fusión Avanzada 7.9 Rerere 7.10 Haciendo debug con Git 7.11 Submódulos 7.12 Agrupaciones 7.13 Replace 7.14 Almacenamiento de credenciales 7.15 Resumen 8. Personalización de Git 8.1 Configuración de Git 8.2 Git Attributes 8.3 Puntos de enganche en Git 8.4 Un ejemplo de implantación de una determinada política en Git 8.5 Recapitulación 9. Git y Otros Sistemas 9.1 Git como Cliente 9.2 Migración a Git 9.3 Resumen 10. Los entresijos internos de Git 10.1 Fontanería y porcelana 10.2 Los objetos Git 10.3 Referencias Git 10.4 Archivos empaquetadores 10.5 Las especificaciones para hacer referencia a… (refspec) 10.6 Protocolos de transferencia 10.7 Mantenimiento y recuperación de datos 10.8 Variables de entorno 10.9 Recapitulación A1. Apéndice A: Git en otros entornos A1.1 Interfaces gráficas A1.2 Git en Visual Studio A1.3 Git en Eclipse A1.4 Git con Bash A1.5 Git en Zsh A1.6 Git en Powershell A1.7 Resumen A2. Apéndice B: Integrando Git en tus Aplicaciones A2.1 Git mediante Línea de Comandos A2.2 Libgit2 A2.3 JGit A3. Apéndice C: Comandos de Git A3.1 Configuración A3.2 Obtener y Crear Proyectos A3.3 Seguimiento Básico A3.4 Ramificar y Fusionar A3.5 Compartir y Actualizar Proyectos A3.6 Inspección y Comparación A3.7 Depuración A3.8 Parcheo A3.9 Correo Electrónico A3.10 Sistemas Externos A3.11 Administración A3.12 Comandos de Fontanería 2nd Edition 2.6 Fundamentos de Git - Etiquetado Etiquetado Como muchos VCS, Git tiene la posibilidad de etiquetar puntos específicos del historial como importantes. Esta funcionalidad se usa típicamente para marcar versiones de lanzamiento (v1.0, por ejemplo). En esta sección, aprenderás cómo listar las etiquetas disponibles, cómo crear nuevas etiquetas y cuáles son los distintos tipos de etiquetas. Listar Tus Etiquetas Listar las etiquetas disponibles en Git es sencillo. Simplemente escribe git tag : $ git tag v0.1 v1.3 Este comando lista las etiquetas en orden alfabético; el orden en el que aparecen no tiene mayor importancia. También puedes buscar etiquetas con un patrón particular. El repositorio del código fuente de Git, por ejemplo, contiene más de 500 etiquetas. Si sólo te interesa ver la serie 1.8.5, puedes ejecutar: $ git tag -l 'v1.8.5*' v1.8.5 v1.8.5-rc0 v1.8.5-rc1 v1.8.5-rc2 v1.8.5-rc3 v1.8.5.1 v1.8.5.2 v1.8.5.3 v1.8.5.4 v1.8.5.5 Crear Etiquetas Git utiliza dos tipos principales de etiquetas: ligeras y anotadas. Una etiqueta ligera es muy parecido a una rama que no cambia - simplemente es un puntero a un commit específico. Sin embargo, las etiquetas anotadas se guardan en la base de datos de Git como objetos enteros. Tienen un checksum ; contienen el nombre del etiquetador, correo electrónico y fecha; tienen un mensaje asociado; y pueden ser firmadas y verificadas con GNU Privacy Guard (GPG). Normalmente se recomienda que crees etiquetas anotadas, de manera que tengas toda esta información; pero si quieres una etiqueta temporal o por alguna razón no estás interesado en esa información, entonces puedes usar las etiquetas ligeras. Etiquetas Anotadas Crear una etiqueta anotada en Git es sencillo. La forma más fácil de hacerlo es especificar la opción -a cuando ejecutas el comando git tag : $ git tag -a v1.4 -m 'my version 1.4' $ git tag v0.1 v1.3 v1.4 La opción -m especifica el mensaje de la etiqueta, el cual es guardado junto con ella. Si no especificas el mensaje de una etiqueta anotada, Git abrirá el editor de texto para que lo escribas. Puedes ver la información de la etiqueta junto con el commit que está etiquetado al usar el comando git show : $ git show v1.4 tag v1.4 Tagger: Ben Straub <ben@straub.cc> Date: Sat May 3 20:19:12 2014 -0700 my version 1.4 commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 changed the version number El comando muestra la información del etiquetador, la fecha en la que el commit fue etiquetado y el mensaje de la etiqueta, antes de mostrar la información del commit . Etiquetas Ligeras La otra forma de etiquetar un commit es mediante una etiqueta ligera. Una etiqueta ligera no es más que el checksum de un commit guardado en un archivo - no incluye más información. Para crear una etiqueta ligera, no pases las opciones -a , -s ni -m : $ git tag v1.4-lw $ git tag v0.1 v1.3 v1.4 v1.4-lw v1.5 Esta vez, si ejecutas git show sobre la etiqueta no verás la información adicional. El comando solo mostrará el commit : $ git show v1.4-lw commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 changed the version number Etiquetado Tardío También puedes etiquetar commits mucho tiempo después de haberlos hecho. Supongamos que tu historial luce como el siguiente: $ git log --pretty=oneline 15027957951b64cf874c3557a0f3547bd83b3ff6 Merge branch 'experiment' a6b4c97498bd301d84096da251c98a07c7723e65 beginning write support 0d52aaab4479697da7686c15f77a3d64d9165190 one more thing 6d52a271eda8725415634dd79daabbc4d9b6008e Merge branch 'experiment' 0b7434d86859cc7b8c3d5e1dddfed66ff742fcbc added a commit function 4682c3261057305bdd616e23b64b0857d832627b added a todo file 166ae0c4d3f420721acbb115cc33848dfcc2121a started write support 9fceb02d0ae598e95dc970b74767f19372d61af8 updated rakefile 964f16d36dfccde844893cac5b347e7b3d44abbc commit the todo 8a5cbc430f1a9c3d00faaeffd07798508422908a updated readme Ahora, supongamos que olvidaste etiquetar el proyecto en su versión v1.2, la cual corresponde al commit “updated rakefile”. Igual puedes etiquetarlo. Para etiquetar un commit, debes especificar el checksum del commit (o parte de él) al final del comando: $ git tag -a v1.2 9fceb02 Puedes ver que has etiquetado el commit: $ git tag v0.1 v1.2 v1.3 v1.4 v1.4-lw v1.5 $ git show v1.2 tag v1.2 Tagger: Scott Chacon <schacon@gee-mail.com> Date: Mon Feb 9 15:32:16 2009 -0800 version 1.2 commit 9fceb02d0ae598e95dc970b74767f19372d61af8 Author: Magnus Chacon <mchacon@gee-mail.com> Date: Sun Apr 27 20:43:35 2008 -0700 updated rakefile ... Compartir Etiquetas Por defecto, el comando git push no transfiere las etiquetas a los servidores remotos. Debes enviar las etiquetas de forma explícita al servidor luego de que las hayas creado. Este proceso es similar al de compartir ramas remotas - puedes ejecutar git push origin [etiqueta] . $ git push origin v1.5 Counting objects: 14, done. Delta compression using up to 8 threads. Compressing objects: 100% (12/12), done. Writing objects: 100% (14/14), 2.05 KiB | 0 bytes/s, done. Total 14 (delta 3), reused 0 (delta 0) To git@github.com:schacon/simplegit.git * [new tag] v1.5 -> v1.5 Si quieres enviar varias etiquetas a la vez, puedes usar la opción --tags del comando git push . Esto enviará al servidor remoto todas las etiquetas que aun no existen en él. $ git push origin --tags Counting objects: 1, done. Writing objects: 100% (1/1), 160 bytes | 0 bytes/s, done. Total 1 (delta 0), reused 0 (delta 0) To git@github.com:schacon/simplegit.git * [new tag] v1.4 -> v1.4 * [new tag] v1.4-lw -> v1.4-lw Por lo tanto, cuando alguien clone o traiga información de tu repositorio, también obtendrá todas las etiquetas. Sacar una Etiqueta En Git, no puedes sacar ( check out ) una etiqueta, pues no es algo que puedas mover. Si quieres colocar en tu directorio de trabajo una versión de tu repositorio que coincida con alguna etiqueta, debes crear una rama nueva en esa etiqueta: $ git checkout -b version2 v2.0.0 Switched to a new branch 'version2' Obviamente, si haces esto y luego confirmas tus cambios, tu rama version2 será ligeramente distinta a tu etiqueta v2.0.0 puesto que incluirá tus nuevos cambios; así que ten cuidado. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
http://www.trello.com/teams/remote-team-management | Trello for Remote Teams | Trello Skip to main content Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Use case: Task management Track progress of tasks in one convenient place with a visual layout that adds ‘ta-da’ to your to-do’s. Use case: Resource hub Save hours when you give teams a well-designed hub to find information easily and quickly. Use case: Project management Keep projects organized, deadlines on track, and teammates aligned with Trello. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Back Navigation Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Read though our use cases to make the most of Trello on your team. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Helping teams work better, together Discover Trello use cases, productivity tips, best practices for team collaboration, and expert remote work advice. Check out the Trello blog < Go back to Team Solutions Trello For Remote Teams From team bonding and brainstorming to meetings and project planning, discover how Trello keeps remote teams connected, no matter where they’re located around the world. Trello’s boards, lists, and cards enable teams to go from ideas to action in seconds. Visual and easy-to-use, Trello helps teams bring projects to life and keep them moving forward. Join over 2,000,000 teams worldwide who are using Trello to get more done. Your Remote Team’s Digital Workspace The sky’s the limit when your team is supported to work virtually. These Trello board templates will help everyone transform remote work woes into wins and set everyone up for success from anywhere, anytime. Get inspired, copy the boards, and make them your own! Explore all remote team templates Remote Team Hub Organize team resources, track projects, and monitor weekly progress all in one place. Remote Team Meetings Enjoy more structured agendas, an open meeting structure, celebrate successes, and remove roadblocks with this easy-to-use board. Remote Team Bonding Bring your team together virtually by creating shared experiences through remote activities. Remote Team Hub Organize team resources, track projects, and monitor weekly progress all in one place. Remote Team Meetings Enjoy more structured agendas, an open meeting structure, celebrate successes, and remove roadblocks with this easy-to-use board. Remote Team Bonding Bring your team together virtually by creating shared experiences through remote activities. Dial in on work happening across your remote team. Table View allows distributed teams to stay aligned, connected, and productive—no matter where team members fall on the map. Learn more about Trello views Power-Ups Your Remote Team Use these Power-Ups to achieve a whole new level of virtual collaboration and remote efficiency. Explore 150+ Power-Ups Move Work Forward, Auto-magically Trello’s built-in automation makes it easy to automate the repetitive, everyday tasks that keep your team from focusing on the work that matters most. Let the robots do the work Resources To Stay Connected From Afar Learn the top tips and techniques for remote success from teams who have lived and perfected the work-from-anywhere lifestyle for years. How To Embrace Remote Work [Guide] Discover the tips, strategies, and advice from the world’s leading companies in order to empower a productive and collaborative remote team. READ MORE Remote Work Playbook for Team Success [Blog Post] Communication, culture, and transparency are key for remote success, and a great place to start is with choosing the right tools. Learn best practices for new (and existing) remote teams and explore five tried and tested Trello boards and workflows made specifically with remote teams in mind. WATCH NOW The Secrets To Sustaining A Strong Remote Team [Blog Post] With the right attitude, tools, and leadership in place, creating a virtual workspace is not only possible, it’s enjoyable. READ MORE NOW AVAILABLE A 14 Day Free Trial of Premium! Get unlimited boards, Trello views, and limitless automation, plus a ton more. Try it today SwagUp: Scale Any Business With Trello BC “Not only did [Trello] unify our process and help everyone understand their role, but we were able to automate essential steps of the process so we could move a lot faster and grow to a multi-million dollar company with a team of ten.” –Founder, SwagUp Learn More Instinct Dog Training “As you scale, you need visibility, accountability, and organization. Trello has provided that for us.” –Brian Burton, Founder, Instinct Dog Training Learn More Desk Plants “We chose Trello because it is well-designed—it’s beautifully designed—intuitive, and really hit the nail on the head with what we needed to solve.” –Lawrence Hanley, founder of Desk Plants Learn More Scan2Cad “We use Trello because our data becomes alive. A bullet point list turns into real tasks that are assigned to real people with due dates and connections to our other apps. The power in that is fantastic.” –Luke Kennedy, CEO, Scan2Cad Learn More Palace Law “People have generally been happier since we started using Trello. It has made our lives a lot easier. People are less stressed.” -Jordan Couch, attorney at Palace Law Learn More Trello Your Way Ready to get your team up and running? Try the business tool so easy to use, your team can’t help but collaborate. Learn more about our pricing and plans Free $ 0 USD Free for up to 10 collaborators per Workspace Capture your to-dos, get organized, and get sh*t done. Standard $ 5 USD Per user/month if billed annually ($6 billed monthly) Get more stuff done with unlimited boards, card mirroring, and more automation. Learn more about Standard Premium $ 10 USD Per user/month if billed annually ($12.50 billed monthly) Add AI to your boards and admin controls to your toolkit. Plus, get more perspective with views. Learn more about Premium Enterprise $ 17.50 USD Per user/month - billed annually ($210.00 annual price per user) Add enterprise-grade security and controls. This plan includes Atlassian Guard Standard and 24/7 Enterprise Admin support. Est. cost for users Learn more about Enterprise Well, what are you waiting for? Head over to your boards and start getting things done! Log In About Trello What’s behind the boards. Jobs Learn about open roles on the Trello team. Apps Download the Trello App for your Desktop or Mobile devices. Contact us Need anything? Get in touch and we can help. Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Privacy Policy Terms Copyright © 2024 Atlassian | 2026-01-13T09:29:20 |
https://git-scm.com/book/sl/v2/Git-na-stre%c5%beniku-Prikriti-proces-Git | Git - Prikriti proces Git About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Začetek 1.1 O nadzoru različic 1.2 Kratka zgodovina Gita 1.3 Kaj je Git? 1.4 Ukazna vrstica 1.5 Namestitev Gita 1.6 Prva nastavitev Gita 1.7 Pridobivanje pomoči 1.8 Povzetek 2. Osnove Git 2.1 Pridobivanje repozitorija Git 2.2 Snemanje sprememb v repozitorij 2.3 Pregled zgodovine potrditev 2.4 Razveljavljanje stvari 2.5 Delo z daljavami 2.6 Označevanje 2.7 Aliasi Git 2.8 Povzetek 3. Veje Git 3.1 Veje na kratko 3.2 Osnove vej in združevanja 3.3 Upravljanje vej 3.4 Poteki dela z vejami 3.5 Oddaljene veje 3.6 Ponovno baziranje 3.7 Povzetek 4. Git na strežniku 4.1 Protokoli 4.2 Pridobitev Gita na strežniku 4.3 Generiranje vaših javnih ključev SSH 4.4 Nastavitev strežnika 4.5 Prikriti proces Git 4.6 Pametni HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti gostovanja pri tretjih ponudnikih 4.10 Povzetek 5. Porazdeljeni Git 5.1 Porazdeljeni poteki dela 5.2 Prispevek k projektu 5.3 Vzdrževanje projekta 5.4 Povzetek 6. GitHub 6.1 Namestitev in konfiguracija računa 6.2 Prispevek k projektu 6.3 Vzdrževanje projekta 6.4 Upravljanje organizacije 6.5 Skriptni GitHub 6.6 Povzetek 7. Orodja Git 7.1 Izbira revizije 7.2 Interaktivno pripravljanje 7.3 Shranjevanje na varno (angl. stashing) in čiščenje 7.4 Podpisovanje vašega dela 7.5 Iskanje 7.6 Prepisovanje zgodovine 7.7 Demistifikacija ponastavitve 7.8 Napredno združevanje 7.9 Rerere 7.10 Razhroščevanje z Gitom 7.11 Podmoduli 7.12 Povezovanje v pakete 7.13 Zamenjava 7.14 Shramba poverilnic 7.15 Povzetek 8. Prilagoditev Gita 8.1 Konfiguracija Git 8.2 Atributi Git 8.3 Kljuke Git 8.4 Primer pravilnika, ki ga uveljavlja Git 8.5 Povzetek 9. Git in ostali sistemi 9.1 Git kot odjemalec 9.2 Migracija na Git 9.3 Povzetek 10. Notranjost Gita 10.1 Napeljava in keramika 10.2 Objekti Git 10.3 Reference Git 10.4 Packfiles (datoteke zmanjšanih podatkov) 10.5 Refspec 10.6 Protokoli prenosa 10.7 Vzdrževanje in obnovitev podatkov 10.8 Spremenljivke okolja 10.9 Povzetek A1. Dodatek A: Git v drugih okoljih A1.1 Grafični vmesniki A1.2 Git v Visual Studio A1.3 Git v Visual Studio Code A1.4 Git v IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git v Sublime Text A1.6 Git v Bashu A1.7 Git v Zsh A1.8 Git v Powershellu A1.9 Povzetek A2. Dodatek B: Vdelava Gita v vašo aplikacijo A2.1 Git v ukazni vrstici A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Dodatek C: Ukazi Git A3.1 Nastavitev in konfiguracija A3.2 Pridobivanje in ustvarjanje projektov A3.3 Osnove posnetkov A3.4 Veje in združevanje A3.5 Deljenje in posodabljanje projektov A3.6 Pregled in primerjava A3.7 Razhroščevanje A3.8 Popravljanje A3.9 E-pošta A3.10 Zunanji sistemi A3.11 Administracija A3.12 Orodja za sisteme napeljave 2nd Edition 4.5 Git na strežniku - Prikriti proces Git Prikriti proces Git Naslednje bomo nastavili prikriti proces (angl. daemon ), ki streže repozitorije preko protokola »Git«. To je pogosta izbira za hiter, neoverjen dostop do vaših podatkov Git. Bodite pozorni, saj to ni overjena storitev in karkoli ponudite preko tega protokola, je javno znotraj njegovega omrežja. Če ga poganjate na strežniku izven svojega požarnega zidu, bi moral biti uporabljen samo za projekte, ki so javno vidni svetu. Če je strežnik, na katerem ga poganjate, znotraj vašega požarnega zidu, ga boste mogoče uporabili za projekte, do katerih ima veliko število ljudi ali računalnikov (stalna integracija ali strežniki za gradnjo) samo bralni dostop, ko ne želite dodati ključa SSH za vsakega. V kateremkoli primeru je protokol Git relativno enostavno nastaviti. V osnovi morate pognati ta ukaz v načinu prikritega procesa: $ git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Možnost --reuseaddr omogoča strežniku ponovni zagon brez čakanja, da stare povezave pretečejo, medtem ko možnost --base-path omogoča ljudem klonirati projekte brez določanja celotne poti in pot na koncu pove prikritemu procesu Git, da poišče repozitorije za izvoz. Če poganjate požarni zid, boste morali narediti vanj tudi luknjo na vratih 9418 na napravi, kjer to nastavljate. Ta proces lahko prikrijete na število načinov, odvisno od operacijskega sistema, na katerem ga poganjate. Ker je systemd najpogostejši zagonski sistem na modernih distribucijah Linuxa, ga lahko uporabite za ta namen. Enostavno dodate datoteko v /etc/systemd/system/git-daemon.service s sledečo vsebino: [Unit] Description=Start Git Daemon [Service] ExecStart=/usr/bin/git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Restart=always RestartSec=500ms StandardOutput=syslog StandardError=syslog SyslogIdentifier=git-daemon User=git Group=git [Install] WantedBy=multi-user.target Morda ste opazili, da je prikriti proces Git tu začet z git tako za skupino kot za uporabnika. Spremenite ga, da ustreza vašim potrebam in zagotovite, da podani uporabnik obstaja na sistemu. Preverite tudi, da je zagonska datoteka Git prav zares na /usr/bin/git , drugače spremenite pot, kot je treba. Na koncu boste pognali systemctl enable git-daemon , da se storitev avtomatsko zažene pri zagonu, in storitev lahko zaženete in končate s systemctl start git-daemon in systemctl stop git-daemon . Na drugih sistemih, boste morda želeli uporabiti xinetd , skript v vašem sistemu sysvinit , ali kaj drugega — dokler dobite ta ukaz kot prikriti proces in da je nekako spremljan. Naslednje morate Gitu povedati, katerim repozitorijem se dovoli neoverjen strežniško osnovani dostop Git. To lahko naredite v vsakem repozitoriju z izdelavo datoteke poimenovane git-daemon-export-ok . $ cd /path/to/project.git $ touch git-daemon-export-ok Prisotnost te datoteke pove Gitu, da je v redu ponuditi ta projekt brez overjanja. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/bg/v2/GitHub-%d0%90%d0%b2%d1%82%d0%be%d0%bc%d0%b0%d1%82%d0%b8%d0%b7%d0%b8%d1%80%d0%b0%d0%bd%d0%b5-%d1%81-GitHub | Git - Автоматизиране с GitHub About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 4.5 GitHub - Автоматизиране с GitHub Автоматизиране с GitHub Разгледахме повечето функции и работни похвати в GitHub, но всеки голям проект или група от разработчици е твърде вероятно да искат да имат собствени настройки или интеграция с външни услуги. За щастие, GitHub е доста гъвкав в това отношение. Тук ще разгледаме как се ползват hooks системата и API-то на GitHub. Услуги и Hooks Hooks and Services секцията в административната част на хранилище в GitHub е най-лесния начин да накарате GitHub да комуникира с външни системи. Services Ще разгледаме първо Services. И Hooks и Services интеграциите могат да се намерят в Settings секцията на вашето хранилище, където преди гледахме при добавяне на сътрудници и смяна на клона по подразбиране за хранилището. В секцията “Webhooks and Services” ще видите нещо подобно на Services and Hooks конфигурационна секция . Фигура 129. Services and Hooks конфигурационна секция Може да избирате от десетки услуги, повечето от тях предлагащи интеграция с други комерсиални или open source системи. Сред тях са Continuous Integration услуги, услуги за проследяване на проблеми и грешки, chat room системи и системи за документация. Нека разгледаме настройката на една от най-простите, Email hook. Изберете “email” от падащия списък “Add Service” и ще попаднете на екран подобен на Email service конфигурация . Фигура 130. Email service конфигурация В този случай, ако натиснете “Add service” бутона, имейл адресът който укажете ще получава съобщение всеки път, когато някой публикува код в хранилището. Услугите могат да слушат за много различни типове събития, но повечето от тях случат само за push събития и предприемат съответните действия с данните. Ако ползвате система, която искате да интегрирате с GitHub, трябва да проверите тук дали не съществува налична интеграционна услуга. Например, ако ползвате Jenkins за тестване на код, можете да разрешите вградената Jenkins интеграция за да пуснете автоматично тест всеки път когато някой публикува код в хранилището ви. Hooks Ако ви трябва нещо по-специфично или желаете да интегрирате с услуга/сайт, които не присъстват в списъка на GitHub, можете да използвате по-общата hooks система. Hooks функционалността на GitHub е доста опростена. Указвате URL и GitHub ще изпрати HTTP заявка към него при всяко желано от вас събитие. В общи линии, можете да пуснете малка уеб услуга, която да следи за hook-заявките от GitHub и да прави нещо с получените данни. За да разрешите hook, натиснете “Add webhook” бутона в Services and Hooks конфигурационна секция . Ще видите страница подобна на Web hook конфигурация . Фигура 131. Web hook конфигурация Конфигурацията е много опростена. В повечето случаи просто въвеждате URL и секретен ключ и натискате “Add webhook”. Има доста опции за това при кои събития искате GitHub да ви изпраща данни — по подразбиране това се случва само при push събития, когато някой публикува промени в произволен клон от хранилището. Нека видим малък пример за уеб услуга, която бихте могли да напишете за обслужване на данните от web hook. Ще използваме уеб framework системата Sinatra за Ruby, понеже тя е сравнително компактна и би следвало лесно да разберете какво вършим. Нека приемем, че искаме да получаваме поща, ако специфичен потребител публикува код в конкретен клон и промени конкретен файл. Можем сравнително лесно да го направим така: require 'sinatra' require 'json' require 'mail' post '/payload' do push = JSON.parse(request.body.read) # parse the JSON # gather the data we're looking for pusher = push["pusher"]["name"] branch = push["ref"] # get a list of all the files touched files = push["commits"].map do |commit| commit['added'] + commit['modified'] + commit['removed'] end files = files.flatten.uniq # check for our criteria if pusher == 'schacon' && branch == 'ref/heads/special-branch' && files.include?('special-file.txt') Mail.deliver do from 'tchacon@example.com' to 'tchacon@example.com' subject 'Scott Changed the File' body "ALARM" end end end Тук прочитаме JSON данните от GitHub и търсим кой е направил публикуването, в кой клон и кои файлове са били модифицирани във всички публикувани къмити. След това проверяваме информацията според нашия критерий и изпращаме имейл, ако срещнем съвпадение. За да разработите и тествате нещо от този род, разполагате с удобна developer конзола на същия екран, в който настройвате вашия hook. Можете да видите последните няколко съобщения, които GitHub се е опитал да направи за този webhook. За всеки hook може да видите в детайли кога е бил изпратен, дали изпращането е успешно, както и тялото и хедърите за заявката и отговора при операцията. Това много улеснява тестването и дебъгването на вашите hooks. Фигура 132. Web hook debugging данни Друга чудесна особеност е, че можете да повтаряте изпращането на всяка заявка за да тествате уеб услугата си лесно. За повече информация как да пишете webhooks и за всички възможни типове GitHub събития, погледнете документацията за разработчици на GitHub на адрес https://developer.github.com/webhooks/ . GitHub API Services and hooks функционалността ви дава инструменти за получаване на push нотификация за събитията, които се случват във вашите хранилища, но какво да правите, ако искате повече информация за съответните събития? Например, бихте искали да автоматизирате неща като добавянето на сътрудници или маркирането на issues. Тук е мястото да се възползвате от GitHub API. GitHub има голямо количество API endpoints позволяващи да правите почти всичко, което можете да правите в сайта, но по автоматизиран начин. В тази част ще видим как да се автентикираме и да се свържем с API интерфейса, как да коментираме по issue и как да променим статуса на Pull Request през API. Основни действия Най-простото нещо, което може да направите е да изпратите проста GET заявка към endpoint, който не изисква автентикация. Това може да е потребителска или read-only информация за open source проект. Например, ако искаме да знаем повече за потебителя “schacon”, можем да изпълним нещо такова: $ curl https://api.github.com/users/schacon { "login": "schacon", "id": 70, "avatar_url": "https://avatars.githubusercontent.com/u/70", # … "name": "Scott Chacon", "company": "GitHub", "following": 19, "created_at": "2008-01-27T17:19:28Z", "updated_at": "2014-06-10T02:37:23Z" } Има безброй подобни endpoints предоставящи информация за организации, проекти, issues, къмити — почти за всичко, което можете да видите публично в GitHub. Можете дори да използвате API за рендериране на специален Markdown или за да намерите .gitignore шаблон. $ curl https://api.github.com/gitignore/templates/Java { "name": "Java", "source": "*.class # Mobile Tools for Java (J2ME) .mtj.tmp/ # Package Files # *.jar *.war *.ear # virtual machine crash logs, see https://www.java.com/en/download/help/error_hotspot.xml hs_err_pid* " } Коментар по Issue Обаче, ако искате да направите определено действие в сайта, като коментар по Issue или Pull Request, или искате да погледнете или комуникирате с частно съдържание, ще се наложи да се автентикирате. Съществуват няколко начина за това. Можете да ползвате базова автентикация с име и парола, но по-добра идея е да ползвате персонален token за достъп. Можете да го генерирате в секцията “Applications” на страницата с настройки. Фигура 133. Генерирайте token за достъп в “Applications” секцията от страницата с настройки Ще бъдете попитани за обхвата на token-а и за кратко описание. Уверете се, че използвате добро описание, така че да сте спокойни по-късно, когато изтривате token-а след като вече не се нуждаете от него. GitHub ще ви покаже token-а само веднъж, така че се уверете, че сте го копирали. Можете вече да го използвате за автентикация вместо име и парола. Това е чудесно, защото можете да ограничите обхвата на това, което желаете да манипулирате и също така, token-ът може да се отмени. Получавате и допълнително предимство. Без автентикация, можете да правите до 60 заявки на час. Ако се автентикирате, броят им нараства до 5,000 на час. Нека го използваме за да пуснем коментар по един от нашите Issues. Ще коментираме Issue #6. За да направим това, изпращаме HTTP POST заявка към repos/<user>/<repo>/issues/<num>/comments с token-а, който току що генерирахме като Authorization хедър. $ curl -H "Content-Type: application/json" \ -H "Authorization: token TOKEN" \ --data '{"body":"A new comment, :+1:"}' \ https://api.github.com/repos/schacon/blink/issues/6/comments { "id": 58322100, "html_url": "https://github.com/schacon/blink/issues/6#issuecomment-58322100", ... "user": { "login": "tonychacon", "id": 7874698, "avatar_url": "https://avatars.githubusercontent.com/u/7874698?v=2", "type": "User", }, "created_at": "2014-10-08T07:48:19Z", "updated_at": "2014-10-08T07:48:19Z", "body": "A new comment, :+1:" } Сега, ако отидем в този issue, можем да видим коментара ни там, както е показано в Коментар изпратен с GitHub API . Фигура 134. Коментар изпратен с GitHub API Може да ползвате API интерфейса за да правите почти всичко, което правите и през сайта — създаване и настройка на milestones, асоцииране на хора към Issues и Pull Request-и, създаване и промяна на етикети, достъп до данните на къмит, създаване на нови къмити и клонове, отваряне, затваряне и сливане на Pull Request-и, създаване и редакция на екипи, коментари по редове на код в Pull Request, търсене в сайта и т.н. Промяна на статуса на Pull Request Разглеждаме последния пример, понеже е наистина полезен, ако работите с Pull Request-и. Всеки къмит може да има един или повече статуси асоциирани с него и разполагате с API за добавяне и запитване към статус. Повечето Continuous Integration и testing услуги използват този API за да реагират на публикувания тествайки кода, който е бил пратен и след това рапортувайки дали конкретния къмит е преминал всички тестове. Можете също да ползвате това за проверка дали къмит съобщенията са коректно форматирани, дали изпратилия къмита е следвал указанията ви за сътрудничество в проекта, дали къмитът е с валиден подпис — и безброй други неща. Да приемем, че сте създали webhook във ваше хранилище, който се свързва с малка уеб услуга, която проверява за стринга Signed-off-by в къмит съобщението. require 'httparty' require 'sinatra' require 'json' post '/payload' do push = JSON.parse(request.body.read) # parse the JSON repo_name = push['repository']['full_name'] # look through each commit message push["commits"].each do |commit| # look for a Signed-off-by string if /Signed-off-by/.match commit['message'] state = 'success' description = 'Successfully signed off!' else state = 'failure' description = 'No signoff found.' end # post status to GitHub sha = commit["id"] status_url = "https://api.github.com/repos/#{repo_name}/statuses/#{sha}" status = { "state" => state, "description" => description, "target_url" => "http://example.com/how-to-signoff", "context" => "validate/signoff" } HTTParty.post(status_url, :body => status.to_json, :headers => { 'Content-Type' => 'application/json', 'User-Agent' => 'tonychacon/signoff', 'Authorization' => "token #{ENV['TOKEN']}" } ) end end Надяваме се, че кодът е лесно проследим. Преглеждаме всеки изпратен къмит, търсим за стринга 'Signed-off-by' в къмит съобщението и накрая изпращаме HTTP POST заявка към /repos/<user>/<repo>/statuses/<commit_sha> API endpoint-а със съответния статус. В този случай, можете да изпратите статус ('success', 'failure', 'error'), за описание на това какво се е случило, URL адрес за повече информация и “context” в случай, че има няколко статуса за единичен къмит. Например, една testing услуга може да предостави статус и една валидизираща услуга също може да предостави статус — “context” полето е това, което ги диференцира. Ако някой отвори нов Pull Request в GitHub и този hook е бил настроен, може да видите нещо като Commit status през API . Фигура 135. Commit status през API Сега може да видите малка зелена отметка до къмита, който има стринга “Signed-off-by” в съобщението си и червено кръстче до този, който авторът е забравил да подпише. Може да видите също, че Pull Request-ът приема статуса на последния къмит в клона и ви предупреждава, ако резултатът е грешка. Това е наистина удобно, ако ползвате това API за тестове, така че да не слеете без да искате някой къмит, който не е минал през теста успешно. Octokit Въпреки, че правим всичко през curl и прости HTTP заявки в нашите примери, налични са няколко open-source библиотеки, които могат да ви помогнат да ползвате API интерфейса в по-идиоматичен стил. По време на писането на книгата, поддържаните езици включваха Go, Objective-C, Ruby, и .NET. Проверете https://github.com/octokit за повече информация, понеже те поемат повечето HTTP действия вместо вас. Надяваме се, че тези инструменти ще ви помогнат да настроите поведението на GitHub така, че да комуникира с вашите системи и работни похвати така като желаете. За пълна документация на целия API интерфейс, както и за упътвания за често извършвани задачи, посетете https://developer.github.com . prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://www.twitter.com/googlesre/ | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T09:29:20 |
https://git-scm.com/book/es/v2/Fundamentos-de-Git-Ver-el-Historial-de-Confirmaciones | Git - Ver el Historial de Confirmaciones About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Inicio - Sobre el Control de Versiones 1.1 Acerca del Control de Versiones 1.2 Una breve historia de Git 1.3 Fundamentos de Git 1.4 La Línea de Comandos 1.5 Instalación de Git 1.6 Configurando Git por primera vez 1.7 ¿Cómo obtener ayuda? 1.8 Resumen 2. Fundamentos de Git 2.1 Obteniendo un repositorio Git 2.2 Guardando cambios en el Repositorio 2.3 Ver el Historial de Confirmaciones 2.4 Deshacer Cosas 2.5 Trabajar con Remotos 2.6 Etiquetado 2.7 Alias de Git 2.8 Resumen 3. Ramificaciones en Git 3.1 ¿Qué es una rama? 3.2 Procedimientos Básicos para Ramificar y Fusionar 3.3 Gestión de Ramas 3.4 Flujos de Trabajo Ramificados 3.5 Ramas Remotas 3.6 Reorganizar el Trabajo Realizado 3.7 Recapitulación 4. Git en el Servidor 4.1 Los Protocolos 4.2 Configurando Git en un servidor 4.3 Generando tu clave pública SSH 4.4 Configurando el servidor 4.5 El demonio Git 4.6 HTTP Inteligente 4.7 GitWeb 4.8 GitLab 4.9 Git en un alojamiento externo 4.10 Resumen 5. Git en entornos distribuidos 5.1 Flujos de trabajo distribuidos 5.2 Contribuyendo a un Proyecto 5.3 Manteniendo un proyecto 5.4 Resumen 6. GitHub 6.1 Creación y configuración de la cuenta 6.2 Participando en Proyectos 6.3 Mantenimiento de un proyecto 6.4 Gestión de una organización 6.5 Scripting en GitHub 6.6 Resumen 7. Herramientas de Git 7.1 Revisión por selección 7.2 Organización interactiva 7.3 Guardado rápido y Limpieza 7.4 Firmando tu trabajo 7.5 Buscando 7.6 Reescribiendo la Historia 7.7 Reiniciar Desmitificado 7.8 Fusión Avanzada 7.9 Rerere 7.10 Haciendo debug con Git 7.11 Submódulos 7.12 Agrupaciones 7.13 Replace 7.14 Almacenamiento de credenciales 7.15 Resumen 8. Personalización de Git 8.1 Configuración de Git 8.2 Git Attributes 8.3 Puntos de enganche en Git 8.4 Un ejemplo de implantación de una determinada política en Git 8.5 Recapitulación 9. Git y Otros Sistemas 9.1 Git como Cliente 9.2 Migración a Git 9.3 Resumen 10. Los entresijos internos de Git 10.1 Fontanería y porcelana 10.2 Los objetos Git 10.3 Referencias Git 10.4 Archivos empaquetadores 10.5 Las especificaciones para hacer referencia a… (refspec) 10.6 Protocolos de transferencia 10.7 Mantenimiento y recuperación de datos 10.8 Variables de entorno 10.9 Recapitulación A1. Apéndice A: Git en otros entornos A1.1 Interfaces gráficas A1.2 Git en Visual Studio A1.3 Git en Eclipse A1.4 Git con Bash A1.5 Git en Zsh A1.6 Git en Powershell A1.7 Resumen A2. Apéndice B: Integrando Git en tus Aplicaciones A2.1 Git mediante Línea de Comandos A2.2 Libgit2 A2.3 JGit A3. Apéndice C: Comandos de Git A3.1 Configuración A3.2 Obtener y Crear Proyectos A3.3 Seguimiento Básico A3.4 Ramificar y Fusionar A3.5 Compartir y Actualizar Proyectos A3.6 Inspección y Comparación A3.7 Depuración A3.8 Parcheo A3.9 Correo Electrónico A3.10 Sistemas Externos A3.11 Administración A3.12 Comandos de Fontanería 2nd Edition 2.3 Fundamentos de Git - Ver el Historial de Confirmaciones Ver el Historial de Confirmaciones Después de haber hecho varias confirmaciones, o si has clonado un repositorio que ya tenía un histórico de confirmaciones, probablemente quieras mirar atrás para ver qué modificaciones se han llevado a cabo. La herramienta más básica y potente para hacer esto es el comando git log . Estos ejemplos usan un proyecto muy sencillo llamado “simplegit”. Para clonar el proyecto, ejecuta: git clone https://github.com/schacon/simplegit-progit Cuando ejecutes git log sobre este proyecto, deberías ver una salida similar a esta: $ git log commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 changed the version number commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 16:40:33 2008 -0700 removed unnecessary test commit a11bef06a3f659402fe7563abf99ad00de2209e6 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 10:31:28 2008 -0700 first commit Por defecto, si no pasas ningún parámetro, git log lista las confirmaciones hechas sobre ese repositorio en orden cronológico inverso. Es decir, las confirmaciones más recientes se muestran al principio. Como puedes ver, este comando lista cada confirmación con su suma de comprobación SHA-1, el nombre y dirección de correo del autor, la fecha y el mensaje de confirmación. El comando git log proporciona gran cantidad de opciones para mostrarte exactamente lo que buscas. Aquí veremos algunas de las más usadas. Una de las opciones más útiles es -p , que muestra las diferencias introducidas en cada confirmación. También puedes usar la opción -2 , que hace que se muestren únicamente las dos últimas entradas del historial: $ git log -p -2 commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 changed the version number diff --git a/Rakefile b/Rakefile index a874b73..8f94139 100644 --- a/Rakefile +++ b/Rakefile @@ -5,7 +5,7 @@ require 'rake/gempackagetask' spec = Gem::Specification.new do |s| s.platform = Gem::Platform::RUBY s.name = "simplegit" - s.version = "0.1.0" + s.version = "0.1.1" s.author = "Scott Chacon" s.email = "schacon@gee-mail.com" s.summary = "A simple gem for using Git in Ruby code." commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 16:40:33 2008 -0700 removed unnecessary test diff --git a/lib/simplegit.rb b/lib/simplegit.rb index a0a60ae..47c6340 100644 --- a/lib/simplegit.rb +++ b/lib/simplegit.rb @@ -18,8 +18,3 @@ class SimpleGit end end - -if $0 == __FILE__ - git = SimpleGit.new - puts git.show -end \ No newline at end of file Esta opción muestra la misma información, pero añadiendo tras cada entrada las diferencias que le corresponden. Esto resulta muy útil para revisiones de código, o para visualizar rápidamente lo que ha pasado en las confirmaciones enviadas por un colaborador. También puedes usar con git log una serie de opciones de resumen. Por ejemplo, si quieres ver algunas estadísticas de cada confirmación, puedes usar la opción --stat : $ git log --stat commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 changed the version number Rakefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 16:40:33 2008 -0700 removed unnecessary test lib/simplegit.rb | 5 ----- 1 file changed, 5 deletions(-) commit a11bef06a3f659402fe7563abf99ad00de2209e6 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 10:31:28 2008 -0700 first commit README | 6 ++++++ Rakefile | 23 +++++++++++++++++++++++ lib/simplegit.rb | 25 +++++++++++++++++++++++++ 3 files changed, 54 insertions(+) Como puedes ver, la opción --stat imprime tras cada confirmación una lista de archivos modificados, indicando cuántos han sido modificados y cuántas líneas han sido añadidas y eliminadas para cada uno de ellos, y un resumen de toda esta información. Otra opción realmente útil es --pretty , que modifica el formato de la salida. Tienes unos cuantos estilos disponibles. La opción oneline imprime cada confirmación en una única línea, lo que puede resultar útil si estás analizando gran cantidad de confirmaciones. Otras opciones son short , full y fuller , que muestran la salida en un formato parecido, pero añadiendo menos o más información, respectivamente: $ git log --pretty=oneline ca82a6dff817ec66f44342007202690a93763949 changed the version number 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 removed unnecessary test a11bef06a3f659402fe7563abf99ad00de2209e6 first commit La opción más interesante es format , que te permite especificar tu propio formato. Esto resulta especialmente útil si estás generando una salida para que sea analizada por otro programa —como especificas el formato explícitamente, sabes que no cambiará en futuras actualizaciones de Git—: $ git log --pretty=format:"%h - %an, %ar : %s" ca82a6d - Scott Chacon, 6 years ago : changed the version number 085bb3b - Scott Chacon, 6 years ago : removed unnecessary test a11bef0 - Scott Chacon, 6 years ago : first commit Opciones útiles de git log --pretty=format lista algunas de las opciones más útiles aceptadas por format . Tabla 1. Opciones útiles de git log --pretty=format Opción Descripción de la salida %H Hash de la confirmación %h Hash de la confirmación abreviado %T Hash del árbol %t Hash del árbol abreviado %P Hashes de las confirmaciones padre %p Hashes de las confirmaciones padre abreviados %an Nombre del autor %ae Dirección de correo del autor %ad Fecha de autoría (el formato respeta la opción -–date ) %ar Fecha de autoría, relativa %cn Nombre del confirmador %ce Dirección de correo del confirmador %cd Fecha de confirmación %cr Fecha de confirmación, relativa %s Asunto Puede que te estés preguntando la diferencia entre autor ( author ) y confirmador ( committer ). El autor es la persona que escribió originalmente el trabajo, mientras que el confirmador es quien lo aplicó. Por tanto, si mandas un parche a un proyecto, y uno de sus miembros lo aplica, ambos recibiréis reconocimiento —tú como autor, y el miembro del proyecto como confirmador—. Veremos esta distinción con mayor profundidad en Git en entornos distribuidos . Las opciones oneline y format son especialmente útiles combinadas con otra opción llamada --graph . Ésta añade un pequeño gráfico ASCII mostrando tu historial de ramificaciones y uniones: $ git log --pretty=format:"%h %s" --graph * 2d3acf9 ignore errors from SIGCHLD on trap * 5e3ee11 Merge branch 'master' of git://github.com/dustin/grit |\ | * 420eac9 Added a method for getting the current branch. * | 30e367c timeout code and tests * | 5a09431 add timeout protection to grit * | e1193f8 support for heads with slashes in them |/ * d6016bc require time for xmlschema * 11d191e Merge branch 'defunkt' into local Este tipo de salidas serán más interesantes cuando empecemos a hablar sobre ramificaciones y combinaciones en el próximo capítulo. Éstas son sólo algunas de las opciones para formatear la salida de git log —existen muchas más. Opciones típicas de git log lista las opciones vistas hasta ahora, y algunas otras opciones de formateo que pueden resultarte útiles, así como su efecto sobre la salida. Tabla 2. Opciones típicas de git log Opción Descripción -p Muestra el parche introducido en cada confirmación. --stat Muestra estadísticas sobre los archivos modificados en cada confirmación. --shortstat Muestra solamente la línea de resumen de la opción --stat . --name-only Muestra la lista de archivos afectados. --name-status Muestra la lista de archivos afectados, indicando además si fueron añadidos, modificados o eliminados. --abbrev-commit Muestra solamente los primeros caracteres de la suma SHA-1, en vez de los 40 caracteres de que se compone. --relative-date Muestra la fecha en formato relativo (por ejemplo, “2 weeks ago” (“hace 2 semanas”)) en lugar del formato completo. --graph Muestra un gráfico ASCII con la historia de ramificaciones y uniones. --pretty Muestra las confirmaciones usando un formato alternativo. Posibles opciones son oneline, short, full, fuller y format (mediante el cual puedes especificar tu propio formato). Limitar la Salida del Historial Además de las opciones de formateo, git log acepta una serie de opciones para limitar su salida —es decir, opciones que te permiten mostrar únicamente parte de las confirmaciones—. Ya has visto una de ellas, la opción -2 , que muestra sólo las dos últimas confirmaciones. De hecho, puedes hacer -<n> , siendo n cualquier entero, para mostrar las últimas n confirmaciones. En realidad es poco probable que uses esto con frecuencia, ya que Git por defecto pagina su salida para que veas cada página del historial por separado. Sin embargo, las opciones temporales como --since (desde) y --until (hasta) sí que resultan muy útiles. Por ejemplo, este comando lista todas las confirmaciones hechas durante las dos últimas semanas: $ git log --since=2.weeks Este comando acepta muchos formatos. Puedes indicar una fecha concreta ( "2008-01-15" ), o relativa, como "2 years 1 day 3 minutes ago" ( "hace 2 años, 1 día y 3 minutos" ). También puedes filtrar la lista para que muestre sólo aquellas confirmaciones que cumplen ciertos criterios. La opción --author te permite filtrar por autor, y --grep te permite buscar palabras clave entre los mensajes de confirmación. (Ten en cuenta que si quieres aplicar ambas opciones simultáneamente, tienes que añadir --all-match , o el comando mostrará las confirmaciones que cumplan cualquiera de las dos, no necesariamente las dos a la vez.) Otra opción útil es -S , la cual recibe una cadena y solo muestra las confirmaciones que cambiaron el código añadiendo o eliminando la cadena. Por ejemplo, si quieres encontrar la última confirmación que añadió o eliminó una referencia a una función específica, puede ejecutar: $ git log -Sfunction_name La última opción verdaderamente útil para filtrar la salida de git log es especificar una ruta. Si especificas la ruta de un directorio o archivo, puedes limitar la salida a aquellas confirmaciones que introdujeron un cambio en dichos archivos. Ésta debe ser siempre la última opción, y suele ir precedida de dos guiones ( -- ) para separar la ruta del resto de opciones. En Opciones para limitar la salida de git log se listan estas opciones, y algunas otras bastante comunes a modo de referencia. Tabla 3. Opciones para limitar la salida de git log Opción Descripción -(n) Muestra solamente las últimas n confirmaciones --since, --after Muestra aquellas confirmaciones hechas después de la fecha especificada. --until, --before Muestra aquellas confirmaciones hechas antes de la fecha especificada. --author Muestra sólo aquellas confirmaciones cuyo autor coincide con la cadena especificada. --committer Muestra sólo aquellas confirmaciones cuyo confirmador coincide con la cadena especificada. -S Muestra sólo aquellas confirmaciones que añaden o eliminen código que corresponda con la cadena especificada. Por ejemplo, si quieres ver cuáles de las confirmaciones hechas sobre archivos de prueba del código fuente de Git fueron enviadas por Junio Hamano, y no fueron uniones, en el mes de octubre de 2008, ejecutarías algo así: $ git log --pretty="%h - %s" --author=gitster --since="2008-10-01" \ --before="2008-11-01" --no-merges -- t/ 5610e3b - Fix testcase failure when extended attributes are in use acd3b9e - Enhance hold_lock_file_for_{update,append}() API f563754 - demonstrate breakage of detached checkout with symbolic link HEAD d1a43f2 - reset --hard/read-tree --reset -u: remove unmerged new paths 51a94af - Fix "checkout --track -b newbranch" on detached HEAD b0ad11e - pull: allow "git pull origin $something:$current_branch" into an unborn branch De las casi 40.000 confirmaciones en la historia del código fuente de Git, este comando muestra las 6 que cumplen estas condiciones. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
http://www.trello.com/teams/startups | Trello for Startups | Trello Skip to main content Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Use case: Task management Track progress of tasks in one convenient place with a visual layout that adds ‘ta-da’ to your to-do’s. Use case: Resource hub Save hours when you give teams a well-designed hub to find information easily and quickly. Use case: Project management Keep projects organized, deadlines on track, and teammates aligned with Trello. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Back Navigation Features Solutions Plans Pricing Resources Explore the features that help your team succeed Inbox Capture every vital detail from emails, Slack, and more directly into your Trello Inbox. Planner Sync your calendar and allocate focused time slots to boost productivity. Automation Automate tasks and workflows with Trello. Power-Ups Power up your teams by linking their favorite tools with Trello plugins. Templates Give your team a blueprint for success with easy-to-use templates from industry leaders and the Trello community. Integrations Find the apps your team is already using or discover new ways to get work done in Trello. Meet Trello Trello makes it easy for your team to get work done. No matter the project, workflow, or type of team, Trello can help keep things organized. It’s simple – sign-up, create a board, and you’re off! Productivity awaits. Check out Trello Take a page out of these pre-built Trello playbooks designed for all teams Marketing teams Whether launching a new product, campaign, or creating content, Trello helps marketing teams succeed. Product management Use Trello’s management boards and roadmap features to simplify complex projects and processes. Engineering teams Ship more code, faster, and give your developers the freedom to be more agile with Trello. Design teams Empower your design teams by using Trello to streamline creative requests and promote more fluid cross-team collaboration. Startups From hitting revenue goals to managing workflows, small businesses thrive with Trello. Remote teams Keep your remote team connected and motivated, no matter where they’re located around the world. See all teams Our product in action Read though our use cases to make the most of Trello on your team. See all use cases Standard For teams that need to manage more work and scale collaboration. Premium Best for teams up to 100 that need to track multiple projects and visualize work in a variety of ways. Enterprise Everything your enterprise teams and admins need to manage projects. Free plan For individuals or small teams looking to keep work organized. Take a tour of Trello Compare plans & pricing Whether you’re a team of 2 or 2,000, Trello’s flexible pricing model means you only pay for what you need. View Trello pricing Learn & connect Trello guide Our easy to follow workflow guide will take you from project set-up to Trello expert in no time. Remote work guide The complete guide to setting up your team for remote work success. Webinars Enjoy our free Trello webinars and become a productivity professional. Customer stories See how businesses have adopted Trello as a vital part of their workflow. Developers The sky's the limit in what you can deliver to Trello users in your Power-Up! Help resources Need help? Articles and FAQs to get you unstuck. Helping teams work better, together Discover Trello use cases, productivity tips, best practices for team collaboration, and expert remote work advice. Check out the Trello blog < Go back to Team Solutions Trello For Startups From hiring your first employee to hitting your revenue goals, discover how to thrive as a startup with Trello. Trello’s boards, lists, and cards enable teams to go from ideas to action in seconds. Visual and easy-to-use, Trello helps teams bring projects to life and keep them moving forward. Join over 2,000,000 teams worldwide who are using Trello to get more done. Workspaces For Growing Businesses Kick your business off on the right foot by working within pre-built templates that your small but mighty team can adapt and scale as the company grows. Explore all business templates Company Overview Give employees a high-level overview of what's happening throughout your growing company, with the ability to find details about teams, projects, and resources. Team Goal Setting Store documents, tips, presentations, answers to common questions all in one place, and easily break down top-level goals into smaller, achievable tasks. Company Meetings Allow employees to ask, questions, discuss what’s on their minds, and share progress on initiatives. Company leaders can discuss priorities, promote cross-team collaboration, and keep transparency top of mind. Company Overview Give employees a high-level overview of what's happening throughout your growing company, with the ability to find details about teams, projects, and resources. Team Goal Setting Store documents, tips, presentations, answers to common questions all in one place, and easily break down top-level goals into smaller, achievable tasks. Company Meetings Allow employees to ask, questions, discuss what’s on their minds, and share progress on initiatives. Company leaders can discuss priorities, promote cross-team collaboration, and keep transparency top of mind. Gain actionable insights and key metrics. Help your start-up scale (without the growing pains) by making informed data-driven decisions using Dashboard view. Get the most of Trello's different views. Learn more about Trello views Power-Up Your New Business All businesses could use some extra support. Allow these tools and integrations, like Confluence, Jira, and Slack to propel your business forward with easier, more effective collaboration. Explore 150+ Power-Ups Move Work Forward, Auto-magically Trello’s built-in automation makes it easy to automate the repetitive, everyday tasks that keep your team from focusing on the work that matters most. Let the robots do the work Resources For Startup Success Whether you’re looking for quick tips or thorough advice, use these resources to launch, run, and grow your business with more ease: 6 Essential Trello Templates You Need To Run A Business [Blog Post] From HR to IT, to every department and acronym in between, there is a Trello board that helps businesses run smoother. Explore six essential templates that, at one point or another, are useful for every member of your company. READ MORE How To Keep Your Small Business Motivated—No Matter What [Blog Post] NY Times bestselling author, business thought leader, and acclaimed B-School founder, Marie Forleo, uncover how to keep motivation high and teams ready for action through up and down. READ MORE How To Use Trello And Indeed To Hire A Dream Team [Blog Post] If your company is growing fast and hiring fast, unleash the power of using Trello and Indeed in-tandem as an easy, light-weight recruiting management tool to keep all your ducks (and candidates) in a row. READ MORE NOW AVAILABLE A 14 Day Free Trial of Premium! Get unlimited boards, Trello views, and limitless automation, plus a ton more. Try it today SwagUp: Scale Any Business With Trello BC “Not only did [Trello] unify our process and help everyone understand their role, but we were able to automate essential steps of the process so we could move a lot faster and grow to a multi-million dollar company with a team of ten.” –Founder, SwagUp Learn More Instinct Dog Training “As you scale, you need visibility, accountability, and organization. Trello has provided that for us.” –Brian Burton, Founder, Instinct Dog Training Learn More Desk Plants “We chose Trello because it is well-designed—it’s beautifully designed—intuitive, and really hit the nail on the head with what we needed to solve.” –Lawrence Hanley, founder of Desk Plants Learn More Scan2Cad “We use Trello because our data becomes alive. A bullet point list turns into real tasks that are assigned to real people with due dates and connections to our other apps. The power in that is fantastic.” –Luke Kennedy, CEO, Scan2Cad Learn More Palace Law “People have generally been happier since we started using Trello. It has made our lives a lot easier. People are less stressed.” -Jordan Couch, attorney at Palace Law Learn More Trello Your Way Ready to get your team up and running? Try the business tool so easy to use, your team can’t help but collaborate. Learn more about our pricing and plans Free $ 0 USD Free for up to 10 collaborators per Workspace Capture your to-dos, get organized, and get sh*t done. Standard $ 5 USD Per user/month if billed annually ($6 billed monthly) Get more stuff done with unlimited boards, card mirroring, and more automation. Learn more about Standard Premium $ 10 USD Per user/month if billed annually ($12.50 billed monthly) Add AI to your boards and admin controls to your toolkit. Plus, get more perspective with views. Learn more about Premium Enterprise $ 17.50 USD Per user/month - billed annually ($210.00 annual price per user) Add enterprise-grade security and controls. This plan includes Atlassian Guard Standard and 24/7 Enterprise Admin support. Est. cost for users Learn more about Enterprise Well, what are you waiting for? Head over to your boards and start getting things done! Log In About Trello What’s behind the boards. Jobs Learn about open roles on the Trello team. Apps Download the Trello App for your Desktop or Mobile devices. Contact us Need anything? Get in touch and we can help. Čeština Deutsch English Español Français Italiano Magyar Nederlands Norsk (bokmål) Polski Português (Brasil) Suomi Svenska Tiếng Việt Türkçe Русский Українська ภาษาไทย 中文 (简体) 中文 (繁體) 日本語 Notice at Collection Privacy Policy Terms Copyright © 2024 Atlassian | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/categories/customer-relationship-management-software?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_subtitle-click | Best Customer Relationship Management (CRM) Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Sales Manager (196) Salesperson (149) Sales Specialist (108) Chief Executive Officer (87) Marketing Specialist (85) See all products Find top products in Customer Relationship Management (CRM) Software category Software used to oversee company interaction with current and potential clients. - Manage relationships with customers and improve customer retention - Use a set of sales-related functions and drive sales growth - Compile data from different channels to a single record system 1535 results Sales Cloud Customer Relationship Management (CRM) Software by Salesforce Accelerate growth with your Humans + AI dream team. Ready to elevate every step of your sales cycle, from pipeline to paycheck? Scale your team with AI agents, equip your human sellers with the data and insights they need to win, and drive operational efficiency—all on Sales Cloud, the #1 agentic sales software platform. View product Zoho CRM Customer Relationship Management (CRM) Software by Zoho Zoho CRM is an online customer relationship management software for managing your sales, marketing, support in a single system. Zoho CRM helps businesses of all sizes build excellent customer relationships, with features like an inbuilt AI sales assistant, sales pipeline management, marketing automation, analytics, and more. Zoho CRM empowers a global network of over 150,000 businesses in 180 countries to convert more leads, engage with customers, and grow their revenue. View product Bigin by Zoho CRM Customer Relationship Management (CRM) Software by Zoho Bigin by Zoho CRM is a simplified customer relationship management (CRM) software designed specifically for small businesses, startups and teams! Trusted by 20,000+ businesses, Bigin helps small businesses unify all customer-facing operations— marketing, sales, onboarding, delivery, and support and manage customer relationships effectively. View product Experian DataShare Customer Relationship Management (CRM) Software by Experian Experian DataShare will accelerate new client onboarding and help increase retention through a simplified user experience. The platform integrates with over 100 versions of cloud and on-premise packages to deliver unparalleled accounting connectivity, flexible platform deployment, and instant audit or credit intelligence. It supports 100% of desktop and online accounting packages... including document uploading. Clients get faster decisions and have technical support if they experience any issues during their onboarding journey. Experian DataShare creates a digital pathway that removes the friction associated with the document gathering process. Start your digital journey to collect, format and interpret your client financials today! View product Odoo CRM Customer Relationship Management (CRM) Software by Odoo With over 5 million users, Odoo is the #1 open-source CRM software in the world! Sales teams can easily keep track of top leads and opportunities with just a few clicks. Users can personalize their sales cycle, take control of their statistics/forecasts, and create incredible marketing campaign automation to increase their overall sales performance. With Odoo CRM, sales teams are able to analyze the quality of their leads, make faster decisions, and save valuable time by integrating emails from all contacts directly into this fully-integrated app. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights Freshsales Customer Relationship Management (CRM) Software by Freshworks Freshsales provides a context-driven CRM solution for businesses of all sizes. We do this by taking a fresh approach to building and delivering an AI-driven and cost-effective omnichannel software—empowering sales teams to engage, nurture, and create delighted customers, to drive clear business results. View product Clickup Customer Relationship Management (CRM) Software by ClickUp Save time with the all-in-one productivity platform that brings teams, tasks, and tools together in one place. View product Infor CRM Customer Relationship Management (CRM) Software by Infor Infor CRM software provides a view of every customer touch point across an organization’s sales, marketing, customer service, and support teams. View product Pega Platform Customer Relationship Management (CRM) Software by Pegasystems Pega Platform helps improve business operation by enhancing employee productivity and delivering rapid, personalized service to customers. With enterprise-grade AI, automation, and low code for all users across an organization, Pega Platform enables you to respond to business needs in real time, scale quickly, and evolve as your needs change. Get work done while reducing costs and manual work across your business operations with Pega’s low-code platform for AI-powered decision and workflow automation. View product Zendesk Sell Customer Relationship Management (CRM) Software by Zendesk Zendesk Sell is a modern sales CRM to help you accelerate revenue. It’s a sales tool that’s quick to set up, intuitive, and easy to love. View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T09:29:20 |
https://git-scm.com/book/es/v2/Fundamentos-de-Git-Obteniendo-un-repositorio-Git | Git - Obteniendo un repositorio Git About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Inicio - Sobre el Control de Versiones 1.1 Acerca del Control de Versiones 1.2 Una breve historia de Git 1.3 Fundamentos de Git 1.4 La Línea de Comandos 1.5 Instalación de Git 1.6 Configurando Git por primera vez 1.7 ¿Cómo obtener ayuda? 1.8 Resumen 2. Fundamentos de Git 2.1 Obteniendo un repositorio Git 2.2 Guardando cambios en el Repositorio 2.3 Ver el Historial de Confirmaciones 2.4 Deshacer Cosas 2.5 Trabajar con Remotos 2.6 Etiquetado 2.7 Alias de Git 2.8 Resumen 3. Ramificaciones en Git 3.1 ¿Qué es una rama? 3.2 Procedimientos Básicos para Ramificar y Fusionar 3.3 Gestión de Ramas 3.4 Flujos de Trabajo Ramificados 3.5 Ramas Remotas 3.6 Reorganizar el Trabajo Realizado 3.7 Recapitulación 4. Git en el Servidor 4.1 Los Protocolos 4.2 Configurando Git en un servidor 4.3 Generando tu clave pública SSH 4.4 Configurando el servidor 4.5 El demonio Git 4.6 HTTP Inteligente 4.7 GitWeb 4.8 GitLab 4.9 Git en un alojamiento externo 4.10 Resumen 5. Git en entornos distribuidos 5.1 Flujos de trabajo distribuidos 5.2 Contribuyendo a un Proyecto 5.3 Manteniendo un proyecto 5.4 Resumen 6. GitHub 6.1 Creación y configuración de la cuenta 6.2 Participando en Proyectos 6.3 Mantenimiento de un proyecto 6.4 Gestión de una organización 6.5 Scripting en GitHub 6.6 Resumen 7. Herramientas de Git 7.1 Revisión por selección 7.2 Organización interactiva 7.3 Guardado rápido y Limpieza 7.4 Firmando tu trabajo 7.5 Buscando 7.6 Reescribiendo la Historia 7.7 Reiniciar Desmitificado 7.8 Fusión Avanzada 7.9 Rerere 7.10 Haciendo debug con Git 7.11 Submódulos 7.12 Agrupaciones 7.13 Replace 7.14 Almacenamiento de credenciales 7.15 Resumen 8. Personalización de Git 8.1 Configuración de Git 8.2 Git Attributes 8.3 Puntos de enganche en Git 8.4 Un ejemplo de implantación de una determinada política en Git 8.5 Recapitulación 9. Git y Otros Sistemas 9.1 Git como Cliente 9.2 Migración a Git 9.3 Resumen 10. Los entresijos internos de Git 10.1 Fontanería y porcelana 10.2 Los objetos Git 10.3 Referencias Git 10.4 Archivos empaquetadores 10.5 Las especificaciones para hacer referencia a… (refspec) 10.6 Protocolos de transferencia 10.7 Mantenimiento y recuperación de datos 10.8 Variables de entorno 10.9 Recapitulación A1. Apéndice A: Git en otros entornos A1.1 Interfaces gráficas A1.2 Git en Visual Studio A1.3 Git en Eclipse A1.4 Git con Bash A1.5 Git en Zsh A1.6 Git en Powershell A1.7 Resumen A2. Apéndice B: Integrando Git en tus Aplicaciones A2.1 Git mediante Línea de Comandos A2.2 Libgit2 A2.3 JGit A3. Apéndice C: Comandos de Git A3.1 Configuración A3.2 Obtener y Crear Proyectos A3.3 Seguimiento Básico A3.4 Ramificar y Fusionar A3.5 Compartir y Actualizar Proyectos A3.6 Inspección y Comparación A3.7 Depuración A3.8 Parcheo A3.9 Correo Electrónico A3.10 Sistemas Externos A3.11 Administración A3.12 Comandos de Fontanería 2nd Edition 2.1 Fundamentos de Git - Obteniendo un repositorio Git Si pudieras leer solo un capítulo para empezar a trabajar con Git, este es el capítulo que debes leer. Este capítulo cubre todos los comandos básicos que necesitas para hacer la gran mayoría de cosas a las que eventualmente vas a dedicar tu tiempo mientras trabajas con Git. Al final del capítulo, deberás ser capaz de configurar e inicializar un repositorio, comenzar y detener el seguimiento de archivos, y preparar (stage) y confirmar (commit) cambios. También te enseñaremos a configurar Git para que ignore ciertos archivos y patrones, cómo enmendar errores rápida y fácilmente, cómo navegar por la historia de tu proyecto y ver cambios entre confirmaciones, y cómo enviar (push) y recibir (pull) de repositorios remotos. Obteniendo un repositorio Git Puedes obtener un proyecto Git de dos maneras. La primera es tomar un proyecto o directorio existente e importarlo en Git. La segunda es clonar un repositorio existente en Git desde otro servidor. Inicializando un repositorio en un directorio existente Si estás empezando a seguir un proyecto existente en Git, debes ir al directorio del proyecto y usar el siguiente comando: $ git init Esto crea un subdirectorio nuevo llamado .git , el cual contiene todos los archivos necesarios del repositorio – un esqueleto de un repositorio de Git. Todavía no hay nada en tu proyecto que esté bajo seguimiento. Puedes revisar [ch10-git-internals] para obtener más información acerca de los archivos presentes en el directorio .git que acaba de ser creado. Si deseas empezar a controlar versiones de archivos existentes (a diferencia de un directorio vacío), probablemente deberías comenzar el seguimiento de esos archivos y hacer una confirmación inicial. Puedes conseguirlo con unos pocos comandos git add para especificar qué archivos quieres controlar, seguidos de un git commit para confirmar los cambios: $ git add *.c $ git add LICENSE $ git commit -m 'initial project version' Veremos lo que hacen estos comandos más adelante. En este momento, tienes un repositorio de Git con archivos bajo seguimiento y una confirmación inicial. Clonando un repositorio existente Si deseas obtener una copia de un repositorio Git existente — por ejemplo, un proyecto en el que te gustaría contribuir — el comando que necesitas es git clone . Si estás familizarizado con otros sistemas de control de versiones como Subversion, verás que el comando es "clone" en vez de "checkout". Es una distinción importante, ya que Git recibe una copia de casi todos los datos que tiene el servidor. Cada versión de cada archivo de la historia del proyecto es descargada por defecto cuando ejecutas git clone . De hecho, si el disco de tu servidor se corrompe, puedes usar cualquiera de los clones en cualquiera de los clientes para devolver el servidor al estado en el que estaba cuando fue clonado (puede que pierdas algunos hooks del lado del servidor y demás, pero toda la información acerca de las versiones estará ahí) — véase Configurando Git en un servidor para más detalles. Puedes clonar un repositorio con git clone [url] . Por ejemplo, si quieres clonar la librería de Git llamada libgit2 puedes hacer algo así: $ git clone https://github.com/libgit2/libgit2 Esto crea un directorio llamado libgit2 , inicializa un directorio .git en su interior, descarga toda la información de ese repositorio y saca una copia de trabajo de la última versión. Si te metes en el directorio libgit2 , verás que están los archivos del proyecto listos para ser utilizados. Si quieres clonar el repositorio a un directorio con otro nombre que no sea libgit2 , puedes especificarlo con la siguiente opción de línea de comandos: $ git clone https://github.com/libgit2/libgit2 mylibgit Ese comando hace lo mismo que el anterior, pero el directorio de destino se llamará mylibgit . Git te permite usar distintos protocolos de transferencia. El ejemplo anterior usa el protocolo https:// , pero también puedes utilizar git:// o usuario@servidor:ruta/del/repositorio.git que utiliza el protocolo de transferencia SSH. En Configurando Git en un servidor se explicarán todas las opciones disponibles a la hora de configurar el acceso a tu repositorio de Git, y las ventajas e inconvenientes de cada una. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://git-scm.com/book/de/v2/Git-Grundlagen-Anzeigen-der-Commit-Historie | Git - Anzeigen der Commit-Historie About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Erste Schritte 1.1 Was ist Versionsverwaltung? 1.2 Kurzer Überblick über die Historie von Git 1.3 Was ist Git? 1.4 Die Kommandozeile 1.5 Git installieren 1.6 Git Basis-Konfiguration 1.7 Hilfe finden 1.8 Zusammenfassung 2. Git Grundlagen 2.1 Ein Git-Repository anlegen 2.2 Änderungen nachverfolgen und im Repository speichern 2.3 Anzeigen der Commit-Historie 2.4 Ungewollte Änderungen rückgängig machen 2.5 Mit Remotes arbeiten 2.6 Taggen 2.7 Git Aliases 2.8 Zusammenfassung 3. Git Branching 3.1 Branches auf einen Blick 3.2 Einfaches Branching und Merging 3.3 Branch-Management 3.4 Branching-Workflows 3.5 Remote-Branches 3.6 Rebasing 3.7 Zusammenfassung 4. Git auf dem Server 4.1 Die Protokolle 4.2 Git auf einem Server einrichten 4.3 Erstellung eines SSH-Public-Keys 4.4 Einrichten des Servers 4.5 Git-Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Von Drittanbietern gehostete Optionen 4.10 Zusammenfassung 5. Verteiltes Git 5.1 Verteilter Arbeitsablauf 5.2 An einem Projekt mitwirken 5.3 Ein Projekt verwalten 5.4 Zusammenfassung 6. GitHub 6.1 Einrichten und Konfigurieren eines Kontos 6.2 Mitwirken an einem Projekt 6.3 Ein Projekt betreuen 6.4 Verwalten einer Organisation 6.5 Skripte mit GitHub 6.6 Zusammenfassung 7. Git Tools 7.1 Revisions-Auswahl 7.2 Interaktives Stagen 7.3 Stashen und Bereinigen 7.4 Deine Arbeit signieren 7.5 Suchen 7.6 Den Verlauf umschreiben 7.7 Reset entzaubert 7.8 Fortgeschrittenes Merging 7.9 Rerere 7.10 Debuggen mit Git 7.11 Submodule 7.12 Bundling 7.13 Replace (Ersetzen) 7.14 Anmeldeinformationen speichern 7.15 Zusammenfassung 8. Git einrichten 8.1 Git Konfiguration 8.2 Git-Attribute 8.3 Git Hooks 8.4 Beispiel für Git-forcierte Regeln 8.5 Zusammenfassung 9. Git und andere VCS-Systeme 9.1 Git als Client 9.2 Migration zu Git 9.3 Zusammenfassung 10. Git Interna 10.1 Basisbefehle und Standardbefehle (Plumbing and Porcelain) 10.2 Git Objekte 10.3 Git Referenzen 10.4 Packdateien (engl. Packfiles) 10.5 Die Referenzspezifikation (engl. Refspec) 10.6 Transfer Protokolle 10.7 Wartung und Datenwiederherstellung 10.8 Umgebungsvariablen 10.9 Zusammenfassung A1. Anhang A: Git in anderen Umgebungen A1.1 Grafische Schnittstellen A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Zusammenfassung A2. Anhang B: Git in deine Anwendungen einbetten A2.1 Die Git-Kommandozeile A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Anhang C: Git Kommandos A3.1 Setup und Konfiguration A3.2 Projekte importieren und erstellen A3.3 Einfache Snapshot-Funktionen A3.4 Branching und Merging A3.5 Projekte gemeinsam nutzen und aktualisieren A3.6 Kontrollieren und Vergleichen A3.7 Debugging A3.8 Patchen bzw. Fehlerkorrektur A3.9 E-mails A3.10 Externe Systeme A3.11 Administration A3.12 Basisbefehle 2nd Edition 2.3 Git Grundlagen - Anzeigen der Commit-Historie Anzeigen der Commit-Historie Nachdem du mehrere Commits erstellt hast, oder wenn du ein Repository mit einer bestehenden Commit-Historie geklont hast, wirst du wahrscheinlich zurückschauen wollen, um zu erfahren, was geschehen ist. Das wichtigste und mächtigste Werkzeug dafür ist der Befehl git log . Diese Beispiele verwenden ein sehr einfaches Projekt namens „simplegit“. Um das Projekt zu erstellen, führe diesen Befehl aus: $ git clone https://github.com/schacon/simplegit-progit Wenn du git log in diesem Projekt aufrufst, solltest du eine Ausgabe erhalten, die ungefähr so aussieht: $ git log commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 Change version number commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 16:40:33 2008 -0700 Remove unnecessary test commit a11bef06a3f659402fe7563abf99ad00de2209e6 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 10:31:28 2008 -0700 Initial commit Standardmäßig, d.h. ohne Argumente, listet git log die in diesem Repository vorgenommenen Commits in umgekehrter chronologischer Reihenfolge auf, d.h. die neuesten Commits werden als Erstes angezeigt. Wie du sehen kannst, listet dieser Befehl jeden Commit mit seiner SHA-1-Prüfsumme, dem Namen und der E-Mail-Adresse des Autors, dem Erstellungs-Datum und der Commit-Beschreibung auf. Eine Vielzahl von Optionen stehen für den Befehl git log zur Verfügung, um dir exakt das anzuzeigen, wonach du suchst. Hier zeigen wir dir einige der gängigsten. Eine der hilfreichsten Optionen ist -p oder --patch . Sie zeigt die Änderungen (die patch -Ausgabe) an, die bei jedem Commit durchgeführt wurden. Du kannst auch die Anzahl der anzuzeigenden Protokolleinträge begrenzen, z.B. mit -2 werden nur die letzten beiden Einträge dargestellt. $ git log -p -2 commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 Change version number diff --git a/Rakefile b/Rakefile index a874b73..8f94139 100644 --- a/Rakefile +++ b/Rakefile @@ -5,7 +5,7 @@ require 'rake/gempackagetask' spec = Gem::Specification.new do |s| s.platform = Gem::Platform::RUBY s.name = "simplegit" - s.version = "0.1.0" + s.version = "0.1.1" s.author = "Scott Chacon" s.email = "schacon@gee-mail.com" s.summary = "A simple gem for using Git in Ruby code." commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 16:40:33 2008 -0700 Remove unnecessary test diff --git a/lib/simplegit.rb b/lib/simplegit.rb index a0a60ae..47c6340 100644 --- a/lib/simplegit.rb +++ b/lib/simplegit.rb @@ -18,8 +18,3 @@ class SimpleGit end end - -if $0 == __FILE__ - git = SimpleGit.new - puts git.show -end Diese Option zeigt die gleichen Informationen an, jedoch mit der diff Ausgabe direkt nach jedem Eintrag. Dies ist sehr hilfreich für die Codeüberprüfung oder um schnell zu durchsuchen, was während einer Reihe von Commits passiert ist, die ein Teammitglied hinzugefügt hat. Du kannst auch mehrere Optionen zur Verdichtung der Ausgabe von git log verwenden. Wenn du beispielsweise einige gekürzte Statistiken für jeden Commit sehen möchtest, kannst du die Option --stat verwenden: $ git log --stat commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 Change version number Rakefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 16:40:33 2008 -0700 Remove unnecessary test lib/simplegit.rb | 5 ----- 1 file changed, 5 deletions(-) commit a11bef06a3f659402fe7563abf99ad00de2209e6 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 10:31:28 2008 -0700 Initial commit README | 6 ++++++ Rakefile | 23 +++++++++++++++++++++++ lib/simplegit.rb | 25 +++++++++++++++++++++++++ 3 files changed, 54 insertions(+) Wie du sehen kannst, gibt die Option --stat unter jedem Commit-Eintrag eine Liste der geänderten Dateien aus, wie viele Dateien geändert wurden und wie viele Zeilen in diesen Dateien hinzugefügt und entfernt wurden. Sie enthält auch eine Zusammenfassung am Ende des Berichts. Eine weitere wirklich nützliche Option ist --pretty . Diese Option ändert das Format der Log-Ausgabe in ein anderes als das Standard-Format. Dir stehen einige vorgefertigte Optionswerte zur Verfügung. Der Wert oneline für diese Option gibt jeden Commit in einer einzigen Zeile aus, was besonders nützlich ist, wenn du dir viele Commits ansiehst. Darüber hinaus zeigen die Werte short , full und fuller die Ausgabe im etwa gleichen Format, allerdings mit mehr oder weniger Informationen an: $ git log --pretty=oneline ca82a6dff817ec66f44342007202690a93763949 Change version number 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Remove unnecessary test a11bef06a3f659402fe7563abf99ad00de2209e6 Initial commit Der interessanteste Wert ist format , mit dem du dein eigenes Log-Ausgabeformat festlegen kannst. Dieses Verfahren ist besonders nützlich, wenn du Ausgaben für das maschinelle Parsen generierst – da du das Format explizit angibst, weißt du, dass es sich mit Updates von Git nicht ändert: $ git log --pretty=format:"%h - %an, %ar : %s" ca82a6d - Scott Chacon, 6 years ago : Change version number 085bb3b - Scott Chacon, 6 years ago : Remove unnecessary test a11bef0 - Scott Chacon, 6 years ago : Initial commit Wichtige Spezifikatoren für git log --pretty=format listet einige der nützlichsten Spezifikatoren auf, die format bietet. Tabelle 1. Wichtige Spezifikatoren für git log --pretty=format Spezifikator Beschreibung der Ausgabe %H Commit-Hash %h gekürzter Commit-Hash %T Hash-Baum %t gekürzter Hash-Baum %P Parent-Hashes %p gekürzte Parent-Hashes %an Name des Autors %ae E-Mail-Adresse des Autors %ad Erstellungs-Datum des Autors (Format berücksichtigt --date=option) %ar relatives Erstellungs-Datum des Autors %cn Name des Committers %ce E-Mail-Adresse des Committers %cd Erstellungs-Datum des Committers %cr relatives Erstellungs-Datum des Committers %s Thema (engl. Subject) Du fragst dich vielleicht, worin der Unterschied zwischen Autor und Committer besteht. Der Autor ist die Person, die das Werk ursprünglich geschrieben hat, während der Committer die Person ist, die das Werk zuletzt bearbeitet hat. Wenn du also einen Patch an ein Projekt sendest und eines der Core-Mitglieder den Patch einbindet, erhalten beide die Anerkennung – du als Autor und das Core-Mitglied als Committer. Wir werden diese Unterscheidung näher in Kapitel 5, Verteiltes Git erläutern. Die Optionswerte oneline und format sind vor allem bei einer anderen log Option mit der Bezeichnung --graph hilfreich. Diese Option fügt ein schönes kleines ASCII-Diagramm hinzu, das deinen Branch und den Merge-Verlauf zeigt: $ git log --pretty=format:"%h %s" --graph * 2d3acf9 Ignore errors from SIGCHLD on trap * 5e3ee11 Merge branch 'master' of https://github.com/dustin/grit |\ | * 420eac9 Add method for getting the current branch * | 30e367c Timeout code and tests * | 5a09431 Add timeout protection to grit * | e1193f8 Support for heads with slashes in them |/ * d6016bc Require time for xmlschema * 11d191e Merge branch 'defunkt' into local Dieser Ausgabetyp wird immer interessanter, wenn wir im nächsten Kapitel über das Branching und Merging sprechen. Das sind nur einige einfache Optionen zur Ausgabe-Formatierung von git log – es gibt noch viele mehr. Allgemeine Optionen für git log listet die bisher von uns behandelten Optionen auf, sowie einige andere gängige Format-Optionen, die sinnvoll sein können, um die Ausgabe des log-Befehls zu ändern. Tabelle 2. Allgemeine Optionen für git log Option Beschreibung -p Zeigt den Patch (bzw. Änderung) an, der mit den jeweiligen Commits eingefügt wurde. --stat Anzeige der Statistiken für Dateien, die in den einzelnen Commits geändert wurden. --shortstat Anzeige der geänderten/eingefügten/gelöschten Zeilen des Befehls --stat. --name-only Listet nach den Commit-Informationen die geänderten Dateien auf --name-status Listet die Dateien mit hinzugefügten/geänderten/gelöschten Informationen auf. --abbrev-commit Zeigt nur die ersten paar Zeichen der SHA-1-Prüfsumme an, nicht aber alle 40. --relative-date Zeigt das Datum in einem relativen Format an (z.B. „vor 2 Wochen“), anstatt das volle Datumsformat zu verwenden. --graph Zeigt neben der Historie ein ASCII-Diagramm des Branch- und Zusammenführungsverlaufs an. --pretty Zeigt Commits in einem anderen Format an. Zu den Optionswerten gehören oneline, short, full, fuller und format (womit du dein eigenes Format angeben kannst). --oneline Kurzform für die gleichzeitige Verwendung von --pretty=oneline und --abbrev-commit . Einschränken der Log-Ausgabe Zusätzlich zu den Optionen für die Ausgabe-Formatierung bietet git log eine Reihe nützlicher einschränkender Optionen, d.h. Optionen, mit denen du nur eine Teilmenge von Commits anzeigen kannst. Du hast eine solche Option bereits gesehen – die Option -2 , die nur die letzten beiden Commits anzeigt. Du kannst die Option -<n> verwenden, wobei n eine beliebige ganze Zahl ist, um die letzten n Commits anzuzeigen. In der Praxis wirst du das selten verwenden, da Git standardmäßig alle Ausgaben über einen Pager leitet, so dass du immer nur eine Seite der Log-Ausgabe siehst. Im Gegensatz dazu sind zeitbeschränkenden Optionen wie --since und --until sehr nützlich. Dieser Befehl ruft z.B. die Liste der in den letzten beiden Wochen durchgeführten Commits ab: $ git log --since=2.weeks Dieser Befehl funktioniert mit vielen Formaten. Du kannst ein bestimmtes Datum wie "2008-01-15" angeben, oder ein relatives Datum wie "vor 2 Jahren 1 Tag 3 Minuten" . Du kannst die Liste auch nach Commits filtern, die bestimmten Suchkriterien entsprechen. Mit der Option --author kannst du nach einem bestimmten Autor filtern und mit der Option --grep kannst du nach Schlüsselwörtern in den Übertragungsmeldungen suchen. Anmerkung Du kannst mehr als eine Instanz der Suchkriterien --author und --grep angeben, was die Commit-Ausgabe auf Commits beschränkt, die jedem der --author Muster und jedem der --grep Muster entsprechen; durch Hinzufügen der Option --all-match wird die Ausgabe jedoch weiter auf diejenigen Commits beschränkt, die allen --grep Mustern entsprechen. Ein weiterer wirklich hilfreicher Filter ist die Option -S (umgangssprachlich als Git’s „Pickel“-Option bezeichnet), die eine Zeichenkette empfängt und nur die Commits anzeigt, die die Anzahl der Vorkommen dieser Zeichenkette geändert haben. Wenn du beispielsweise den letzten Commit suchen möchtest, der einen Verweis auf eine bestimmte Funktion hinzugefügt oder entfernt hat, kannst du Folgendes aufrufen: $ git log -S function_name Die letzte hier angesprochene nützliche Option, die als Filter an git log`übergeben werden kann, ist ein Pfad. Wenn du ein Verzeichnis oder einen Dateinamen angibst, kannst du die Log-Ausgabe auf Commits beschränken, die eine Änderung an diesen Dateien vorgenommen haben. Das ist immer die letzte Option und wird in der Regel durch Doppelstriche ( --`) eingeleitet, um Pfade von den Optionen zu trennen. $ git log -- path/to/file In Optionen zum Anpassen der Ausgabe von git log sind diese und einige andere gängige Optionen als Referenz aufgelistet. Tabelle 3. Optionen zum Anpassen der Ausgabe von git log Option Beschreibung -<n> Zeigt nur die letzten n Commits an --since , --after Begrenzt die angezeigten Commits auf die, die nach dem angegebenen Datum gemacht wurden. --until , --before Begrenzt die angezeigten Commits auf die, die vor dem angegebenen Datum gemacht wurden. --author Zeigt nur Commits an, bei denen der Autoren-Eintrag mit der angegebenen Zeichenkette übereinstimmt. --committer Zeigt nur Commits an, bei denen der Committer-Eintrag mit der angegebenen Zeichenkette übereinstimmt. --grep Zeigt nur Commits an, deren Commit-Beschreibung die Zeichenkette enthält -S Zeigt nur Commits an, die solchen Code hinzufügen oder entfernen, der mit der Zeichenkette übereinstimmt Wenn du zum Beispiel sehen möchtest, welche der Commits die Testdateien in der Git-Quellcode-Historie ändern, die von Junio Hamano im Monat Oktober 2008 committet wurden und keine Merge-Commits sind, kannst du in etwa folgendes aufrufen: $ git log --pretty="%h - %s" --author='Junio C Hamano' --since="2008-10-01" \ --before="2008-11-01" --no-merges -- t/ 5610e3b - Fix testcase failure when extended attributes are in use acd3b9e - Enhance hold_lock_file_for_{update,append}() API f563754 - demonstrate breakage of detached checkout with symbolic link HEAD d1a43f2 - reset --hard/read-tree --reset -u: remove unmerged new paths 51a94af - Fix "checkout --track -b newbranch" on detached HEAD b0ad11e - pull: allow "git pull origin $something:$current_branch" into an unborn branch Von den fast 40.000 Commits in der Git-Quellcode-Historie zeigt dieser Befehl die 6 Commits an, die diesen Kriterien entsprechen. Hinweis Die Anzeige von Merge-Commits unterdrücken Abhängig von dem in deinem Repository verwendeten Workflow ist es möglich, dass ein beträchtlicher Prozentsatz der Commits in deiner Log-Historie nur Merge-Commits sind, die in der Regel nicht sehr informativ sind. Um zu vermeiden, dass die Anzeige von Merge-Commits deinen Log-Verlauf überflutet, füge einfach die Log-Option --no-merges hinzu. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:20 |
https://www.linkedin.com/products/axway-amplify-managed-file-transfer/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_full-click | Axway Managed File Transfer | LinkedIn Skip to main content LinkedIn Axway in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Axway Managed File Transfer Managed File Transfer (MFT) Software by Axway See who's skilled in this Add as skill Learn more Report this product About Secure, reliable, and easy-to-manage solution for transferring data between people, partners, businesses, and applications. Manage and control how your organization sends and receives data so you can ensure it stays protected and meets compliance regulations such as HIPAA, PCI, DSS, and GDPR. This product is intended for Chief Information Officer Head of Operations Head of Supply Chain Management Head of Information Technology Head of Logistics Head of Business Operations Director Information Technology Infrastructure Director of Operations Media Products media viewer No more previous content Axway SecureTransport Interactive Demo Contact us right here 💬 https://www.axway.com/en/contact-us-mft Welcome to our interactive demo of SecureTransport. One of many solutions in the Axway MFT product line. This quick demo will take you through a number of scenarios, showing you how and where to configure SecureTransport to achieve efficient and secure file transfers for your organization. Axway's Approach to Secure File Transfer in Financial Services -- Meetesh Patel, MFT General Manager Meetesh Patel, MFT General Manager, discusses Axway's approach to secure file transfer in financial services. Daimler Truck | Using Axway MFT to operate critical flows globally Discover how Daimler Truck, a global leader in commercial vehicle manufacturing, has harnessed the power of Axway MFT to enhance its worldwide operations, enabling them to achieve unparalleled agility, reliability, and security in both B2B and B2C. Customer Spotlight: Alaska Airlines' journey with Axway MFT Watch the Alaska Airlines team as they share their journey with Axway and the pivotal role MFT plays in their business operations. In this video, you’ll hear firsthand how they’ve experienced improved reliability and enhanced security, ensuring seamless data transfers and bolstering their operational efficiency. No more next content Featured customers of Axway Managed File Transfer State of California Government Administration 146,301 followers Textron Aviation and Aerospace Component Manufacturing 180,015 followers Ciena Telecommunications 280,960 followers Groupe CAT Transportation, Logistics, Supply Chain and Storage 39,638 followers Dun & Bradstreet Information Services 288,356 followers Groupe AGRICA Insurance 15,432 followers Banco do Brasil Banking 1,981,305 followers Railinc Corp. IT Services and IT Consulting 7,097 followers Bosch Software Development 1,600,877 followers AG2R LA MONDIALE Insurance 95,160 followers Skipton Building Society Financial Services 33,578 followers Alaska Airlines Airlines and Aviation 322,367 followers Acerta Human Resources Services 33,616 followers Inmar Intelligence Software Development 41,915 followers Bpifrance Banking 441,486 followers Sopra Steria IT Services and IT Consulting 984,370 followers Cardinal Health Hospitals and Health Care 773,374 followers CommonSpirit Health Hospitals and Health Care 145,016 followers Serasa Experian Information Services 709,161 followers Bundesagentur für Arbeit Government Administration 184,821 followers B3 Financial Services 691,997 followers Show more Show less Similar products Progress MOVEit Progress MOVEit Managed File Transfer (MFT) Software Serv-U Managed File Transfer Server Serv-U Managed File Transfer Server Managed File Transfer (MFT) Software JSCAPE by Redwood JSCAPE by Redwood Managed File Transfer (MFT) Software Cerberus by Redwood Cerberus by Redwood Managed File Transfer (MFT) Software MLADU MLADU Managed File Transfer (MFT) Software dDataBox dDataBox Managed File Transfer (MFT) Software Sign in to see more Show more Show less Axway products Amplify API Management Platform Amplify API Management Platform API Management Software Axway Financial Accounting Hub Axway Financial Accounting Hub LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:29:20 |
https://sre.google/workbook/incident-response/ | Google SRE - Root Cause Analysis for Probing Incident Chapter 9 - Incident Response Table of Contents Foreword I Foreword II Preface 1. How SRE Relates to DevOps Part I - Foundations 2. Implementing SLOs 3. SLO Engineering Case Studies 4. Monitoring 5. Alerting on SLOs 6. Eliminating Toil 7. Simplicity Part II - Practices 8. On-Call 9. Incident Response 10. Postmortem Culture: Learning from Failure 11. Managing Load 12. Introducing Non-Abstract Large System Design 13. Data Processing Pipelines 14. Configuration Design and Best Practices 15. Configuration Specifics 16. Canarying Releases Part III - Processes 17. Identifying and Recovering from Overload 18. SRE Engagement Model 19. SRE: Reaching Beyond Your Walls 20. SRE Team Lifecycles 21. Organizational Change Management in SRE Conclusion Appendix A. Example SLO Document Appendix B. Example Error Budget Policy Appendix C. Results of Postmortem Analysis Index About the Editors Colophon Incident Response By Jennifer Mace, Jelena Oertel, Stephen Thorne, and Arup Chakrabarti (PagerDuty) with Jian Ma and Jessie Yang Everyone wants their services to run smoothly all the time, but we live in an imperfect world in which outages do occur. What happens when a not-so-ordinary, urgent problem requires multiple individuals or teams to resolve it? You are suddenly faced with simultaneously managing the incident response and resolving the problem. Resolving an incident means mitigating the impact and/or restoring the service to its previous condition. Managing an incident means coordinating the efforts of responding teams in an efficient manner and ensuring that communication flows both between the responders and to those interested in the incident’s progress. Many tech companies, including Google, have adopted and adapted best practices for managing incidents from emergency response organizations, which have been using these practices for many years. The basic premise of incident management is to respond to an incident in a structured way. Large-scale incidents can be confusing; a structure that teams agree on beforehand can reduce chaos. Formulating rules about how to communicate and coordinate your efforts before disaster strikes allows your team to concentrate on resolving an incident when it occurs. If your team has already practiced and familiarized themselves with communication and coordination, they don’t need to worry about these factors during an incident. Setting up an incident response process doesn’t need to be a daunting task. There are a number of widely available resources that can provide some guidance, such as Managing Incidents in the first SRE Book. The basic principles of incident response include the following: Maintain a clear line of command. Designate clearly defined roles. Keep a working record of debugging and mitigation as you go. Declare incidents early and often. This chapter shows how incident management is set up at Google and PagerDuty, and gives examples of where we got this process right and where we didn’t. The simple checklist in Putting Best Practices into Practice can help you get started on creating your own incident response practice, if you don’t already have one. Incident Management at Google Incident response provides a system for responding to and managing an incident. A framework and set of defined procedures allow a team to respond to an incident effectively and scale up their response. Google’s incident response system is based on the Incident Command System (ICS) . Incident Command System ICS was established in 1968 by firefighters as a way to manage wildfires. This framework provides standardized ways to communicate and fill clearly specified roles during an incident. Based upon the success of the model, companies later adapted ICS to respond to computer and system failures. This chapter explores two such frameworks: PagerDuty’s Incident Response process and Incident Management At Google ( IMAG ). Incident response frameworks have three common goals, also known as the “three Cs” (3Cs) of incident management: Coordinate response effort. Communicate between incident responders, within the organization, and to the outside world. Maintain control over the incident response. When something goes wrong with incident response, the culprit is likely in one of these areas. Mastering the 3Cs is essential for effective incident response. Main Roles in Incident Response The main roles in incident response are the Incident Commander (IC), Communications Lead (CL), and Operations or Ops Lead (OL). IMAG organizes these roles into a hierarchy: the IC leads the incident response, and the CL and OL report to the IC. When disaster strikes, the person who declares the incident typically steps into the IC role and directs the high-level state of the incident. The IC concentrates on the 3Cs and does the following: Commands and coordinates the incident response, delegating roles as needed. By default, the IC assumes all roles that have not been delegated yet. Communicates effectively. Stays in control of the incident response. Works with other responders to resolve the incident. The IC may either hand off their role to someone else and assume the OL role, or assign the OL role to someone else. The OL works to respond to the incident by applying operational tools to mitigate or resolve the incident. While the IC and OL work on mitigating and resolving the incident, the CL is the public face of the incident response team . The CL’s main duties include providing periodic updates to the incident response team and stakeholders, and managing inquiries about the incident. Both the CL and OL may lead a team of people to help manage their specific areas of incident response. These teams can expand or contract as needed. If the incident becomes small enough, the CL role can be subsumed back into the IC role. Case Studies The following four large-scale incidents illustrate how incident response works in practice. Three of these case studies are from Google, and the last is a case study from PagerDuty, which provides perspective on how other organizations use ICS-derived frameworks. The Google examples start with an incident that wasn’t managed effectively, and progress to incidents that were managed well. Case Study 1: Software Bug—The Lights Are On but No One’s (Google) Home This example shows how failing to declare an incident early on can leave a team without the tools to respond to an incident quickly and efficiently. While this incident was resolved without major calamity, early escalation would have produced a quicker, more organized response, and a better outcome. Context Google Home is a smart speaker and home assistant that responds to voice commands. The voice commands interact with Google Home’s software, which is called Google Assistant. Interacting with Google Home starts when a user says a hotword , a given phrase that triggers Google Assistant. Multiple users can use the same Google Home device by training the assistant to listen for a given hotword. The hotword model that identifies speakers is trained on the client, but the training data (i.e., the speaker recognition files) is stored on the server. The server handles bidirectional streaming of data. To handle overload during busy times, the server has a quota policy for Google Assistant. In order to protect servers from overly large request values, the quota limit is significantly higher than the baseline usage for Google Assistant on a given device. A bug in Google Assistant version 1.88 caused speaker recognition files to be fetched 50 times more often than expected, exceeding this quota. Initially, Google Home users in the central United States experienced only small traffic losses. As the rollout increased progressively to all Google Home devices, however, users lost half of their requests during the weekend of June 3, 2017. Incident At 11:48 a.m. PST on Monday, May 22, Jasper, the developer on-call for Google Home, happened to be looking at the queries per second (QPS) graphs and noticed something strange: Google Assistant had been pinging training data every 30 minutes, instead of once per day as expected. He stopped the release of version 1.88, which had rolled out to 25% of users. He raised a bug—let’s call it bug 12345—with Google’s bug tracking system to explore why this was happening. On the bug, he noted that Google Assistant was pinging data 48 times a day, causing it to exceed its QPS capacity. Another developer, Melinda, linked the issue to a previously reported bug, which we’ll call bug 67890: any time an app refreshed the device authentication and enrollment state, the speech processor restarted. This bug was slated to be fixed after the version 1.88 release, so the team requested a temporary increase in quota for the model to mitigate the overload from extra queries. The version 1.88 release was started again and continued to roll out, reaching 50% of users by Wednesday, May 31. Unfortunately, the team later learned that bug 67890, while responsible for some extra traffic, was not the actual root cause of the more frequent fetches that Jasper had noticed. That same morning, customers started reporting an issue to Google’s support team: any time someone said “OK Google” (or any other hotword to activate Google Home), the device responded with an error message. This issue prevented users from giving commands to Google Assistant. The team began to investigate what could be causing the errors that users reported. They suspected quota issues, so they requested another increase to the quota, which seemed to mitigate the problem. Meanwhile, the team continued to investigate bug 12345 to see what was triggering the errors. Although the quota connection was established early in the debugging process, miscommunication between the client and server developers had led developers down the wrong path during troubleshooting, and the full solution remained out of reach. The team also puzzled over why Google Assistant’s traffic kept hitting quota limits. The client and server developers were confused by client-side errors that didn’t seem to be triggered by any problems on the server side. The developers added logging to the next release to help the team understand the errors better, and hopefully make progress in resolving the incident. By Thursday, June 1, users reported that the issue had been resolved. No new issues were reported, so the version 1.88 release continued to roll out. However, the root cause of the original issue had not yet been identified. By early Saturday morning, June 3, the version 1.88 release rollout surpassed 50%. The rollout was happening on a weekend, when developers were not readily available. The team had not followed the best practice of performing rollouts only during business days to ensure developers are around in case something goes wrong. When the version 1.88 release rollout reached 100% on Saturday, June 3, the client once more hit server limits for Google Assistant traffic. New reports from customers started coming in. Google employees reported that their Google Home devices were throwing errors. The Google Home support team received numerous customer phone calls, tweets, and Reddit posts about the issue, and Google Home’s help forum displayed a growing thread discussing the issue. Despite all the user reports and feedback, the bug wasn’t escalated to a higher priority. On Sunday, June 4, as the number of customer reports continued to increase, the support team finally raised the bug priority to the highest level. The team did not declare an incident, but continued to troubleshoot the issue via “normal” methods, using the bug tracking system for communication. The on-call developer noticed error rates in one of the datacenter clusters and pinged SRE, asking them to drain it. At the same time, the team submitted another request for a quota increase. Afterward, an engineer on the developer team noticed the drain had pushed errors into other cells, which provided additional evidence of quota issues. At 3:33 p.m., the developer team manager increased the quota for Google Assistant once again, and the impact on users stopped. The incident was over. The team identified the root cause (see the previous “Context” section) shortly thereafter. Review Some aspects of incident handling went really well, while others had room for improvement. First, the developers rallied on the weekend and provided valuable input to resolve the issue. This was both good and bad. While the team valued the time and effort these individuals contributed over the weekend, successful incident management shouldn’t rely on heroic efforts of individuals. What if the developers had been unreachable? At the end of the day, Google supports a good work-life balance—engineers shouldn’t be tapped during their free time to fix work-related problems. Instead, we should have conducted rollouts during business hours or organized an on-call rotation that provided paid coverage outside of business hours. Next, the team worked to mitigate the issue. Google always aims to first stop the impact of an incident, and then find the root cause (unless the root cause just happens to be identified early on). Once the issue is mitigated, it’s just as important to understand the root cause in order to prevent the issue from happening again. In this case, mitigation successfully stopped the impact on three separate occasions, but the team could only prevent the issue from recurring when they discovered the root cause. After the first mitigation, it would have been better to postpone the rollout until the root cause was fully determined, avoiding the major disruption that happened over the weekend. Finally, the team did not declare an incident when problems first appeared. Our experience shows that managed incidents are resolved faster. Declaring an incident early ensures that: Miscommunication between the client and server developers is prevented. Root-cause identification and incident resolution occur sooner. Relevant teams are looped in earlier, making external communications faster and smoother. Centralized communication is an important principle of the IMAG protocol. For example, when disaster strikes, SREs typically gather in a “war room.” The war room can be a physical location like a conference room, or it can be virtual: teams might gather on an IRC channel or Hangout. The key here is to gather all the incident responders in one place and to communicate in real time to manage—and ultimately resolve—an incident. Case Study 2: Service Fault—Cache Me If You Can The following incident illustrates what happens when a team of experts tries to debug a system with so many interactions that no single person can grasp all the details. Sound familiar? Context Kubernetes is an open source container management system built collaboratively by many companies and individual contributors. Google Kubernetes Engine, or GKE, is a Google-managed system that creates, hosts, and runs Kubernetes clusters for users. This hosted version operates the control plane, while users upload and manage workloads in the way that suits them best. When a user first creates a new cluster, GKE fetches and initializes the Docker images their cluster requires. Ideally, these components are fetched and built internally so we can validate them. But because Kubernetes is an open source system, new dependencies sometimes slip in through the cracks. Incident One Thursday at 6:41 a.m. PST, London’s on-call SRE for GKE, Zara, was paged for CreateCluster prober failures across several zones. No new clusters were being successfully created. Zara checked the prober dashboard and saw that failures were above 60% for two zones. She verified this issue was affecting user attempts to create new clusters, though traffic to existing clusters was not affected. Zara followed GKE’s documented procedure and declared an incident at 7:06 a.m. Initially, four people were involved in the incident: Zara, who first noticed the problem, and was therefore the designated default Incident Commander Two of Zara’s teammates Rohit, the customer support engineer paged by the incident procedure Since Rohit was based in Zurich, Zara (the IC) opened a GKE Panic IRC channel where the team could debug together. While the other two SREs dug into monitoring and error messages, Zara explained the outage and its impact to Rohit. By 7:24 a.m., Rohit posted a notice to users that CreateCluster was failing in the Europe-West region. This was turning into a large incident. Between 7 a.m. and 8:20 a.m., Zara, Rohit, and the others worked on troubleshooting the issue. They examined cluster startup logs, which revealed an error: error: failed to run Kubelet: cannot create certificate signing request: Post https://192.0.2.53/apis/certificates.k8s.io/v1beta1/certificatesigningrequests They needed to determine which part of the certificate creation failed. The SREs investigated the network, resource availability, and the certificate signing process. All seemed to work fine separately. At 8:22 a.m., Zara posted a summary of the investigation to the incident management system, and looked for a developer who could help her. Thankfully, GKE had a developer on-call who could be paged for emergencies. The developer, Victoria, joined the channel. She asked for a tracking bug and requested that the team escalate the issue to the infrastructure on-call team. It was now 8:45 a.m. The first Seattle SRE, Il-Seong, arrived at the office, lightly caffeinated and ready for the day. Il-Seong was a senior SRE with many years of experience in incident response. When he was informed about the ongoing incident, he jumped in to help. First, Il-Seong checked the day’s release against the timing of the alerts, and determined that the day’s release did not cause the incident. He then started a working document 1 to collect notes. He suggested that Zara escalate the incident to the infrastructure, cloud networking, and compute engine teams to possibly eliminate those areas as root causes. As a result of Zara’s escalation, additional people joined the incident response: The developer lead for GKE nodes Cloud Networking on-call Compute Engine on-call Herais, another Seattle SRE At 9:10 a.m., the incident channel had a dozen participants. The incident was 2.5 hours old, with no root cause and no mitigation. Communication was becoming a challenge. Normally, on-call handover from London to Seattle occurred at 10 a.m., but Zara decided to hand over incident command to Il-Seong before 10 a.m., since he had more experience with IMAG. As Incident Commander, Il-Seong set up a formal structure to address the incident. He then designated Zara as Ops Lead and Herais as Communications (Comms) Lead. Rohit remained the External Communications Lead. Herais immediately sent an “all hands on deck” email to several GKE lists, including all developer leads, and asked experts to join the incident response. So far, the incident responders knew the following: Cluster creation failed where nodes attempted to register with the master. The error message indicated the certificate signing module as the culprit. All cluster creation in Europe was failing; all other continents were fine. No other GCP services in Europe were seeing network or quota problems. Thanks to the call for all hands on deck, Puanani, a GKE Security team member, joined the effort. She noticed the certificate signer was not starting. The certificate signer was trying to pull an image from DockerHub, and the image appeared to be corrupted. Victoria (the on-call GKE developer) ran Docker’s pull command for the image in two geographic locations. It failed when it ran on a cluster in Europe and succeeded on a cluster in the US. This indicated that the European cluster was the problem. At 9:56 a.m., the team had identified a plausible root cause. Because DockerHub was an external dependency, mitigation and root causing would be especially challenging. The first option for mitigation was for someone at Docker to quickly fix the image. The second option was to reconfigure the clusters to fetch the image from a different location, such as Google Container Registry (GCR), Google’s secure image hosting system. All the other dependencies, including other references to the image, were located in GCR. Il-Seong assigned owners to pursue both options. He then delegated a team to investigate fixing the broken cluster. Discussion became too dense for IRC, so detailed debugging moved to the shared document, and IRC became the hub for decision making. For the second option, pushing a new configuration meant rebuilding binaries, which took about an hour. At 10:59 a.m., when the team was 90% done rebuilding, they discovered another location that was using the bad image fetch path. In response, they had to restart the build. While the engineers on IRC worked on the two mitigation options, Tugay, an SRE, had an idea. Instead of rebuilding the configuration and pushing it out (a cumbersome and risky process), what if they intercepted Docker’s pull requests and substituted the response from Docker with an internal cached image? GCR had a mirror for doing precisely this. Tugay reached out to contacts on GCR’s SRE team, and they confirmed that the team could set --registry-mirror= https://mirror.gcr.io on the Docker configuration. Tugay started setting up this functionality and discovered that the mirror was already in place! At 11:29 a.m., Tugay reported to IRC that these images were being pulled from the GCR mirror, not DockerHub . At 11:37 a.m., the Incident Commander paged GCR on-call. At 11:59 a.m., GCR on-call purged the corrupt image from their European storage layer. By 12:11 p.m., all European zones had fallen to 0% error. The outage was over. All that remained was cleanup, and writing a truly epic postmortem. CreateCluster had failed in Europe for 6 hours and 40 minutes before it was fixed. In IRC, 41 unique users appeared throughout the incident, and IRC logs stretched to 26,000 words. The effort spun up seven IMAG task forces at various times, and as many as four worked simultaneously at any given time. On-calls were summoned from six teams, not including those from the “all hands on deck” call. The postmortem contained 28 action items. Review The GKE CreateCluster outage was a large incident by anyone’s standards. Let’s explore what went well, and what could have been handled better. What went well? The team had several documented escalation paths and was familiar with incident response tactics. Zara, the GKE on-call, quickly verified that the impact was affecting actual customers. She then used an incident management system prepared beforehand to bring in Rohit, who communicated the outage to customers. What could have been handled better? The service itself had some areas of concern. Complexity and dependence on specialists were problematic. Logging was insufficient for diagnosis, and the team was distracted by the corruption on DockerHub, which was not the real issue. At the beginning of the incident, the Incident Commander didn’t put a formal incident response structure in place. While Zara assumed this role and moved the conversation to IRC, she could have been much more proactive in coordinating information and making decisions. As a result, a handful of first responders pursued their own investigations without coordination. Il-Seong put a formal incident response structure in place two hours after the first page. Finally, the incident revealed a gap in GKE’s disaster readiness: the service didn’t have any early generic mitigations that would reduce user pain. Generic mitigations are actions that first responders take to alleviate pain, even before the root cause is fully understood. For example, responders could roll back a recent release when an outage is correlated with the release cycle, or reconfigure load balancers to avoid a region when errors are localized. It’s important to note that generic mitigations are blunt instruments and may cause other disruptions to the service. However, while they may have broader impact than a precise solution, they can be put in place quickly to stop the bleeding while the team discovers and addresses the root cause. Let’s look at the timeline of this incident again to see where a generic mitigation might have been effective: 7 a.m. (Assessed impact). Zara confirmed that users were affected by the outage. 9:56 a.m. (Found possible cause). Puanani and Victoria identified a rogue image. 10:59 a.m. (Bespoke mitigation). Several team members worked on rebuilding binaries to push a new configuration that would fetch images from a different location. 11:59 a.m. (Found root cause and fixed the issue). Tugay and GCR on-call disabled GCR caching and purged a corrupt image from their European storage layer. A generic mitigation after step 2 (found possible cause) would have been very useful here. If the responders had rolled back all images to a known good state once they discovered the issue’s general location, the incident would have been mitigated by 10 a.m. To mitigate an incident, you don’t have to fully understand the details—you only need to know the location of the root cause. Having the ability to mitigate an outage before its cause is fully understood is crucial for running robust services with high availability. In this case, the responders would have benefited from some sort of tool that facilitated rollbacks. Mitigation tools do take engineering time to develop. The right time to create general-purpose mitigation tools is before an incident occurs, not when you are responding to an emergency. Browsing postmortems is a great way to discover mitigations and/or tools that would have been useful in retrospect, and build them into services so that you can better manage incidents in the future. It’s important to remember that first responders must prioritize mitigation above all else , or time to resolution suffers. Having a generic mitigation in place, such as rollback and drain, speeds recovery and leads to happier customers. Ultimately, customers do not care whether or not you fully understand what caused an outage. What they want is to stop receiving errors. With mitigation as top priority, an active incident should be addressed as follows: Assess the impact of the incident. Mitigate the impact. Perform a root-cause analysis of the incident. After the incident is over, fix what caused the incident and write a postmortem. Afterward, you can run incident response drills to exercise the vulnerabilities in the system, and engineers can work on projects to address these vulnerabilities. Case Study 3: Power Outage—Lightning Never Strikes Twice…Until It Does The previous examples showed what can go wrong when you don’t have good incident response strategies in place. The next example illustrates an incident that was successfully managed. When you follow a well-defined and clear response protocol, you can handle even rare or unusual incidents with ease. Context Power grid events, such as lightning strikes, cause the power coming into a datacenter facility to vary wildly. Lightning strikes affecting the power grid are rare, but not unexpected. Google protects against sudden, unexpected power outages with backup generators and batteries, which are well tested and known to work in these scenarios. Many of Google’s servers have a large number of disks attached to them, with the disks located on a separate tray above or below the server. These trays have their own uninterruptible power supply (UPS) battery. When a power outage occurs, the backup generators activate but take a few minutes to start. During this period, the backup batteries attached to the servers and disk trays provide power until the backup generators are fully running, thereby preventing power grid events from impacting datacenter operation. Incident In mid-2015, lightning struck the power grid near a Google datacenter in Belgium four times within two minutes. The datacenter’s backup generators activated to supply power to all the machines. While the backup generators were starting up, most of the servers ran on backup batteries for a few minutes. The UPS batteries in the disk trays did not swap power usage to the backup batteries on the third and fourth lightning strikes because the strikes were too closely spaced. As a result, the disk trays lost power until the backup generators kicked in. The servers did not lose power, but were unable to access the disks that had power cycled. Losing a large number of disk trays on persistent disk storage resulted in read and write errors for many virtual machine (VM) instances running on Google Compute Engine (GCE). The Persistent Disk SRE on-call was immediately notified of these errors. Once the Persistent Disk SRE team established the impact, a major incident was declared and announced to all affected parties. The Persistent Disk SRE on-call assumed the role of Incident Commander. After an initial investigation and communication between stakeholders, we established that: Each machine that lost a disk tray because of the temporary power outage needed to be rebooted. While waiting for the reboot, some customer VMs had trouble reading and writing to their disks. Any host that had both a disk tray and customer VMs could not simply be “rebooted” without losing the customer VMs that hadn’t been affected. Persistent Disk SRE asked GCE SRE to migrate unaffected VMs to other hosts. The Persistent Disk SRE’s primary on-call retained the IC role, since that team had the best visibility into customer impact. Operations team members were tasked with the following objectives: Safely restore power to use grid power instead of backup generators. Restart all machines that were not hosting VMs. Coordinate between Persistent Disk SRE and GCE SRE to safely move VMs away from the affected machines before restarting them. The first two objectives were clearly defined, well understood, and documented. The datacenter ops on-call immediately started working to safely restore power, providing regular status reports to the IC. Persistent Disk SRE had defined procedures for restarting all machines not hosting virtual machines. A team member began restarting those machines. The third objective was more vague and wasn’t covered by any existing procedures. The Incident Commander assigned a dedicated operations team member to coordinate with GCE SRE and Persistent Disk SRE. These teams collaborated to safely move VMs away from the affected machines so the affected machines could be rebooted. The IC closely monitored their progress and realized that this work called for new tools to be written quickly. The IC organized more engineers to report to the operations team so they could create the necessary tools. The Communications Lead observed and asked questions about all incident-related activities, and was responsible for reporting accurate information to multiple audiences: Company leaders needed information about the extent of the problem, and assurance that the problem was being addressed. Teams with storage concerns needed to know when their storage would be fully available again. External customers needed to be proactively informed about the problem with their disks in this cloud region. Specific customers who had filed support tickets needed more information about the problems they were seeing, and advice on workarounds and timelines. After we mitigated the initial customer impact, we needed to do some follow-up, such as: Diagnosing why the UPS used by the disk trays failed, and making sure that it doesn’t happen again. Replacing the batteries in the datacenter that failed. Manually clearing “stuck” operations caused by losing so many storage systems simultaneously. Post-incident analysis revealed that only a small number of writes—the writes pending on the machines that lost power during the incident—weren’t ever written to disk. Since Persistent Disk snapshots and all Cloud Storage data are stored in multiple datacenters for redundancy, only 0.000001% of data from running GCE machines was lost, and only data from running instances was at risk. Review By declaring the incident early and organizing a response with clear leadership, a carefully managed group of people handled this complex incident effectively. The Incident Commander delegated the normal problems of restoring power and rebooting servers to the appropriate Operations Lead. Engineers worked on fixing the issue and reported their progress back to the Operations Lead. The more complex problem of meeting the needs of both GCE and Persistent Disk required coordinated decision making and interaction among multiple teams. The Incident Commander made sure to assign appropriate operations team members from both teams to the incident, and worked directly with them to drive toward a solution. The Incident Commander wisely focused on the most important aspect of the incident: addressing the needs of the impacted customers as quickly as possible. Case Study 4: Incident Response at PagerDuty by Arup Chakrabarti of PagerDuty PagerDuty has developed and refined our internal incident response practices over the course of several years. Initially, we staffed a permanent, company-wide Incident Commander and dedicated specific engineers per service to take part in incident response. As PagerDuty grew to over 400 employees and dozens of engineering teams, our Incident Response processes also changed. Every few months, we take a hard look at our processes, and update them to reflect business needs. Nearly everything we have learned is documented at https://response.pagerduty.com. Our Incident Response processes are purposefully not static; they change and evolve just as our business does. Major incident response at PagerDuty Typically, small incidents require only a single on-call engineer to respond. When it comes to larger incidents, we place heavy emphasis on teamwork. An engineer shouldn’t feel alone in high-stress and high-impact scenarios. We use the following techniques to help promote teamwork: Participating in simulation exercises One way we teach teamwork is by participating in Failure Friday . PagerDuty drew inspiration from Netflix’s Simian Army to create this program. Originally, Failure Friday was a manual failure injection exercise aimed at learning more about the ways our systems could break. Today, we also use this weekly exercise to recreate common problems in production and incident response scenarios. Before Failure Friday starts, we nominate an Incident Commander (typically, a person training to become an IC). They are expected to behave and act like a real IC while conducting failure injection exercises. Throughout the drill, subject-matter experts use the same processes and vernacular they would use during an actual incident. This practice both familiarizes new on-call engineers with incident response language and processes and provides more seasoned on-call engineers with a refresher. Playing time-bound simulation games While Failure Friday exercises go a long way toward training engineers on different roles and processes, they can’t fully replicate the urgency of actual major incidents. We use simulation games with a time-bound urgency to capture that aspect of incident response. “Keep Talking and Nobody Explodes” is one game we’ve leveraged heavily. It requires players to work together to defuse bombs within time limits. The stressful and communication-intensive nature of the game forces players to cooperate and work together effectively. Learning from previous incidents Learning from previous incidents helps us respond better to major incidents in the future. To this end, we conduct and regularly review postmortems. PagerDuty’s postmortem process involves open meetings and thorough documentation. By making this information easily accessible and discoverable, we aim to reduce the resolution time of future incidents, or prevent a future incident from happening altogether. We also record all of the phone calls involved in a major incident so we can learn from the real-time communication feed. Let’s look at a recent incident in which PagerDuty had to leverage our incident response process. The incident occurred on October 6, 2017, and lasted more than 10 hours, but had very minimal customer impact. 7:53 p.m. A member of the PagerDuty SRE team was alerted that PagerDuty internal NTP servers were exhibiting clock drift. The on-call SRE validated that all automated recovery actions had been executed, and completed the mitigation steps in relevant runbooks. This work was documented in the SRE team’s dedicated Slack channel. 8:20 p.m. A member of PagerDuty Software Team A received an automated alert about clock drift errors in their services. Software Team A and the SRE team worked toward resolving the problem. 9:17 p.m. A member of PagerDuty Software Team B received an automated alert about clock drift errors on their services. The engineer from Team B joined the Slack channel where the issue was already being triaged and debugged. 9:49 p.m. The SRE on-call declared a major incident and alerted the Incident Commander on-call. 9:55 p.m. The IC assembled the response team, which included every on-call engineer that had a service dependent on NTP, and PagerDuty’s customer support on-call. The IC had the response team join the dedicated conference call and Slack channel. For the next eight hours, the response team worked on addressing and mitigating the issue. When the procedures in our runbooks didn’t resolve the issue, the response team started trying new recovery options in a methodical manner. During this time, we rotated on-call engineers and the IC every four hours. Doing so encouraged engineers to get rest and brought new ideas into the response team. 5:33 a.m. The on-call SRE made a configuration change to the NTP servers. 6:13 a.m. The IC validated that all services had recovered with their respective on-call engineers. Once validation was complete, the IC shut off the conference call and Slack channel and declared the incident complete. Given the wide impact of the NTP service, a postmortem was warranted. Before closing out the incident, the IC assigned the postmortem analysis to the SRE team on-call for the service. Tools used for incident response Our Incident Response processes leverage three main tools: PagerDuty We store all of our on-call information, service ownership, postmortems, incident metadata, and the like, in PagerDuty. This allows us to rapidly assemble the right team when something goes wrong. Slack We maintain a dedicated channel (#incident-war-room) as a gathering place for all subject-matter experts and Incident Commanders. The channel is used mostly as an information ledger for the scribe, who captures actions, owners, and timestamps. Conference calls When asked to join any incident response, on-call engineers are required to dial in to a static conference call number. We prefer that all coordination decisions are made in the conference call, and that decision outcomes are recorded in Slack. We found this was the fastest way to make decisions. We also record every call to make sure that we can recreate any timeline in case the scribe misses important details. While Slack and conference calls are our communication channels of choice, you should use the communication method that works best for your company and its engineers. At PagerDuty, how we handle incident response relates directly to the success of the company. Rather than facing such events unprepared, we purposefully prepare for incidents by conducting simulation exercises, reviewing previous incidents, and choosing the right tools to help us be resilient to any major incident that may come our way. Putting Best Practices into Practice We’ve seen examples of incidents that were handled well, and some that were not. By the time a pager alerts you to a problem, it’s too late to think about how to manage the incident. The time to start thinking about an incident management process is before an incident occurs. So how do you prepare and put theory into practice before disaster strikes? This section provides some recommendations. Incident Response Training We highly recommend training responders to organize an incident so they have a pattern to follow in a real emergency. Knowing how to organize an incident, having a common language to use throughout the incident, and sharing the same expectations reduce the chance of miscommunication. The full Incident Command System approach may be more than you need, but you can develop a framework for handling incidents by selecting the parts of the incident management process that are important to your organization. For example: Let on-calls know they can delegate and escalate during an incident. Encourage a mitigation-first response. Define Incident Commander, Communications Lead, and Operations Lead roles. You can adapt and summarize your incident response framework, and create a slide deck to present to new team members. We’ve learned that people are more receptive to incident response training when they can connect the theory of incident response to actual scenarios and concrete actions. Therefore, be sure to include hands-on exercises and share what happened in past incidents, analyzing what went well and what didn’t go so well. You might also consider using external agencies that specialize in incident response classes and training. Prepare Beforehand In addition to incident response training, it helps to prepare for an incident beforehand. Use the following tips and strategies to be better prepared. Decide on a communication channel Decide and agree on a communication channel (Slack, a phone bridge, IRC, HipChat, etc.) beforehand—no Incident Commander wants to make this decision during an incident. Practice using it so there are no surprises. If possible, pick a communications channel the team is already familiar with so that everyone on the team feels comfortable using it. Keep your audience informed Unless you acknowledge that an incident is happening and actively being addressed, people will automatically assume nothing is being done to resolve the issue. Similarly, if you forget to call off the response once the issue has been mitigated or resolved, people will assume the incident is ongoing. You can preempt this dynamic by keeping your audience informed throughout the incident with regular status updates. Having a prepared list of contacts (see the next tip) saves valuable time and ensures you don’t miss anyone. Think ahead about how you’ll draft, review, approve, and release public blog posts or press releases. At Google, teams seek guidance from the PR team. Also, prepare two or three ready-to-use templates for sharing information, making sure the on-call knows how to send them. No one wants to write these announcements under extreme stress with no guidelines. The templates make sharing information with the public easy and minimally stressful. Prepare a list of contacts Having a list of people to email or page prepared beforehand saves critical time and effort. In Case Study 2: Service Fault—Cache Me If You Can , the Comms Lead made an “all hands on deck” call by sending an email to several GKE lists that were prepared beforehand. Establish criteria for an incident Sometimes it’s clear that a paging issue is truly an incident. Other times, it’s not so clear. It’s helpful to have an established list of criteria for determining if an issue is indeed an incident. A team can come up with a solid list of criteria by looking at past outages, taking known high-risk areas into consideration. In summary, it’s important to establish common ground for coordination and communication when responding to incidents. Decide on ways to communicate the incident, who your audience is, and who is responsible for what during an incident. These guidelines are easy to set up and have high impact on shortening the resolution time of an incident. Drills The final step in the incident management process is practicing your incident management skills. By practicing during less critical situations, your team develops good habits and patterns of behavior for when lightning strikes—figuratively and literally. After introducing the theory of incident response through training, practice ensures that your incident response skills stay fresh. There are several ways to conduct incident management drills. Google runs company-wide resilience testing (called Disaster Recovery Testing, or DiRT; see Kripa Krishnan’s article “Weathering the Unexpected” 2 ), in which we create a controlled emergency that doesn’t actually impact customers. Teams respond to the controlled emergency as if it were a real emergency. Afterward, the teams review the emergency response procedures and discuss what happened. Accepting failure as a means of learning, finding value in gaps identified, and getting our leadership on board were key to successfully establishing the DiRT program at Google. On a smaller scale, we practice responding to specific incidents using exercises like Wheel of Misfortune (see “Disaster Role Playing” in Site Reliability Engineering ). You can also practice incident response by intentionally treating minor problems as major ones requiring a large-scale response. This lets your team practice with the procedures and tools in a real-world situation with lower stakes. Drills are a friendly way of trying out new incident response skills. Anyone on your team who could get swept into incident response—SREs, developers, and even customer support and marketing partners—should feel comfortable with these tactics. To stage a drill, you can invent an outage and allow your team to respond to the incident. You can also create outages from postmortems, which contain plenty of ideas for incident management drills. Use real tools as much as possible to manage the incident. Consider breaking your test environment so the team can perform real troubleshooting using existing tools. All these drills are far more useful if they’re run periodically. You can make drills impactful by following up each exercise with a report detailing what went well, what didn’t go well, and how things could have been handled better. The most valuable part of running a drill is examining their outcomes, which can reveal a lot about any gaps in incident management. Once you know what they are, you can work toward closing them. Conclusion Be prepared for when disaster strikes. If your team practices and refreshes your incident response procedures regularly, you won’t panic when the inevitable outage occurs. The circle of people you need to collaborate with during an incident expands with the size of the incident. When you’re working with people you don’t know, procedures help create the structure you need to quickly move toward a resolution. We strongly recommend establishing these procedures ahead of time when the world is not on fire. Regularly review and iterate on your incident management plans and playbooks. The Incident Command System is a simple concept that is easily understood. It scales up or down according to the size of the company and the incident. Although it’s simple to understand, it isn’t easy to implement, especially in the middle of an incident when panic suddenly overtakes you. Staying calm and following the response structure during an emergency takes practice, and practice builds “muscle memory.” This gives you the confidence you’ll need for a real emergency. We strongly recommend carving out some time in your team’s busy schedule to practice incident management on a regular basis. Secure support from leadership for dedicated practice time, and make sure they understand how incident response works in case you need to involve them in a real incident. Disaster preparedness can shave off valuable minutes or hours from response time and gives you a competitive edge. No company gets it right all the time—learn from your mistakes, move on, and do better the next time. 1 When three or more people work on an incident, it’s useful to start a collaborative document that lists working theories, eliminated causes, and useful debugging information, such as error logs and suspect graphs. The document preserves this information so it doesn’t get lost in the conversation. 2 Kripa Krishan, “Weathering the Unexpected,” Communications of the ACM 10, no. 9 (2012), https://queue.acm.org/detail.cfm?id=2371516 . Previous Chapter 8 - On-Call Next Chapter 10 - Postmortem Culture: Learning from Failure Copyright © 2018 Google, Inc. Published by O'Reilly Media, Inc. Licensed under CC BY-NC-ND 4.0 | 2026-01-13T09:29:20 |
https://www.linkedin.com/uas/login?session_redirect=%2Fproducts%2Frd-station-rd-station-crm&trk=products_details_guest_primary_call_to_action | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:20 |
https://goo.gle/sre-classroom-imageserver | Google SRE classroom - Distributed imageserver workshop Site Reliability Engineering Jump to Content Home Resources Latest resources Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Distributed PubSub Distributed Image Server The Art of SLO Latest resources Resources overview Google SRE Video Gallery New! Product-Focused Reliability for SRE Twentieth Anniversary Twenty years of SRE lessons learned Prodverbs SRE Fundamentals Measuring Reliability Why Heroism is Bad System Theoretic Process Analysis Books Books overview Building Secure & Reliable Systems The Site Reliability Workbook Site Reliability Engineering Mobaa Mobaa overview 2024 Gallery 2022 Gallery 2020 Gallery Vector Methods Classroom Classroom overview Distributed PubSub Distributed Image Server The Art of SLO Books Careers Cloud Local Prodcast Spotlight Site Reliability Engineering Jump to Content SRE Classroom: Distributed ImageServer Introduction SRE Classroom: Distributed ImageServer is a workshop developed by Google's Site Reliability Engineering group. The goals of this workshop are to (1) introduce participants to the principles of non-abstract large systems design (NALSD) , and (2) provide hands-on experiences with applying these principles to the design and evaluation of these systems. We consider NALSD a concept fundamental to SRE, and understanding its principles provides a basis for having meaningful conversations about the design and operation of large software systems. In the first theoretical part of the workshop, participants learn about some foundational large system design principles and concepts. Topics include correctness, reliability, performance, different inter-system communication styles, and more. We introduce the problem requirements in detail and walk through the first parts of an example solution. This is a presentation style workshop, where the speakers first present the problem, then walk through an example solution and any relevant system design concepts. However, we welcome participants to work through their own solutions before learning about the sample solution. This will give participants an opportunity to apply the principles they have learned to develop an ImageServer system that meets certain performance and correctness requirements and Service Level Objectives (SLOs). Target Audience This workshop includes technical content, and its primary audience is software developers and site reliability engineers. We have also welcomed folks in various other roles, including product management and senior engineering management, to this workshop. The workshop includes hands-on work well-suited for groups of five, and scales well from 1 to 20 groups-as many as a hundred participants! Workshop Materials Distributed ImageServer – Slides & Video This presentation is the backbone of the workshop. It contains the training content that prepares participants for the practical exercises. We provide a pre-recorded video version of this workshop for reference. There are also detailed speaker notes for presenters that make it possible to deliver their own instance of the workshop with minimum preparation. We also provide a Presenter Guide with additional tips and guidance for leading the workshop. Presentation Slides Workshop Presentation Video Recording PDF version of these slides, without speaker notes Presenter Guide - A4 Distributed ImageServer – Participant Resources The Participant Handout contains additional details about the exercise. The Latency Numbers Everyone Should Know handout contains reference numbers that are useful for back-of-the-envelope calculations. The NALSD Workbook contains reference material that is useful both during the workshop and more generally when applying the NALSD approach to solving system design problems. The Imageserver project code is an open-source repository with a simple imageserver web application using GCP services. The application allows users to upload photos in a few different formats, search photos by tags, and then download them. Use this as a reference system for exploring the behavior of microservices running inside a Kubernetes cluster. Participant Handout - A4 Participant Handout - Letter Latency Numbers Everyone Should Know - A4 Latency Numbers Everyone Should Know - Letter NALSD Workbook - A4 NALSD Workbook - Letter Imageserver project code Distributed Imageserver – Facilitator Resources The Facilitator Guide contains tips and guidance for facilitators of the workshop. Facilitators should read this ahead of time to prepare for making the workshop an awesome experience for everyone involved. The breakout template can be used to set up breakout groups during the hands-on portion of the workshop. This preparation step can be done by either the facilitators or the presenter – be sure to coordinate and make a game plan ahead of time! Facilitator Guide - A4 Breakout Template Additional Resources We aim to develop durable SRE Classroom materials for folks learning about NALSD. If you find this useful, tell us what you want to see in future exercises. Please use the issue tracker to send us your thoughts and suggestions. Alternatively, send us a tweet at @googlesre . Visit the SRE Classroom page to learn more about NALSD and SRE. Licensing The materials above are released under the Creative Commons CC-BY-4.0 license for anyone to use and reuse, as long as Google is credited as the original author. If you want to suggest improvements, have any problems with the content, or just want to ask a question, please create a bug in our issue tracker component . Follow us About Google Google products Privacy Terms Help | 2026-01-13T09:29:20 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.