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://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#param-url-1 | Instagram API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Instagram API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Posts API Collect by URL Discover by URL Comments API Collect by URL Reels API Collect by URL Discover by URL Social Media APIs Instagram API Scrapers Copy page Copy page Overview The Instagram API Suite offers multiple types of APIs, each designed for specific data collection needs from Instagram. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : N/A Interesting Columns : followers , post_count , post_hashtags , profile_name . Posts API This API allows users to collect multiple posts based on a single input URL (such as an Instagram reels URL, search URL or profile URL). Discovery functionality : - Direct URL of the Instagram reel - Direct URL of the search - Direct URL of the profile Interesting Columns : url , followers , hashtags , engagement_score_view . Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : comment_user , comment , likes_number , replies_number . The suite of APIs is designed to offer flexibility for targeted data collection, where users can input specific URLs to gather detailed post and comment data, either in bulk or with precise filtering options. Profiles API Collect by URL This API allows users to collect detailed data about an Instagram profile by providing the profile URL. It provides a comprehensive overview of an Instagram profile, including business and engagement information, posts, and user details. Input Parameters URL string required The Instagram profile URL. Output Structure Includes comprehensive data points: Page/Profile Details : account , id , followers , posts_count , is_business_account , is_professional_account , is_verified , avg_engagement , profile_name , profile_url , profile_image_link , and more. For all data points, click here . Posts API Collect by URL This API enables users to collect detailed data from Instagram posts by providing a post URL. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Post Details : post_id , description , hashtags , date_posted , num_comments , likes , content_type , video_view_count , video_play_count , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : photos , videos , thumbnail , display_url (link only, not the file itself), audio. Discover by URL This API allows users to discover recent Instagram posts from a public profile by providing the profile URL and specifying additional parameters. Input Parameters URL string required The Instagram profile URL. num_of_posts number The number of recent posts to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date). post_type string Specify the type of posts to collect (e.g., post, reel). Output Structure Includes comprehensive data points: Post Details: post_id , description , hashtags , date_posted , num_comments , likes , video_view_count , video_play_count ,and more. For all data points, click here . Page/Profile Details: user_posted , followers , posts_count , profile_image_link , is_verified , profile_url , is_paid_partnership , partnership_details , user_posted_id Attachments and Media: photos , videos , thumbnail , audio , display_url , content_type , product_type , coauthor_producers , tagged_users . This API is designed to allow for filtering, exclusion of specific posts, and collecting posts by type (regular post or reel) within a defined time frame. It provides detailed post and profile information, making it ideal for data collection and analytics. Comments API Collect by URL This API allows users to collect the latest comments from a specific Instagram post by providing the post URL. This API retrieves the most recent 10 comments along with associated metadata. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Comment Details : comment_id , comment_user , comment_user_url , comment_date , comment , likes_number , replies_number , replies , hashtag_comment , tagged_users_in_comment , and more. For all data points, click here . User Details : user_name , user_id , user_url We provide a limited set of data points about the profile. Post Metadata : post_url , post_user , post_id . Reels API Collect by URL This API allows users to collect detailed data about Instagram reels from public profiles by providing the reel URL. Input Parameters URL string required The Instagram reel URL. Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , tagged_users , num_comments , likes , views , video_play_count , length , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : video_url , thumbnail , audio_url . Discover by URL This API allows users to discover Instagram Reels videos from a profile URL or direct search URL. Input Parameters URL string required The Instagram profile or direct search URL. num_of_posts number The number of recent reels to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering reels in MM-DD-YYYY format. end_date string End date for filtering reels in MM-DD-YYYY format (should be later than start_date ). Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , num_comments , likes , views , video_play_count , top_comments , length , video_url , audio_url , content_id , and more. For all data points, click here . Profile Details : user_posted , followers , posts_count , following . Attachments and Media : video_url , thumbnail , audio_url (link only, not the file itself). This API provides detailed information about Instagram Reels, with filtering options by date range, exclusion of specific posts, and a limit on the number of reels collected. Was this page helpful? Yes No Facebook LinkedIn ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://babelfish.money/wp-json/oembed/1.0/embed?url=https%3A%2F%2F%2F#038;format=xml | Babelfish – BabelFish BABELFISH Github Docs Forum Launch Dapp X sun (Traced) crescent-moon-phase-shape-with-two-stars (Traced)2022 BABELFISH Github Docs Analytics X LAUNCH DAPP UNIVERSAL MULTI-CHAIN STABLECOIN BabelFish's mind-boggling objective is to aggregate and distribute stablecoins, enhance flow, and push hyperBitcoinization. ABOUT BabelFish DAO Money Protocol is the simplest and most mind-bogglingly useful thing in the DeFi Universe. It absorbs, aggregates and distributes USD-pegged stablecoins across chains; the practical upshot of all this is that if you stick stablecoins to it, you can neatly cross the language divide between any chains. BabelFish's meta-stablecoin, XUSD, is backed by the underlying aggregated stablecoins to leverage and enhance their combined flow and utility across protocols and users. FISH holders can vote on improvement proposals, such as which stablecoins to accept, or what percent of collateral to lend. Learn More About It GO TO OUR GITBOOK What It Does What It Does: Since the big bang of DeFi in the crypto galaxy, many stablecoin projects have been created to meet the demand for USD. Different stablecoin brands with unique selling points are competing to represent the same dollar, but they do not translate 1:1, and crypto dollar liquidity is fractured between issuers and protocols. As DeFi markets expand beyond Ethereum to multiple chains, stablecoin liquidity is fractured further by the bridges used, which is suboptimal for the industry. BabelFish abstracts away these differences by aggregating stablecoins from multiple isolated liquidity lakes and providing users with access to the combined ocean of crypto-dollars available. Think of it as a translator or a converter: if a user wants to use crypto dollars on another chain, she can stick it on BabelFish and seamlessly get a par-value equivalent on the other side. What Is The FISH DAO The BabelFish DAO Money Protocol is ultimately directed by the will of FISH token holders participating in governance. From protocol improvement proposals to budget allocation and partnerships, it is the community that will be able to decide on the direction of the protocol. If you are passionate about the stablecoin ecosystem, this is the DAO for you. Help define protocol rules and parameters around the collateral accepted, discuss community incentives, manage risk, and much more. The future of BabelFish depends on active FISH holder participation. Help build, shape and enhance the stablecoin ecosystem. Participate in stablecoin collateral management. Be rewarded for staking and actively participating with FISH in governance. Mind-Bogglingly Useful XUSD is collateralized 1:1 by a hedged basket of accepted stablecoins across chains, which enables users and protocols to tap into the combined liquidity and utility of the underlying collateral and also enhances stablecoin flow across the ecosystem. User deposits an accepted stablecoin on BabelFish protocol. Protocol issues XUSD, its convertible stablecoin backed 1:1 User can use XUSD on accepted protocols, bridge between chains, and redeem back at any time What Moves BabelFish The need for a "trustless stablecoin translation device" seems painfully clear. The accelerated growth and velocity of crypto dollars is unstoppable, we expect demand for programmable money to continue accelerating as we onboard the first billion users. But the market remains fragmented, two players dominate >80% of the total USD-stablecoin float, and systemic and idiosyncratic risks abound. In the decentralised economy we ought not to rely on one or two issuers of USD-stablecoins but rather enable a thousand stablecoins to bloom and communicate with each other to bring mass adoption. For BabelFish DAO Money Protocol it is important that our first product, XUSD, is the safest, easiest and ultimate stablecoin instrument out there in crypto space. JOIN US TO EXPERIENCE BABELFISH | 2026-01-13T09:29:25 |
https://git-scm.com/book/tl/v2/GitHub-Pag-iiskrip-sa-GitHub | Git - Pag-iiskrip sa 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. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 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 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 6.5 GitHub - Pag-iiskrip sa GitHub Pag-iiskrip sa GitHub At ngayong natalakay na natin ang lahat ng mga pangunahing tampok at workflow ng GitHub, ngunit anumang malaking grupo o proyekto ay magkakaroon ng mga pasadya na gusto nila na gawin o mga serbisyo na panlabas na gusto nilang isama. Sa kabutihang-palad para sa atin, ang GitHub ay talagang lubos na maaaring i-hack sa maraming paraan. Sa seksyong ito, tatalakayon natin kung paano gamitin ang sistema ng mga hook ng GitHub at ang API nito upang gawin ang GitHub na gumana ayon sa gusto natin. Mga Serbisyo at mga Hook Ang seksyon ng mga Hook at mga Serbisyo ng pag-aadministrabo sa repositoryo ng GitHub ay ang pinakamadaling paraan upang makipag-ugnay ang GitHub sa mga panlabas na sistema. Mga Serbisyo Una nating tingnan ang mga Serbisyo. Ang parehong mga pagsasama ng mga Hook at Serbisyo ay matatagpuan sa seksyon ng mga Setting ng iyong repositoryo, kung saan dati nating natingnan sa pagdaragdag ng mga Tagatulong at pagbabago ng default na branch ng iyong proyekto. Sa ilalim ng tab na “Mga Webhook at mga Serbisyo” makikita natin ang isang bagay tulad ng Seksyon ng pagsasaayos sa mga Serbisyo at mga Hook. . Figure 130. Seksyon ng pagsasaayos sa mga Serbisyo at mga Hook. Mayroong dose-dosenang mga serbisyo ang maaari mong pagpipilian, karamihan sa mga ito ay mga pagsasama sa iba pang mga komersyal at mga sistema na open source. Karamihan sa kanila ay para sa mga serbisyo ng Patuloy na Pagsasama, bug, at mga tracker ng isyu, mga sistema ng chat room at mga sistema ng dokumentasyon. Tatalakayin natin ang pag-set up ng isang napaka-simple, ang hook ng Email. Kung pipiliin mo ang “email” mula sa dropdown na “Magdagdag ng Serbisyo”, makakakuha ng isang screen ng pagsasaayos tulad ng Pagsasaayos ng serbisyo ng Email. . Figure 131. Pagsasaayos ng serbisyo ng Email. Sa kasong ito, kung pinindot natin ang pindutan na “Magdagdag ng serbisyo”, ang tinukoy natin na email address ay makakakuha ng isang email sa tuwing may isang tao ang nag-push sa repositoryo. Ang mga serbisyo ay maaaring makinig para sa maraming iba’t-ibang uri ng mga kaganapan, ngunit karamihan lamang ay makinig para sa mga push na mga kaganapan at pagkatapos ay gawin ang isang bagay sa datos na iyon. Kung mayroong isang sistema na iyong ginagamit na nais mong isama sa GitHub, dapat mong suriin dito upang makita kung mayroong umiiral na magagamit na pagsasama ng serbisyo. Halimbawa, kung gumagamit ka ng Jenkins upang magpatakbo ng mga pagsusuri sa iyong codebase, maaari mong paganahin ang pagsasama ng Jenkins builtin na serbisyo upang mag-umpisa ng isang patakbuhing pagsusuri sa tuwing may isang taong nag-push sa iyong repositoryo. Mga Hook Kung kailangan mo ng isang bagay na mas tiyak o nais mong isama sa isang serbisyo o site na hindi nabibilang sa listahang ito, maaari mong gamitin sa halip ang mas panlahat na sistema ng mga hook. Ang mga hook sa repositoryo ng GitHub ay simple lamang. Magtukoy ka ng isang URL at ipapaskil ng GitHub ang isang payload na HTTP sa URL na iyon sa anumang kaganapan na nais mo. Sa pangkalahatan, ang paraan ng paggana nito ay maaari mong i-setup ang isang maliit na serbisyo sa web upang makinig para sa isang payload sa hook ng GitHub at pagkatapos ay gawin ang isang bagay sa datos kapag ito ay natanggap. Upang magpagana ng isang hook, i-click ang pindutan na “Magdagdag ng webhook” sa Seksyon ng pagsasaayos sa mga Serbisyo at mga Hook. . Ito ay magdadala sa iyo sa isang pahina na katulad ng Pagsasaayos sa hook ng web. . Figure 132. Pagsasaayos sa hook ng web. Ang pagsasaayos para sa isang hook ng web ay simple lamang. Karamihan sa mga kaso, ipasok mo lamang ang isang URL at isang sekretong key at pindutin ang “Magdagdag ng webhook”. May ilang mga opsyon para sa kung aling mga kaganapan ang gusto mong saan ipadala sa iyo ng GitHub ang isang kargamento - ang default ay upang makakuha lamang ng isang kargamento para sa push na kaganapan, kapag ang isang tao ay nag-push ng bagong code sa anumang branch ng iyong repositoryo. Tingnan natin ang isang maliit na halimbawa ng isang serbisyo sa web na maaari mong i-set up upang mahawakan ang isang hook ng web. Gagamitin natin ang balangkas na Sinatra ng web na Ruby dahil ito ay medyo maigsi at dapat mong madaling makita kung ano ang ginagawa natin. Sabihin nating nais nating makakuha ng isang email kung ang isang partikular na tao ay nag-push sa isang partikular na branch ng ating proyekto na nagbabago sa isang partikular na file. Maaari nating madaling gawin ito na may code tulad nito: require 'sinatra' require 'json' require 'mail' post '/payload' do push = JSON.parse(request.body.read) # i-parse ang JSON # tipunin ang datos na ating hinahanap pusher = push["pusher"]["name"] branch = push["ref"] # kumuha ng isang listahan ng lahat ng mga file na hinawakan files = push["commits"].map do |commit| commit['added'] + commit['modified'] + commit['removed'] end files = files.flatten.uniq # suriin para sa ating pamantayan 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 Dito, kinukuha natin ang kargamento ng JSON na inilulunsad ng GitHub sa atin at hinahanap kung sino ang nag-push nito, kung anong branch sila nag-push at kung anu-ano ang mga file sa lahat ng mga gawaing na-push. Pagkatapos ay sinusuri natin laban sa pamantayan at nagpadala ng isang email kung ito ay tumutugma. Upang bumuo at suriin ang isang bagay tulad nito, mayroon kang isang magaling na developer console sa parehong screen kung saan mo isi-net up ang hook. Maaari mong makita ang huling mga paghahatid na sinubukan ng GitHub upang gawin para sa webhook na iyon. Sa bawat hook maaari kang maghukay pababa kapag ito ay naihatid, kung ito ay matagumpay at ang nilalaman at mga header para sa parehong kahilingan at tugon. Ginagawa nito maging hindi kapani-paniwalang madali na suriin at i-debug ang iyong mga hook. Figure 133. Impormasyon sa pag-debug ng Web hook. Ang iba pang mahusay na tampok nito ay na maaari mong maibalik ang anumang mga kargamento upang madaling masubukan ang iyong serbisyo. Para sa karagdagang impormasyon kung paano magsulat ng mga webhook at lahat ng iba’t-ibang mga uri ng kaganapan na maaari mong pakinggan, pumunta sa dokumentasyon ng GitHub Developer sa https://developer.github.com/webhooks/ Ang API ng GitHub Ang mga serbisyo at mga hook ay nagbibigay sa iyo ng isang paraan upang makatanggap ng mga abiso na push tungkol sa mga kaganapan na nangyayari sa iyong mga repositoryo, ngunit paano kung kailangan mo ng karagdagang impormasyon tungkol sa mga kaganapang ito? Paano kung kailangan mong gawing awtomatiko ang isang bagay tulad ng pagdaragdag ng mga tagatulong o mga isyu sa pag-label? Ito ay kung saan ang API ng GitHub ay madaling gamitin. Ang GitHub ay may toneladang mga endpoint ng API para sa paggawa ng halos anumang bagay na maaari mong gawin sa website sa isang awtomatiko na paraan. Sa seksyong ito, matututo tayo kung paano magpatunay at kumonekta sa API, paano magkomento sa isang isyu at paano baguhin ang katayuan ng isang Kahilingan na Pull sa pamamagitan ng API. Pangunahing Paggamit Ang pinaka-pangunahing bagay na maaari mong gawin ay isang simpleng kahilingan na GET sa isang endpoint na hindi nangangailangan ng pagpapatunay. Ito ay maaaring isang gumagamit o impormasyon sa pagbasa lamang sa isang proyekto na open source. Halimbawa, kung gusto nating malaman ang higit pa tungkol sa isang gumagamit na pinangalanang “schacon”, maaari nating patakbuhin ang isang bagay tulad nito: $ 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" } Mayroong toneladang mga endpoint tulad nito upang kumuha ng impormasyon tungkol sa mga organisasyon, mga proyekto, mga isyu, mga commit — halos anumang bagay na maaari mong makita nang publiko sa GitHub. Maaari mo ring gamitin ang API upang magbigay ng arbitraryo na Markdown o makahanap ng template na .gitignore . $ curl https://api.github.com/gitignore/templates/Java { "name": "Java", "source": "*.class # Kasangkapan sa Mobile para sa Java (J2ME) .mtj.tmp/ # Mga File ng Package # *.jar *.war *.ear # mga log ng pag-crash ng virtual machine, tingnan sa http://www.java.com/en/download/help/error_hotspot.xml hs_err_pid* " } Pagkokomento sa isang Isyu Gayunpaman, kung nais mong gumawa ng isang aksyon sa website tulad ng komento sa isang Isyu o Kahilingan na Pull o kung nais mong tingnan o makipag-ugnayan sa pribadong nilalaman, kakailanganin mong magpatunay. Mayroong maraming mga paraan upang magpatunay. Maaari mong gamitin ang pangunahing pagpapatunay gamit lamang ang iyong username at password, ngunit sa pangkalahatan mas magaling na ideya na gumamit ng isang access token na personal. Maaari mong mabuo ito mula sa tab na “Mga Aplikasyon” sa pahina ng iyong mga setting. Figure 134. Buuin ang iyong access token mula sa tab na “Mga Aplikasyon” sa pahina ng iyong settings. Magtatanong ito sa iyo kung anong mga saklaw ang gusto mo para sa token na ito at isang paglalarawan. Siguraduhin na gumamit ng isang mahusay na paglalarawan upang komportable ka sa pagtatanggal ng token kapag ang iyong iskrip o aplikasyon ay hindi na nagamit. Ipapakita lamang sa iyo ng GitHub ang token ng isang beses, kaya siguraduhin na kopyahin ito. Maaari mo na ngayong gamitin ito sa pagpapatunay ng iyong iskrip sa halip na gagamit ng isang username at password. Ito ay maganda dahil maaari mong limitahan ang saklaw kung ano ang gusto mong gawin at ang token ay mababawi. Ito rin ay may dagdag na kalamangan ng pagtaas ng iyong limitasyon sa rate. Kung walang pagpapatunay, limitado ka sa 60 na kahilingan sa bawat oras. Kung nagpapatunay ka, maaari kang gumawa ng hanggang 5,0000 na mga kahilingan sa bawat oras. Kaya gamitin natin ito upang gumawa ng isang komento sa isa sa ating mga isyu. Sabihin natin na nais nating mag-iwan ng isang komento sa isang partikular na isyu, Isyu #6. Para gawin ito kailangan nating gumawa ng isang kahilingan na HTTP POST sa repos/<user>/<repo>/issues/<num>/comments gamit ang token na binuo natin bilang isang header ng Pagpapatunay. $ 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:" } Ngayon kung pupunta ka sa isyung iyon, makikita mo ang komento na matagumpay nating naipaskil tulad sa Isang komentong naipaskil mula sa API ng GitHub. . Figure 135. Isang komentong naipaskil mula sa API ng GitHub. Maaari mong gamitin ang API upang gawin ang tungkol sa anumang bagay na maaari mong gawin sa website — paglilikha at pagtatakda ng mga milyahe, pagtatalaga ng mga tao sa mga Isyu at mga Kahilingan na Pull, paglilikha at pagbabago ng mga label, pag-access sa datos ng commit, paglilikha ng mga bagong commit at mga branch, pagbubukas, pagsasara o pagsasama ng mga Kahilingan na Pull, paglilikha at pag-edit ng mga koponan, pagkokomento sa mga linya ng code sa isang Kahilingan na Pull, paghahanap sa site at iba pa. Pagbabago sa Katayuan ng isang Kahilingan na Pull May isang pangwakas na halimbawang titingnan natin dahil talagang kapaki-pakinabang ito kung nagtatrabaho ka sa mga Kahilingan na Pull. Bawat commit ay maaaring magkaroon ng isa o higit pang mga katayuan na nauugnay dito at may isang API na idagdag at i-query ang katayuan nito. Karamihan sa Patuloy na Integrasyon at mga serbisyo ng pagsusuri ay gumagamit ng API na ito upang tumugon sa mga push sa pamamagitan ng pagsusuri sa code na na-push na, at pagkatapos mag-ulat pabalik kung ang commit na iyon ay nakapasa sa lahat ng mga pagsusuri. Maaari mo ring gamitin ito upang suriin kung ang mensahe ng commit ay maayos na nai-format, kung ang nagsumite ay sumunod sa lahat ng mga patnubay, kung ang commit ay balidong na-sign — anumang bilang ng mga bagay. Sabihin nating ikaw ay nag-set up ng isang webhook sa iyong repositoryo na tumatama sa isang maliit na serbisyo ng web na nagsusuri para sa isang string na Signed-off-by sa mensahe ng commit. require 'httparty' require 'sinatra' require 'json' post '/payload' do push = JSON.parse(request.body.read) # i-parse ang JSON repo_name = push['repository']['full_name'] # tingnan ang bawat mensahe ng commit push["commits"].each do |commit| # maghanap ng isang string na Signed-off-by if /Signed-off-by/.match commit['message'] state = 'tagumpay' description = 'Matagumpay na na-sign off!' else state = 'kabiguan' description = 'Walang natagpuan na signoff.' end # magpaskil ng katayuan sa GitHub sha = commit["id"] status_url = "https://api.github.com/repos/#{repo_name}/statuses/#{sha}" status = { "katayuan" => state, "paglalarawan" => description, "target_url" => "http://example.com/how-to-signoff", "konteksto" => "validate/signoff" } HTTParty.post(status_url, :body => status.to_json, :headers => { 'Content-Type' => 'application/json', 'User-Agent' => 'tonychacon/signoff', 'Pagpapatunay' => "token #{ENV['TOKEN']}" } ) end end Sana ito ay medyo simple na sundin. Sa humahawak ng web hook na ito, tinitingnan natin ang bawat commit na na-push lamang, hinahanap natin ang string na Signed-off-by sa mensahe ng commit at sa wakas tayo ay nag-POST sa pamamagitan ng HTTP sa endpoint ng API na /repos/<user>/<repo>/statuses/<commit_sha>` na may katayuan. Sa kasong ito, maaari kang magpadala ng isang katayuan ( tagumpay , kabiguan , kamalian ), isang paglalarawan sa kung ano ang nangyari, isang target URL na maaari puntahan ng gumagamit para sa karagdagang impormasyon at isang “konteksto” sa kaso na mayroong maramihang katayuan para sa isang solong commit. Halimbawa, isang serbisyo ng pagsusuri ay maaaring magpahintulot ng isang katayuan at isang serbisyo ng pagpapatunay tulad ng sa ito ay maaaring magpahintulot ng isang katayuan — ang patlang ng “konteksto” ay paano sila naiiba. Kung may nagbubukas ng isang bagong Kahilingan na Pull sa GitHub at ang hook na ito ay na-set up, maaari mong makita ang isang bagay tulad ng Katayuan ng Commit sa pamamagitan ng API. . Figure 136. Katayuan ng Commit sa pamamagitan ng API. Maaari mo na ngayong makita ang isang maliit na berdeng marka ng tsek sa tabi ng commit na may “igned-off-by” na string sa mensahe at isang pulang krus sa pamamagitan ng isa kung saan ang may-akda ay nakalimutan na mag-sign off. Maaari mo ring makita na ang Kahilingan na Pull ay kumukuha sa katayuan ng huling commit sa branch at binabalaan ka kung ito ay isang kabiguan. Ito ay talagang kapaki-pakinabang kung gumagamit ka ng API na ito para sa mga resulta ng pagsusuri upang hindi mo sinasadyang pagsamahin ang isang bagay kung saan ang huling paggawa ay hindi nakakapagpapatunay ng mga pagsusuri. Octokit Kahit na ginagawa natin ang halos lahat ng bagay sa pamamagitan ng curl at simpleng mga kahilingan sa HTTP sa mga halimbawang ito, maraming mga open-source library na umiiral na ginagawang magagamit ang API na ito sa mas pansalitain na paraan. Sa panahon ng pagsulat na ito, ang suportadong mga language ay kinabibilangan ng Go, Objective-C, Ruby, at .NET. Tingnan mo sa http://github.com/octokit para sa karagdagang impormasyon sa mga ito, habang pinangangasiwaan nila ang marami sa HTTP para sa iyo. Sana ang mga kasangkapan na ito ay maaaring makatulong sa iyo na ipasadya at baguhin ang GitHub upang gumana nang mas mahusay para sa iyong partikular na mga workflow. Para sa kumpletong dokumentasyon sa buong API pati na rin ang mga gabay para sa mga karaniwang gawain, tingnan ang 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:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#discover-by-keywords-2 | Pinterest API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Pinterest API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Discover by Keywords Posts API Collect by URL Discover by Profile URL Discover by Keywords Social Media APIs Pinterest API Scrapers Copy page Copy page Overview The Pinterest API Suite offers multiple types of APIs, each designed for specific data collection needs from Pinterest. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Discover by Keywords. Interesting Columns : name , following_count , website , follower_count . Posts API This API allows users to collect multiple posts based on a single input. Discovery functionality : - Discover by profile URL. - Discover by Keywords. Interesting Columns : title , content , user_name , likes . Profiles API Collect by URL This API allows users to retrieve detailed Pinterest profile information using the provided profile URL. Input Parameters : URL string required The Pinterest profile URL. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metrics : following_count , follower_count , boards_num , saved . Additional Information : last_updated , posts_page_url , discovery_input . This API allows users to collect detailed insights into a Pinterest profile, including user statistics, engagement metrics, and profile information. Discover by Keywords This API allows users to discover Pinterest profiles based on a specified keyword. Input Parameters : keyword string required The keyword to search for profiles. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metric s: following_count , follower_count , boards_num , saved. Additional Information : last_updated , posts_page_url , discovery_input . This API enables users to find Pinterest profiles related to a specific keyword, offering insights into user statistics, engagement, and profile details. Posts API Collect by URL This API allows users to collect detailed post data from a specific Pinterest post using the provided post URL. Input Parameters : URL string required The Pinterest post URL. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , post_type . For all data points, click here . User Details : user_name , user_url , user_id , followers . Post Metrics : likes , comments_num , comments , categories . Media & Attachments : image_video_url , video_length , attached_files . Hashtags & Discovery : hashtags , discovery_input . This API allows users to retrieve detailed insights into a specific Pinterest post, including user engagement, post content, media, and other related information. Discover by Profile URL This API allows users to retrieve posts from a specific Pinterest profile based on the provided profile URL. Input Parameters : URL string required The Pinterest profile URL from which to collect posts. num_of_posts number The number of posts to collect. If omitted, there is no limit. posts_to_not_include array An array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date ). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date ). Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users tso collect posts from a specific Pinterest profile, allowing for filtering by date, exclusion of specific posts, and retrieval of detailed post data including media, comments, and engagement metrics. Discover by Keywords This API allows users to discover Pinterest posts based on a specific keyword, enabling efficient content discovery. Input Parameters : keyword string required The keyword to search for posts, such as “food” or any other relevant term. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users to search for Pinterest posts based on a specific keyword, providing detailed insights into the content, engagement, media, and associated metrics for efficient discovery. Was this page helpful? Yes No Twitter Quora ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://git-scm.com/book/cs/v2/GitHub-Z%c5%99%c3%adzen%c3%ad-%c3%ba%c4%8dtu-a-%c3%baprava-konfigurace | Git - Zřízení účtu a úprava konfigurace 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. Úvod 1.1 Správa verzí 1.2 Stručná historie systému Git 1.3 Základy systému Git 1.4 Příkazový řádek 1.5 Instalace systému Git 1.6 První nastavení systému Git 1.7 Získání nápovědy 1.8 Shrnutí 2. Základy práce se systémem Git 2.1 Získání repozitáře Git 2.2 Nahrávání změn do repozitáře 2.3 Zobrazení historie revizí 2.4 Návrat do předchozího stavu 2.5 Práce se vzdálenými repozitáři 2.6 Používání značek 2.7 Aliasy v Gitu 2.8 Shrnutí 3. Větve v systému Git 3.1 Větve v kostce 3.2 Základy větvení a slučování 3.3 Správa větví 3.4 Postupy při práci s větvemi 3.5 Vzdálené větve 3.6 Přeskládání 3.7 Shrnutí 4. Git na serveru 4.1 Protokoly 4.2 Zprovoznění Gitu na serveru 4.3 Generování veřejného klíče SSH 4.4 Nastavení serveru 4.5 Démon Git 4.6 Chytrý HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti hostování u třetí strany 4.10 Shrnutí 5. Distribuovaný Git 5.1 Distribuované pracovní postupy 5.2 Přispívání do projektu 5.3 Správa projektu 5.4 Shrnutí 6. GitHub 6.1 Zřízení účtu a úprava konfigurace 6.2 Přispívání do projektu 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Shrnutí 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 Ladění v systému Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Shrnutí 8. Customizing Git 8.1 Git Configuration 8.2 Atributy Git 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Shrnutí 9. Git a ostatní systémy 9.1 Git as a Client 9.2 Migrating to Git 9.3 Shrnutí 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Balíčkové soubory 10.5 The Refspec 10.6 Přenosové protokoly 10.7 Správa a obnova dat 10.8 Environment Variables 10.9 Shrnutí 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 Shrnutí 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 6.1 GitHub - Zřízení účtu a úprava konfigurace GitHub je největší hostingový server pro gitové repozitáře. Je centrem pro spolupráci miliónů vývojářů a úložištěm jejich projektů. Značné procento všech gitových repozitářů je hostováno právě na GitHubu a mnoho open-source projektů ho využívá pro Git hosting, pro diskuse o problémech (issue tracking), pro recenzování kódu a pro další věci. Takže i když není přímou součástí open-source projektu (zvaného) Git, je velmi pravděpodobné, že při profesionálním používání Gitu budete chtít nebo potřebovat s GitHubem pracovat. Tato kapitola je zaměřena na efektivní používání GitHubu. Popíšeme si zřízení a správu účtu, vytvoření a používání gitových repozitářů, běžné pracovní postupy při přispívání do (jiných) projektů a přijímání příspěvku do vlastních projektů, programátorské rozhraní GitHubu a řadu drobných tipů, které vám mohou usnadnit život. Pokud vás nezajímá používání GitHubu pro hostování vlastních projektů nebo pro spolupráci na jiných projektech hostovaných na GitHubu, přeskočte na kapitolu Git Tools . Zřízení účtu a úprava konfigurace The first thing you need to do is set up a free user account. Simply visit https://github.com , choose a user name that isn’t already taken, provide an email address and a password, and click the big green “Sign up for GitHub” button. Figure 82. The GitHub sign-up form. The next thing you’ll see is the pricing page for upgraded plans, but it’s safe to ignore this for now. GitHub will send you an email to verify the address you provided. Go ahead and do this, it’s pretty important (as we’ll see later). Note GitHub provides all of its functionality with free accounts, with the limitation that all of your projects are fully public (everyone has read access). GitHub’s paid plans include a set number of private projects, but we won’t be covering those in this book. Clicking the Octocat logo at the top-left of the screen will take you to your dashboard page. You’re now ready to use GitHub. SSH Access As of right now, you’re fully able to connect with Git repositories using the https:// protocol, authenticating with the username and password you just set up. However, to simply clone public projects, you don’t even need to sign up - the account we just created comes into play when we fork projects and push to our forks a bit later. If you’d like to use SSH remotes, you’ll need to configure a public key. (If you don’t already have one, see Generování veřejného klíče SSH .) Open up your account settings using the link at the top-right of the window: Figure 83. The “Account settings” link. Then select the “SSH keys” section along the left-hand side. Figure 84. The “SSH keys” link. From there, click the " Add an SSH key " button, give your key a name, paste the contents of your ~/.ssh/id_rsa.pub (or whatever you named it) public-key file into the text area, and click “Add key”. Note Be sure to name your SSH key something you can remember. You can name each of your keys (e.g. "My Laptop" or "Work Account") so that if you need to revoke a key later, you can easily tell which one you’re looking for. Your Avatar Next, if you wish, you can replace the avatar that is generated for you with an image of your choosing. First go to the “Profile” tab (above the SSH Keys tab) and click “Upload new picture”. Figure 85. The “Profile” link. We’ll choose a copy of the Git logo that is on our hard drive and then we get a chance to crop it. Figure 86. Crop your avatar Now anywhere you interact on the site, people will see your avatar next to your username. If you happen to have uploaded an avatar to the popular Gravatar service (often used for Wordpress accounts), that avatar will be used by default and you don’t need to do this step. Your Email Addresses The way that GitHub maps your Git commits to your user is by email address. If you use multiple email addresses in your commits and you want GitHub to link them up properly, you need to add all the email addresses you have used to the Emails section of the admin section. Figure 87. Add email addresses In Add email addresses we can see some of the different states that are possible. The top address is verified and set as the primary address, meaning that is where you’ll get any notifications and receipts. The second address is verified and so can be set as the primary if you wish to switch them. The final address is unverified, meaning that you can’t make it your primary address. If GitHub sees any of these in commit messages in any repository on the site, it will be linked to your user now. Two Factor Authentication Finally, for extra security, you should definitely set up Two-factor Authentication or “2FA”. Two-factor Authentication is an authentication mechanism that is becoming more and more popular recently to mitigate the risk of your account being compromised if your password is stolen somehow. Turning it on will make GitHub ask you for two different methods of authentication, so that if one of them is compromised, an attacker will not be able to access your account. You can find the Two-factor Authentication setup under the Security tab of your Account settings. Figure 88. 2FA in the Security Tab If you click on the “Set up two-factor authentication” button, it will take you to a configuration page where you can choose to use a phone app to generate your secondary code (a “time based one-time password”), or you can have GitHub send you a code via SMS each time you need to log in. After you choose which method you prefer and follow the instructions for setting up 2FA, your account will then be a little more secure and you will have to provide a code in addition to your password whenever you log into GitHub. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#param-num-of-posts | Instagram API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Instagram API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Posts API Collect by URL Discover by URL Comments API Collect by URL Reels API Collect by URL Discover by URL Social Media APIs Instagram API Scrapers Copy page Copy page Overview The Instagram API Suite offers multiple types of APIs, each designed for specific data collection needs from Instagram. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : N/A Interesting Columns : followers , post_count , post_hashtags , profile_name . Posts API This API allows users to collect multiple posts based on a single input URL (such as an Instagram reels URL, search URL or profile URL). Discovery functionality : - Direct URL of the Instagram reel - Direct URL of the search - Direct URL of the profile Interesting Columns : url , followers , hashtags , engagement_score_view . Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : comment_user , comment , likes_number , replies_number . The suite of APIs is designed to offer flexibility for targeted data collection, where users can input specific URLs to gather detailed post and comment data, either in bulk or with precise filtering options. Profiles API Collect by URL This API allows users to collect detailed data about an Instagram profile by providing the profile URL. It provides a comprehensive overview of an Instagram profile, including business and engagement information, posts, and user details. Input Parameters URL string required The Instagram profile URL. Output Structure Includes comprehensive data points: Page/Profile Details : account , id , followers , posts_count , is_business_account , is_professional_account , is_verified , avg_engagement , profile_name , profile_url , profile_image_link , and more. For all data points, click here . Posts API Collect by URL This API enables users to collect detailed data from Instagram posts by providing a post URL. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Post Details : post_id , description , hashtags , date_posted , num_comments , likes , content_type , video_view_count , video_play_count , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : photos , videos , thumbnail , display_url (link only, not the file itself), audio. Discover by URL This API allows users to discover recent Instagram posts from a public profile by providing the profile URL and specifying additional parameters. Input Parameters URL string required The Instagram profile URL. num_of_posts number The number of recent posts to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date). post_type string Specify the type of posts to collect (e.g., post, reel). Output Structure Includes comprehensive data points: Post Details: post_id , description , hashtags , date_posted , num_comments , likes , video_view_count , video_play_count ,and more. For all data points, click here . Page/Profile Details: user_posted , followers , posts_count , profile_image_link , is_verified , profile_url , is_paid_partnership , partnership_details , user_posted_id Attachments and Media: photos , videos , thumbnail , audio , display_url , content_type , product_type , coauthor_producers , tagged_users . This API is designed to allow for filtering, exclusion of specific posts, and collecting posts by type (regular post or reel) within a defined time frame. It provides detailed post and profile information, making it ideal for data collection and analytics. Comments API Collect by URL This API allows users to collect the latest comments from a specific Instagram post by providing the post URL. This API retrieves the most recent 10 comments along with associated metadata. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Comment Details : comment_id , comment_user , comment_user_url , comment_date , comment , likes_number , replies_number , replies , hashtag_comment , tagged_users_in_comment , and more. For all data points, click here . User Details : user_name , user_id , user_url We provide a limited set of data points about the profile. Post Metadata : post_url , post_user , post_id . Reels API Collect by URL This API allows users to collect detailed data about Instagram reels from public profiles by providing the reel URL. Input Parameters URL string required The Instagram reel URL. Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , tagged_users , num_comments , likes , views , video_play_count , length , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : video_url , thumbnail , audio_url . Discover by URL This API allows users to discover Instagram Reels videos from a profile URL or direct search URL. Input Parameters URL string required The Instagram profile or direct search URL. num_of_posts number The number of recent reels to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering reels in MM-DD-YYYY format. end_date string End date for filtering reels in MM-DD-YYYY format (should be later than start_date ). Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , num_comments , likes , views , video_play_count , top_comments , length , video_url , audio_url , content_id , and more. For all data points, click here . Profile Details : user_posted , followers , posts_count , following . Attachments and Media : video_url , thumbnail , audio_url (link only, not the file itself). This API provides detailed information about Instagram Reels, with filtering options by date range, exclusion of specific posts, and a limit on the number of reels collected. Was this page helpful? Yes No Facebook LinkedIn ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://git-scm.com/book/pt-br/v2/Fundamentos-de-Git-Apelidos-Git | Git - Apelidos 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. 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 2.7 Fundamentos de Git - Apelidos Git Apelidos Git Antes de finalizarmos o capítulo básico sobre o Git, temos apenas uma pequena dica que pode tornar sua experiência com o Git mais simples, fácil e familiar: apelidos(aliases). Não iremos nos referir a eles ou assumir que você já os tenha usado mais adiante neste livro, porém você provavelmente deve saber como usá-los. Git não infere automaticamente seu comando se você digitá-lo parcialmente. Se você não quiser digitar o texto inteiro de cada comando, você pode facilmente configurar um apelido para cada comando usando git config . Aqui estão alguns exemplos que talvez você queira configurar: $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status Isto significa que, por exemplo, ao invés de digitar git commit , você só precisa digitar git ci . A medida que você for usando o Git, provavelmente usará outros comandos com frequência também. Então, não hesite em criar novos apelidos. Esta técnica também pode ser muito útil na criação de comandos que você acredita que deveriam existir. Por exemplo, para corrigir o problema de usabilidade que você encontrou em um arquivo unstaging , você pode adicionar seu próprio apelido unstage ao Git: $ git config --global alias.unstage 'reset HEAD --' Isto faz dos dois comandos a seguir equivalentes $ git unstage fileA $ git reset HEAD -- fileA Este parece um pouco mais claro. Também é comum adicionar ao comando last algo como: $ git config --global alias.last 'log -1 HEAD' Deste jeito, você pode ver o último commit mais facilmente: $ git last commit 66938dae3329c7aebe598c2246a8e6af90d04646 Author: Josh Goebel <dreamer3@example.com> Date: Tue Aug 26 19:48:51 2008 +0800 test for current head Signed-off-by: Scott Chacon <schacon@example.com> Como você pode ver, o Git simplesmente substitui o novo comando por qualquer apelido que você escolher. Entretanto, talvez você queira executar um comando externo em vez de um subcomando Git. Nesse caso, você inicia o comando com um caracter de exclamação ( ! ). Isto é muito útil se você escreve suas próprias tools que trabalham com um repositório Git. Podemos demonstrar isso apelidando git visual com gitk : $ git config --global alias.visual '!gitk' prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#content-area | Pinterest API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Pinterest API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Discover by Keywords Posts API Collect by URL Discover by Profile URL Discover by Keywords Social Media APIs Pinterest API Scrapers Copy page Copy page Overview The Pinterest API Suite offers multiple types of APIs, each designed for specific data collection needs from Pinterest. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Discover by Keywords. Interesting Columns : name , following_count , website , follower_count . Posts API This API allows users to collect multiple posts based on a single input. Discovery functionality : - Discover by profile URL. - Discover by Keywords. Interesting Columns : title , content , user_name , likes . Profiles API Collect by URL This API allows users to retrieve detailed Pinterest profile information using the provided profile URL. Input Parameters : URL string required The Pinterest profile URL. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metrics : following_count , follower_count , boards_num , saved . Additional Information : last_updated , posts_page_url , discovery_input . This API allows users to collect detailed insights into a Pinterest profile, including user statistics, engagement metrics, and profile information. Discover by Keywords This API allows users to discover Pinterest profiles based on a specified keyword. Input Parameters : keyword string required The keyword to search for profiles. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metric s: following_count , follower_count , boards_num , saved. Additional Information : last_updated , posts_page_url , discovery_input . This API enables users to find Pinterest profiles related to a specific keyword, offering insights into user statistics, engagement, and profile details. Posts API Collect by URL This API allows users to collect detailed post data from a specific Pinterest post using the provided post URL. Input Parameters : URL string required The Pinterest post URL. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , post_type . For all data points, click here . User Details : user_name , user_url , user_id , followers . Post Metrics : likes , comments_num , comments , categories . Media & Attachments : image_video_url , video_length , attached_files . Hashtags & Discovery : hashtags , discovery_input . This API allows users to retrieve detailed insights into a specific Pinterest post, including user engagement, post content, media, and other related information. Discover by Profile URL This API allows users to retrieve posts from a specific Pinterest profile based on the provided profile URL. Input Parameters : URL string required The Pinterest profile URL from which to collect posts. num_of_posts number The number of posts to collect. If omitted, there is no limit. posts_to_not_include array An array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date ). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date ). Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users tso collect posts from a specific Pinterest profile, allowing for filtering by date, exclusion of specific posts, and retrieval of detailed post data including media, comments, and engagement metrics. Discover by Keywords This API allows users to discover Pinterest posts based on a specific keyword, enabling efficient content discovery. Input Parameters : keyword string required The keyword to search for posts, such as “food” or any other relevant term. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users to search for Pinterest posts based on a specific keyword, providing detailed insights into the content, engagement, media, and associated metrics for efficient discovery. Was this page helpful? Yes No Twitter Quora ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://git-scm.com/book/id/v2/Git-di-Server-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. 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.8 Git di Server - GitLab GitLab GitWeb is pretty simplistic though. If you’re looking for a more modern, fully featured Git server, there are some several open source solutions out there that you can install instead. As GitLab is one of the more popular ones, we’ll cover installing and using it as an example. This is a bit more complex than the GitWeb option and likely requires more maintainance, but it is a much more fully featured option. Installation GitLab is a database-backed web application, so its installation is a bit more involved than some other git servers. Fortunately, this process is very well-documented and supported. There are a few methods you can pursue to install GitLab. To get something up and running quickly, you can download a virtual machine image or a one-click installer from https://bitnami.com/stack/gitlab , and tweak the configuration to match your particular environment. One nice touch Bitnami has included is the login screen (accessed by typing alt-→); it tells you the IP address and default username and password for the installed GitLab. Figure 50. The Bitnami GitLab virtual machine login screen. For anything else, follow the guidance in the GitLab Community Edition readme, which can be found at https://gitlab.com/gitlab-org/gitlab-ce/tree/master . There you’ll find assistance for installing GitLab using Chef recipes, a virtual machine on Digital Ocean, and RPM and DEB packages (which, as of this writing, are in beta). There’s also “unofficial” guidance on getting GitLab running with non-standard operating systems and databases, a fully-manual installation script, and many other topics. Administration GitLab’s administration interface is accessed over the web. Simply point your browser to the hostname or IP address where GitLab is installed, and log in as an admin user. The default username is admin@local.host , and the default password is 5iveL!fe (which you will be prompted to change as soon as you enter it). Once logged in, click the “Admin area” icon in the menu at the top right. Figure 51. The “Admin area” item in the GitLab menu. Users Users in GitLab are accounts that correspond to people. User accounts don’t have a lot of complexity; mainly it’s a collection of personal information attached to login data. Each user account comes with a namespace , which is a logical grouping of projects that belong to that user. If the user jane had a project named project , that project’s url would be http://server/jane/project . Figure 52. The GitLab user administration screen. Removing a user can be done in two ways. “Blocking” a user prevents them from logging into the GitLab instance, but all of the data under that user’s namespace will be preserved, and commits signed with that user’s email address will still link back to their profile. “Destroying” a user, on the other hand, completely removes them from the database and filesystem. All projects and data in their namespace is removed, and any groups they own will also be removed. This is obviously a much more permanent and destructive action, and its uses are rare. Groups A GitLab group is an assemblage of projects, along with data about how users can access those projects. Each group has a project namespace (the same way that users do), so if the group training has a project materials , its url would be http://server/training/materials . Figure 53. The GitLab group administration screen. Each group is associated with a number of users, each of which has a level of permissions for the group’s projects and the group itself. These range from “Guest” (issues and chat only) to “Owner” (full control of the group, its members, and its projects). The types of permissions are too numerous to list here, but GitLab has a helpful link on the administration screen. Projects A GitLab project roughly corresponds to a single git repository. Every project belongs to a single namespace, either a user or a group. If the project belongs to a user, the owner of the project has direct control over who has access to the project; if the project belongs to a group, the group’s user-level permissions will also take effect. Every project also has a visibility level, which controls who has read access to that project’s pages and repository. If a project is Private , the project’s owner must explicitly grant access to specific users. An Internal project is visible to any logged-in user, and a Public project is visible to anyone. Note that this controls both git “fetch” access as well as access to the web UI for that project. Hooks GitLab includes support for hooks, both at a project or system level. For either of these, the GitLab server will perform an HTTP POST with some descriptive JSON whenever relevant events occur. This is a great way to connect your git repositories and GitLab instance to the rest of your development automation, such as CI servers, chat rooms, or deployment tools. Basic Usage The first thing you’ll want to do with GitLab is create a new project. This is accomplished by clicking the “+” icon on the toolbar. You’ll be asked for the project’s name, which namespace it should belong to, and what its visibility level should be. Most of what you specify here isn’t permanent, and can be re-adjusted later through the settings interface. Click “Create Project”, and you’re done. Once the project exists, you’ll probably want to connect it with a local Git repository. Each project is accessible over HTTPS or SSH, either of which can be used to configure a Git remote. The URLs are visible at the top of the project’s home page. For an existing local repository, this command will create a remote named gitlab to the hosted location: $ git remote add gitlab https://server/namespace/project.git If you don’t have a local copy of the repository, you can simply do this: $ git clone https://server/namespace/project.git The web UI provides access to several useful views of the repository itself. Each project’s home page shows recent activity, and links along the top will lead you to views of the project’s files and commit log. Working Together The simplest way of working together on a GitLab project is by giving another user direct push access to the git repository. You can add a user to a project by going to the “Members” section of that project’s settings, and associating the new user with an access level (the different access levels are discussed a bit in Groups ). By giving a user an access level of “Developer” or above, that user can push commits and branches directly to the repository with impunity. Another, more decoupled way of collaboration is by using merge requests. This feature enables any user that can see a project to contribute to it in a controlled way. Users with direct access can simply create a branch, push commits to it, and open a merge request from their branch back into master or any other branch. Users who don’t have push permissions for a repository can “fork” it (create their own copy), push commits to that copy, and open a merge request from their fork back to the main project. This model allows the owner to be in full control of what goes into the repository and when, while allowing contributions from untrusted users. Merge requests and issues are the main units of long-lived discussion in GitLab. Each merge request allows a line-by-line discussion of the proposed change (which supports a lightweight kind of code review), as well as a general overall discussion thread. Both can be assigned to users, or organized into milestones. This section has focused mainly on the Git-related parts of GitLab, but it’s a fairly mature system, and provides many other features that can help your team work together. These include project wikis, discussion “walls”, and system maintenance tools. One benefit to GitLab is that, once the server is set up and running, you’ll rarely need to tweak a configuration file or access the server via SSH; most administration and general usage can be accomplished through the in-browser interface. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://www.linkedin.com/uas/login?session_redirect=%2Fproducts%2Foutsystems%3FviewConnections%3Dtrue&trk=products_details_guest_face-pile-cta | 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:25 |
https://babelfish.money/wp-json/ | Babelfish – BabelFish BABELFISH Github Docs Forum Launch Dapp X sun (Traced) crescent-moon-phase-shape-with-two-stars (Traced)2022 BABELFISH Github Docs Analytics X LAUNCH DAPP UNIVERSAL MULTI-CHAIN STABLECOIN BabelFish's mind-boggling objective is to aggregate and distribute stablecoins, enhance flow, and push hyperBitcoinization. ABOUT BabelFish DAO Money Protocol is the simplest and most mind-bogglingly useful thing in the DeFi Universe. It absorbs, aggregates and distributes USD-pegged stablecoins across chains; the practical upshot of all this is that if you stick stablecoins to it, you can neatly cross the language divide between any chains. BabelFish's meta-stablecoin, XUSD, is backed by the underlying aggregated stablecoins to leverage and enhance their combined flow and utility across protocols and users. FISH holders can vote on improvement proposals, such as which stablecoins to accept, or what percent of collateral to lend. Learn More About It GO TO OUR GITBOOK What It Does What It Does: Since the big bang of DeFi in the crypto galaxy, many stablecoin projects have been created to meet the demand for USD. Different stablecoin brands with unique selling points are competing to represent the same dollar, but they do not translate 1:1, and crypto dollar liquidity is fractured between issuers and protocols. As DeFi markets expand beyond Ethereum to multiple chains, stablecoin liquidity is fractured further by the bridges used, which is suboptimal for the industry. BabelFish abstracts away these differences by aggregating stablecoins from multiple isolated liquidity lakes and providing users with access to the combined ocean of crypto-dollars available. Think of it as a translator or a converter: if a user wants to use crypto dollars on another chain, she can stick it on BabelFish and seamlessly get a par-value equivalent on the other side. What Is The FISH DAO The BabelFish DAO Money Protocol is ultimately directed by the will of FISH token holders participating in governance. From protocol improvement proposals to budget allocation and partnerships, it is the community that will be able to decide on the direction of the protocol. If you are passionate about the stablecoin ecosystem, this is the DAO for you. Help define protocol rules and parameters around the collateral accepted, discuss community incentives, manage risk, and much more. The future of BabelFish depends on active FISH holder participation. Help build, shape and enhance the stablecoin ecosystem. Participate in stablecoin collateral management. Be rewarded for staking and actively participating with FISH in governance. Mind-Bogglingly Useful XUSD is collateralized 1:1 by a hedged basket of accepted stablecoins across chains, which enables users and protocols to tap into the combined liquidity and utility of the underlying collateral and also enhances stablecoin flow across the ecosystem. User deposits an accepted stablecoin on BabelFish protocol. Protocol issues XUSD, its convertible stablecoin backed 1:1 User can use XUSD on accepted protocols, bridge between chains, and redeem back at any time What Moves BabelFish The need for a "trustless stablecoin translation device" seems painfully clear. The accelerated growth and velocity of crypto dollars is unstoppable, we expect demand for programmable money to continue accelerating as we onboard the first billion users. But the market remains fragmented, two players dominate >80% of the total USD-stablecoin float, and systemic and idiosyncratic risks abound. In the decentralised economy we ought not to rely on one or two issuers of USD-stablecoins but rather enable a thousand stablecoins to bloom and communicate with each other to bring mass adoption. For BabelFish DAO Money Protocol it is important that our first product, XUSD, is the safest, easiest and ultimate stablecoin instrument out there in crypto space. JOIN US TO EXPERIENCE BABELFISH | 2026-01-13T09:29:25 |
https://git-scm.com/book/gr/v2/%ce%a4%ce%b1-%ce%b8%ce%b5%ce%bc%ce%b5%ce%bb%ce%b9%cf%8e%ce%b4%ce%b7-%cf%83%cf%84%ce%bf%ce%b9%cf%87%ce%b5%ce%af%ce%b1-%cf%84%ce%bf%cf%85-Git-%ce%a3%cf%85%ce%bd%cf%84%ce%bf%ce%bc%ce%b5%cf%8d%ce%b5%cf%83%ce%b5%ce%b9%cf%82-%cf%83%cf%84%ce%bf-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 2.7 Τα θεμελιώδη στοιχεία του Git - Συντομεύεσεις στο Git Συντομεύεσεις στο Git Πριν προχωρήσουμε στο επόμενο κεφάλαιο, θέλουμε να εισάγουμε μια λειτουργικότητα που μπορεί να διευκολύνει και απλουστεύσει την εμπειρία μας με το Git: τα ψευδώνυμα. Δεν θα τα χρησιμοποιήσουμε πουθενά αλλού σε αυτό το βιβλίο, αλλά αν σκοπεύουμε να χρησιμοποιούμε το Git τακτικά, τα ψευδώνυμα είναι κάτι που πρέπει να γνωρίζουμε. Το Git δεν μπορεί να μαντέψει μια εντολή αν τη γράψουμε μόνο μερικώς. Αν δεν θέλουμε να πληκτρολογούμε όλα τα γράμματα των εντολών του Git, μπορούμε εύκολα να ορίσουμε ένα ψευδώνυμο για κάθε εντολή με την εντολή git config . Μερικά παραδείγματα για το πώς μπορούμε να ορίσουμε μερικά ψευδώνυμα: $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status Αυτό σημαίνει ότι μπορούμε, για παράδειγμα, να πληκτρολογήσουμε git ci αντί για git commit . Καθώς χρησιμοποιούμε το Git, θα δούμε ότι υπάρχουν και άλλες εντολές που χρησιμοποιούμε συχνά — μην διστάσουμε να δημιουργήσουμε νέα ψευδώνυμα. Η τεχνική αυτή μπορεί να φανεί χρήσιμη για να δημιουργήσουμε εντολές που πιστεύουμε ότι θα έπρεπε να υπήρχαν. Για παράδειγμα, αν θέλουμε να κάνουμε πιο εύχρηστη τη διαδικασία αφαίρεσης ενός αρχείου από τον προθάλαμο, μπορούμε να δημιουργήσουμε ένα ψευδώνυμο: $ git config --global alias.unstage 'reset HEAD --' Αυτό καθιστά τις δύο παρακάτω εντολές ισοδύναμες: $ git unstage fileA $ git reset HEAD -- fileA Η εντολή που εκτελούμε φαίνεται πλέον πιο καθαρά. Το ψευδώνυμο last είναι επίσης πολύ συνηθισμένο: $ git config --global alias.last 'log -1 HEAD' Με αυτό τον τρόπο μπορούμε να δούμε πιο εύκολα την τελευταία υποβολή: $ git last commit 66938dae3329c7aebe598c2246a8e6af90d04646 Author: Josh Goebel <dreamer3@example.com> Date: Tue Aug 26 19:48:51 2008 +0800 Test for current head Signed-off-by: Scott Chacon <schacon@example.com> Όπως μπορούμε να δούμε, το Git μπορεί να αντικαταστήσει μια εντολή με οποιοδήποτε ψευδώνυμο ορίσουμε. Μπορεί όμως αντί για μια εντολή του Git, να θέλουμε να εκτελέσουμε μια εξωτερική εντολή. Στην περίπτωση αυτή, θα πρέπει να ξεκινήσουμε την εντολή με τον χαρακτήρα ! . Αυτό θα μας φανεί χρήσιμο αν γράφουμε δικά μας εργαλεία που δουλεύουν με αποθετήρια Git. Για παράδειγμα, μπορούμε να χρησιμοποιήσουμε το ψευδώνυμο git visual για να εκτελέσουμε την εντολή gitk : $ git config --global alias.visual '!gitk' prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://www.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Frootstock.io | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 새 계정 만들기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:29:25 |
https://git-scm.com/book/de/v2/Git-Grundlagen-%c3%84nderungen-nachverfolgen-und-im-Repository-speichern | Git - Änderungen nachverfolgen und im Repository speichern 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.2 Git Grundlagen - Änderungen nachverfolgen und im Repository speichern Änderungen nachverfolgen und im Repository speichern An dieser Stelle solltest du ein angemessenes Git-Repository auf deinem lokalen Computer und eine Checkout- oder Arbeitskopie aller deiner Dateien vor dir haben. Normalerweise wirst du damit beginnen wollen, Änderungen vorzunehmen und Schnappschüsse dieser Änderungen in dein Repository zu committen, wenn das Projekt so weit fortgeschritten ist, dass du es sichern möchten. Denke daran, dass sich jede Datei in deinem Arbeitsverzeichnis in einem von zwei Zuständen befinden kann: tracked oder untracked – Änderungen an der Datei werden verfolgt (engl. tracked ) oder eben nicht (engl. untracked ). Tracked Dateien sind Dateien, die im letzten Snapshot enthalten sind. Genauso wie alle neuen Dateien in der Staging-Area. Sie können entweder unverändert, modifiziert oder für den nächsten Commit vorgemerkt (staged) sein. Kurz gesagt, nachverfolgte Dateien sind Dateien, die Git kennt. Alle anderen Dateien in deinem Arbeitsverzeichnis dagegen, sind nicht versioniert: Das sind all diejenigen Dateien, die nicht schon im letzten Schnappschuss enthalten waren und die sich nicht in der Staging-Area befinden. Wenn du ein Repository zum ersten Mal klonst, sind alle Dateien versioniert und unverändert. Nach dem Klonen wurden sie ja ausgecheckt und bis dahin hast du auch noch nichts an ihnen verändert. Sobald du anfängst versionierte Dateien zu bearbeiten, erkennt Git diese als modifiziert, weil sie sich im Vergleich zum letzten Commit verändert haben. Die geänderten Dateien kannst du dann für den nächsten Commit vormerken und schließlich alle Änderungen, die sich in der Staging-Area befinden, einchecken (engl. committen). Danach wiederholt sich dieser Vorgang. Abbildung 8. Der Status deiner Dateien im Überblick Zustand von Dateien prüfen Das wichtigste Hilfsmittel, um den Zustand zu überprüfen, in dem sich deine Dateien gerade befinden, ist der Befehl git status . Wenn du diesen Befehl unmittelbar nach dem Klonen eines Repositorys ausführen, sollte er in etwa folgende Ausgabe liefern: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working tree clean Dieser Zustand wird auch als sauberes Arbeitsverzeichnis (engl. clean working directory) bezeichnet. Mit anderen Worten, es gibt keine Dateien, die unter Versionsverwaltung stehen und seit dem letzten Commit geändert wurden – andernfalls würden sie hier aufgelistet werden. Außerdem teilt dir der Befehl mit, auf welchem Branch du gerade arbeitest und informiert dich darüber, dass dieser sich im Vergleich zum Branch auf dem Server nicht verändert hat. Momentan ist dieser Branch immer master , was der Vorgabe entspricht; Du musst dich jetzt nicht darum kümmern. Wir werden im Kapitel Git Branching detaillierter auf Branches eingehen. Anmerkung GitHub änderte Mitte 2020 den Standard-Branch-Namen von master in main , und andere Git-Hosts folgten diesem Beispiel. Daher wirst du möglicherweise feststellen, dass der Standard-Branch-Name in einigen neu erstellten Repositorys main und nicht master ist. Außerdem kann der Standard-Branch-Name geändert werden (wie du in Der standardmäßige Branch-Name gesehen hast), sodass du möglicherweise einen anderen Namen für den Standard-Branch vorfindest. Git selbst verwendet jedoch immer noch master als Standard, also werden wir es auch im gesamten Buch verwenden. Nehmen wir einmal an, du fügst eine neue Datei mit dem Namen README zu deinem Projekt hinzu. Wenn die Datei zuvor nicht existiert hat und du jetzt git status ausführst, zeigt Git die bisher nicht versionierte Datei wie folgt an: $ echo 'My Project' > README $ git status On branch master Your branch is up-to-date with 'origin/master'. Untracked files: (use "git add <file>..." to include in what will be committed) README nothing added to commit but untracked files present (use "git add" to track) Alle Dateien, die im Abschnitt „Untracked files“ aufgelistet werden, sind Dateien, die bisher noch nicht versioniert sind. Dort wird jetzt auch die Datei README angezeigt. Mit anderen Worten, die Datei README wird in diesem Bereich gelistet, weil sie im letzten Schnappschuss nicht enthalten war und noch nicht gestaged wurde. Git nimmt eine solche Datei nicht automatisch in die Versionsverwaltung auf. Du musst Git dazu ausdrücklich auffordern. Ansonsten würden generierte Binärdateien oder andere Dateien, die du nicht in deinem Repository haben möchtest, automatisch hinzugefügt werden. Das möchte man in den meisten Fällen vermeiden. Jetzt wollen wir aber Änderungen an der Datei README verfolgen und fügen sie deshalb zur Versionsverwaltung hinzu. Neue Dateien zur Versionsverwaltung hinzufügen Um eine neue Datei zu versionieren, kannst du den Befehl git add verwenden. Für deine neue README Datei, kannst du folgendes ausführen: $ git add README Wenn du erneut den Befehl git status ausführst, wirst du sehen, dass sich deine README Datei jetzt unter Versionsverwaltung befindet und für den nächsten Commit vorgemerkt ist: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git restore --staged <file>..." to unstage) new file: README Du kannst erkennen, dass die Datei für den nächsten Commit vorgemerkt ist, weil sie unter der Rubrik „Changes to be committed“ aufgelistet ist. Wenn du jetzt einen Commit anlegst, wird der Schnappschuss den Zustand der Datei festhalten, den sie zum Zeitpunkt des Befehls git add hat. Du erinnerst dich vielleicht daran, wie du vorhin git init und anschließend git add <files> ausgeführt hast. Mit diesen Befehlen hast du die Dateien in deinem Verzeichnis zur Versionsverwaltung hinzugefügt. Der Befehl git add akzeptiert einen Pfadnamen einer Datei oder eines Verzeichnisses. Wenn du ein Verzeichnis angibst, fügt git add alle Dateien in diesem Verzeichnis und allen Unterverzeichnissen rekursiv hinzu. Geänderte Dateien zur Staging-Area hinzufügen Lass uns jetzt eine bereits versionierte Datei ändern. Wenn du zum Beispiel eine bereits unter Versionsverwaltung stehende Datei mit dem Dateinamen CONTRIBUTING.md änderst und danach den Befehl git status erneut ausführst, erhältst du in etwa folgende Ausgabe: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Die Datei CONTRIBUTING.md erscheint im Abschnitt „Changes not staged for commit“. Das bedeutet, dass eine versionierte Datei im Arbeitsverzeichnis verändert worden ist, aber noch nicht für den Commit vorgemerkt wurde. Um sie vorzumerken, führst du den Befehl git add aus. Der Befehl git add wird zu vielen verschiedenen Zwecken eingesetzt. Man verwendet ihn, um neue Dateien zur Versionsverwaltung hinzuzufügen, Dateien für einen Commit vorzumerken und verschiedene andere Dinge – beispielsweise einen Konflikt aus einem Merge als aufgelöst zu kennzeichnen. Leider wird der Befehl git add oft missverstanden. Viele assoziieren damit, dass damit Dateien zum Projekt hinzugefügt werden. Wie du aber gerade gelernt hast, wird der Befehl auch noch für viele andere Dinge eingesetzt. Wenn du den Befehl git add einsetzt, solltest du das eher so sehen, dass du damit einen bestimmten Inhalt für den nächsten Commit vormerkst. Las uns nun mit git add die Datei CONTRIBUTING.md zur Staging-Area hinzufügen und danach das Ergebnis mit git status kontrollieren: $ git add CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Beide Dateien sind nun für den nächsten Commit vorgemerkt. Nehmen wir an, du willst jetzt aber noch eine weitere Änderung an der Datei CONTRIBUTING.md vornehmen, bevor du den Commit tatsächlich startest. Du öffnest die Datei erneut, änderst sie entsprechend ab und eigentlich wärst du jetzt bereit den Commit durchzuführen. Las uns vorher noch einmal den Befehl git status ausführen: $ vim CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Was zum Kuckuck …? Jetzt wird die Datei CONTRIBUTING.md sowohl in der Staging-Area als auch als geändert aufgelistet. Wie ist das möglich? Die Erklärung dafür ist, dass Git eine Datei in exakt dem Zustand für den Commit vormerkt, in dem sie sich befindet, wenn du den Befehl git add ausführst. Wenn du den Commit jetzt anlegst, wird die Version der Datei CONTRIBUTING.md denjenigen Inhalt haben, den sie hatte, als du git add zuletzt ausgeführt hast und nicht denjenigen, den sie in dem Moment hat, wenn du den Befehl git commit ausführst. Wenn du stattdessen die gegenwärtige Version im Commit haben möchten, müsst du erneut git add ausführen, um die Datei der Staging-Area hinzuzufügen: $ git add CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Kompakter Status Die Ausgabe von git status ist sehr umfassend und auch ziemlich wortreich. Git hat auch ein Kurzformat, mit dem du deine Änderungen kompakter sehen kannst. Wenn du git status -s oder git status --short ausführst, erhältst du eine kürzere Darstellung des Befehls: $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt Neue Dateien, die nicht versioniert werden, werden mit ?? markiert. Neue Dateien, die der Staging-Area hinzugefügt wurden, haben ein A , geänderte Dateien haben ein M usw. Es gibt zwei Spalten für die Ausgabe – die linke Spalte zeigt den Status der Staging-Area und die rechte Spalte den Status des Arbeitsverzeichnis. So ist beispielsweise in der Bildschirmausgabe oben die Datei README im Arbeitsverzeichnis geändert, aber noch nicht staged, während die Datei lib/simplegit.rb geändert und staged ist. Das Rakefile wurde modifiziert, staged und dann wieder modifiziert, so dass es Änderungen an ihm gibt, die sowohl staged als auch unstaged sind. Ignorieren von Dateien Häufig gibt es eine Reihe von Dateien, die Git nicht automatisch hinzufügen oder schon gar nicht als „nicht versioniert“ (eng. untracked) anzeigen soll. Dazu gehören in der Regel automatisch generierte Dateien, wie Log-Dateien oder Dateien, die von deinem Build-System erzeugt werden. In solchen Fällen kannst du die Datei .gitignore erstellen, die eine Liste mit Vergleichsmustern enthält. Hier ist eine .gitignore Beispieldatei: $ cat .gitignore *.[oa] *~ Die erste Zeile weist Git an, alle Dateien zu ignorieren, die auf „.o“ oder „.a“ enden – Objekt- und Archivdateien, die das Ergebnis einer Codegenerierung sein könnten. Die zweite Zeile weist Git an, alle Dateien zu ignorieren, deren Name mit einer Tilde ( ~ ) enden, was von vielen Texteditoren wie Emacs zum Markieren temporärer Dateien verwendet wird. Du kannst auch ein Verzeichnis „log“, „tmp“ oder „pid“ hinzufügen, eine automatisch generierte Dokumentation usw. Es ist im Allgemeinen eine gute Idee, die .gitignore Datei für dein neues Repository einzurichten, noch bevor du loslegen. So kannst du nicht versehentlich Dateien committen, die du nicht in deinem Git-Repository haben möchtest. Die Richtlinien für Vergleichsmuster, die du in der Datei .gitignore eingeben kannst, lautet wie folgt: Leerzeilen oder Zeilen, die mit # beginnen, werden ignoriert. Standard-Platzhalter-Zeichen funktionieren und werden rekursiv im gesamten Verzeichnisbaum angewendet. Du kannst Vergleichsmuster mit einem Schrägstrich ( / ) beginnen , um die Rekursivität zu verhindern. Du kannst Vergleichsmuster mit einem Schrägstrich ( / ) beenden , um ein Verzeichnis anzugeben. Du kannst ein Vergleichsmuster negieren, indem es mit einem Ausrufezeichen ( ! ) beginnt. Platzhalter-Zeichen sind wie einfache, reguläre Ausdrücke, die von der Shell genutzt werden. Ein Sternchen ( * ) entspricht null oder mehr Zeichen; [abc] entspricht jedem Zeichen innerhalb der eckigen Klammern (in diesem Fall a, b oder c); ein Fragezeichen ( ? ) entspricht einem einzelnen Zeichen und eckige Klammern, die durch einen Bindestrich ( [0-9] ) getrennte Zeichen einschließen, passen zu jedem Zeichen dazwischen (in diesem Fall von 0 bis 9). Du kannst auch zwei Sterne verwenden, um verschachtelte Verzeichnisse abzugleichen; a/**/z würde zu a/z , a/b/z , a/b/c/z usw. passen. Hier ist eine weitere .gitignore Beispieldatei: # ignore all .a files *.a # but do track lib.a, even though you're ignoring .a files above !lib.a # only ignore the TODO file in the current directory, not subdir/TODO /TODO # ignore all files in any directory named build build/ # ignore doc/notes.txt, but not doc/server/arch.txt doc/*.txt # ignore all .pdf files in the doc/ directory and any of its subdirectories doc/**/*.pdf Hinweis GitHub unterhält eine ziemlich umfassende Liste guter .gitignore Beispiel-Dateien für Dutzende von Projekten und Sprachen auf https://github.com/github/gitignore , falls du einen Ansatzpunkt für dein Projekt suchst. Anmerkung Im einfachsten Fall kann ein Repository eine einzelne .gitignore Datei in seinem Root-Verzeichnis haben, die rekursiv für das gesamte Repository gilt. Es ist aber auch möglich, weitere .gitignore Dateien in Unterverzeichnissen anzulegen. Die Regeln dieser verschachtelten .gitignore Dateien gelten nur für die in dem Verzeichnis (und unterhalb) liegenden Dateien. Das Linux-Kernel-Source-Repository hat beispielsweise 206 .gitignore Dateien. Es würde den Rahmen dieses Buches sprengen, detaillierter auf den Einsatz mehrerer .gitignore Dateien einzugehen; siehe die Manpage man gitignore für weitere Informationen. Überprüfen der Staged- und Unstaged-Änderungen Wenn der Befehl git status zu wage für dich ist und du genau wissen willst, was du geändert hast, kannst du den Befehl git diff verwenden. Wir werden git diff später ausführlicher behandeln, aber du wirst es wahrscheinlich oft verwenden, um dir diese beiden Fragen zu beantworten: Was hat sich geändert, ist aber noch nicht zum Commit vorgemerkt (engl. staged)? Was hast du zum Commit vorgemerkt und wird demnächst committet? Der Befehl git status beantwortet diese Fragen ganz allgemein, indem er die Dateinamen auflistet; git diff zeigt dir aber genau die hinzugefügten und entfernten Zeilen – sozusagen den aktuellen Patch. Nehmen wir an, du bearbeitest und stagst die Datei README nochmal und bearbeitest dann die Datei CONTRIBUTING.md , ohne sie zu stagen. Wenn du den Befehl git status ausführst, siehst du erneut so etwas: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Um die Änderungen zu sehen, die du noch nicht zum Commit vorgemerkt hast, gibst du den Befehl git diff ohne weitere Argumente, ein: $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,8 @@ branch directly, things can get messy. Please include a nice description of your changes when you submit your PR; if we have to read the whole diff to figure out why you're contributing in the first place, you're less likely to get feedback and have your change -merged in. +merged in. Also, split your changes into comprehensive chunks if your patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's Dieses Kommando vergleicht, was sich in deinem Arbeitsverzeichnis befindet, mit dem, was sich in deiner Staging-Area befindet. Das Ergebnis gibt dir an, welche Änderungen du vorgenommen hast, die noch nicht gestaged sind. Wenn du wissen willst, was du zum Commit vorgemerkt hast, das in deinem nächsten Commit einfließt, kannst du git diff --staged verwenden. Dieser Befehl vergleicht deine zum Commit vorgemerkten Änderungen mit deinem letzten Commit: $ git diff --staged diff --git a/README b/README new file mode 100644 index 0000000..03902a1 --- /dev/null +++ b/README @@ -0,0 +1 @@ +My Project Es ist wichtig zu wissen, dass git diff von sich aus nicht alle Änderungen seit deinem letzten Commit anzeigt – nur die Änderungen, die noch „unstaged“ sind. Wenn du alle deine Änderungen bereits „gestaged“ hast, wird git diff dir keine Antwort geben. Ein weiteres Beispiel: Wenn du die Datei CONTRIBUTING.md stagst und dann bearbeitest, kannst du git diff verwenden, um die Änderungen in der Datei anzuzeigen, die staged und nicht staged sind. Wenn es bei dir so aussieht: $ git add CONTRIBUTING.md $ echo '# test line' >> CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md kannst du jetzt mit git diff sehen, was noch nicht zum Commit vorgemerkt ist $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 643e24f..87f08c8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -119,3 +119,4 @@ at the ## Starter Projects See our [projects list](https://github.com/libgit2/libgit2/blob/development/PROJECTS.md). +# test line und git diff --cached zeigt an, was du bisher zum Commit vorgemerkt hast ( --staged und --cached sind Synonyme, sie bewirken das Gleiche): $ git diff --cached diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,8 @@ branch directly, things can get messy. Please include a nice description of your changes when you submit your PR; if we have to read the whole diff to figure out why you're contributing in the first place, you're less likely to get feedback and have your change -merged in. +merged in. Also, split your changes into comprehensive chunks if your patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's Anmerkung Git Diff mit einem externen Tool Wir werden den Befehl git diff im weiteren Verlauf des Buches auf vielfältige Weise verwenden. Es gibt eine weitere Methode, diese Diffs zu betrachten, solltest du lieber ein graphisches oder externes Diff-Viewing-Programm bevorzugen. Wenn du git difftool anstelle von git diff verwendest, könntest du alle diese Unterschiede in einer Software wie emerge, vimdiff und viele andere (einschließlich kommerzieller Produkte) anzeigen lassen. Führe einfach den Befehl git difftool --tool-help aus, um zu sehen, was auf deinem System verfügbar ist. Die Änderungen committen Nachdem deine Staging-Area nun so eingerichtet ist, wie du es wünschst, kannst du deine Änderungen committen. Denke daran, dass alles, was noch nicht zum Commit vorgemerkt ist – alle Dateien, die du erstellt oder geändert hast und für die du seit deiner Bearbeitung nicht mehr git add ausgeführt hast – nicht in diesen Commit einfließen werden. Sie bleiben aber als geänderte Dateien auf deiner Festplatte erhalten. In diesem Beispiel nehmen wir an, dass du beim letzten Mal, als du git status ausgeführt hast, gesehen hast, dass alles zum Commit vorgemerkt wurde und du bereit bist, alle deine Änderungen zu committen. Am einfachsten committen man, wenn git commit eingegeben wird: $ git commit Dadurch wird der Editor deiner Wahl gestartet. Anmerkung Das wird durch die Umgebungsvariable EDITOR deiner Shell festgelegt – normalerweise Vim oder Emacs. Du kannst den Editor aber auch mit dem Befehl git config --global core.editor beliebig konfigurieren, wie du es in Kapitel 1, Erste Schritte gesehen hast. Der Editor zeigt den folgenden Text an (dieses Beispiel ist eine Vim-Ansicht): # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # new file: README # modified: CONTRIBUTING.md # ~ ~ ~ ".git/COMMIT_EDITMSG" 9L, 283C Du kannst erkennen, dass die Standard-Commit-Meldung die neueste Ausgabe des auskommentierten Befehls git status und eine leere Zeile darüber enthält. Du kannst diese Kommentare entfernen und deine eigene Commit-Nachricht eingeben oder du kannst sie dort stehen lassen, damit du dir merken kannst, was was du committed hast. Anmerkung Für eine noch bessere Gedächtnisstütze über das, was du geändert hast, kannst du die Option -v an git commit übergeben. Dadurch wird auch die Änderung in den Editor geschrieben, so dass du genau sehen kannst, welche Änderungen du committest. Wenn du den Editor verlässt, erstellt Git deinen Commit mit dieser Commit-Nachricht (mit den Kommentaren und ausgeblendetem Diff). Alternativ kannst du deine Commit-Nachricht auch inline mit dem Befehl commit -m eingeben. Das Flag -m ermöglicht die direkte Eingabe eines Kommentartextes: $ git commit -m "Story 182: fix benchmarks for speed" [master 463dc4f] Story 182: fix benchmarks for speed 2 files changed, 2 insertions(+) create mode 100644 README Jetzt hast du deinen ersten Commit erstellt! Du kannst sehen, dass der Commit eine Nachricht über sich selbst ausgegeben hat: in welchen Branch du committet hast ( master ), welche SHA-1-Prüfsumme der Commit hat ( 463dc4f ), wie viele Dateien geändert wurden und Statistiken über hinzugefügte und entfernte Zeilen im Commit. Denke daran, dass der Commit den Snapshot aufzeichnet, den du in deiner Staging-Area eingerichtet hast. Alles, was von dir nicht zum Commit vorgemerkt wurde, ist weiterhin verfügbar. Du kannst einen weiteren Commit durchführen, um es zu deiner Historie hinzuzufügen. Jedes Mal, wenn du einen Commit ausführst, zeichnest du einen Schnappschuss deines Projekts auf, auf den du zurückgreifen oder mit dem du später vergleichen kannst. Die Staging-Area überspringen Obwohl es außerordentlich nützlich sein kann, Commits so zu erstellen, wie du es wünschst, ist die Staging-Area manchmal etwas komplexer, als du es für deinen Workflow benötigst. Wenn du die Staging-Area überspringen möchten, bietet Git eine einfache Kurzform. Durch das Hinzufügen der Option -a zum Befehl git commit wird jede Datei, die bereits vor dem Commit versioniert war, automatisch von Git zum Commit staged, so dass du den Teil git add überspringen kannst: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md no changes added to commit (use "git add" and/or "git commit -a") $ git commit -a -m 'Add new benchmarks' [master 83e38c7] Add new benchmarks 1 file changed, 5 insertions(+), 0 deletions(-) Beachte, dass du in diesem Fall git add nicht für die Datei CONTRIBUTING.md ausführen musst, bevor du committest. Das liegt daran, dass das -a -Flag alle geänderten Dateien einschließt. Das ist bequem. Aber sei vorsichtig, manchmal führt dieses Flag dazu, dass du ungewollte Änderungen vornimmst. Dateien löschen Um eine Datei aus Git zu entfernen, musst du sie aus der Versionsverwaltung entfernen (genauer gesagt, aus deinem Staging-Bereich löschen) und dann committen. Der Befehl git rm erledigt das und entfernt die Datei auch aus deinem Arbeitsverzeichnis, so dass du sie beim nächsten Mal nicht mehr als „untracked“-Datei siehst. Wenn du die Datei einfach aus deinem Arbeitsverzeichnis entfernst, erscheint sie unter dem „Changes not staged for commit“-Bereich (das ist die unstaged -Area) deiner git status Ausgabe: $ rm PROJECTS.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add/rm <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) deleted: PROJECTS.md no changes added to commit (use "git add" and/or "git commit -a") Wenn du dann git rm ausführst, wird die Entfernung der Datei zum Commit vorgemerkt: $ git rm PROJECTS.md rm 'PROJECTS.md' $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) deleted: PROJECTS.md Wenn du das nächste Mal einen Commit ausführst, ist die Datei weg und ist nicht mehr versioniert (engl. tracked). Wenn du die Datei geändert oder bereits zur Staging-Area hinzugefügt hast, musst du das Entfernen mit der Option -f erzwingen. Hierbei handelt es sich um eine Sicherheitsfunktion, die ein versehentliches Entfernen von Dateien verhindert, die noch nicht in einem Snapshot aufgezeichnet wurden und die nicht von Git wiederhergestellt werden können. Eine weitere nützliche Sache, die du möglicherweise nutzen möchtest, ist, die Datei in deinem Verzeichnisbaum zu behalten, sie aber aus deiner Staging-Area zu entfernen. Mit anderen Worten, du kannst die Datei auf deiner Festplatte behalten, aber nicht mehr von Git protokollieren/versionieren lassen. Das ist besonders dann nützlich, wenn du vergessen hast, etwas zu deiner Datei .gitignore hinzuzufügen und dies dann versehentlich gestaged hast (eine große Logdatei z.B. oder eine Reihe von .a-kompilierten Dateien). Das erreichst du mit der Option --cached : $ git rm --cached README Du kannst Dateien, Verzeichnisse und Platzhalter-Zeichen an den Befehl git rm übergeben. Das bedeutet, dass du folgende Möglichkeit hast: $ git rm log/\*.log Beachten den Backslash ( \ ) vor dem * . Der ist notwendig, weil Git zusätzlich zur Dateinamen-Erweiterung deiner Shell eine eigene Dateinamen-Erweiterung vornimmt. Mit dem Befehl oben werden alle Dateien entfernt, die die Erweiterung .log im Verzeichnis log/ haben. Oder du kannst Folgendes ausführen: $ git rm \*~ Dieses Kommando entfernt alle Dateien, deren Name mit ~ endet. Dateien verschieben Im Gegensatz zu vielen anderen VCS-Systemen verfolgt (engl. track) Git das Verschieben von Dateien nicht ausdrücklich. Wenn du eine Datei in Git umbenennst, werden keine Metadaten in Git gespeichert, die dem System mitteilen, dass du die Datei umbenannt hast. Allerdings ist Git ziemlich clever, das im Nachhinein herauszufinden – wir werden uns etwas später mit der Erkennung von Datei-Verschiebungen befassen. Daher ist es etwas verwirrend, dass Git einen Befehl mv vorweisen kann. Wenn du eine Datei in Git umbenennen möchten, kannst du beispielsweise Folgendes ausführen: $ git mv file_from file_to Das funktioniert gut. Tatsache ist, wenn du so einen Befehl ausführst und dir den Status ansiehst, wirst du sehen, dass Git es für eine umbenannte Datei hält: $ git mv README.md README $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Unabhängig davon, ist dieser Befehl zu dem Folgenden gleichwertig: $ mv README.md README $ git rm README.md $ git add README Git erkennt, dass es sich um eine umbenannte Datei handelt, so dass es egal ist, ob du eine Datei auf diese Weise oder mit dem Befehl mv umbenennst. Der alleinige, reale Unterschied ist, dass git mv ein einziger Befehl ist statt deren drei – es ist eine Komfortfunktion. Wichtiger ist, dass du jedes beliebige Tool verwenden können, um eine Datei umzubenennen und das du add / rm später aufrufen kannst, bevor du committest. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://git-scm.com/book/ru/v2/%d0%9e%d1%81%d0%bd%d0%be%d0%b2%d1%8b-Git-%d0%9f%d1%81%d0%b5%d0%b2%d0%b4%d0%be%d0%bd%d0%b8%d0%bc%d1%8b-%d0%b2-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 Командная строка 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 2.7 Основы Git - Псевдонимы в Git Псевдонимы в Git Прежде, чем закончить эту главу по основам Git, рассмотрим ещё одну маленькую хитрость, которая поможет сделать использование Git проще, легче, и более привычным: псевдонимы (aliases). Мы не будем ссылаться на них дальше или предполагать, что вы будете пользоваться ими по ходу чтения книги, но вам лучше было бы знать, как их использовать. Git не будет пытаться сделать вывод о том, какую команду вы хотели ввести, если вы ввели её не полностью. Если вы не хотите печатать каждую команду для Git целиком, вы легко можете настроить псевдонимы (alias) для любой команды с помощью git config . Вот несколько примеров псевдонимов, которые вы, возможно, захотите задать: $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status Это означает, что, например, вместо ввода git commit , вам достаточно набрать только git ci . По мере освоения Git вам, вероятно, придётся часто пользоваться и другими командами. В этом случае без колебаний создавайте новые псевдонимы. Такой способ может также быть полезен для создания команд, которые, как вы думаете, должны существовать. Например, чтобы исправить неудобство, с которым мы столкнулись при исключении файла из индекса, можно добавить в Git свой собственный псевдоним unstage : $ git config --global alias.unstage 'reset HEAD --' Это делает эквивалентными следующие две команды: $ git unstage fileA $ git reset HEAD -- fileA Такой вариант кажется немного более понятным. Также, обычно, добавляют команду last следующим образом: $ git config --global alias.last 'log -1 HEAD' Таким образом, можно легко просмотреть последний коммит: $ git last commit 66938dae3329c7aebe598c2246a8e6af90d04646 Author: Josh Goebel <dreamer3@example.com> Date: Tue Aug 26 19:48:51 2008 +0800 Test for current head Signed-off-by: Scott Chacon <schacon@example.com> Можно сказать, что Git просто заменяет эти команды на созданные вами псевдонимы (alias). Однако, возможно, вы захотите выполнить внешнюю команду, а не подкоманду Git. В этом случае, следует начать команду с символа ! . Это полезно, если вы пишете свои утилиты для работы с Git-репозиторием. Продемонстрируем этот случай на примере создания псевдонима git visual для запуска gitk : $ git config --global alias.visual '!gitk' prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://git-scm.com/book/uk/v2/GitHub-%d0%a1%d1%83%d0%bf%d1%80%d0%be%d0%b2%d0%be%d0%b4%d0%b6%d1%83%d0%b2%d0%b0%d0%bd%d0%bd%d1%8f-%d0%bf%d1%80%d0%be%d1%94%d0%ba%d1%82%d1%83 | 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 6.3 GitHub - Супроводжування проєкту Супроводжування проєкту Тепер, коли ми знаємо, як робити внески до проєктів, поглянемо з іншого боку: створення, супроводжування та адміністрування вашого власного проєкту. Створення нового сховища Створимо нове сховище, до якого ми додамо код нашого проєкту. Спочатку натиснемо кнопку `New repository'' (нове сховище) праворуч панелі керування, чи за допомогою кнопки `+ у верхній панелі інструментів біля вашого імені користувача, як можна побачити в ``New repository'' (нове сховище) у випадному списку. . Рисунок 109. Область ``Your repositories'' (ваші сховища). Рисунок 110. ``New repository'' (нове сховище) у випадному списку. Тоді ми потрапимо до форми ``нове сховище'': Рисунок 111. Форма ``нове сховище''. Вам треба лише надати проєкту ім’я. Усі інші поля зовсім не обов’язкові. Зараз просто натисніть на кнопку `Create Repository'' (створити сховище), і бах – у вас вже є нове сховище на GitHub, під назвою `<ім’я користувача>/<назва проєкту> . Оскільки у вашому проєкті наразі нема коду, GitHub покаже вам інструкції щодо створення абсолютно нового сховища Git, або приєднання існуючого проєкту Git. Ми не будемо її тут викладати. Якщо вам необхідно щось з цього пригадати, дивіться Основи Git . Тепер у вас є проєкт на GitHub, ви можете дати URL будь-кому, з ким хочете поділитись своїм проєктом. Кожен проєкт на GitHub є доступним через HTTPS за адресою https://github.com/<user>/<project_name> , та через SSH за адресою git@github.com:<user>/<project_name> . Git може отримувати та викладати зміни користуючись обома URL, проте вони мають контроль доступу, що базується на запиті ім’я/паролю користувача. Зауваження Часто більш бажано поширювати HTTPS URL публічного проєкту, адже тоді користувачу не доведеться мати обліковий запис GitHub щоб зробити клон проєкту. Користувачам доведеться мати обліковий запис та відвантажений SSH ключ щоб мати доступ до вашого проєкту через SSH. Посилання HTTPS ще можна просто вставити до вашого веб-оглядача, щоб побачити там ваш проєкт. Додавання співпрацівників Якщо ви працюєте з іншими людьми, та бажаєте надати їм право робити коміти, ви маєте додати їх до співпрацівників'' ( collaborators ). Якщо Бен, Джефф та Луїза усі мають облікові записи на GitHub, та ви бажаєте надати їм доступ на запис до вашого сховища, ви можете додати їх до свого проєкту. Це надасть їм можливість робити push'', тобто вони матимуть доступ і на читання, і на запис до проєкту та сховища Git. Натисніть на посилання ``Settings'' (налаштування) знизу бокової панелі праворуч. Рисунок 112. Посилання на налаштування сховища. Потім виберіть Collaborators'' (співпрацівники) з меню ліворуч. Потім просто наберіть ім’я в поле, та натисніть Add collaborator.'' (додати співпрацівника) Ви можете повторювати це скільки завгодно раз, щоб надати доступ усім, кому ви бажаєте. Якщо вам треба скасувати доступ, просто натисніть на ``X'' з правого боку рядка потрібного користувача. Рисунок 113. Співпрацівники сховища. Керування Запитами на Пул (Pull Requests) Тепер у вас є проєкт з якимось кодом та можливо навіть декілька співпрацівників з доступом на запис, розгляньмо що робити, якщо хтось направив вам Запит на Пул. Запити на пул можуть надходити або з гілки у форку вашого сховища, або просто з іншої гілки вашого сховища. Єдина різниця, що якщо він з форку, то зазвичай від людей, до гілки яких ви не маєте права викладати зміни та вони не мають права викладати зміни до вашої, а в разі внутрішнього Запиту на Злиття зазвичай обидві сторони мають на це право. Для наступних прикладів, припустімо, що ви tonychacon'', та ви створили новий проєкт Arduino під назвою fade''. Повідомлення електронною поштою Хтось приходить, змінює ваш код та відправляє вам Запит на Пул. Вам має надійти лист з повідомленням про новий Запит на Пул, що має виглядати як Лист з повідомленням про новий Запит на Пул. . Рисунок 114. Лист з повідомленням про новий Запит на Пул. Варто звернути увагу на декілька речей у цьому листі. Він включає невелику статистику змін ( diffstat ) - список файлів, що були змінені в Запиті на Пул, та наскільки вони змінились. Також у ньому є посилання на сторінку GitHub Запиту на Пул. І ще декілька URL, які ви можете використовувати з командного рядка. Якщо ви помітили рядок з текстом git pull <url> patch-1 , то це простий метод злити зміни з віддаленої гілки без необхідності додавати віддалене сховище. Ми швидко це розглянули в Отримання віддалених гілок . Якщо ви бажаєте, то можете створити та перейти до тематичної гілки, а потім виконати цю команду, щоб злити зміни Запиту на Пул. Інші цікаві посилання це .diff та .patch , які, як ви можете здогадатись, містять Запит на Пул у вигляді об’єднаних змін (unified diff) та патчу. Ви можете злити Запит на Пул навіть так: $ curl http://github.com/tonychacon/fade/pull/1.patch | git am Співпраця над Запитом на Пул Як ми вже бачили в Потік роботи GitHub , ви тепер можете спілкуватись з людиною, яка відкрила Запит на Пул. Ви можете коментувати окремі рядки коду, коментувати цілі коміти, чи коментувати весь Запит на Пул, за допомогою GitHub різновиду Markdown. Щоразу хтось інший коментує Запит на Пул, ви знову будете отримувати лист з повідомленням, отже ви будете знати що відбувається. Кожен з листів буде містити посилання на Запит на Пул саме туди, де щось відбулося, а також ви можете відповісти прямо на лист, і коментар у Запиті на Пул буде створено автоматично. Рисунок 115. Відповідь на лист включається в переписку на GitHub. Щойно код стає вам до вподоби та ви бажаєте його злити, ви можете або зробити пул коду та злити його локально, або використати git pull <url> <branch> , як ми бачили раніше, або можете додати форк як віддалене сховище, отримати з нього всі коміти, а потім вже злити зміни. Якщо злиття тривіальне, ви також можете просто натиснути на кнопку Merge'' (злити) на сайті GitHub. Це зробить злиття не-швидко-вперед'' ( non-fast-forward ): створить коміт злиття навіть якщо злиття швидко-вперед можливе. Це означає що за будь-яких обставин, щоразу ви натискаєте на кнопку merge , буде створено коміт злиття. Як ви можете побачити на Кнопка злиття та інструкції щодо злиття Запиту на Пул вручну. , GitHub надасть вам усю цю інформацію, якщо ви натиснете на посилання вказівки ( hint ). Рисунок 116. Кнопка злиття та інструкції щодо злиття Запиту на Пул вручну. Якщо ви вирішите не зливати Запит, ви також можете просто закрити Запит на Злиття, про що автора запиту буде повідомлено. Посилання (Refs) Запитів на Пул Якщо вам доводиться працювати з багатьма Запитами на Злиття, та ви не бажаєте додавати купу віддалених сховищ чи робити по одному пулу на кожен, є один дотепний засіб, який GitHub вам дозволяє використати. Це дещо складний засіб та ми дещо докладніше розглянемо подробиці того, що відбувається в Специфікація посилань (refspec) , проте він може бути доволі корисним. Насправді GitHub сприймає гілки Запитів на Злиття для сховища як щось на кшталт псевдо-гілок на сервері. Без додаткових дій ви не отримуєте їх при клонуванні, проте вони є в прихованому вигляді та ви можете доволі легко отримати до них доступ. Щоб це продемонструвати, ми збираємося використати команду низького рівня (часто їх називають команди `plumbing'', про що ми прочитаємо більше в Кухонні та парадні команди ) під назвою `ls-remote . Ця команда не потрібна при повсякденному використанні Git, проте вона корисна щоб показати нам, які посилання ( references ) присутні на сервері. Якщо ми виконаємо цю команду на сховищі ``blink'', яке ми вже раніше використовували, ми отримаємо список усіх гілок та теґів, а також інших посилань у сховищі. $ git ls-remote https://github.com/schacon/blink 10d539600d86723087810ec636870a504f4fee4d HEAD 10d539600d86723087810ec636870a504f4fee4d refs/heads/master 6a83107c62950be9453aac297bb0193fd743cd6e refs/pull/1/head afe83c2d1a70674c9505cc1d8b7d380d5e076ed3 refs/pull/1/merge 3c8d735ee16296c242be7a9742ebfbc2665adec1 refs/pull/2/head 15c9f4f80973a2758462ab2066b6ad9fe8dcf03d refs/pull/2/merge a5a7751a33b7e86c5e9bb07b26001bb17d775d1a refs/pull/4/head 31a45fc257e8433c8d8804e3e848cf61c9d3166c refs/pull/4/merge Авжеж, якщо ви у своєму сховищі виконаєте git ls-remote origin (замість origin може бути будь-яке віддалене сховище), ви отримаєте щось схоже на це. Якщо сховище розміщене на GitHub та у вас є хоч один відкритий Запит на Пул, ви побачите посилання з префіксом refs/pull/ . Це звичайні гілки, проте оскільки вони не мають префікса refs/heads/ , ви не отримуєте їх при клонуванні або отриманні змін з серверу — процес отримання зазвичай повністю їх ігнорує. Для кожного Запиту на Пул є по два посилання: те, що закінчується на /head вказує саме на останній коміт до гілки Запиту на Пул. Отже, якщо хтось відкриє Запит на Пул до вашого сховища, та їхня гілка називається bug-fix та вона вказує на коміт a5a775 , то у вашому сховищі в нас не буде гілки bug-fix (адже це не у вашому форку), проте у нас буде pull/<pr#>/head , яке вказує на a5a775 . Це означає, що ми легко можемо злити кожну гілку Запиту на Пул одразу, і не маємо для цього додавати купу віддалених сховищ. Тепер ви можете отримати посилання явно наступним чином: $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD Ця команда каже Git: `Приєднайся до віддаленого сховища `origin , завантаж звідти посилання під назвою refs/pull/958/head .'' Git радісно це виконує, та завантажує все, що вам необхідно, щоб відновити це посилання, та записує вказівник до потрібного вам коміту в .git/FETCH_HEAD . Далі ви можете виконати git merge FETCH_HEAD , щоб злити зміни до гілки, в якій ви бажаєте перевірити зміни, проте повідомлення коміту зливання буде виглядати дещо дивно. Також, якщо ви переглядаєте багато запитів на пул, це стає марудним. Існує також метод отримати всі запити на пул, та оновлювати їх кожен раз, коли ви з’єднуєтесь з віддаленим сховищем. Відкрийте .git/config у вашому улюбленому редакторі, та знайдіть там віддалене сховище origin . Воно має виглядати приблизно так: [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* Рядок, що починається з fetch = є `специфікацією посилань'' (`refspec ). Це спосіб відображення імен у віддаленому сховищі в імена у вашій локальній директорії .git . Саме цей рядок з прикладу каже Git: "усе, що на віддаленому сховищі знаходиться під refs/head має опинитись у моєму локальному сховищі під `refs/remotes/origin`". Ви можете відредагувати цю секцію щоб додати іншу специфікацію посилань: [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* Цей останній рядок каже Git: `Усі посилання, що мають вигляд `refs/pull/123/head , мають бути збережені локально як refs/remotes/origin/pr/123 .'' Тепер, якщо ви збережете файл та виконаєте git fetch : $ git fetch # … * [new ref] refs/pull/1/head -> origin/pr/1 * [new ref] refs/pull/2/head -> origin/pr/2 * [new ref] refs/pull/4/head -> origin/pr/4 # … Тепер усі віддалені запити на пул представлені локально посиланнями так само, як і інші віддалені гілки. У них не можна вносити зміни, та вони оновлюються при отриманні змін. Це робить локальну перевірку коду із запиту на пул супер легкою: $ git checkout pr/2 Checking out files: 100% (3769/3769), done. Branch pr/2 set up to track remote branch pr/2 from origin. Switched to a new branch 'pr/2' Найуважніші з вас помітили head наприкінці імені віддаленої частини специфікації посилання. У сховищі GitHub також є посилання refs/pull/#/merge , що вказують на коміт, який ви би отримали при натисканні на кнопку ``merge'' сайту. Це дозволяє вам протестувати зливання до власно натискання на кнопку. Запити на Пул до Запитів на Пул Ви можете відкривати Запити на Пул не тільки до головної ( master ) гілки, ви насправді можете відкривати Запит на Пул до будь-якої гілки в мережі. Ви дійсно можете навіть відкрити його навіть до іншого Запиту на Пул. Якщо ви побачили Запит на Пул, що рухається у вірному напрямку, та у вас є ідеє зміни, що залежить від цього запиту, або ви невпевнені, що думка гарна, або у вас просто немає прав на запис до гілки запиту, ви можете відкрити Запит на Пул прямо до неї. Коли ви відкриваєте Запит на Пул, нагорі сторінки є поле, що задає гілку, до якої ви створюєте запит на пул, та поле, що задає гілку, з якої ви просите взяти зміни. Якщо ви натиснете на кнопку ``Edit'' (редагувати) праворуч від поля, ви зможете вибрати не тільки гілки, а й форк. Рисунок 117. Вручну змінюємо цільову гілку та форк Запиту на Пул. Як бачите, доволі просто запросити зливання вашої нової гілки до іншого Запиту на Пул або до іншого форку проєкту. Згадки та повідомлення У GitHub також є доволі гарна вбудована система повідомлень, яка може бути доречною, якщо у вас є питання чи вам потрібна допомога від конкретних людей чи команд. У кожному коментарі ви можете набрати символ @ та він почне автодоповнювання імен та імен користувачів людей, що є співпрацівниками цього проєкту, чи просто робили до нього внески. Рисунок 118. Починаємо набирати символ @ щоб когось згадати. Ви також можете згадати користувача, якого нема в цьому випадному віконці, проте часто це виходить швидше за допомогою автодоповнювача. Щойно ви зробите коментар зі згадкою користувача, він отримає повідомлення. Тобто це може бути дуже ефективним методом втягнути людей в спілкування, щоб їм не доводилось весь час продивлятись усі дискусії. Дуже часто люди на GitHub запрошують інших з їхньої команди чи компанії щоб переглянути Завдання чи Запит на Пул. Якщо когось згадують у Запиті на Пул або Завданні, вони стають підписаними'' (subscribed) на них та продовжать отримувати повідомлення щоразу, коли з ними відбувається якась активність. Ви також можете бути підписані до чогось, що ви відкрили, якщо ви слідкуєте за сховищем або якщо ви коментували щось. Якщо ви більше не бажаєте отримувати повідомлення, є кнопка Unsubscribe'' (відписатись) на сторінці, достатньо натиснути на неї, щоб GitHub припинив повідомляти вам про оновлення цієї сторінки. Рисунок 119. Відписуємось від Завдання чи Запиту на Пул. Сторінка повідомлень Коли ми кажемо повідомлення'' (notification) тут щодо GitHub, ми маємо на увазі окремий метод, яким GitHub намагається вам повідомити про якісь події. У вас є декілька різних методів їх налаштувати. Якщо ви перейдете до вкладки Notification center'' (центр повідомлень) зі сторінки налаштувань, ви побачите деякі доступні вам опції. Рисунок 120. Опції центру повідомлень. У вас є дві можливості отримувати повідомлення: через Електронну пошту'' або через Веб'' та ви можете вибрати один з них, жодного, або обидва для Запитів/Завдань та для активності в сховищах, за якими ви слідкуєте. ======= Веб повідомлення Веб повідомлення існують тільки на GitHub і ви можете їх перевіряти виключно на GitHub. Якщо ця опція ввімкнута у ваших налаштуваннях та вам надійшло повідомлення, ви побачите маленьку синю точку над іконкою повідомлень нагорі вашого екрану, як видно на Центр повідомлень . Рисунок 121. Центр повідомлень Якщо ви на неї натиснете, то побачите список усіх ваших повідомлень, згрупованих по проєктам. Ви можете фільтрувати повідомлення за проєктом, якщо натиснете на його назву в панелі ліворуч. Також ви можете підтвердити повідомлення, якщо натиснете на пташку ( checkmark ) біля повідомлення, або підтвердити всі повідомлення проєкту, якщо натиснете на пташку зверху групи. Також є кнопка приглушення біля кожної пташки, якщо ви на неї натиснете, ви більше не будете отримувати повідомлень про цю тему. Усі ці інструменти дуже корисні для роботи з великою кількістю повідомлень. Багато досвідчених користувачів GitHub просто вимикають усі поштові повідомлення та працюють з ними виключно через цю сторінку. Поштові повідомлення Поштові повідомлення — це інший спосіб обробляти повідомлення GitHub. Якщо вони ввімкнені, ви будете отримувати листа щодо кожного повідомлення. Ми вже бачили їх приклади в Коментарі, що їх відправили як поштові повідомлення та Лист з повідомленням про новий Запит на Пул. . Листи також будуть вірно впорядковані у групи повідомлень, що дуже корисно, якщо ваш поштовий клієнт їх підтримує. Також у листах від GitHub є чимало вбудованих до заголовків метаданих, що дуже допомагає при створенні особистих фільтрів та правил. Наприклад, якщо ми подивимось на заголовки листа, що був відправлений до Тоні в Лист з повідомленням про новий Запит на Пул. , ми побачимо наступне серед відправлених даних: To: tonychacon/fade <fade@noreply.github.com> Message-ID: <tonychacon/fade/pull/1@github.com> Subject: [fade] Wait longer to see the dimming effect better (#1) X-GitHub-Recipient: tonychacon List-ID: tonychacon/fade <fade.tonychacon.github.com> List-Archive: https://github.com/tonychacon/fade List-Post: <mailto:reply+i-4XXX@reply.github.com> List-Unsubscribe: <mailto:unsub+i-XXX@reply.github.com>,... X-GitHub-Recipient-Address: tchacon@example.com Тут є декілька цікавих рядків. Якщо ви бажаєте обрати або направити всі листи цього проєкту, або тільки цього Запиту на Пул, для цього достатньо даних у Message-ID : цей заголовок має формат <користувач>/<проєкт>/<тип>/<id> . Якби б це було, наприклад, завдання, <тип> був би issues'' замість pull''. Поля List-Post та List-Unsubscribe означають, що, якщо ваш поштовий клієнт їх підтримує, ви легко можете написати ( post ) до списку, або відписатись ( unsubscribe ) від розсилки. Останнє нічим не відрізняється від використання кнопки приглушити'' (mute) у веб версії повідомлення та від кнопки Unsubscribe'' на сторінці Завдання чи Запиту на Пул. Також варто сказати, що якщо у вас ввімкнені поштові та веб повідомлення, та ви прочитаєте поштову версію повідомлення, веб версія також буде позначена прочитаною, якщо ваш поштовий клієнт дозволяє зображення. Особливі файли Є декілька особливих файлів, що їх присутність у вашому сховищі помічає GitHub. README (Прочитай мене) Першим є файл README , який може бути майже будь-якого формату, який GitHub сприймає як текст. Наприклад, це може бути README , README.md , README.asciidoc тощо. Якщо GitHub побачить файл README у вашому коді, він відобразить його на головній сторінці вашого проєкту. Багато команд використовують цей файл для зберігання всієї інформації, яка доречна для когось незнайомого зі сховищем або проєктом. Зазвичай це такі речі як: Для чого цей проєкт Як його конфігурувати та інсталювати Приклад його використання або запуску Ліцензія проєкту Як зробити внесок до нього Оскільки GitHub буде відображати цей файл, ви можете додати до нього зображення або посилання щоб полегшати його читання. CONTRIBUTING (Як зробити внесок) Інший особливий файл, на який звертає увагу GitHub, називається CONTRIBUTING . Якщо у вас є файл CONTRIBUTING з будь-яким розширенням, GitHub покаже Відкриття Запиту на Пул, якщо існує файл CONTRIBUTING. коли хтось почне відкривати Запит на Пул. Рисунок 122. Відкриття Запиту на Пул, якщо існує файл CONTRIBUTING. Це зроблено задля того, щоб ви могли вказати що саме ви хочете чи не хочете бачити в Запиті на Пул, який направляють до вашого проєкту. Таким чином люди можуть прочитати ці інструкції до відкриття Запиту на Пул. Адміністрування Проекту Взагалі-то на GitHub небагато інструментів адміністрування проєкту, проте деякі з них можуть бути корисними. Зміна типової гілки Якщо ви використовуєте не гілку master'' як головну, тобто гілку, до якої ви бажаєте щоб люди відкривали Запити на Пул, ви можете це змінити на сторінці налаштуваньсвого сховища на вкладці Options'' (опції). Рисунок 123. Зміна типової гілки проєкту. Просто змініть типову гілку в випадному віконці та без окремої вказівки всі головні операції будуть відбуватися над нею, зокрема яку гілку буде отримувати сховище при клонуванні. Передача проєкту Якщо ви бажаєте передати проєкт іншому користувачу або організації на GitHub, для цього є опція Transfer ownership'' (передача власності) наприкінці тої самої вкладки Options'' на сторінці налаштувань вашого сховища. Рисунок 124. Передача проєкту іншому користувачу або організації GitHub. Це корисно якщо ви покидаєте проєкт та хтось бажає його продовжити, або якщо ваш проєкт стає більшим і ви бажаєте перемістити його до організації. Це не тільки переміщує сховище разом з усіма глядачами ( watcher ) та зірками до іншого місця, а ще й налаштує перенаправлення з вашого URL до нового місця. Також будуть перенаправлені клонування та отримання змін з Git — не тільки веб запити. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
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-GitWeb | Git - GitWeb 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.7 Git на сервері - GitWeb GitWeb Тепер, коли у вас є базовий доступ до вашого проекту з правом читання та з правами на читання та запис, можливо ви бажаєте налаштувати простий візуалізатор через веб. Git поставляє CGI скрипт GitWeb, який іноді для цього використовують. Рисунок 49. Веб інтерфейс користувача за допомогою GitWeb Якщо ви бажаєте подивитись, як виглядає GitWeb для вашого проекту, Git має команду для запуску тимчасового прикладу, якщо у вас є легкий веб-сервер на системі, наприклад lighttpd або webrick . На машинах Linux часто є lighttpd , отже ви може швидко його запустити, якщо наберете git instaweb у теці вашого проекту. Якщо ви використовуєте Mac, Leopard одразу має Ruby, отже webrick має бути найпростіше запустити. Щоб запустити instaweb не з lighttpd сервером, передайте бажане ім’я серверу опції --httpd . $ git instaweb --httpd=webrick [2009-02-21 10:02:21] INFO WEBrick 1.3.1 [2009-02-21 10:02:21] INFO ruby 1.8.6 (2008-03-03) [universal-darwin9.0] Ця команда запускає HTTPD сервер на порту 1234 та автоматично запускає веб-оглядач, що відразу покаже цю сторінку. Вам майже нічого не треба робити. Коли ви закінчили та бажаєте вимкнути сервер, ви можете виконати таку ж команду з опцією --stop : $ git instaweb --httpd=webrick --stop Якщо ви бажаєте, щоб веб інтерфейс працював на сервері весь час для вашої команди чи для проекту з відкритим кодом, для якого ви керуєте хостингом, вам треба встановити CGI скрипт, щоб він працював на вашому звичайному веб сервері. Деякі дистрибутиви Linux мають пакет gitweb , який ви можливо можете встановити за допомогою apt або dnf , отже можливо варто спочатку спробувати ці команди. Ми дуже швидко розглянемо встановлення GitWeb вручну. Спочатку треба отримати програмний код Git, в якому є і код GitWeb, та згенерувати власний CGI скрипт: $ git clone git://git.kernel.org/pub/scm/git/git.git $ cd git/ $ make GITWEB_PROJECTROOT="/srv/git" prefix=/usr gitweb SUBDIR gitweb SUBDIR ../ make[2]: `GIT-VERSION-FILE' is up to date. GEN gitweb.cgi GEN static/gitweb.js $ sudo cp -Rf gitweb /var/www/ Зауважте, що ви маєте вказати цій команді, де розташовані ваші сховища Git за допомогою змінної змінної GITWEB_PROJECTROOT . Тепер вам треба щоб Apache використовувати CGI для цього скрипту, що можна зробити за допомогою VirtualHost: <VirtualHost *:80> ServerName gitserver DocumentRoot /var/www/gitweb <Directory /var/www/gitweb> Options +ExecCGI +FollowSymLinks +SymLinksIfOwnerMatch AllowOverride All order allow,deny Allow from all AddHandler cgi-script cgi DirectoryIndex gitweb.cgi </Directory> </VirtualHost> Як і попередній CGI скрипт, GitWeb може працювати на будь-якому здатному на CGI або Perl веб сервері. Якщо ви хочете використовувати щось інше, налаштування має бути легким. Тепер ви можете зайти до http://gitserver/ та побачити ваші сховища. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#param-start-date | Pinterest API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Pinterest API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Discover by Keywords Posts API Collect by URL Discover by Profile URL Discover by Keywords Social Media APIs Pinterest API Scrapers Copy page Copy page Overview The Pinterest API Suite offers multiple types of APIs, each designed for specific data collection needs from Pinterest. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Discover by Keywords. Interesting Columns : name , following_count , website , follower_count . Posts API This API allows users to collect multiple posts based on a single input. Discovery functionality : - Discover by profile URL. - Discover by Keywords. Interesting Columns : title , content , user_name , likes . Profiles API Collect by URL This API allows users to retrieve detailed Pinterest profile information using the provided profile URL. Input Parameters : URL string required The Pinterest profile URL. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metrics : following_count , follower_count , boards_num , saved . Additional Information : last_updated , posts_page_url , discovery_input . This API allows users to collect detailed insights into a Pinterest profile, including user statistics, engagement metrics, and profile information. Discover by Keywords This API allows users to discover Pinterest profiles based on a specified keyword. Input Parameters : keyword string required The keyword to search for profiles. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metric s: following_count , follower_count , boards_num , saved. Additional Information : last_updated , posts_page_url , discovery_input . This API enables users to find Pinterest profiles related to a specific keyword, offering insights into user statistics, engagement, and profile details. Posts API Collect by URL This API allows users to collect detailed post data from a specific Pinterest post using the provided post URL. Input Parameters : URL string required The Pinterest post URL. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , post_type . For all data points, click here . User Details : user_name , user_url , user_id , followers . Post Metrics : likes , comments_num , comments , categories . Media & Attachments : image_video_url , video_length , attached_files . Hashtags & Discovery : hashtags , discovery_input . This API allows users to retrieve detailed insights into a specific Pinterest post, including user engagement, post content, media, and other related information. Discover by Profile URL This API allows users to retrieve posts from a specific Pinterest profile based on the provided profile URL. Input Parameters : URL string required The Pinterest profile URL from which to collect posts. num_of_posts number The number of posts to collect. If omitted, there is no limit. posts_to_not_include array An array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date ). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date ). Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users tso collect posts from a specific Pinterest profile, allowing for filtering by date, exclusion of specific posts, and retrieval of detailed post data including media, comments, and engagement metrics. Discover by Keywords This API allows users to discover Pinterest posts based on a specific keyword, enabling efficient content discovery. Input Parameters : keyword string required The keyword to search for posts, such as “food” or any other relevant term. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users to search for Pinterest posts based on a specific keyword, providing detailed insights into the content, engagement, media, and associated metrics for efficient discovery. Was this page helpful? Yes No Twitter Quora ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#collect-by-url | Pinterest API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Pinterest API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Discover by Keywords Posts API Collect by URL Discover by Profile URL Discover by Keywords Social Media APIs Pinterest API Scrapers Copy page Copy page Overview The Pinterest API Suite offers multiple types of APIs, each designed for specific data collection needs from Pinterest. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Discover by Keywords. Interesting Columns : name , following_count , website , follower_count . Posts API This API allows users to collect multiple posts based on a single input. Discovery functionality : - Discover by profile URL. - Discover by Keywords. Interesting Columns : title , content , user_name , likes . Profiles API Collect by URL This API allows users to retrieve detailed Pinterest profile information using the provided profile URL. Input Parameters : URL string required The Pinterest profile URL. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metrics : following_count , follower_count , boards_num , saved . Additional Information : last_updated , posts_page_url , discovery_input . This API allows users to collect detailed insights into a Pinterest profile, including user statistics, engagement metrics, and profile information. Discover by Keywords This API allows users to discover Pinterest profiles based on a specified keyword. Input Parameters : keyword string required The keyword to search for profiles. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metric s: following_count , follower_count , boards_num , saved. Additional Information : last_updated , posts_page_url , discovery_input . This API enables users to find Pinterest profiles related to a specific keyword, offering insights into user statistics, engagement, and profile details. Posts API Collect by URL This API allows users to collect detailed post data from a specific Pinterest post using the provided post URL. Input Parameters : URL string required The Pinterest post URL. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , post_type . For all data points, click here . User Details : user_name , user_url , user_id , followers . Post Metrics : likes , comments_num , comments , categories . Media & Attachments : image_video_url , video_length , attached_files . Hashtags & Discovery : hashtags , discovery_input . This API allows users to retrieve detailed insights into a specific Pinterest post, including user engagement, post content, media, and other related information. Discover by Profile URL This API allows users to retrieve posts from a specific Pinterest profile based on the provided profile URL. Input Parameters : URL string required The Pinterest profile URL from which to collect posts. num_of_posts number The number of posts to collect. If omitted, there is no limit. posts_to_not_include array An array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date ). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date ). Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users tso collect posts from a specific Pinterest profile, allowing for filtering by date, exclusion of specific posts, and retrieval of detailed post data including media, comments, and engagement metrics. Discover by Keywords This API allows users to discover Pinterest posts based on a specific keyword, enabling efficient content discovery. Input Parameters : keyword string required The keyword to search for posts, such as “food” or any other relevant term. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users to search for Pinterest posts based on a specific keyword, providing detailed insights into the content, engagement, media, and associated metrics for efficient discovery. Was this page helpful? Yes No Twitter Quora ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#param-posts-to-not-include | Instagram API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Instagram API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Posts API Collect by URL Discover by URL Comments API Collect by URL Reels API Collect by URL Discover by URL Social Media APIs Instagram API Scrapers Copy page Copy page Overview The Instagram API Suite offers multiple types of APIs, each designed for specific data collection needs from Instagram. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : N/A Interesting Columns : followers , post_count , post_hashtags , profile_name . Posts API This API allows users to collect multiple posts based on a single input URL (such as an Instagram reels URL, search URL or profile URL). Discovery functionality : - Direct URL of the Instagram reel - Direct URL of the search - Direct URL of the profile Interesting Columns : url , followers , hashtags , engagement_score_view . Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : comment_user , comment , likes_number , replies_number . The suite of APIs is designed to offer flexibility for targeted data collection, where users can input specific URLs to gather detailed post and comment data, either in bulk or with precise filtering options. Profiles API Collect by URL This API allows users to collect detailed data about an Instagram profile by providing the profile URL. It provides a comprehensive overview of an Instagram profile, including business and engagement information, posts, and user details. Input Parameters URL string required The Instagram profile URL. Output Structure Includes comprehensive data points: Page/Profile Details : account , id , followers , posts_count , is_business_account , is_professional_account , is_verified , avg_engagement , profile_name , profile_url , profile_image_link , and more. For all data points, click here . Posts API Collect by URL This API enables users to collect detailed data from Instagram posts by providing a post URL. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Post Details : post_id , description , hashtags , date_posted , num_comments , likes , content_type , video_view_count , video_play_count , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : photos , videos , thumbnail , display_url (link only, not the file itself), audio. Discover by URL This API allows users to discover recent Instagram posts from a public profile by providing the profile URL and specifying additional parameters. Input Parameters URL string required The Instagram profile URL. num_of_posts number The number of recent posts to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date). post_type string Specify the type of posts to collect (e.g., post, reel). Output Structure Includes comprehensive data points: Post Details: post_id , description , hashtags , date_posted , num_comments , likes , video_view_count , video_play_count ,and more. For all data points, click here . Page/Profile Details: user_posted , followers , posts_count , profile_image_link , is_verified , profile_url , is_paid_partnership , partnership_details , user_posted_id Attachments and Media: photos , videos , thumbnail , audio , display_url , content_type , product_type , coauthor_producers , tagged_users . This API is designed to allow for filtering, exclusion of specific posts, and collecting posts by type (regular post or reel) within a defined time frame. It provides detailed post and profile information, making it ideal for data collection and analytics. Comments API Collect by URL This API allows users to collect the latest comments from a specific Instagram post by providing the post URL. This API retrieves the most recent 10 comments along with associated metadata. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Comment Details : comment_id , comment_user , comment_user_url , comment_date , comment , likes_number , replies_number , replies , hashtag_comment , tagged_users_in_comment , and more. For all data points, click here . User Details : user_name , user_id , user_url We provide a limited set of data points about the profile. Post Metadata : post_url , post_user , post_id . Reels API Collect by URL This API allows users to collect detailed data about Instagram reels from public profiles by providing the reel URL. Input Parameters URL string required The Instagram reel URL. Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , tagged_users , num_comments , likes , views , video_play_count , length , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : video_url , thumbnail , audio_url . Discover by URL This API allows users to discover Instagram Reels videos from a profile URL or direct search URL. Input Parameters URL string required The Instagram profile or direct search URL. num_of_posts number The number of recent reels to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering reels in MM-DD-YYYY format. end_date string End date for filtering reels in MM-DD-YYYY format (should be later than start_date ). Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , num_comments , likes , views , video_play_count , top_comments , length , video_url , audio_url , content_id , and more. For all data points, click here . Profile Details : user_posted , followers , posts_count , following . Attachments and Media : video_url , thumbnail , audio_url (link only, not the file itself). This API provides detailed information about Instagram Reels, with filtering options by date range, exclusion of specific posts, and a limit on the number of reels collected. Was this page helpful? Yes No Facebook LinkedIn ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://git-scm.com/book/be/v2/GitHub-Maintaining-a-Project | Git - Maintaining a Project 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 6.3 GitHub - Maintaining a Project Maintaining a Project Now that we’re comfortable contributing to a project, let’s look at the other side: creating, maintaining and administering your own project. Creating a New Repository Let’s create a new repository to share our project code with. Start by clicking the “New repository” button on the right-hand side of the dashboard, or from the + button in the top toolbar next to your username as seen in The “New repository” dropdown . Малюнак 109. The “Your repositories” area Малюнак 110. The “New repository” dropdown This takes you to the “new repository” form: Малюнак 111. The “new repository” form All you really have to do here is provide a project name; the rest of the fields are completely optional. For now, just click the “Create Repository” button, and boom – you have a new repository on GitHub, named <user>/<project_name> . Since you have no code there yet, GitHub will show you instructions for how to create a brand-new Git repository, or connect an existing Git project. We won’t belabor this here; if you need a refresher, check out Git Basics . Now that your project is hosted on GitHub, you can give the URL to anyone you want to share your project with. Every project on GitHub is accessible over HTTPS as https://github.com/<user>/<project_name> , and over SSH as git@github.com:<user>/<project_name> . Git can fetch from and push to both of these URLs, but they are access-controlled based on the credentials of the user connecting to them. Заўвага It is often preferable to share the HTTPS based URL for a public project, since the user does not have to have a GitHub account to access it for cloning. Users will have to have an account and an uploaded SSH key to access your project if you give them the SSH URL. The HTTPS one is also exactly the same URL they would paste into a browser to view the project there. Adding Collaborators If you’re working with other people who you want to give commit access to, you need to add them as “collaborators”. If Ben, Jeff, and Louise all sign up for accounts on GitHub, and you want to give them push access to your repository, you can add them to your project. Doing so will give them “push” access, which means they have both read and write access to the project and Git repository. Click the “Settings” link at the bottom of the right-hand sidebar. Малюнак 112. The repository settings link Then select “Collaborators” from the menu on the left-hand side. Then, just type a username into the box, and click “Add collaborator.” You can repeat this as many times as you like to grant access to everyone you like. If you need to revoke access, just click the “X” on the right-hand side of their row. Малюнак 113. Repository collaborators Managing Pull Requests Now that you have a project with some code in it and maybe even a few collaborators who also have push access, let’s go over what to do when you get a Pull Request yourself. Pull Requests can either come from a branch in a fork of your repository or they can come from another branch in the same repository. The only difference is that the ones in a fork are often from people where you can’t push to their branch and they can’t push to yours, whereas with internal Pull Requests generally both parties can access the branch. For these examples, let’s assume you are “tonychacon” and you’ve created a new Arduino code project named “fade”. Email Notifications Someone comes along and makes a change to your code and sends you a Pull Request. You should get an email notifying you about the new Pull Request and it should look something like Email notification of a new Pull Request . Малюнак 114. Email notification of a new Pull Request There are a few things to notice about this email. It will give you a small diffstat — a list of files that have changed in the Pull Request and by how much. It gives you a link to the Pull Request on GitHub. It also gives you a few URLs that you can use from the command line. If you notice the line that says git pull <url> patch-1 , this is a simple way to merge in a remote branch without having to add a remote. We went over this quickly in Checking Out Remote Branches . If you wish, you can create and switch to a topic branch and then run this command to merge in the Pull Request changes. The other interesting URLs are the .diff and .patch URLs, which as you may guess, provide unified diff and patch versions of the Pull Request. You could technically merge in the Pull Request work with something like this: $ curl https://github.com/tonychacon/fade/pull/1.patch | git am Collaborating on the Pull Request As we covered in The GitHub Flow , you can now have a conversation with the person who opened the Pull Request. You can comment on specific lines of code, comment on whole commits or comment on the entire Pull Request itself, using GitHub Flavored Markdown everywhere. Every time someone else comments on the Pull Request you will continue to get email notifications so you know there is activity happening. They will each have a link to the Pull Request where the activity is happening and you can also directly respond to the email to comment on the Pull Request thread. Малюнак 115. Responses to emails are included in the thread Once the code is in a place you like and want to merge it in, you can either pull the code down and merge it locally, either with the git pull <url> <branch> syntax we saw earlier, or by adding the fork as a remote and fetching and merging. If the merge is trivial, you can also just hit the “Merge” button on the GitHub site. This will do a “non-fast-forward” merge, creating a merge commit even if a fast-forward merge was possible. This means that no matter what, every time you hit the merge button, a merge commit is created. As you can see in Merge button and instructions for merging a Pull Request manually , GitHub gives you all of this information if you click the hint link. Малюнак 116. Merge button and instructions for merging a Pull Request manually If you decide you don’t want to merge it, you can also just close the Pull Request and the person who opened it will be notified. Pull Request Refs If you’re dealing with a lot of Pull Requests and don’t want to add a bunch of remotes or do one time pulls every time, there is a neat trick that GitHub allows you to do. This is a bit of an advanced trick and we’ll go over the details of this a bit more in The Refspec , but it can be pretty useful. GitHub actually advertises the Pull Request branches for a repository as sort of pseudo-branches on the server. By default you don’t get them when you clone, but they are there in an obscured way and you can access them pretty easily. To demonstrate this, we’re going to use a low-level command (often referred to as a “plumbing” command, which we’ll read about more in Plumbing and Porcelain ) called ls-remote . This command is generally not used in day-to-day Git operations but it’s useful to show us what references are present on the server. If we run this command against the “blink” repository we were using earlier, we will get a list of all the branches and tags and other references in the repository. $ git ls-remote https://github.com/schacon/blink 10d539600d86723087810ec636870a504f4fee4d HEAD 10d539600d86723087810ec636870a504f4fee4d refs/heads/master 6a83107c62950be9453aac297bb0193fd743cd6e refs/pull/1/head afe83c2d1a70674c9505cc1d8b7d380d5e076ed3 refs/pull/1/merge 3c8d735ee16296c242be7a9742ebfbc2665adec1 refs/pull/2/head 15c9f4f80973a2758462ab2066b6ad9fe8dcf03d refs/pull/2/merge a5a7751a33b7e86c5e9bb07b26001bb17d775d1a refs/pull/4/head 31a45fc257e8433c8d8804e3e848cf61c9d3166c refs/pull/4/merge Of course, if you’re in your repository and you run git ls-remote origin or whatever remote you want to check, it will show you something similar to this. If the repository is on GitHub and you have any Pull Requests that have been opened, you’ll get these references that are prefixed with refs/pull/ . These are basically branches, but since they’re not under refs/heads/ you don’t get them normally when you clone or fetch from the server — the process of fetching ignores them normally. There are two references per Pull Request - the one that ends in /head points to exactly the same commit as the last commit in the Pull Request branch. So if someone opens a Pull Request in our repository and their branch is named bug-fix and it points to commit a5a775 , then in our repository we will not have a bug-fix branch (since that’s in their fork), but we will have pull/<pr#>/head that points to a5a775 . This means that we can pretty easily pull down every Pull Request branch in one go without having to add a bunch of remotes. Now, you could do something like fetching the reference directly. $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD This tells Git, “Connect to the origin remote, and download the ref named refs/pull/958/head .” Git happily obeys, and downloads everything you need to construct that ref, and puts a pointer to the commit you want under .git/FETCH_HEAD . You can follow that up with git merge FETCH_HEAD into a branch you want to test it in, but that merge commit message looks a bit weird. Also, if you’re reviewing a lot of pull requests, this gets tedious. There’s also a way to fetch all of the pull requests, and keep them up to date whenever you connect to the remote. Open up .git/config in your favorite editor, and look for the origin remote. It should look a bit like this: [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* That line that begins with fetch = is a “refspec.” It’s a way of mapping names on the remote with names in your local .git directory. This particular one tells Git, "the things on the remote that are under refs/heads should go in my local repository under refs/remotes/origin ." You can modify this section to add another refspec: [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* That last line tells Git, “All the refs that look like refs/pull/123/head should be stored locally like refs/remotes/origin/pr/123 .” Now, if you save that file, and do a git fetch : $ git fetch # … * [new ref] refs/pull/1/head -> origin/pr/1 * [new ref] refs/pull/2/head -> origin/pr/2 * [new ref] refs/pull/4/head -> origin/pr/4 # … Now all of the remote pull requests are represented locally with refs that act much like tracking branches; they’re read-only, and they update when you do a fetch. This makes it super easy to try the code from a pull request locally: $ git checkout pr/2 Checking out files: 100% (3769/3769), done. Branch pr/2 set up to track remote branch pr/2 from origin. Switched to a new branch 'pr/2' The eagle-eyed among you would note the head on the end of the remote portion of the refspec. There’s also a refs/pull/#/merge ref on the GitHub side, which represents the commit that would result if you push the “merge” button on the site. This can allow you to test the merge before even hitting the button. Pull Requests on Pull Requests Not only can you open Pull Requests that target the main or master branch, you can actually open a Pull Request targeting any branch in the network. In fact, you can even target another Pull Request. If you see a Pull Request that is moving in the right direction and you have an idea for a change that depends on it or you’re not sure is a good idea, or you just don’t have push access to the target branch, you can open a Pull Request directly to it. When you go to open a Pull Request, there is a box at the top of the page that specifies which branch you’re requesting to pull to and which you’re requesting to pull from. If you hit the “Edit” button at the right of that box you can change not only the branches but also which fork. Малюнак 117. Manually change the Pull Request target fork and branch Here you can fairly easily specify to merge your new branch into another Pull Request or another fork of the project. Mentions and Notifications GitHub also has a pretty nice notifications system built in that can come in handy when you have questions or need feedback from specific individuals or teams. In any comment you can start typing a @ character and it will begin to autocomplete with the names and usernames of people who are collaborators or contributors in the project. Малюнак 118. Start typing @ to mention someone You can also mention a user who is not in that dropdown, but often the autocompleter can make it faster. Once you post a comment with a user mention, that user will be notified. This means that this can be a really effective way of pulling people into conversations rather than making them poll. Very often in Pull Requests on GitHub people will pull in other people on their teams or in their company to review an Issue or Pull Request. If someone gets mentioned on a Pull Request or Issue, they will be “subscribed” to it and will continue getting notifications any time some activity occurs on it. You will also be subscribed to something if you opened it, if you’re watching the repository or if you comment on something. If you no longer wish to receive notifications, there is an “Unsubscribe” button on the page you can click to stop receiving updates on it. Малюнак 119. Unsubscribe from an Issue or Pull Request The Notifications Page When we mention “notifications” here with respect to GitHub, we mean a specific way that GitHub tries to get in touch with you when events happen and there are a few different ways you can configure them. If you go to the “Notification center” tab from the settings page, you can see some of the options you have. Малюнак 120. Notification center options The two choices are to get notifications over “Email” and over “Web” and you can choose either, neither or both for when you actively participate in things and for activity on repositories you are watching. Web Notifications Web notifications only exist on GitHub and you can only check them on GitHub. If you have this option selected in your preferences and a notification is triggered for you, you will see a small blue dot over your notifications icon at the top of your screen as seen in Notification center . Малюнак 121. Notification center If you click on that, you will see a list of all the items you have been notified about, grouped by project. You can filter to the notifications of a specific project by clicking on its name in the left hand sidebar. You can also acknowledge the notification by clicking the checkmark icon next to any notification, or acknowledge all of the notifications in a project by clicking the checkmark at the top of the group. There is also a mute button next to each checkmark that you can click to not receive any further notifications on that item. All of these tools are very useful for handling large numbers of notifications. Many GitHub power users will simply turn off email notifications entirely and manage all of their notifications through this screen. Email Notifications Email notifications are the other way you can handle notifications through GitHub. If you have this turned on you will get emails for each notification. We saw examples of this in Comments sent as email notifications and Email notification of a new Pull Request . The emails will also be threaded properly, which is nice if you’re using a threading email client. There is also a fair amount of metadata embedded in the headers of the emails that GitHub sends you, which can be really helpful for setting up custom filters and rules. For instance, if we look at the actual email headers sent to Tony in the email shown in Email notification of a new Pull Request , we will see the following among the information sent: To: tonychacon/fade <fade@noreply.github.com> Message-ID: <tonychacon/fade/pull/1@github.com> Subject: [fade] Wait longer to see the dimming effect better (#1) X-GitHub-Recipient: tonychacon List-ID: tonychacon/fade <fade.tonychacon.github.com> List-Archive: https://github.com/tonychacon/fade List-Post: <mailto:reply+i-4XXX@reply.github.com> List-Unsubscribe: <mailto:unsub+i-XXX@reply.github.com>,... X-GitHub-Recipient-Address: tchacon@example.com There are a couple of interesting things here. If you want to highlight or re-route emails to this particular project or even Pull Request, the information in Message-ID gives you all the data in <user>/<project>/<type>/<id> format. If this were an issue, for example, the <type> field would have been “issues” rather than “pull”. The List-Post and List-Unsubscribe fields mean that if you have a mail client that understands those, you can easily post to the list or “Unsubscribe” from the thread. That would be essentially the same as clicking the “mute” button on the web version of the notification or “Unsubscribe” on the Issue or Pull Request page itself. It’s also worth noting that if you have both email and web notifications enabled and you read the email version of the notification, the web version will be marked as read as well if you have images allowed in your mail client. Special Files There are a couple of special files that GitHub will notice if they are present in your repository. README The first is the README file, which can be of nearly any format that GitHub recognizes as prose. For example, it could be README , README.md , README.asciidoc , etc. If GitHub sees a README file in your source, it will render it on the landing page of the project. Many teams use this file to hold all the relevant project information for someone who might be new to the repository or project. This generally includes things like: What the project is for How to configure and install it An example of how to use it or get it running The license that the project is offered under How to contribute to it Since GitHub will render this file, you can embed images or links in it for added ease of understanding. CONTRIBUTING The other special file that GitHub recognizes is the CONTRIBUTING file. If you have a file named CONTRIBUTING with any file extension, GitHub will show Opening a Pull Request when a CONTRIBUTING file exists when anyone starts opening a Pull Request. Малюнак 122. Opening a Pull Request when a CONTRIBUTING file exists The idea here is that you can specify specific things you want or don’t want in a Pull Request sent to your project. This way people may actually read the guidelines before opening the Pull Request. Project Administration Generally there are not a lot of administrative things you can do with a single project, but there are a couple of items that might be of interest. Changing the Default Branch If you are using a branch other than “master” as your default branch that you want people to open Pull Requests on or see by default, you can change that in your repository’s settings page under the “Options” tab. Малюнак 123. Change the default branch for a project Simply change the default branch in the dropdown and that will be the default for all major operations from then on, including which branch is checked out by default when someone clones the repository. Transferring a Project If you would like to transfer a project to another user or an organization in GitHub, there is a “Transfer ownership” option at the bottom of the same “Options” tab of your repository settings page that allows you to do this. Малюнак 124. Transfer a project to another GitHub user or Organization This is helpful if you are abandoning a project and someone wants to take it over, or if your project is getting bigger and want to move it into an organization. Not only does this move the repository along with all its watchers and stars to another place, it also sets up a redirect from your URL to the new place. It will also redirect clones and fetches from Git, not just web requests. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://www.sushi.com/stake | Trade Explore Positions Stake Sushi Bar For every swap on Sushi, a portion of the swap fee is locked into the liquidity pool awaiting to be served to xSUSHI holders. APY (1m) Network Ethereum XSUSHI 0x8798...4272 Learn More Your Voting Power 0 SUSHI POWAH Delegate Manage Manage your position in the Sushi Bar. Stake Unstake Stake SUSHI XSUSHI Your Balance $0.00 Staked XSUSHI 0 $0.00 Available SUSHI 0 $0.00 APR Total Supply 1D 1W 1M 1Y All Ethereum Connect Wallet Connect Stake | Sushi 🍣 | 2026-01-13T09:29:25 |
https://git-scm.com/book/zh/v2/%e6%9c%8d%e5%8a%a1%e5%99%a8%e4%b8%8a%e7%9a%84-Git-GitWeb | Git - GitWeb 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.7 服务器上的 Git - GitWeb GitWeb 如果你对项目有读写权限或只读权限，你可能需要建立起一个基于网页的简易查看器。 Git 提供了一个叫做 GitWeb 的 CGI 脚本来做这项工作。 Figure 49. GitWeb 的网页用户界面 如果你想要查看 GitWeb 如何展示你的项目，并且在服务器上安装了轻量级 Web 服务器比如 lighttpd 或 webrick ， Git 提供了一个命令来让你启动一个临时的服务器。 在 Linux 系统的电脑上， lighttpd 通常已经安装了，所以你只需要在项目目录里执行 git instaweb 命令即可。 如果你使用 Mac 系统， Mac OS X Leopard 系统已经预安装了 Ruby，所以 webrick 或许是你最好的选择。 如果不想使用 lighttpd 启动 instaweb 命令，你需要在执行时加入 --httpd 参数。 $ git instaweb --httpd=webrick [2009-02-21 10:02:21] INFO WEBrick 1.3.1 [2009-02-21 10:02:21] INFO ruby 1.8.6 (2008-03-03) [universal-darwin9.0] 这个命令启动了一个监听 1234 端口的 HTTP 服务器，并且自动打开了浏览器。 这对你来说十分方便。 当你已经完成了工作并想关闭这个服务器，你可以执行同一个命令，并加上 --stop 选项： $ git instaweb --httpd=webrick --stop 如果你现在想为你的团队或你托管的开源项目持续的运行这个页面，你需要通过普通的 Web 服务器来设置 CGI 脚本。 一些 Linux 发行版的软件库有 gitweb 包，可以通过 apt 或 dnf 来安装，你可以先试试。 接下来我们来快速的了解一下如何手动安装 GitWeb。 首先，你需要获得 Git 的源代码，它包含了 GitWeb ，并可以生成自定义的 CGI 脚本： $ git clone git://git.kernel.org/pub/scm/git/git.git $ cd git/ $ make GITWEB_PROJECTROOT="/srv/git" prefix=/usr gitweb SUBDIR gitweb SUBDIR ../ make[2]: `GIT-VERSION-FILE' is up to date. GEN gitweb.cgi GEN static/gitweb.js $ sudo cp -Rf gitweb /var/www/ 需要注意的是，你需要在命令中指定 GITWEB_PROJECTROOT 变量来让程序知道你的 Git 版本库的位置。 现在，你需要在 Apache 中使用这个 CGI 脚本，你需要为此添加一个虚拟主机： <VirtualHost *:80> ServerName gitserver DocumentRoot /var/www/gitweb <Directory /var/www/gitweb> Options +ExecCGI +FollowSymLinks +SymLinksIfOwnerMatch AllowOverride All order allow,deny Allow from all AddHandler cgi-script cgi DirectoryIndex gitweb.cgi </Directory> </VirtualHost> 再次提醒，GitWeb 可以通过任何一个支持 CGI 或 Perl 的网络服务器架设；如果你需要的话，架设起来应该不会很困难。 现在，你可以访问 http://gitserver/ 在线查看你的版本库。 prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://www.artistechmedia.com/mixterplus-license | MixterPlus License — ARTisTECH MEDIA Home ccMixter Artists About Contact Welcome MixterPlus MixterPlus FAQ Why MixterPlus? MixterPlus License MixterPlus Terms of Use MixterPlus Privacy Policy Dreaming Together Event ARTisTECH MEDIA Home ccMixter Artists About Contact Welcome MixterPlus MixterPlus FAQ Why MixterPlus? MixterPlus License MixterPlus Terms of Use MixterPlus Privacy Policy Dreaming Together Event MixterPlus License (BETA): Community Use -- free on MixterPlus . MixterPlus community members may download, adapt and remix any MixterPlus upload to share on MixterPlus. We Give Credit to each artist in the remix tree and Group Copyright applies to every collaboration. Content Creator Use -- free on social media . Creators can use MixterPlus tracks in their social media projects for free. MixterPlus will claim our artists’ portion of such projects through Content ID without a copyright strike. This process Gives Credit to our artists and ensures our music remains open for creators to use. Add-on Licenses Professional Use -- royalty-free license for monetized projects . A Professional Use License can be purchased for a project that generates income (sponsored channel, branded media, fundraiser, advertisement, ebook, podcast, videogame, website, music release on Spotify, Apple Music, etc.). The licensee is exempt from paying royalties, but venues/platforms may be responsible for public performance royalties. Email us to get this license. Venue Use: Restaurants, stores, theatres, and other venues can purchase a Venue Use License. Royalty exemptions are issued on your behalf with Performing Rights Organizations (PRO). Email us for more information. Back To Top Powered by Squarespace Cart ( 0 ) | 2026-01-13T09:29:25 |
https://ko-kr.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.meta.ai%252Fpages%252Frinnai-tankless-water-heaters-top-models%252F%253Futm_source%253Dfoa_web_footer%26amp%253Bh%3DAT1iDzpS1eFAsDVI5dqc_Jr6I7GOYbAu-zP1B61xCNJYLL76OIwYZ7PcVnf5VK3DyKf4yMM3BQFArU3QTxnGGNGO7pGOk-PsbGzX5Sa8a2qh7wVqGlpkj2x6Zfpzln-1YygrJhwby9sIL6A2 | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 새 계정 만들기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:29:25 |
https://babelfish.money/xmlrpc.php?rsd | Babelfish – BabelFish BABELFISH Github Docs Forum Launch Dapp X sun (Traced) crescent-moon-phase-shape-with-two-stars (Traced)2022 BABELFISH Github Docs Analytics X LAUNCH DAPP UNIVERSAL MULTI-CHAIN STABLECOIN BabelFish's mind-boggling objective is to aggregate and distribute stablecoins, enhance flow, and push hyperBitcoinization. ABOUT BabelFish DAO Money Protocol is the simplest and most mind-bogglingly useful thing in the DeFi Universe. It absorbs, aggregates and distributes USD-pegged stablecoins across chains; the practical upshot of all this is that if you stick stablecoins to it, you can neatly cross the language divide between any chains. BabelFish's meta-stablecoin, XUSD, is backed by the underlying aggregated stablecoins to leverage and enhance their combined flow and utility across protocols and users. FISH holders can vote on improvement proposals, such as which stablecoins to accept, or what percent of collateral to lend. Learn More About It GO TO OUR GITBOOK What It Does What It Does: Since the big bang of DeFi in the crypto galaxy, many stablecoin projects have been created to meet the demand for USD. Different stablecoin brands with unique selling points are competing to represent the same dollar, but they do not translate 1:1, and crypto dollar liquidity is fractured between issuers and protocols. As DeFi markets expand beyond Ethereum to multiple chains, stablecoin liquidity is fractured further by the bridges used, which is suboptimal for the industry. BabelFish abstracts away these differences by aggregating stablecoins from multiple isolated liquidity lakes and providing users with access to the combined ocean of crypto-dollars available. Think of it as a translator or a converter: if a user wants to use crypto dollars on another chain, she can stick it on BabelFish and seamlessly get a par-value equivalent on the other side. What Is The FISH DAO The BabelFish DAO Money Protocol is ultimately directed by the will of FISH token holders participating in governance. From protocol improvement proposals to budget allocation and partnerships, it is the community that will be able to decide on the direction of the protocol. If you are passionate about the stablecoin ecosystem, this is the DAO for you. Help define protocol rules and parameters around the collateral accepted, discuss community incentives, manage risk, and much more. The future of BabelFish depends on active FISH holder participation. Help build, shape and enhance the stablecoin ecosystem. Participate in stablecoin collateral management. Be rewarded for staking and actively participating with FISH in governance. Mind-Bogglingly Useful XUSD is collateralized 1:1 by a hedged basket of accepted stablecoins across chains, which enables users and protocols to tap into the combined liquidity and utility of the underlying collateral and also enhances stablecoin flow across the ecosystem. User deposits an accepted stablecoin on BabelFish protocol. Protocol issues XUSD, its convertible stablecoin backed 1:1 User can use XUSD on accepted protocols, bridge between chains, and redeem back at any time What Moves BabelFish The need for a "trustless stablecoin translation device" seems painfully clear. The accelerated growth and velocity of crypto dollars is unstoppable, we expect demand for programmable money to continue accelerating as we onboard the first billion users. But the market remains fragmented, two players dominate >80% of the total USD-stablecoin float, and systemic and idiosyncratic risks abound. In the decentralised economy we ought not to rely on one or two issuers of USD-stablecoins but rather enable a thousand stablecoins to bloom and communicate with each other to bring mass adoption. For BabelFish DAO Money Protocol it is important that our first product, XUSD, is the safest, easiest and ultimate stablecoin instrument out there in crypto space. JOIN US TO EXPERIENCE BABELFISH | 2026-01-13T09:29:25 |
https://git-scm.com/book/gr/v2/%ce%94%ce%b9%ce%b1%ce%ba%ce%bb%ce%b1%ce%b4%cf%8e%cf%83%ce%b5%ce%b9%cf%82-%cf%83%cf%84%ce%bf-Git-%ce%9f%ce%b9-%ce%ba%ce%bb%ce%ac%ce%b4%ce%bf%ce%b9-%ce%bc%ce%b5-%ce%bb%ce%af%ce%b3%ce%b1-%ce%bb%cf%8c%ce%b3%ce%b9%ce%b1 | 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 3.1 Διακλαδώσεις στο Git - Οι κλάδοι με λίγα λόγια Σχεδόν κάθε VCS διαθέτει κάποιας μορφής μηχανισμό διακλάδωσης. Διακλάδωση σημαίνει ότι αποκλίνετε από την κύρια γραμμή ανάπτυξης ώστε να μπορείτε να συνεχίσετε να εργάζεστε χωρίς να την επηρεάζετε. Σε πολλά εργαλεία VCS, η διακλάδωση είναι μία σχετικά ακριβή διαδικασία με την έννοια ότι συχνά απαιτεί τη δημιουργία αντιγράφου του φακέλου στον οποίο βρίσκεται ο πηγαίος κώδικας, κάτι που μπορεί να είναι χρονοβόρο για μεγάλα έργα. Κάποιοι θεωρούν ότι το μοντέλο διακλάδωσης του Git είναι το μεγαλύτερο προτέρημά του και πάντως είναι σίγουρα κάτι που κάνει το Git να ξεχωρίζει στην κοινότητα των VCS. Γιατί είναι τόσο ξεχωριστό; Ο τρόπος με τον οποίο το Git δημιουργεί διακλαδώσεις είναι απίστευτα ελαφρύς, κάτι που καθιστά τις εργασίες διακλάδωσης σχεδόν στιγμιαίες και τη μετάβαση από τον έναν κλάδο στον άλλο εξίσου γρήγορη. Σε αντίθεση με πολλά άλλα VCS, το Git ενθαρρύνει έναν τρόπο εργασίας κατά τον οποίο διακλαδώσεις και συγχωνεύσεις γίνονται συχνά, ακόμα και πολλές φορές μέσα σε μία ημέρα. Η κατανόηση και ευχέρεια στη χρήση αυτού του χαρακτηριστικού θα σας εφοδιάσει με ένα ισχυρό και μοναδικό εργαλείο, που μπορεί να αλλάξει ολοκληρωτικά τον τρόπο με τον οποίο αναπτύσσετε εφαρμογές. Οι κλάδοι με λίγα λόγια Για να κατανοήσουμε πραγματικά τον τρόπο με τον οποίο το Git υλοποιεί τις διακλαδώσεις, πρέπει πρώτα να εξετάσουμε τον τρόπο με τον οποίο το Git αποθηκεύει τα δεδομένα. Όπως ίσως θυμόμαστε από την ενότητα Τι είναι το Git; , το Git δεν αποθηκεύει τα δεδομένα ως μία ακολουθία αλλαγών ή διαφορών αλλά ως μία ακολουθία στιγμιότυπων (snapshots). Όταν κάνουμε μία υποβολή (commit), το Git αποθηκεύει ένα αντικείμενο υποβολής που περιέχει έναν δείκτη προς το στιγμιότυπο του περιεχομένου που έχει υποβληθεί. Αυτό το αντικείμενο περιέχει επίσης το όνομα και e-mail του συγγραφέα, το μήνυμα που έχουμε πληκτρολογήσει καθώς και δείκτες προς την υποβολή ή τις υποβολές που προηγήθηκαν ακριβώς πριν από αυτή την υποβολή (δηλαδή, τον γονέα ή τους γονείς της): όταν ένα αρχείο υποβάλλεται για πρώτη φορά, τότε δεν έχει κανέναν γονέα· μία συνηθισμένη υποβολή έχει έναν γονέα, ενώ μία υποβολή που προέκυψε από τη συγχώνευση δύο ή περισσότερων κλάδων έχει περισσότερους από έναν γονέα. Για να το οπτικοποιήσουμε λίγο, ας υποθέσουμε ότι έχουμε έναν κατάλογο που περιέχει τρία αρχεία, τα οποία έχουμε προσθέσει στο στάδιο καταχώρησης και στη συνέχεια υποβάλλουμε (commit). Κατά την προσθήκη των αρχείων στο στάδιο καταχώρησης υπολογίζονται τα αθροίσματα ελέγχου (checksums) των αρχείων (με τον αλγόριθμο SHA-1, που αναφέρθηκε στην ενότητα Τι είναι το Git; ), αποθηκεύονται οι συγκεκριμένες εκδόσεις των αρχείων στο αποθετήριο Git (το Git ονομάζει αυτές τις εκδόσεις blobs ) και προσθέτει τα αθροίσματα ελέγχου στο στάδιο καταχώρησης. $ git add README test.rb LICENSE $ git commit -m 'Initial commit' Όταν κάνουμε την υποβολή, τρέχοντας την εντολή git commit , το Git υπολογίζει ένα άθροισμα ελέγχου για καθέναν υποκατάλογο (στη συγκεκριμένη περίπτωση μόνο για τον βασικό κατάλογο του έργου) και τους αποθηκεύει ως αντικείμενα δομής δένδρου στο αποθετήριο Git. Στη συνέχεια το Git δημιουργεί ένα αντικείμενο υποβολής που περιέχει τα μεταδεδομένα και έναν δείκτη στη βάση του δένδρου του έργου, ώστε να μπορεί να επαναδημιουργήσει το στιγμιότυπο, όταν χρειαστεί. Πλέον το αποθετήριό μας περιέχει πέντε αντικείμενα: τρία blob για τα περιεχόμενα των αρχείων (ένα blob για κάθε αρχείο), μία δομή δένδρου που καταγράφει τα περιεχόμενα του καταλόγου και προσδιορίζει ποιο αρχείο αντιστοιχίζεται σε ποιο blob και ένα αντικείμενο commit που περιέχει τον δείκτη στον βασικό κατάλογο και όλα τα μεταδεδομένα της υποβολής. Figure 9. Μια υποβολή και το δένδρο της Αν κάνουμε μερικές αλλαγές και τις υποβάλλουμε, η επόμενη υποβολή αποθηκεύει έναν δείκτη στην ακριβώς προηγούμενη υποβολή. Figure 10. Υποβολές (commits) και οι γονείς τους. Οι κλάδοι του Git είναι απλά μετακινήσιμοι δείκτες σε υποβολές. Το προεπιλεγμένο όνομα κλάδου στο Git είναι master (κύριος κλάδος). Όταν ξεκινάμε να κάνουμε υποβολές, μας δίνεται ένας κλάδος master που δείχνει στην τελευταία υποβολή που κάναμε. Κάθε φορά που υποβάλλουμε, ο κλάδος master προχωρά αυτόματα. Note Ο κλάδος “master” στο Git δεν είναι κάποιος ειδικός κλάδος. Είναι ακριβώς το ίδιο με οποιονδήποτε άλλο κλάδο. Ο μόνος λόγος για τον οποίο σχεδόν κάθε αποθετήριο έχει έναν κλάδο master είναι επειδή η εντολή git init τον ονομάζει έτσι και οι περισσότεροι χρήστες του Git δεν ασχολούνται με το να τον αλλάξουν. Figure 11. Ένας κλάδος και το ιστορικό υποβολών του Δημιουργία νέου κλάδου Τι γίνεται όταν δημιουργούμε έναν νέο κλάδο; Αυτό που συμβαίνει είναι ότι δημιουργείται ένα νέος δείκτης τον οποίο μπορούμε να μετακινούμε από δω κι από κει. Ας πούμε ότι δημιουργούμε έναν νέο κλάδο που ονομάζεται testing . Αυτό γίνεται με την εντολή git branch : $ git branch testing Αυτή η εντολή δημιουργεί έναν νέο δείκτη στην υποβολή στην οποία βρισκόμαστε αυτή τη στιγμή. Figure 12. Δύο κλάδοι που δείχνουν στην ίδια ακολουθία υποβολών Πώς όμως γνωρίζει το Git σε ποιον κλάδο βρισκόμαστε τώρα; Το γνωρίζει επειδή διατηρεί έναν ειδικό δείκτη που ονομάζεται HEAD . Σημειώνουμε ότι αυτός ο δείκτης HEAD είναι πολύ διαφορετικός από την έννοια του HEAD με την οποία είμαστε ενδεχομένως εξοικειωμένοι σε άλλα VCS, όπως το Subversion ή το CVS. Στο Git αυτός είναι ένας δείκτης στον τοπικό κλάδο στον οποίο στον οποίο βρισκόμαστε αυτή τη στιγμή. Στη συγκεκριμένη περίπτωση, βρισκόμαστε ακόμα στον κλάδο master . Η εντολή git branch απλά δημιούργησε έναν νέο κλάδο — δεν μετέβη σε αυτό τον κλάδο. Figure 13. Ο δείκτης HEAD δείχνει σε έναν κλάδο Αυτό μπορούμε να το διαπιστώσουμε εύκολα τρέχοντας την εντολή git log που παραθέτει πού δείχνουν οι δείκτες των κλάδων. Η επιλογή ονομάζεται`--decorate`, $ git log --oneline --decorate f30ab (HEAD -> master, testing) Add feature #32 - ability to add new formats to the central interface 34ac2 Fix bug #1328 - stack overflow under certain conditions 98ca9 Initial commit Βλέπουμε τους κλάδους “master” και “testing” που βρίσκονται δίπλα στην υποβολή f30ab . Μετάβαση σε άλλο κλάδο Για να μεταβούμε σε έναν ήδη υπάρχοντα κλάδο, τρέχουμε την εντολή git checkout . Ας μεταβούμε στον νέο κλάδο testing : $ git checkout testing Η εντολή αυτή μετατοπίζει τον δείκτη HEAD ώστε να δείχνει στον κλάδο testing . Figure 14. Ο HEAD δείχνει στον τρέχοντα κλάδο. Ποια είναι η σημασία αυτού του πράγματος; Ας κάνουμε ακόμα μία υποβολή: $ vim test.rb $ git commit -a -m 'Make a change' Figure 15. Ο κλάδος HEAD μετακινείται ότι γίνεται μία υποβολή Αυτό είναι ενδιαφέρον, διότι τώρα ο νέος μας κλάδος testing έχει προχωρήσει, αλλά ο κλάδος master ακόμα δείχνει στην υποβολή που βρισκόμασταν όταν είχαμε τρέξει την εντολή git checkout για να αλλάξουμε κλάδο. Ας επιστρέψουμε στον κλάδο master : $ git checkout master Note Η εντολή git log δεν δείχνει όλους τους κλάδους πάντα Αν εκτελούσατε git log τώρα, θα αναρωτιόσασταν πού πήγε ο κλάδος "testing" που μόλις δημιουργήσατε, αφού δεν θα εμφανιζόταν στην έξοδο της εντολής. Ο κλάδος δεν έχει εξαφανιστεί· το Git δεν γνωρίζει ότι ενδιαφέροσαστε για αυτόν τον κλάδο και προσπαθεί να σας δείξει μόνο αυτό για το οποίο νομίζει ότι σας ενδιαφέρει. Με άλλα λόγια, εξ ορισμού, η git log θα σας δείξει το ιστορικό υποβολών του κλάδου τον οποίο έχουμε κάνει checked out. Για να δείτε όλο το ιστορικό υποβολών για τον κλάδο που θέλουμε, πρέπει να το πούμε ρητά: git log testing . Για να δείτε το ιστορικό όλων των κλάδων, προσθέστε και το --all στην εντολή git log . Figure 16. Ο δείκτης HEAD μετακινείται όταν εκτελούμε checkout Αυτή η εντολή έκανε δύο πράγματα: Μετατόπισε τον δείκτη HEAD ώστε να ξαναδείχνει στον κλάδο master και επανέφερε τα αρχεία στον τρέχοντα κατάλογο στο στιγμιότυπο που δείχνει ο κλάδος master'. Αυτό σημαίνει επίσης ότι όποιες αλλαγές κάνουμε από αυτό το σημείο και μετά θα αποκλίνουν από μια παλιότερη έκδοση του έργου. Ουσιαστικά αναιρεί όποιες αλλαγές έχουμε κάνει στον κλάδο `testing ώστε να μπορέσουμε να κινηθούμε σε μία διαφορετική κατεύθυνση. Note Η μετάβαση από έναν κλάδο σε άλλον αλλάζει τα αρχεία στον κατάλογο εργασίας === Είναι σημαντικό να τονιστεί ότι όταν μετακινείστε από έναν κλάδο σε άλλο στο Git, τα αρχεία στον τρέχοντα κατάλογο αλλάζουν. Αν μεταβείτε σε κάποιον παλιότερο κλάδο, ο τρέχων κατάλογος θα επαναφερθεί στην κατάσταση στην οποία βρισκόταν την τελευταία φορά που είχατε κάνει κάποια υποβολή σε αυτό τον κλάδο. Αν το Git δεν μπορεί να το κάνει χωρίς προβλήματα, δεν θα σας επιτρέψει να μεταβείτε σε αυτό τον κλάδο. === Ας κάνουμε μερικές ακόμα αλλαγές και να τις υποβάλλουμε: $ vim test.rb $ git commit -a -m 'Make other changes' Τώρα το ιστορικό του έργου έχει αποκλίνει (βλ. Αποκλίνον ιστορικό ). Δημιουργήσαμε έναν κλάδο, μεταβήκαμε σε αυτόν, κάναμε κάποιες αλλαγές και μετά επιστρέψαμε στον κύριο κλάδο μας και κάναμε κάποιες άλλες αλλαγές. Οι αλλαγές αυτές είναι απομονωμένες σε διαφορετικούς κλάδους: μπορούμε να μεταπηδούμε από τον έναν κλάδο στον άλλο και να τους συγχωνεύσουμε όταν είμαστε έτοιμοι. Και όλα αυτά τα καταφέρνουμε με απλές εντολές branch , checkout και commit . Figure 17. Αποκλίνον ιστορικό Αυτό μπορούμε επίσης να το δούμε εύκολα με την εντολή git log . Αν εκτελέσουμε την εντολή git log --oneline --decorate --graph --all θα εκτυπωθεί το ιστορικό των υποβολών στο οποίο θα φαίνεται πού βρίσκονται οι δείκτες των κλάδων μας και με ποιον τρόπο έχει αποκλίνει το ιστορικό. $ git log --oneline --decorate --graph --all * c2b9e (HEAD, master) Make other changes | * 87ab2 (testing) Make a change |/ * f30ab Add feature #32 - ability to add new formats to the central interface * 34ac2 Fix bug #1328 - stack overflow under certain conditions * 98ca9 Initial commit of my project Επειδή ένας κλάδος στο Git είναι στην πραγματικότητα ένα αρχείο που περιέχει τους 40 χαρακτήρες του αθροίσματος ελέγχου SHA-1 της υποβολής στην οποία δείχνει, η δημιουργία και καταστροφή κλάδων είναι μία φθηνή διαδικασία. Η δημιουργία ενός κλάδου είναι τόσο γρήγορη και απλή όσο το να γράφονται 41 byte σε ένα αρχείο (40 αλφαριθμητικοί χαρακτήρες και ένας χαρακτήρας αλλαγής γραμμής). Αυτή είναι μία σημαντική διαφορά σε σχέση με τον τρόπο με τον οποίο τα περισσότερα παλιότερα VCS δημιουργούν κλάδους, που περιλαμβάνει την αντιγραφή όλων των αρχείων του έργου σε έναν άλλο κατάλογο. Αυτό μπορεί να διαρκέσει αρκετά δευτερόλεπτα ή ακόμα και λεπτά, ανάλογα με το μέγεθος του έργου, ενώ στο Git η διαδικασία είναι σχεδόν στιγμιαία. Επιπλέον, επειδή σε κάθε υποβολή καταγράφονται οι γονείς της, η εύρεση μίας κατάλληλης βάσης για συγχώνευση γίνεται αυτόματα και γενικά πολύ εύκολα. Αυτά τα χαρακτηριστικά ενθαρρύνουν τους προγραμματιστές να δημιουργούν και να χρησιμοποιούν κλάδους συχνά. Ας δούμε γιατί πρέπει να το κάνουμε αυτό. Note Δημιουργία κλάδου και μετάβαση σε αυτόν με τη μία Είναι σύνηθες όταν δημιουργείτε έναν κλάδο να θέλετε να μεταβείτε σε αυτόν άμεσα — αυτό μπορεί να γίνει με την εκτέλεση μίας μόνο εντολής, της git checkout -b <newbranchname> . Note Από την έκδοση 2.23 του Git και μετά, μπορείτε να χρησιμοποιήσετε την git switch αντί για git checkout ώστε: Να μεταβείτε σε έναν προϋπάρχοντα κλάδο: git switch testing-branch . Να δημιουργήσετε έναν νέο κλάδο και να μεταβείτε σε αυτόν: git switch -c new-branch . Η σημαία -c σημαίνει create, μπορείτε επίσης να χρησιμοποιήσετε την πλήρη σημαία: --create . Να επιστρέψετε στον αμέσως προηγούμενο κλάδο που είχατε κάνει checkout: git switch - . prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#discover-by-profile-url | Pinterest API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Pinterest API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Discover by Keywords Posts API Collect by URL Discover by Profile URL Discover by Keywords Social Media APIs Pinterest API Scrapers Copy page Copy page Overview The Pinterest API Suite offers multiple types of APIs, each designed for specific data collection needs from Pinterest. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Discover by Keywords. Interesting Columns : name , following_count , website , follower_count . Posts API This API allows users to collect multiple posts based on a single input. Discovery functionality : - Discover by profile URL. - Discover by Keywords. Interesting Columns : title , content , user_name , likes . Profiles API Collect by URL This API allows users to retrieve detailed Pinterest profile information using the provided profile URL. Input Parameters : URL string required The Pinterest profile URL. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metrics : following_count , follower_count , boards_num , saved . Additional Information : last_updated , posts_page_url , discovery_input . This API allows users to collect detailed insights into a Pinterest profile, including user statistics, engagement metrics, and profile information. Discover by Keywords This API allows users to discover Pinterest profiles based on a specified keyword. Input Parameters : keyword string required The keyword to search for profiles. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metric s: following_count , follower_count , boards_num , saved. Additional Information : last_updated , posts_page_url , discovery_input . This API enables users to find Pinterest profiles related to a specific keyword, offering insights into user statistics, engagement, and profile details. Posts API Collect by URL This API allows users to collect detailed post data from a specific Pinterest post using the provided post URL. Input Parameters : URL string required The Pinterest post URL. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , post_type . For all data points, click here . User Details : user_name , user_url , user_id , followers . Post Metrics : likes , comments_num , comments , categories . Media & Attachments : image_video_url , video_length , attached_files . Hashtags & Discovery : hashtags , discovery_input . This API allows users to retrieve detailed insights into a specific Pinterest post, including user engagement, post content, media, and other related information. Discover by Profile URL This API allows users to retrieve posts from a specific Pinterest profile based on the provided profile URL. Input Parameters : URL string required The Pinterest profile URL from which to collect posts. num_of_posts number The number of posts to collect. If omitted, there is no limit. posts_to_not_include array An array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date ). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date ). Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users tso collect posts from a specific Pinterest profile, allowing for filtering by date, exclusion of specific posts, and retrieval of detailed post data including media, comments, and engagement metrics. Discover by Keywords This API allows users to discover Pinterest posts based on a specific keyword, enabling efficient content discovery. Input Parameters : keyword string required The keyword to search for posts, such as “food” or any other relevant term. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users to search for Pinterest posts based on a specific keyword, providing detailed insights into the content, engagement, media, and associated metrics for efficient discovery. Was this page helpful? Yes No Twitter Quora ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://babelfish.money/feed/ | Babelfish – BabelFish BABELFISH Github Docs Forum Launch Dapp X sun (Traced) crescent-moon-phase-shape-with-two-stars (Traced)2022 BABELFISH Github Docs Analytics X LAUNCH DAPP UNIVERSAL MULTI-CHAIN STABLECOIN BabelFish's mind-boggling objective is to aggregate and distribute stablecoins, enhance flow, and push hyperBitcoinization. ABOUT BabelFish DAO Money Protocol is the simplest and most mind-bogglingly useful thing in the DeFi Universe. It absorbs, aggregates and distributes USD-pegged stablecoins across chains; the practical upshot of all this is that if you stick stablecoins to it, you can neatly cross the language divide between any chains. BabelFish's meta-stablecoin, XUSD, is backed by the underlying aggregated stablecoins to leverage and enhance their combined flow and utility across protocols and users. FISH holders can vote on improvement proposals, such as which stablecoins to accept, or what percent of collateral to lend. Learn More About It GO TO OUR GITBOOK What It Does What It Does: Since the big bang of DeFi in the crypto galaxy, many stablecoin projects have been created to meet the demand for USD. Different stablecoin brands with unique selling points are competing to represent the same dollar, but they do not translate 1:1, and crypto dollar liquidity is fractured between issuers and protocols. As DeFi markets expand beyond Ethereum to multiple chains, stablecoin liquidity is fractured further by the bridges used, which is suboptimal for the industry. BabelFish abstracts away these differences by aggregating stablecoins from multiple isolated liquidity lakes and providing users with access to the combined ocean of crypto-dollars available. Think of it as a translator or a converter: if a user wants to use crypto dollars on another chain, she can stick it on BabelFish and seamlessly get a par-value equivalent on the other side. What Is The FISH DAO The BabelFish DAO Money Protocol is ultimately directed by the will of FISH token holders participating in governance. From protocol improvement proposals to budget allocation and partnerships, it is the community that will be able to decide on the direction of the protocol. If you are passionate about the stablecoin ecosystem, this is the DAO for you. Help define protocol rules and parameters around the collateral accepted, discuss community incentives, manage risk, and much more. The future of BabelFish depends on active FISH holder participation. Help build, shape and enhance the stablecoin ecosystem. Participate in stablecoin collateral management. Be rewarded for staking and actively participating with FISH in governance. Mind-Bogglingly Useful XUSD is collateralized 1:1 by a hedged basket of accepted stablecoins across chains, which enables users and protocols to tap into the combined liquidity and utility of the underlying collateral and also enhances stablecoin flow across the ecosystem. User deposits an accepted stablecoin on BabelFish protocol. Protocol issues XUSD, its convertible stablecoin backed 1:1 User can use XUSD on accepted protocols, bridge between chains, and redeem back at any time What Moves BabelFish The need for a "trustless stablecoin translation device" seems painfully clear. The accelerated growth and velocity of crypto dollars is unstoppable, we expect demand for programmable money to continue accelerating as we onboard the first billion users. But the market remains fragmented, two players dominate >80% of the total USD-stablecoin float, and systemic and idiosyncratic risks abound. In the decentralised economy we ought not to rely on one or two issuers of USD-stablecoins but rather enable a thousand stablecoins to bloom and communicate with each other to bring mass adoption. For BabelFish DAO Money Protocol it is important that our first product, XUSD, is the safest, easiest and ultimate stablecoin instrument out there in crypto space. JOIN US TO EXPERIENCE BABELFISH | 2026-01-13T09:29:25 |
https://www.linkedin.com/products/nxofrance-cybers%C3%A9curit%C3%A9/#main-content | Cybersécurité | LinkedIn Skip to main content LinkedIn NXO France 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 Cybersécurité Secure Web Gateways by NXO France See who's skilled in this Add as skill Contact us Report this product About Afin de répondre aux enjeux critiques de confidentialité, d’intégrité, de traçabilité et de disponibilité toujours plus élevés, il est primordial d’accompagner votre transformation digitale au travers de trois axes : protéger, auditer, connecter. Nos solutions de sécurité pour la mobilité assurent la protection des données sensibles des smartphones et tablettes. Nos solutions pour la sécurité du cloud permettent de contrôler l’accès ou la propreté des données. Les « security analytics » rendent l’entreprise plus proactive et mieux défendue en collectant et reliant tous les événements de sécurité. NXO certifié ExpertCyber, assure votre cyberdéfense. This product is intended for Chief Information Security Officer Information Technology Manager Director of Information Technology Safety Specialist Safety Manager Safety Director Information Technology Security Specialist Information Technology Security Manager Head Information Technology Security Director Information Technology Security Media Products media viewer No more previous content Propositions de valeurs NXO en cybersécurité NXO vous accompagne dans vos solutions de sécurité IT. Découvrez nos propositions de valeurs dans cette vidéo. En savoir plus sur nos offres de cybersécurité : https://www.nxo.eu/cybersecurite/ Contactez-NXO : https://www.nxo.eu/contact/ NXO partenaire Fortinet Fortinet est une entreprise américaine spécialisée dans la conception de solutions de sécurité globale et de haute performance des systèmes d’informations. NXO partenaire Checkpoint Check Point Software Technologies est le leader mondial de la sécurité Internet avec pour objectif de sécuriser et fiabiliser les communications Internet, les données vitales et les rendre disponibles en tout lieu. Fondée en 1993 à Ramat-Gan en Israel, Check Point compte aujourd’hui environ 4 300 employés dans le monde. Ligne de produits : Sécurité réseau, sécurité du cloud, sécurité du mobile Pour plus d’informations, consultez le site internet Check Point. NXO Checkpoint 4 Star Partner NXO partenaire Cisco Cisco & NXO : un partenariat stratégique construit sur la durée ! NXO & Cisco travaillent ensemble sur de nombreux sujets. Ils développent un grand nombre d’offres conjointement, organisent régulièrement des événements et des campagnes. NXO partenaire Proofpoint Proofpoint, Inc. (NASDAQ:PFPT) est une entreprise leader dans le domaine de la cybersécurité qui protège les ressources les plus importantes et les plus à risques des entreprises : leurs collaborateurs. Grâce à une suite intégrée de solutions cloud, Proofpoint aide les entreprises du monde entier à stopper les menaces ciblées, à protéger leurs données et à rendre leurs utilisateurs plus résistants face aux cyberattaques. No more next content Similar products Cisco Umbrella Cisco Umbrella Secure Web Gateways Enterprise Threat Protector Enterprise Threat Protector Secure Web Gateways Accops HySecure Accops HySecure Secure Web Gateways User-First Browser Security Platform User-First Browser Security Platform Secure Web Gateways SmartEdge Secure Web Gateway SmartEdge Secure Web Gateway Secure Web Gateways Reblaze Bot Management Reblaze Bot Management Secure Web Gateways Sign in to see more Show more Show less NXO France products Communication et collaboration Communication et collaboration Cloud Content Collaboration Software NXO CLOUD REPLICATION VEEAM CLOUD CONNECT NXO CLOUD REPLICATION VEEAM CLOUD CONNECT Server Backup Software NXO SOC Protect NXO SOC Protect 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:25 |
https://www.linkedin.com/products/one-network-enterprises-integrated-business-planning-execution/?trk=products_seo_search#main-content | Integrated Business Planning &amp; Execution | LinkedIn Skip to main content LinkedIn One Network Enterprises 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 Integrated Business Planning & Execution Strategic Planning Software by One Network Enterprises See who's skilled in this Add as skill Learn more Report this product About The Integrated Business Planning & Execution solution suite is designed for today’s organizations with complex, globally sourced supply chains. It leverages One Network’s underlying cloud platform— the Digital Supply Chain Network™—to coordinate and synchronize end-customer demand across all internal operations and key trading partners, including contract manufacturers, suppliers, logistics providers, and retailers; it tracks, monitors, and plans continuously and in real time. The Integrated Business Planning & Execution solution includes services for Sales and Operations Planning (S&OP), Business Continuity and Risk Management, Sustainability. Media Products media viewer No more previous content One Network Control Tower Your Entire Supply Chain Digitized: From inbound supply to outbound order fulfillment and logistics, optimize and automate across your entire supply network and every trading partner. The NEO Platform’s intelligent agent technology delivers predictive and prescriptive analytics with real time information to help you lead your industry - for the highest service levels and product quality at lowest cost. Transform your business with the global leader in Supply Chain Control Towers: onenetwork.com No more next content Similar products Focus Focus Strategic Planning Software Aha! Roadmaps Aha! Roadmaps Strategic Planning Software DIGITAL PRODUCTS DIGITAL PRODUCTS Strategic Planning Software Cascade Cascade Strategic Planning Software WorkBoard WorkBoard Strategic Planning Software Stratsys platform for compliance and efficiency Stratsys platform for compliance and efficiency Strategic Planning Software Sign in to see more Show more Show less One Network Enterprises products NEO NEO Supply Chain Management Software Neo Platform Neo Platform Supply Chain Management Software One Network Master Data Management One Network Master Data Management Master Data Management (MDM) Software The Digital Supply Chain Network The Digital Supply Chain Network Supply Chain Management 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:25 |
https://www.linkedin.com/products/opentext-developer-cloud/ | OpenText Developer Cloud | LinkedIn Skip to main content LinkedIn OpenText 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 OpenText Developer Cloud Low-Code Development Platforms by OpenText See who's skilled in this Add as skill Get started Report this product About OpenText Developer Cloud provides access to the full spectrum of information management services. Reduce your development time to connect information sources to business activities. Visit the website for more information and try it for free-no obligations! This product is intended for Software Engineer Product Manager Operations Manager Director of Operations Information Technology Consultant Director of Business Development Chief Technology Officer Application Developer Director of Product Development Chief Product Officer Media Products media viewer No more previous content What is the OpenText OEM Program? Build better technology products with OpenText OEM solutions. The OpenText OEM program allows partners to customize, extend, embed and white-label OpenText technology for use in their own products and services. Job Scheduler – A Developer Service OpenText provides developers with several services to facilitate their work and accelerate time to market. Job Scheduler is one of these services and allows developers to schedule tasks to run automatically, reducing manual work, overhead and providing time back. Content metadata for Developers A short video that provides Developers a brief description of the functionalities and benefits of using Content Metadata Microservices when building EIM applications No more next content Similar products Salesforce Platform Salesforce Platform Low-Code Development Platforms Zoho Creator Zoho Creator Low-Code Development Platforms ServiceNow App Engine ServiceNow App Engine Low-Code Development Platforms Spring Boot Spring Boot Low-Code Development Platforms Amdocs Low-Code Experience Platform Amdocs Low-Code Experience Platform Low-Code Development Platforms OutSystems OutSystems Low-Code Development Platforms Sign in to see more Show more Show less OpenText products OpenText Business Network Cloud OpenText Business Network Cloud Supply Chain Management Software OpenText Content Cloud OpenText Content Cloud Cloud Content Collaboration Software OpenText Experience Cloud OpenText Experience Cloud Customer Experience Management Software OpenText Security & Protection Cloud OpenText Security & Protection Cloud Endpoint Protection Systems 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:25 |
https://git-scm.com/book/zh-tw/v2/%e4%bc%ba%e6%9c%8d%e5%99%a8%e4%b8%8a%e7%9a%84-Git-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. 開始 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.8 伺服器上的 Git - GitLab GitLab GitWeb is pretty simplistic though. If you’re looking for a more modern, fully featured Git server, there are some several open source solutions out there that you can install instead. As GitLab is one of the more popular ones, we’ll cover installing and using it as an example. This is a bit more complex than the GitWeb option and likely requires more maintenance, but it is a much more fully featured option. 安裝 GitLab is a database-backed web application, so its installation is a bit more involved than some other git servers. Fortunately, this process is very well-documented and supported. There are a few methods you can pursue to install GitLab. To get something up and running quickly, you can download a virtual machine image or a one-click installer from https://bitnami.com/stack/gitlab , and tweak the configuration to match your particular environment. One nice touch Bitnami has included is the login screen (accessed by typing alt-→); it tells you the IP address and default username and password for the installed GitLab. 圖表 50. The Bitnami GitLab virtual machine login screen. For anything else, follow the guidance in the GitLab Community Edition readme, which can be found at https://gitlab.com/gitlab-org/gitlab-ce/tree/master . There you’ll find assistance for installing GitLab using Chef recipes, a virtual machine on Digital Ocean, and RPM and DEB packages (which, as of this writing, are in beta). There’s also “unofficial” guidance on getting GitLab running with non-standard operating systems and databases, a fully-manual installation script, and many other topics. 管理員權限 GitLab’s administration interface is accessed over the web. Simply point your browser to the hostname or IP address where GitLab is installed, and log in as an admin user. The default username is admin@local.host , and the default password is 5iveL!fe (which you will be prompted to change as soon as you enter it). Once logged in, click the “Admin area” icon in the menu at the top right. 圖表 51. The “Admin area” item in the GitLab menu. 使用者 Users in GitLab are accounts that correspond to people. User accounts don’t have a lot of complexity; mainly it’s a collection of personal information attached to login data. Each user account comes with a namespace , which is a logical grouping of projects that belong to that user. If the user jane had a project named project , that project’s url would be http://server/jane/project . 圖表 52. The GitLab user administration screen. Removing a user can be done in two ways. “Blocking” a user prevents them from logging into the GitLab instance, but all of the data under that user’s namespace will be preserved, and commits signed with that user’s email address will still link back to their profile. “Destroying” a user, on the other hand, completely removes them from the database and filesystem. All projects and data in their namespace is removed, and any groups they own will also be removed. This is obviously a much more permanent and destructive action, and its uses are rare. 群組 A GitLab group is an assemblage of projects, along with data about how users can access those projects. Each group has a project namespace (the same way that users do), so if the group training has a project materials , its url would be http://server/training/materials . 圖表 53. The GitLab group administration screen. Each group is associated with a number of users, each of which has a level of permissions for the group’s projects and the group itself. These range from “Guest” (issues and chat only) to “Owner” (full control of the group, its members, and its projects). The types of permissions are too numerous to list here, but GitLab has a helpful link on the administration screen. 專案 A GitLab project roughly corresponds to a single git repository. Every project belongs to a single namespace, either a user or a group. If the project belongs to a user, the owner of the project has direct control over who has access to the project; if the project belongs to a group, the group’s user-level permissions will also take effect. Every project also has a visibility level, which controls who has read access to that project’s pages and repository. If a project is Private , the project’s owner must explicitly grant access to specific users. An Internal project is visible to any logged-in user, and a Public project is visible to anyone. Note that this controls both git “fetch” access as well as access to the web UI for that project. 掛句 GitLab includes support for hooks, both at a project or system level. For either of these, the GitLab server will perform an HTTP POST with some descriptive JSON whenever relevant events occur. This is a great way to connect your git repositories and GitLab instance to the rest of your development automation, such as CI servers, chat rooms, or deployment tools. 基本使用 The first thing you’ll want to do with GitLab is create a new project. This is accomplished by clicking the “+” icon on the toolbar. You’ll be asked for the project’s name, which namespace it should belong to, and what its visibility level should be. Most of what you specify here isn’t permanent, and can be re-adjusted later through the settings interface. Click “Create Project”, and you’re done. Once the project exists, you’ll probably want to connect it with a local Git repository. Each project is accessible over HTTPS or SSH, either of which can be used to configure a Git remote. The URLs are visible at the top of the project’s home page. For an existing local repository, this command will create a remote named gitlab to the hosted location: $ git remote add gitlab https://server/namespace/project.git If you don’t have a local copy of the repository, you can simply do this: $ git clone https://server/namespace/project.git The web UI provides access to several useful views of the repository itself. Each project’s home page shows recent activity, and links along the top will lead you to views of the project’s files and commit log. 協同工作 The simplest way of working together on a GitLab project is by giving another user direct push access to the git repository. You can add a user to a project by going to the “Members” section of that project’s settings, and associating the new user with an access level (the different access levels are discussed a bit in 群組 ). By giving a user an access level of “Developer” or above, that user can push commits and branches directly to the repository with impunity. Another, more decoupled way of collaboration is by using merge requests. This feature enables any user that can see a project to contribute to it in a controlled way. Users with direct access can simply create a branch, push commits to it, and open a merge request from their branch back into master or any other branch. Users who don’t have push permissions for a repository can “fork” it (create their own copy), push commits to that copy, and open a merge request from their fork back to the main project. This model allows the owner to be in full control of what goes into the repository and when, while allowing contributions from untrusted users. Merge requests and issues are the main units of long-lived discussion in GitLab. Each merge request allows a line-by-line discussion of the proposed change (which supports a lightweight kind of code review), as well as a general overall discussion thread. Both can be assigned to users, or organized into milestones. This section is focused mainly on the Git-related features of GitLab, but as a mature project, it provides many other features to help your team work together, such as project wikis and system maintenance tools. One benefit to GitLab is that, once the server is set up and running, you’ll rarely need to tweak a configuration file or access the server via SSH; most administration and general usage can be accomplished through the in-browser interface. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://www.linkedin.com/uas/login?session_redirect=%2Fservices%2Fproducts%2Fsalesforce-lightning-platform%2F&fromSignIn=true&trk=cold_join_sign_in | 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:25 |
https://www.linkedin.com/products/categories/whiteboard-software | Best Whiteboard 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 Department Manager (2) Chief Digital Officer (2) Marketing Manager (2) Product Manager (2) Salesperson (2) See all products Find top products in Whiteboard Software category Software used to collaborate simultaneously on a digital canvas. - Share and edit idea space in real time with video conferencing and chat - Insert templates, images, and diagrams, and use drawing and annotation tools while presenting - Share screen with multiple contributors and manage review and access rights - Save whiteboards to a central location and export in multiple formats 32 results FigJam Whiteboard Software by Figma An online whiteboard for teams to ideate and brainstorm together. View product Lucidspark Whiteboard Software by Lucid Software Lucidspark is a cloud-based virtual whiteboard where teams can work together creatively in real time. The intuitive digital canvas allows teams to effectively brainstorm, collaborate and align on new ideas, and organize collective thinking into actionable next steps. View product Freehand Whiteboard Software by InVision The all-in-one collaborative workspace where productive teams work. Unlock your team's workflow; Ideate, plan, execute, and track projects all with Freehand. Try Freehand with your team for free – visit www.freehandapp.com View product Aha! Whiteboards Whiteboard Software by Aha! Aha! Whiteboards is the visual space for product innovation — define user flows, create mockups, and collaborate on roadmaps. View product Whiteboard Whiteboard Software by Brightidea Use Brightidea Whiteboard to brainstorm and take ideas into reality by making data-driven decisions that ensure the best ideas win. 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 Digital Whiteboards Whiteboard Software by Core Mobile AI Core Mobile’s Digital Whiteboards allow providers to plan and document patient interventions on tablets and large touch screen displays in recovery wards. View product Collaboard Whiteboard Software by Collaboard Collaboard is a dynamic online whiteboard revolutionizing the way professionals collaborate. Ideal for remote teams and educators, Collaboard offers an intuitive, user-friendly platform for brainstorming, project planning, and interactive learning. With real-time synchronization, diverse drawing tools, and extensive multimedia support, it bridges the gap between in-person and virtual meetings. An extensive set of facilitator tools ensure smooth management of discussions and activities in online meetings and workshops. Collaboard offers the highest security standards. You can choose between 100% GDPR-compliant cloud hosting with European data sovereignty or self-hosting options for on-premises and private cloud. Enhance your team's creativity and efficiency with Collaboard – where ideas come to life. View product Conceptboard – Collaborative and GDPR compliant Online Whiteboard (also available as on-premises) Whiteboard Software by Conceptboard On-Premises Collaboration-Lösung für maximale Datensouveränität und IT-Kontrolle Die Conceptboard Data Center Edition ist die Self-Hosting-Variante unserer digitalen Whiteboard- und Collaboration-Plattform – entwickelt für Unternehmen mit höchsten Anforderungen an Datenschutz, Compliance und IT-Sicherheit. Als On-Premises Software wird Conceptboard vollständig in Deiner eigenen IT-Infrastruktur betrieben – lokal oder im Rechenzentrum Deiner Wahl. Alle Daten bleiben in Deiner Verantwortung – ideal für Organisationen mit sensiblen Informationen, regulierten Branchen oder geschlossenen Netzwerken. Die Lösung ist DSGVO-konform, ISO-zertifiziert und unterstützt die Integration in bestehende Systeme wie SSO, LDAP, Firewalls und Kubernetes. Schnelles Deployment, klare Dokumentation, persönlicher Support – und auf Wunsch vollständig ohne Internetverbindung betreibbar. View product FlatFrog Board Whiteboard Software by FlatFrog Replace the traditional whiteboard in your meeting room with FlatFrog Board and let anyone collaborate from anywhere. FlatFrog Board makes hybrid work easy and equally productive for everyone, wherever you are located In the meeting room FlatFrog Board for Rooms is easy to use and feels and behaves just like an traditional whiteboard. Install the software on a touch display with FlatFrog's InGlass™ touch technology and feel the natural writing experience. View product Conceptboard by IT.NRW – Deutsche Verwaltungscloud Whiteboard Software by Conceptboard Conceptboard is the sovereign collaboration platform for public sector organizations. Whether as a digital whiteboard or a central space for visual teamwork – Conceptboard enables GDPR-compliant, accessible, and federally integrable collaboration in real time. The solution is hosted in Germany and certified according to ISO 27001, 27017, and 27018. Public authorities can procure Conceptboard by IT.NRW easily, securely, and in a legally compliant manner via the German Administrative Cloud (DVC) – or directly from the provider. Ideal for digital participation formats, hybrid project work, or collaborative workshops. Conceptboard helps administrations visualize complexity, streamline decision-making, and enable sovereign digital collaboration – from local governments to federal institutions. 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:25 |
https://www.linkedin.com/products/outsystems/#main-content | OutSystems | LinkedIn Skip to main content LinkedIn OutSystems 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 OutSystems Low-Code Development Platforms by OutSystems See who's skilled in this Add as skill Learn more Report this product About The OutSystems platform is the best way to crush your backlog by building enterprise-grade, mission-critical software in a fraction of the time. Now you can use low-code and GenAI to improve and accelerate every part of the software development lifecycle. Bye-bye, backlog. Hello, world. This product is intended for Developer Information Technology Manager Chief Technology Officer Director of Information Technology Chief Information Officer Application Developer Vice President Information Technology Application Development Manager Vice President of Application Development App Developer Media Products media viewer No more previous content OutSystems Platform Overview in 2 Minutes Interested in app development but growing weary of hand coding? How does it all work? Step up to OutSystems and learn how to create and manage large app portfolios to reach millions of users of desktop, web and mobile! Learn more here about how to build apps fast, right and for the future with OutSystems: https://www.outsystems.com/platform/ Mentor: Your AI partner for app generation Use GenAI to generate apps instantly, automate the entire SDLC, and say goodbye to busywork. Mentor leads the way as the first full SDLC digital worker, transforming app generation, delivery, and monitoring using low-code, generative AI (GenAI), and AI-driven guidance. From app creation and automating repetitive tasks to streamlining code reviews and automatic security checks, Mentor ensures fast, error-free, secure application deployment every time. Generative AI and the future of software development Our CEO Paulo Rosado reveals how low-code and Generative AI are shaping the future of software development. Dive into the unveiling of OutSystems Mentor, the industry’s first digital worker for the complete software development lifecycle. Hear firsthand from Oceaneering and Sport Lisboa e Benfica on their transformative use of OutSystems in enterprise solutions. No more next content Featured customers of OutSystems Bosch Software Development 1,600,877 followers Tamkeen Government Administration 46,306 followers Carrefour Retail 1,370,253 followers The HEINEKEN Company Food and Beverage Services 2,703,523 followers KeyBank Banking 122,781 followers Crown Prosecution Service Law Practice 141,201 followers Oceaneering Oil and Gas 628,999 followers Toyota Motor Corporation Motor Vehicle Manufacturing 2,293,377 followers INCM Imprensa Nacional - Casa da Moeda Printing Services 21,380 followers Morgan, Lewis & Bockius LLP Law Practice 78,705 followers Show more Show less Similar products Salesforce Platform Salesforce Platform Low-Code Development Platforms Zoho Creator Zoho Creator Low-Code Development Platforms ServiceNow App Engine ServiceNow App Engine Low-Code Development Platforms Spring Boot Spring Boot Low-Code Development Platforms Amdocs Low-Code Experience Platform Amdocs Low-Code Experience Platform Low-Code Development Platforms OpenText Developer Cloud OpenText Developer Cloud Low-Code Development Platforms Sign in to see more 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:25 |
https://www.linkedin.com/uas/login?session_redirect=%2Fservices%2Fproducts%2Foutsystems%2F&fromSignIn=true&trk=products_details_guest_nav-header-signin | 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:25 |
https://www.linkedin.com/products/workvivo--the-employee-experience-app/?trk=products_details_guest_similar_products_section_similar_products_section_product_link_result-card_image-click#main-content | Workvivo by Zoom | LinkedIn Skip to main content LinkedIn Workvivo by Zoom 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 Workvivo by Zoom Employee Communications Software by Workvivo by Zoom See who's skilled in this Add as skill Request demo Report this product About The employee experience app that brings your entire company together This product is intended for Chief Executive Officer Chief Human Resources Officer Chief People Officer Head of Human Resources Vice President Human Resources Chief Information Officer Chief Digital Officer Chief Communications Officer Head of Internal Communication Director Internal Communications Media Products media viewer No more previous content Workvivo - The Employee Experience App No more next content Featured customers of Workvivo by Zoom Amazon Software Development 36,032,701 followers Exos Wellness and Fitness Services 91,499 followers Evri Transportation, Logistics, Supply Chain and Storage 76,173 followers RSK Group Environmental Services 81,054 followers Virgin Venture Capital and Private Equity Principals 320,544 followers Keyloop Software Development 97,081 followers Madison Square Garden Entertainment Corp. Entertainment 110,136 followers AIB Banking 135,994 followers Morgan McKinley Staffing and Recruiting 953,603 followers Everton Football Club Spectator Sports 74,196 followers Clipper Logistics plc Warehousing and Storage 28,043 followers Kent Engineering Services 434,815 followers Hoover Institution, Stanford University Think Tanks 43,478 followers Bupa UK Hospitals and Health Care 401,734 followers Dollar General Retail 366,895 followers Hearst Networks EMEA Broadcast Media Production and Distribution 15,095 followers Bus Éireann Ground Passenger Transportation 9,885 followers Kenvue Personal Care Product Manufacturing 454,789 followers Ryanair - Europe's Favourite Airline Airlines and Aviation 866,771 followers Show more Show less Similar products Zoho Cliq Zoho Cliq Employee Communications Software HCL Sametime HCL Sametime Employee Communications Software Flip Flip Employee Communications Software Poppulo Poppulo Employee Communications Software Staffbase Staffbase Employee Communications Software Firstup Firstup Employee Communications Software Sign in to see more 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:25 |
https://twitter.com/intent/tweet?text=%22%F0%93%85%AA%20Huginn%3A%20A%20Discord%20Bot%20for%20My%20Valheim%20Server%20~%20felt%20too%20lazy%20to%20click%20on%20bash%20script%20%E2%80%94%20so%20made%20a%20bot%20%3B3%22%20by%20Pratyush%20Soni%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fpratyush_soni_853633e1553%2Fhuginn-a-discord-bot-for-my-valheim-server-felt-too-lazy-to-click-on-bash-script-so-made-a-42l8 | 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:25 |
https://git-scm.com/book/uz/v2/Git-%d0%b0%d1%81%d0%be%d1%81%d0%bb%d0%b0%d1%80%d0%b8-%d0%8e%d0%b7%d0%b3%d0%b0%d1%80%d0%b8%d1%88%d0%bb%d0%b0%d1%80%d0%bd%d0%b8-%d0%be%d0%bc%d0%b1%d0%be%d1%80%d0%b3%d0%b0-%d1%91%d0%b7%d0%b8%d1%88 | 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 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 2.2 Git асослари - Ўзгаришларни омборга ёзиш Ўзгаришларни омборга ёзиш Шундай қилиб сизда Git нинг ҳақиқий омбори ва қандайдир лойиҳа учун ишчи файллар нусҳаси мавжуд. Сиз лойиҳа билан ишлаш давомида керакли жойда сақлаш пайтида бир қанча ўзгаришлар ва ушбу ўзгаришларни ҳолатини “суръат” (snapshots)га олиб фиксирлашингиз керак. Эсда тутинг ишчи каталогигингиздаги ҳар бир файл икки ҳолатдан бирида: талқин кузатуви остида ёки кузатилмаётган ҳолатда. Кузатилаётган файллар – бу лойиҳанинг охирги формадаги ҳолати файллари (snapshot). Улар ўзгартирилмаган, ўзгартирилган ёки жўнатиш учун тайёрланган(staged) бўлиши мумкин. Кузатилмайдиган файллар бу ишчи каталогингиздаги кузатилаётган файлларга кирмайдиган қолган барча файллардир. Қачон сиз биринчи бор омборни клондаштирсангиз, барча файллар кузатилаётган ва ўзгартирилмаган бўлади, чунки сиз уларни эндигина сақланувчи омбордан олдингиз (checked them out) ва ҳеч нимани ўзгартирганингиз йўқ. Сиз файлларни таҳрирлашингиз биланоқ Git уларни ўзгаотирилганлар деб қарай бошлайди. Чунки сиз охирги жўнатилгандан кейин яна ўзгартириш киритган ҳисобланаябсиз. Сиз ушбу ўзгаришларни индекслайсиз(stage) ва кейин барча индекланган ўзгаришларни фиксирлайсиз, шу тарзда жараён такрорланади. Бу жараённинг тасвири қуйида келтирилган: Figure 8. Сизнинг файлларингизни иш жараёнидаги ҳолатларининг цикл ҳолати. Файлларингиз ҳолатини аниқлаш Қайси файл қанақа ҳолатда эканлигини аниқлаш учун асосий ускуна – git status. Агар сиз клонлаштириш сўнг дарров ушбу командани ишлатсангиз қуйидаги кабиларни кўришингиз мумкин: $ git status On branch master nothing to commit, working directory clean Бу сизни каталогингиз тоза эканлигидан бошқача қилиб айтганда эса каталогда кузатилаётган ўзгартирилган файллар йўқ эканлигидан дарак беради. Git шунингдек кузатилмаётган файлларни ҳам топа олгани йўқ, акс ҳолда улар акс этган бўларди. Ва ниҳоят, команда сиз айни вақтда қайси ирмоқ (branch) да эканлигингизни ҳам кўрсатади. Хозирча бу ирмоқ доим “master” - одатий тарзда қабул қилинган, бу бўлимда бу муҳим эмас. Навбатдаги Git да тармоқланиш бўлимда ирмоқ ва мурожатлар ҳақида батафсилроқ гапириб берилади. Тасаввур қилайлик сиз лойиҳангизга янги файл қўшдингиз, оддий README файл. Агар ушбу файл олдин бўлмаган бўлса ва сиз git status ни бажарсангиз кузатилмаётган файл ҳақидаги қуйидаги маълумотни кўришингиз мумкин: $ echo 'My Project' > README $ git status On branch master Untracked files: (use "git add <file>..." to include in what will be committed) README nothing added to commit but untracked files present (use "git add" to track) Сиз янги README файл кузатилмаётган эканлигини уни “ntracked files” бўлимидаги (секциясидаги) рўйҳатдан кўриб билишингиз мумкин. Одатда кузатилмаётган файл тарзида Git аввалги ҳолатда тасдиқланганлар ичида топа олмаган файлларни назарда тутади. Git га уларни сизни коммит(тасдиқларингизга)ларингизга қўшиш кераклиги ҳақидаги буйруқни бермаганингизча қўшмайди. Бу сизни тасодифан генерация қилинган иккилик файлларини ёки сиз хоҳламаган файлларни омборга қўшилиб кетишининг олдини олади. Сиз README файлини қўшишни хоҳлаябсизми келинг унда буни амалга оширамиз. Янги файлларни кузатиш Янги файлни кузатишни бошлаш учун (талқинлар кузатуви остига олиш учун) git add командаси ишлатилади. README файлини кузатишни бошлаш учун қуйидагини бажаришингиз керак: $ git add README Агар сиз яна status командасини берсангиз README файл кузатилаётган ва индексланганлигини кўришингиз мумкин: $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Файлни индексланганлар рўйҳатида эканлигини уни “Changes to be committed” бўлимидаги (секциясидаги) рўйҳатда кўриб билишингиз мумкин. Агар сиз ушбу вақтда жўнатиш (коммит) буйруғини берсангиз, у ҳолда git add командаси ёрдамида қўшилган файл талқини ҳолатлар тарихи суръатига қўшилади. Сизни эсингизда бўлса керак, аввалги бўлимларда git init командасини бажаргандан кейин git add (files) командасини бажарган эдингиз. Ушбу буйруқ каталогингиздаги файлларни талқинлар кузатуви остига олиш мақсадида берилган эди. git add команда параметр сифатида файл ёки каталог йўлини қабул қилади ва агар у каталог бўлса рекурсив усулда ундаги барча файлларни индекслаб чиқади. Ўзгартирилган файлларни индекслаш Келинг талқинлар кузатуви отида бўлган файлга ўзгартириш киритамиз. Агар сиз кузатилаётган файл “CONTRIBUTING.md” ни ўзгартирсангиз сўнг status командасини ишлатсангиз у ҳолда натижа тахминан қуйидагича бўлади: $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Файл “CONTRIBUTING.md” “Changed but not updated” - бўлими (секцияси) ичида ётибди, бу эса ишчи каталогдаги файл ўзгартирилганлигини лекин ҳалигача индексланмаганлигини билдиради. Уни индекслаш учун git add (бу кўп функцияли команда талқинларни кузатуви остига янги файлларни қўшишни ва шунинг билан биргаликда бошқа мақсадларда масалан ўзгартирилган файлларни омбордаги билан бирлаштириш вақтида келиб чиққан тафовут (конфликт) ларда қайси файлни қўшиш кераклигини кўрсатишда ишлатилади) командасини бажариш керак. “CONTRIBUTING.md” файлини индекслаш учун git add командасини бажарамиз, сўнг git status командасини берамиз: $ git add CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Энди иккала файл ҳам индексланган ва улар навбатдаги жўнатиш(коммит) учун тайёр. Фараз қилайлик сиз шу онда CONTRIBUTING.md файл учун киритиладиган битта катта бўлмаган ўзгартиришни эслаб қолдингиз ва уни фиксирлашдан олдин амалга оширмоқчисиз. Сиз файлни очасиз ўзгартирш киритиб сақлаб ёпасиз ва гўёки ҳаммаси жўнатишга тайёрдай. Лекин, келинг git status командаси ёрдамида ростдан ҳам шундаймикан текшириб кўрамиз: $ vim CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Нима бўлди? Қизиқ, энди CONTRIBUTING.md файл икки секцияда ҳам индексланган ҳам индексланмаганлар рўйҳатида акс этиб турибди. Бу қандай бўлиши мумкин? Бундай вазият Git нинг файлларни аниқ ҳолатини яъни охирги бор берилган git add командасидаги ҳолатни индекслашини яна бир бор намойиш қилади. Агар сиз хозир юборишни (коммит) амалга оширсангиз, CONTRIBUTING.md файлнинг охирги бор git add командаси ёрдамида қўшилган ўзгартиришлари жўнатилиб git commit вақтидаги ҳолати жўнатилмайди. Сиз git add командасидан кейин ўзгартириш киритган бўлсангиз файлни охирги талқинини индекслаш учун яна git add командасини бажаришингизга тўғри келади: $ git add CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Қисқа ҳолат git status командаси натижаси тўлиқ ҳолатни кўрсатса у яна бошқа маънода ҳам ишлатилиши мумкин. Git яна қисқа ҳолат белисига эга бўлганлиги боис сиз киритган ўзгаришларингизни янада ихчамроқ кўринишда кўришингиз мумкин. Агар сиз git status -s ёки git status --short командасини чақирсангиз сиз янада яхлитланган натижани оласиз. $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt Янги файллар кузатилмаётганлари ?? дан кейин, янги файлларни жўнатишга қўшилганлари A дан кейин, ўзгартирилган файллар M ва хокозо каби келтирилади. Натижа иккита майдонда чиқарилган бўлиб, чап томондаги майдон уни жўнатишга қўшилганлигини ва ўнг томондаги майдон ўзгартирилганлигини билдиради. Масалан, ушбу натижадаги README файлини ҳолатини олсак, у ўзгартирилган аммо жўнатишга тайёрланмаган, lib/simplegit.rb файли эса ҳам ўзгартирилган ҳам жўнатишга қўшилганлигини билдиради. Rakefile файли ўзгартирилган, жўнатишга қўшилган, сўнгра яна ўзгартирилган шу сабабли у жўнатишга қўшилган ва қўшилмаганлигини англатувчи устунлари иккисида ҳам ўзгаришлар бор ҳолатда. Файлларни ҳисобга олмаслик Қисман бўлсада сизда автоматик тарзда омборга қўшилишини ва нафақат қўшилишини балким уларни кузатилувчилар рўйҳатида ҳам кўришни истамаган файллар мавжуд бўлади. Бундай файлларга автоматик тарзда генерация қилинадиган файллар киради (турли хил журналлар, дастур йиғилиш натижалари ва ҳок.). Шундай вазиятларда сиз ана шу каби файллар учун яратилган шаблонларни ўз ичига оладиган .gitignore файлни яратишингиз мумкин. Мана .gitignore файл мисол тариқасида келтирилган: $ cat .gitignore *.[oa] *~ Биринчи қатор Git га кодларни йиғиш давомида пайдо бўладиган объектли ёки архивли, “.o” ёки “.a” билан тугайдиган ихтиёрий файлларни ҳисобга олмасликни англатади. Иккинчи қатор тильда ( ~ ) билан тугайдиган барча файлларни ҳисобга олмасликни англатади. Бундай файллар кўпгина матнни таҳрирловчи дастурларда масалан Emacs дастурида вақтинчалик яратилган файлларни номлашда ишлатилади. Сиз шунингдек каталогларни (log, tmp ёки pid), автоматик яратиладиган ҳужжатларни ва бошқа турдаги файл ва каталогларни ҳам қўшишингиз мумкин. Яхши амалиётдан маълумки, ишга жиддий киришишдан олдин .gitignore файлини созлаш - омборга у ерда кўришни хоҳламаган файлларни тасодифан қўшилишидан сақлайди. .gitignore файлида яратилаётган шаблонлар учун қуйидагича қоида қўлланилади: Бўш ва # белги билан бошланувчи сатрлар ҳисобга олинмайди. Стандарт glob шаблонларни қўллаш мумкин. Шаблонни каталогни кўрсатиш мақсадида ( / ) белги билан тугатиш мумкин. Акс амални билдирувчи ундов( ! ) белгисини қўллаб шаблонга кирмайдиганлар рўйҳатини олиш мумкин. Glob шаблонлар бошқарувчи ифодалар тилида ёзилан содда командалар интерпретаторларидан ташкил топган. * белги 0 ёки ундан ортиқ белгига мос келади; [abc] кетма-кетлик қавс ичидаги ихтиёрий белгидан биронтасига (айни мисолда a , b ёки c ); сўроқ белгиси ( ? ) битта белгига мос келади; [0-9] интервалдаги ихтиёрий белгига мос келади (ушбу ҳолатда 0 дан 9 гача). Сиз бир гуруҳ каталоглар учун яна иккита юлдузча (asterisk) белгисини ишлатишингиз мумкин; a/**/z эҳтимол a/z , a/b/z , a/b/c/z кабиларга мосликни ўрнатиш учун ишлатилар. Мана яна .gitignore файлидан мисол: *.a # номи .a билан тугайдиган файлларни ҳисобга олмаслик !lib.a # Лекин lib.a файлини кузатиш керак гарчан биз .a билан тугайдиган #барча файлларни ҳисобга олмасликни буюрсакда /TODO # бош каталогда жойлашган фақат TODO файлни ҳисобга олмаслик бу # subdir/TODO каби файлларга тааллуқли эмас build/ # build/ каталогидаги барча файлларни ҳисобга олмаслик doc/*.txt # doc/notes.txt файлини ҳисобга олмаслик, лекин doc/server/arch.txt # файлига бу тааллуқли эмас Tip GitHub ўзида сиз лойиҳа яратишни бошлаган вақтингизда сизга ва кўпгина лойиҳалар ёки тилларга мисол бўла оладиган тўлиқ рўйҳатга эга бўлган .gitignore файлга https://github.com/github/gitignore эга. Индексланган ва индекланмаган файлларни кўриш Агар git status командаси сизга етарлича маълумот бера олмаса ва сизни қайси файллар ўзгарганлигини билишдан ташқари яна айнан нима ўзгаргани қизиқтирса git diff командасини ишлатишингиз мумкин. Бироз кейинроқ биз git diff командаси ҳақида батафсилроқ маълумот берамиз. Сиз умуман олганда уни иккита саволга жавоб топиш учун ишлатасиз: Нимани мен ўзгартирдим ва индексламадим? Нимани мен индексладим ва қайсиларини фиксирласам бўлади? Агарда git status ушбу саволларга умумлаштирган ҳолатда жавоб берса, git diff командаси бевосита ўзгаришлар (patch) ўзини – қўшилган ва ўчирилган сатрларни кўрсатади. Айтайлик сиз яна README файлини ўзгартирдингиз ва индексладингиз сўнгра CONTRIBUTING.md файлини ўзгартирдингизу лекин индекламадингиз. Агар сиз git status командасини ишлатсангиз сиз яна қуйидаги каби маълумотларни кўришингиз мумкин бўлади: $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Нима ўзгартириш киритганингиз ва нимани индексламаганингизни кўришингиз учун git diff командасини аргументсиз киритинг: $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3cb747f..e445e28 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -36,6 +36,10 @@ def main @commit.parents[0].parents[0].parents[0] end + run_code(x, 'commits 1') do + git.commits.size + end + run_code(x, 'commits 2') do log = git.commits('master', 15) log.size Ушбу команда сизнинг ишчи каталогингизни индексни ичидаги билан солиштиради. Натижа индексланмаган ўзгаришларни кўрсатади. Агар сиз нимани индекслаганингизни ва нималар навбатдаги жўнатишга киришини кўришни хоҳласангиз сиз git diff --staged командасини беришингиз мумкин. Ушбу команда сизнинг индексланган ўзгаришларингизни охирги жўнатишга тайёрланганлар билан солиштиради: $ git diff --staged diff --git a/README b/README new file mode 100644 index 0000000..03902a1 --- /dev/null +++ b/README @@ -0,0 +1,4 @@ +My Project + + This is my project and it is amazing. + Шуни таъкидлаш муҳимки git diff - ўз ўзидан охирги бор жўнатишга тайёрланганлардан кейинги ўзгаришларни кўрсатмайди у фақат индекланмаганларни кўрсатади. Бундай ҳислати уринишларни пучга чиқариши мумкин агарда сиз ҳамма ўзгаришларни индексласангизда ва кейин git diff ҳеч нарса қайтармай турса! Бошқа мисол: айтайлик сиз CONTRIBUTING.md файлни индексладингиз ва кейин ўзгартирдингиз. git diff ни ишлатиб ушбу файлдаги индексланган ўзгартиришларни ва индексланмаганларни кўришингиз мумкин: $ git add CONTRIBUTING.md $ echo '# test line' >> CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Энди сиз git diff ни ишлатган ҳолда индексланмаган ўзгаришларни кўришингиз мумкин $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e445e28..86b2f7c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -127,3 +127,4 @@ end main() ##pp Grit::GitRuby.cache_client.stats +# test line шунингдек индексланганларини ҳам кўришингиз мумкин агарда git diff --cached ни ишлатсангиз: $ git diff --cached diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3cb747f..e445e28 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -36,6 +36,10 @@ def main @commit.parents[0].parents[0].parents[0] end + run_code(x, 'commits 1') do + git.commits.size + end + run_code(x, 'commits 2') do log = git.commits('master', 15) log.size Note Git Diff ташқи дастгоҳларда Биз китобда git diff командасини турли хил йўллар билан ишлатилишини кўришни давом этамиз. Ушбу фарқларга қарашни яна бошқа йўллари бор бўлиб, агар сиз график кўринишни хоҳласангиз ташқи дастурни фарқларни кўриш дастурига алмаштиришингиз керак бўлади. Агар сиз git difftool ни git diff нинг ўрнига алмаштирсангиз, сиз ушбу фарқларни Araxis, emerge, vimdiff ва бошқа кўпгина дастурлардаги каби кўринишда кўришингиз мумкин бўлади. git difftool --tool-help командасини чақириб сизнинг тизимингизда қайси биридан фойдаланиш имкони борлигини кўришингиз мумкин. Ўзгаришларни фиксирлаш Энди индекс хоҳлаганиздек созланганидан кейин сиз ўзгаришларингизни фиксирлашингиз мумкин. Эслаб қолинг ихтиёрий яратилган ёки ўзгартирилган файллар ва таҳрирлашдан сўнг сиз git add командасини ишлатмаган барча индексланмаган файллар бу фиксирлашга кирмайди. Улар сизни дискингизда ўзгартирлган файллар орасида қолади. Бизнинг ҳолатда сиз охирги бор git status`командасини ишлатган вақтингизда кўрдингизки ҳаммаси индексланган.Бу эса сизни фиксирлашга тайёр эканлигингизни билдиради. (((git commands, status))) Сизни ўзгаришларингизни фиксирлашни энг содда усули бу `git commit командасини териш: $ git commit Ушбу команда сиз танлаган матн таҳрирловчисини очади. (Таҳрирловчи тизим ўзгарувчиси $EDITOR билан ўрнатилади. Сиз ўз ёқтирганингизни Иш бошланиши бўлимда кўрсатилганидек git config --global core.editor командаси ёрдамида ўрнатишингиз мумкин бўлсада одатда бу vim ёки emacs бўлади.) Таҳрирловчида қуйидаги матн намойиш этилган бўлади. (бу Vim нинг ойнасидан мисол): # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Changes to be committed: # new file: README # modified: CONTRIBUTING.md # ~ ~ ~ ".git/COMMIT_EDITMSG" 9L, 283C Сиз кўришингиз мумкинки фиксирлашнинг шарҳи одатда git status командаси ишининг натижасининг шарҳларини ва юқоридан битта бўш сатрни ўз ичига олади. Сиз ушбу шарҳларни ўчириб уни ўрнига ўз ҳабарларингизни киритишингиз ёки уларни нимани фиксирлаётганингизни англатиб туриши учун қолдиришингиз мумкин. (Нимани ўзгартирганингизни янада батафсилроқ эсга солиб туриши учун сиз аргумент -v ни git commit командасига беришингиз мумкин. Бу шунга олиб келадики, изоҳда сиз киритган ўзгаришларни фарқи diff ҳам киритилган бўлади. Шу тарзда сиз нималар қилинганини кўришингиз мумкин бўлади.) Қачон сиз таҳрирлаш ойнасидан чиқиб кетар экансиз Git сизнинг фиксирлаганингизни ушбу хабар билан яратади (изоҳлар ва diff ларни чиқаришни ўчирган ҳолда). Бошқа усул – сиз шарҳингизни командалар сатридан қуйидаги мисолда келтирилганидек commit командаси билан биргаликда –m параметридан сўнг ёзиб киритишингиз мумкин: $ git commit -m "Story 182: Fix benchmarks for speed" [master 463dc4f] Story 182: Fix benchmarks for speed 2 files changed, 2 insertions(+) create mode 100644 README Шундай қилиб сиз ўзингизни биринчи фиксирлашингизни яратдингиз! Сиз кўриб турибсизки фиксирлаш командаси сизга кўп бўлмаган ўз ҳақидаги маълумотни кўрсатди:қайси тармоққа сиз фиксирлашни амалга оширдингиз ( master ), ушбу фиксирлаш( 463dc4f )нинг SHA-1 назорат йиғиндиси қанақа, қанча файлларга ўзгартириш киритилди ва шунингдек ушбу фиксирлашда қўшилган/ўчирилган сатрлар статистикасини. Эслаб қолинг фиксирлаш сизни индексингизни суръатини сақлаб қолади. Нимани индекламаган бўлсангиз у ишчи каталогда ўзгартирилганлар орасида ётади; сиз яна битта фиксирлашни амалга ошириб ушбу ўзгаришларни омборга қўшишингиз мумкин. Ҳар сафар қачон сиз фиксирлашни амалга ошираркансиз сиз ўз лойиҳангизни суръатини сақлаб қўясиз, ушбу сақлашлар кейинчалик қайта тиклаш ёки хозирги ҳолат билан солиштириш учун хизмат қилади. Индекслашларни ўтказиб юбориш Индекслаш сиз хоҳлагандек фиксирлашлар учун анча қулайлик яратсада иш жараёнида сиз кутгандан кўпроқ вақт олиши билан бошқача таъсир кўрсатиши мумкин. Агар сизда индекслаш қадамини ташлаб кетиш хоҳиши бўлса, Git сизга оддий учулни тақдим этади. -a параметрини git commit командасига қўшиш Git ни автоматик тарзда охирги фиксирлашдан кейинги кузатилаётган ҳар бир файлни индекслашга буюради ва сизга git add командасини бермасдан фиксирлаш жараёнини амалга ошириш имконини беради: $ git status On branch master Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md no changes added to commit (use "git add" and/or "git commit -a") $ git commit -a -m 'added new benchmarks' [master 83e38c7] added new benchmarks 1 file changed, 5 insertions(+), 0 deletions(-) Шунга эътибор берингки, ушбу ҳолатда сизга “CONTRIBUTING.md” файлини фиксирлашдан олдин git add командасини бериш шарт бўлмади. Файлларни ўчириш Git дан файлларни ўчириш учун уни кузатилаётган файллар орасидан (аниқроқ қилиб айтганда сизнинг индексингиздан ўчириш керак) ўчириш сўнг фиксирлашни амалга ошириш зарур. Буни git rm командаси амалга оширади.Ушбу команда файлингизни ишчи каталогингиздан ҳам ўчиради ва сиз уни кейинги сафар “кузатилаётганлар” орасида ҳам кўрмайсиз. Агар сиз уни оддийгина ишчи каталогидан ўчириб қўя қолсангиз git status бериб биз у (“Ўзгартирилган лекин янгиланмаган” – индексланмаган деб ўқинг) секциясида кўрсатилаётганини кўрамиз: $ rm grit.gemspec $ git status On branch master Changes not staged for commit: (use "git add/rm <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) deleted: grit.gemspec no changes added to commit (use "git add" and/or "git commit -a") Сўнг агар сиз git rm командасини берсангиз файлни ўчириш индексга тушади: $ git rm grit.gemspec rm 'grit.gemspec' $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) deleted: grit.gemspec Навбатдаги фиксирлашдан сўнг файл йўқ бўлиб кетади ва энди кузатилмайди. Агар сиз файлни ўчиришдан олдин уни ўзгартиришга ва индекслашга ҳам улгурган бўлсангиз у ҳолда –f параметри ёрдамида мажбурий ўчириш командасини беришингиз керак бўлади. Бу хавфсизликни ошириш мақсадида қилинган бўлиб, Git дан қайта тиклаб бўлмайдиган ва ҳалигача ҳолатлар суръатига қўшилмаган файлларни беҳосдан ўчиб кетишидан сақлайди. Яна бошқа сиз бажаришни хоҳлашингиз мумкин бўлган жараён борки – бу файлни сизни ишчи каталогингизда қолдирган ҳолатда индексдан ўчириш. Бошқа сўзлар билан айтганда сиз сергак Git кузатувидан файлингизни озод қилиб винчестерингизда қолдиришингиз мумкин. Бу асосан файлингизни .gitignore файлига киритишни ёддан чиқарганингизда ва адашиб бир қанча “лог” ёки компиляциялар бир қанча файлларини индекслаб қўйганингизда фойда беради. Буни амалга ошириш учун --cached опцияни ишлатинг: $ git rm --cached README git rm командасига файлларни, каталогларни ёки glob-шаблонларни бериш мумкин. Бу сизга қуйидагича командаларни амалга ошириш имконини беради: That means you can do things such as $ git rm log/\*.log Note the backslash ( \ ) in front of the * . * дан олдинги тескари слешга(\) эътибор беринг. Бу зарур, чунки Git сиз киритган командаларингиз орасига ўз файллар номи билан ишлаш унсурини ишлатади. Ушбу команда log/ .log кенгайтмали файлларни ўчиради. Ёки сиз бундай қилишингиз мумкин: $ git rm \*~ Ушбу команда барча номи ~ белгиси билан тугайдиган барча файлларни ўчиради. Файлларни бошқа жойга кўчириш Бошқа талқинларни бошқарувчи тизимлар каби Git бевосита файлларнинг кўчирилишини кузатмайди. Агар сиз файлни номини алмаштирсангиз бу ҳақда Git да ҳеч қандай метамаълумот бўлмайди. Бироқ Git файлларни кўчириш жараёнини бўлиб ўтганини аниқлашда етарли даражада ақлли. Биз файлларни кўчиришни аниқлашни бироз кейинроқ кўрамиз. Шу туфайли Git нинг mv командаси бир қанча бошқачароқ кўринишга эга. Агар сиз файл номини алмаштиришни хоҳлаётган бўлсангиз сиз қуйидаги каби йўл тутишингиз мумкин: $ git mv file_from file_to ва бу жуда яхши ишлайди. Аслида, агар сиз шунга ўхшаш командани бажариб сўнг ҳолатни қарасангиз, Git ни файл номини ўзгартириш жараёни бўлиб ўтган деб ҳисоблаётганини кўрасиз: $ git mv README.md README $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Бироқ у қуйидаги командаларни бажарилишига эквивалент: $ mv README.md README $ git rm README.md $ git add README Git қайта номлаш бўлганлигини яққол бўлмаган ҳолатда аниқлайди ва файлни сиз бу усулда номлайсизми ёки mv командасини ишлатиб номлайсизми муҳим эмас. Ягона фарқ шуки mv – учта команданинг ўрнига битта команда сифатида ишлатилаябди ва бу қулайлик учун яратилган фукция. Муҳими бошқа нарса – файл номини ўзгартириш учун сиз ўзингизга қулай услубингизни қўллашингиз ва сўнг фиксирлашдан олдин add/rm командасини ишлатишингиз мумкин. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#profiles-api | Pinterest API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Pinterest API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Discover by Keywords Posts API Collect by URL Discover by Profile URL Discover by Keywords Social Media APIs Pinterest API Scrapers Copy page Copy page Overview The Pinterest API Suite offers multiple types of APIs, each designed for specific data collection needs from Pinterest. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Discover by Keywords. Interesting Columns : name , following_count , website , follower_count . Posts API This API allows users to collect multiple posts based on a single input. Discovery functionality : - Discover by profile URL. - Discover by Keywords. Interesting Columns : title , content , user_name , likes . Profiles API Collect by URL This API allows users to retrieve detailed Pinterest profile information using the provided profile URL. Input Parameters : URL string required The Pinterest profile URL. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metrics : following_count , follower_count , boards_num , saved . Additional Information : last_updated , posts_page_url , discovery_input . This API allows users to collect detailed insights into a Pinterest profile, including user statistics, engagement metrics, and profile information. Discover by Keywords This API allows users to discover Pinterest profiles based on a specified keyword. Input Parameters : keyword string required The keyword to search for profiles. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metric s: following_count , follower_count , boards_num , saved. Additional Information : last_updated , posts_page_url , discovery_input . This API enables users to find Pinterest profiles related to a specific keyword, offering insights into user statistics, engagement, and profile details. Posts API Collect by URL This API allows users to collect detailed post data from a specific Pinterest post using the provided post URL. Input Parameters : URL string required The Pinterest post URL. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , post_type . For all data points, click here . User Details : user_name , user_url , user_id , followers . Post Metrics : likes , comments_num , comments , categories . Media & Attachments : image_video_url , video_length , attached_files . Hashtags & Discovery : hashtags , discovery_input . This API allows users to retrieve detailed insights into a specific Pinterest post, including user engagement, post content, media, and other related information. Discover by Profile URL This API allows users to retrieve posts from a specific Pinterest profile based on the provided profile URL. Input Parameters : URL string required The Pinterest profile URL from which to collect posts. num_of_posts number The number of posts to collect. If omitted, there is no limit. posts_to_not_include array An array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date ). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date ). Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users tso collect posts from a specific Pinterest profile, allowing for filtering by date, exclusion of specific posts, and retrieval of detailed post data including media, comments, and engagement metrics. Discover by Keywords This API allows users to discover Pinterest posts based on a specific keyword, enabling efficient content discovery. Input Parameters : keyword string required The keyword to search for posts, such as “food” or any other relevant term. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users to search for Pinterest posts based on a specific keyword, providing detailed insights into the content, engagement, media, and associated metrics for efficient discovery. Was this page helpful? Yes No Twitter Quora ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://www.linkedin.com/uas/login?session_redirect=%2Fservices%2Fproducts%2Fnotionhq-notion&fromSignIn=true&trk=products_details_guest_nav-header-signin | 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:25 |
https://www.facebook.com/sharer.php?u=https%3A%2F%2Fdev.to%2Fpratyush_soni_853633e1553%2Fhuginn-a-discord-bot-for-my-valheim-server-felt-too-lazy-to-click-on-bash-script-so-made-a-42l8 | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 새 계정 만들기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:29:25 |
https://l.facebook.com/l.php?u=https%3A%2F%2Fwww.instagram.com%2F&h=AT2sWzqx6iRaCW4vof35AgaQ1Y8RkiW8m0_hgvLGU3noCNK_NuQV_IibPZfF097N5g9sVsC_Rh5e02HiWOpzTV-sClK18-gRny_MwS_2ETfgoTuFERBi9PXN05MjYvKv9ZWtuvztGYV6GLPE | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 새 계정 만들기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:29:25 |
https://www.linkedin.com/legal/cookie-policy?session_redirect=%2Fservices%2Fproducts%2Fsalesforce-lightning-platform%2F&trk=registration-frontend_join-form-cookie-policy | Cookie Policy | LinkedIn Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws Cookie Policy Effective on June 3, 2022 At LinkedIn, we believe in being clear and open about how we collect and use data related to you. This Cookie Policy applies to any LinkedIn product or service that links to this policy or incorporates it by reference. We use cookies and similar technologies such as pixels, local storage and mobile ad IDs (collectively referred to in this policy as “cookies”) to collect and use data as part of our Services, as defined in our Privacy Policy (“Services”) and which includes our sites, communications, mobile applications and off-site Services, such as our ad services and the “Apply with LinkedIn” and “Share with LinkedIn” plugins or tags. In the spirit of transparency, this policy provides detailed information about how and when we use these technologies. By continuing to visit or use our Services, you are agreeing to the use of cookies and similar technologies for the purposes described in this policy. What technologies are used? ENTER A SUMMARY Type of technology Description Cookies A cookie is a small file placed onto your device that enables LinkedIn features and functionality. Any browser visiting our sites may receive cookies from us or cookies from third parties such as our customers, partners or service providers. We or third parties may also place cookies in your browser when you visit non-LinkedIn sites that display ads or that host our plugins or tags . We use two types of cookies: persistent cookies and session cookies. A persistent cookie lasts beyond the current session and is used for many purposes, such as recognizing you as an existing user, so it’s easier to return to LinkedIn and interact with our Services without signing in again. Since a persistent cookie stays in your browser, it will be read by LinkedIn when you return to one of our sites or visit a third party site that uses our Services. Session cookies last only as long as the session (usually the current visit to a website or a browser session). Pixels A pixel is a tiny image that may be embedded within web pages and emails, requiring a call (which provides device and visit information) to our servers in order for the pixel to be rendered in those web pages and emails. We use pixels to learn more about your interactions with email content or web content, such as whether you interacted with ads or posts. Pixels can also enable us and third parties to place cookies on your browser. Local storage Local storage enables a website or application to store information locally on your device(s). Local storage may be used to improve the LinkedIn experience, for example, by enabling features, remembering your preferences and speeding up site functionality. Other similar technologies We also use other tracking technologies, such as mobile advertising IDs and tags for similar purposes as described in this Cookie Policy. References to similar technologies in this policy includes pixels, local storage, and other tracking technologies. Our cookie tables lists cookies and similar technologies that are used as part of our Services. Please note that the names of cookies and similar technologies may change over time. What are these technologies used for? Below we describe the purposes for which we use these technologies. ENTER SUMMARY Purpose Description Authentication We use cookies and similar technologies to recognize you when you visit our Services. If you’re signed into LinkedIn, these technologies help us show you the right information and personalize your experience in line with your settings. For example, cookies enable LinkedIn to identify you and verify your account. Security We use cookies and similar technologies to make your interactions with our Services faster and more secure. For example, we use cookies to enable and support our security features, keep your account safe and to help us detect malicious activity and violations of our User Agreement. Preferences, features and services We use cookies and similar technologies to enable the functionality of our Services, such as helping you to fill out forms on our Services more easily and providing you with features, insights and customized content in conjunction with our plugins. We also use these technologies to remember information about your browser and your preferences. For example, cookies can tell us which language you prefer and what your communications preferences are. We may also use local storage to speed up site functionality. Customized content We use cookies and similar technologies to customize your experience on our Services. For example, we may use cookies to remember previous searches so that when you return to our services, we can offer additional information that relates to your previous search. Plugins on and off LinkedIn We use cookies and similar technologies to enable LinkedIn plugins both on and off the LinkedIn sites. For example, our plugins, including the "Apply with LinkedIn" button or the "Share" button may be found on LinkedIn or third-party sites, such as the sites of our customers and partners. Our plugins use cookies and other technologies to provide analytics and recognize you on LinkedIn and third-party sites. If you interact with a plugin (for instance, by clicking "Apply"), the plugin will use cookies to identify you and initiate your request to apply. You can learn more about plugins in our Privacy Policy . Advertising Cookies and similar technologies help us show relevant advertising to you more effectively, both on and off our Services and to measure the performance of such ads. We use these technologies to learn whether content has been shown to you or whether someone who was presented with an ad later came back and took an action (e.g., downloaded a white paper or made a purchase) on another site. Similarly, our partners or service providers may use these technologies to determine whether we've shown an ad or a post and how it performed or provide us with information about how you interact with ads. We may also work with our customers and partners to show you an ad on or off LinkedIn, such as after you’ve visited a customer’s or partner’s site or application. These technologies help us provide aggregated information to our customers and partners. For further information regarding the use of cookies for advertising purposes, please see Sections 1.4 and 2.4 of the Privacy Policy . As noted in Section 1.4 of our Privacy Policy, outside Designated Countries , we also collect (or rely on others who collect) information about your device where you have not engaged with our Services (e.g., ad ID, IP address, operating system and browser information) so we can provide our Members with relevant ads and better understand their effectiveness. For further information, please see Section 1.4 of the Privacy Policy . Analytics and research Cookies and similar technologies help us learn more about how well our Services and plugins perform in different locations. We or our service providers use these technologies to understand, improve, and research products, features and services, including as you navigate through our sites or when you access LinkedIn from other sites, applications or devices. We or our service providers, use these technologies to determine and measure the performance of ads or posts on and off LinkedIn and to learn whether you have interacted with our websites, content or emails and provide analytics based on those interactions. We also use these technologies to provide aggregated information to our customers and partners as part of our Services. If you are a LinkedIn member but logged out of your account on a browser, LinkedIn may still continue to log your interaction with our Services on that browser until the expiration of the cookie in order to generate usage analytics for our Services. We may share these analytics in aggregate form with our customers. What third parties use these technologies in connection with our Services? Third parties such as our customers, partners and service providers may use cookies in connection with our Services. For example, third parties may use cookies in their LinkedIn pages, job posts and their advertisements on and off LinkedIn for their own marketing purposes. For an illustration, please visit LinkedIn’s Help Center . Third parties may also use cookies in connection with our off-site Services, such as LinkedIn ad services. Third parties may use cookies to help us to provide our Services. We may also work with third parties for our own marketing purposes and to enable us to analyze and research our Services. Your Choices You have choices on how LinkedIn uses cookies and similar technologies. Please note that if you limit the ability of LinkedIn to set cookies and similar technologies, you may worsen your overall user experience, since it may no longer be personalized to you. It may also stop you from saving customized settings like login information. Opt out of targeted advertising As described in Section 2.4 of the Privacy Policy , you have choices regarding the personalized ads you may see. LinkedIn Members can adjust their settings here . Visitor controls can be found here . Some mobile device operating systems such as Android provide the ability to control the use of mobile advertising IDs for ads personalization. You can learn how to use these controls by visiting the manufacturer’s website. We do not use iOS mobile advertising IDs for targeted advertising. Browser Controls Most browsers allow you to control cookies through their settings, which may be adapted to reflect your consent to the use of cookies. Further, most browsers also enable you to review and erase cookies, including LinkedIn cookies. To learn more about browser controls, please consult the documentation that your browser manufacturer provides. What is Do Not Track (DNT)? DNT is a concept that has been promoted by regulatory agencies such as the U.S. Federal Trade Commission (FTC), for the Internet industry to develop and implement a mechanism for allowing Internet users to control the tracking of their online activities across websites by using browser settings. As such, LinkedIn does not generally respond to “do not track” signals. Other helpful resources To learn more about advertisers’ use of cookies, please visit the following links: Internet Advertising Bureau (US) European Interactive Digital Advertising Alliance (EU) Internet Advertising Bureau (EU) LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (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)) Language | 2026-01-13T09:29:25 |
https://beefy.com/ | Beefy $150 Launch App Multichain Yield Optimizer Earn the highest APYs across 39 chains with safety and efficiency in mind. Launch App View Docs Earn with Beefy Single Asset Liquidity Pools Earning Pools ZAP 1 Stake Invest your token in a Beefy single asset Vault. 2 Earn Beefy stakes the token on an external, interest-bearing platform. 3 Reinvest Your interest is used to purchase more of the asset and reinvested. 4 Autocompound Beefy regularly and automatically repeats the process, saving you time and fees. Our Ecosystem TVL $251.03M Vaults Chains 39 Explore Partners BIFI Token $BIFI is the native revenue-share & governance token for our protocol. BIFI Maxi BIFI holders share in our revenue by staking their BIFI in Beefy Maxi vaults. Earn BIFI BIFI Earnings Pools Staking BIFI in a BIFI Earnings Pool rewards you with native tokens with the platform’s earnings. Earn Native Vote Our Snapshot governance mechanism gives your BIFI voting power in Beefy’s DAO. Vote Fixed-Supply A fixed supply of 80,000 BIFI acts as a control against token inflation. Learn More News Keep up to date with Beefy Quarterly Report Q3 2025 Dive into Beefy's third quarter of 2025 with our latest quarterly report. December 29, 2025 The Scars Of Battle Reflections on recent shockwaves in DeFi and the changes Beefy is implementing to better protect our users. December 23, 2025 5 Years Of Beefy Beefy turns 5 — celebrating billions autocompounded, zero hacks, and nonstop innovation. October 8, 2025 Quarterly Report Q2 2025 Learn more about Beefy's financial performance in the second quarter of 2025. September 25, 2025 View all Articles Proposals News Docs Audit Media Kit Partners | 2026-01-13T09:29:25 |
https://babelfish.gitbook.io/the-babelfish-gitbook | Welcome! | BabelFish.Money bars BabelFish.Money search circle-xmark Ctrl k Welcome! Getting Started 💡 What is BabelFish ⚖️ What does Babelfish Solve 💫 Cross-Chain Multiverse 📊 Balancing Curves 👥 The Team & The Dao 🗺️ Roadmap ❓ FAQ ❗ Risk Tokens 🪙 Staking ⏰ Early unstaking 📜 Governance 🐡 Tokenomics Tutorials & guides 🏦 Connecting Your Wallet 🪐 Bridge 🌉 Using BabelFish Bridge 🚀 Rules for Turbocharging Rootstock's Stablecoin Liquidity Pilot Campaign ✅ Voting 🖥️ Voting Power 🛠️ Troubleshooting 📊 XUSD Statistics Content & Social Media 🗣️ Social Media 📺 Community Calls 🧑🔬 Join us 🏁 Bounties gitbook Powered by GitBook block-quote On this page chevron-down copy Copy chevron-down Welcome! Welcome DeFi Hitchhiker! We are glad that your DeFi-journey brought you to Babelfish! If you still have any questions after your visit here, please do not hesitate to connect with your fellow travelers through our social media . Our community is there to help and support each other and we welcome you with open arms. Next What is BabelFish chevron-right Last updated 3 years ago | 2026-01-13T09:29:25 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=ml | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상� | 2026-01-13T09:29:25 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fpratyush_soni_853633e1553%2Fhuginn-a-discord-bot-for-my-valheim-server-felt-too-lazy-to-click-on-bash-script-so-made-a-42l8&title=%F0%93%85%AA%20Huginn%3A%20A%20Discord%20Bot%20for%20My%20Valheim%20Server%20~%20felt%20too%20lazy%20to%20click%20on%20bash%20script%20%E2%80%94%20so%20made%20a%20bot%20%3B3&summary=Why%20Valheim%3F%28%E2%97%8F%27%E2%97%A1%27%E2%97%8F%29%20%20%20It%E2%80%99s%20been%20a%20while%20%E2%80%94%20I%E2%80%99ve%20been%20playing%20the%20game%20Valheim%20quite%20often%2C...&source=DEV%20Community | 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:25 |
https://git-scm.com/book/es/v2/Git-en-el-Servidor-Resumen | Git - Resumen 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.10 Git en el Servidor - Resumen Resumen Tienes varias opciones para obtener un repositorio Git remoto y ponerlo a funcionar para que puedas colaborar con otras personas o compartir tu trabajo. Mantener tu propio servidor te da control y te permite correr tu servidor dentro de tu propio cortafuegos, pero tal servidor generalmente requiere una importante cantidad de tu tiempo para configurar y mantener. Si almacenas tus datos en un servidor hospedado, es fácil de configurar y mantener; sin embargo, tienes que ser capaz de mantener tu código en los servidores de alguien más, y algunas organizaciones no te lo permitirán. Debería ser un proceso claro determinar que solución o combinación de soluciones es apropiada para ti y para tu organización. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://docs.aws.amazon.com/fr_fr/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-configure-related-telemetry.html | Configuration des noms CloudWatch d'agent, de service et d'environnement pour les entités associées - Amazon CloudWatch Configuration des noms CloudWatch d'agent, de service et d'environnement pour les entités associées - Amazon CloudWatch Documentation Amazon CloudWatch Guide de l’utilisateur Les traductions sont fournies par des outils de traduction automatique. En cas de conflit entre le contenu d'une traduction et celui de la version originale en anglais, la version anglaise prévaudra. Configuration des noms CloudWatch d'agent, de service et d'environnement pour les entités associées L' CloudWatch agent peut envoyer des métriques et des journaux contenant des données d'entité pour soutenir le volet Explore de la CloudWatch console. Le nom du service ou le nom de l'environnement peut être configuré par la configuration JSON de l'CloudWatch agent . Note La configuration de l’agent peut être remplacée. Pour plus de détails sur la manière dont l’agent détermine quelles données envoyer pour les entités associées, consultez Utilisation de l' CloudWatch agent avec la télémétrie associée . Pour les métriques, le paramètre peut être défini au niveau de l’agent, des métriques ou du plugin. Pour les journaux, il peut être défini au niveau de l’agent, des journaux ou du fichier. La configuration la plus spécifique est toujours utilisée. Par exemple, si la configuration existe au niveau de l’agent et au niveau des métriques, les métriques utiliseront la configuration des métriques, et tout le reste (journaux) utilisera la configuration de l’agent. L’exemple suivant montre différentes manières de configurer le nom du service et le nom de l’environnement. { "agent": { "service.name": "agent-level-service", "deployment.environment": "agent-level-environment" }, "metrics": { "service.name": "metric-level-service", "deployment.environment": "metric-level-environment", "metrics_collected": { "statsd": { "service.name": "statsd-level-service", "deployment.environment": "statsd-level-environment", }, "collectd": { "service.name": "collectdd-level-service", "deployment.environment": "collectd-level-environment", } } }, "logs": { "service.name": "log-level-service", "deployment.environment": "log-level-environment", "logs_collected": { "files": { "collect_list": [ { "file_path": "/opt/aws/amazon-cloudwatch-agent/logs/amazon-cloudwatch-agent.log", "log_group_name": "amazon-cloudwatch-agent.log", "log_stream_name": "amazon-cloudwatch-agent.log", "service.name": "file-level-service", "deployment.environment": "file-level-environment" } ] } } } } JavaScript est désactivé ou n'est pas disponible dans votre navigateur. Pour que vous puissiez utiliser la documentation AWS, Javascript doit être activé. Vous trouverez des instructions sur les pages d'aide de votre navigateur. Conventions de rédaction Configurer et configurer la collecte de métriques Prometheus sur les instances Amazon EC2 Démarrez l' CloudWatch agent Cette page vous a-t-elle été utile ? - Oui Merci de nous avoir fait part de votre satisfaction. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer ce qui vous a plu afin que nous puissions nous améliorer davantage. Cette page vous a-t-elle été utile ? - Non Merci de nous avoir avertis que cette page avait besoin d'être retravaillée. Nous sommes désolés de ne pas avoir répondu à vos attentes. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer comment nous pourrions améliorer cette documentation. | 2026-01-13T09:29:25 |
https://docs.aws.amazon.com/id_id/AmazonCloudWatch/latest/monitoring/CloudWatch-ServiceLevelObjectives.html | Tujuan tingkat layanan (SLOs) - Amazon CloudWatch Tujuan tingkat layanan (SLOs) - Amazon CloudWatch Dokumentasi Amazon CloudWatch Panduan Pengguna Konsep-konsep SLO Hitung anggaran kesalahan dan pencapaian untuk berbasis periode SLOs Hitung anggaran kesalahan dan pencapaian berdasarkan permintaan SLOs Hitung laju pembakaran dan atur alarm laju pembakaran secara opsional Membuat SLO Menampilkan dan melakukan penilaian awal pada status SLO Sunting SLO yang ada Menghapus SLO Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Tujuan tingkat layanan (SLOs) Anda dapat menggunakan Sinyal Aplikasi untuk membuat tujuan tingkat layanan untuk layanan untuk operasi atau dependensi bisnis penting Anda. Dengan membuat SLOs layanan ini, Anda akan dapat melacaknya di dasbor SLO, memberi Anda at-a-glance gambaran tentang operasi terpenting Anda. Selain membuat tampilan cepat yang dapat digunakan operator Anda untuk melihat status operasi kritis saat ini, Anda dapat menggunakannya SLOs untuk melacak kinerja jangka panjang layanan Anda, untuk memastikan bahwa mereka memenuhi harapan Anda. Jika Anda memiliki perjanjian tingkat layanan dengan pelanggan, SLOs adalah alat yang hebat untuk memastikan bahwa mereka terpenuhi. Menilai kesehatan layanan Anda dengan SLOs memulai dengan menetapkan tujuan yang jelas dan terukur berdasarkan metrik kinerja utama— indikator tingkat layanan (). SLIs SLO melacak performa SLI terhadap ambang batas dan sasaran yang Anda tetapkan, dan melaporkan seberapa jauh atau seberapa dekat performa aplikasi Anda dengan ambang batas. Sinyal Aplikasi membantu Anda mengatur SLOs metrik kinerja utama Anda. Sinyal Aplikasi secara otomatis mengumpulkan Latency dan Availability metrik untuk setiap layanan dan operasi yang ditemukannya, dan metrik ini seringkali ideal untuk digunakan sebagai. SLIs Dengan wizard pembuatan SLO, Anda dapat menggunakan metrik ini untuk Anda. SLOs Anda kemudian dapat melacak status semua Anda SLOs dengan dasbor Sinyal Aplikasi. Anda dapat mengatur SLOs operasi atau dependensi tertentu yang dipanggil atau digunakan oleh layanan Anda. Anda dapat menggunakan ekspresi CloudWatch metrik atau metrik apa pun sebagai SLI, selain menggunakan Latency dan Availability metrik. Membuat SLOs sangat penting untuk mendapatkan manfaat maksimal dari Sinyal CloudWatch Aplikasi. Setelah Anda membuat SLOs, Anda dapat melihat statusnya di konsol Sinyal Aplikasi untuk dengan cepat melihat layanan dan operasi penting Anda yang berkinerja baik dan mana yang tidak sehat. Harus SLOs melacak memberikan manfaat utama berikut: Lebih mudah bagi para operator layanan Anda untuk melihat kondisi kesehatan operasional saat ini dari layanan kritis yang diukur berdasarkan SLI. Kemudian mereka dapat dengan cepat melakukan penilaian awal dan mengidentifikasi layanan dan operasi yang sedang dalam kondisi tidak sehat. Anda dapat melacak performa layanan Anda terhadap sasaran bisnis yang terukur dalam jangka waktu yang lebih lama. Dengan memilih apa yang akan ditetapkan SLOs , Anda memprioritaskan apa yang penting bagi Anda. Dasbor Sinyal Aplikasi secara otomatis akan menyajikan informasi mengenai apa yang telah Anda prioritaskan. Saat Anda membuat SLO, Anda juga dapat memilih untuk membuat CloudWatch alarm pada saat yang sama untuk memantau. SLOs Anda dapat mengatur alarm yang memantau terjadinya pelanggaran ambang batas, dan juga alarm untuk tingkat-tingkat peringatan. Alarm-alarm ini dapat secara otomatis memberikan notifikasi kepada Anda jika metrik-metrik SLO melanggar ambang batas yang Anda tetapkan, atau jika mendekati ambang peringatan. Misalnya, SLO yang mendekati ambang peringatannya dapat memberi tahu Anda bahwa tim Anda mungkin perlu memperlambat churn dalam aplikasi untuk memastikan bahwa tujuan performa jangka panjang terpenuhi. Topik Konsep-konsep SLO Hitung anggaran kesalahan dan pencapaian untuk berbasis periode SLOs Hitung anggaran kesalahan dan pencapaian berdasarkan permintaan SLOs Hitung laju pembakaran dan atur alarm laju pembakaran secara opsional Membuat SLO Menampilkan dan melakukan penilaian awal pada status SLO Sunting SLO yang ada Menghapus SLO Konsep-konsep SLO Suatu SLO mencakup komponen-komponen berikut: Indikator tingkat layanan (SLI) , yang merupakan sebuah metrik performa utama yang Anda tentukan. Ini mewakili tingkat performa yang diinginkan untuk aplikasi Anda. Sinyal Aplikasi secara otomatis mengumpulkan metrik utama Latency dan Availability untuk layanan dan operasi yang ditemukannya, dan ini sering kali dapat menjadi metrik yang ideal untuk ditetapkan. SLOs Anda memilih ambang batas yang akan Anda gunakan untuk SLI Anda. Seperti, 200 ms untuk latensi. Tujuan atau tujuan pencapaian , yang merupakan persentase waktu atau permintaan agar SLI diharapkan memenuhi ambang batas selama setiap interval waktu. Interval waktu tersebut bisa dalam hitungan jam atau selama setahun. Interval dapat berupa interval kalender atau interval bergulir. Interval kalender diselaraskan dengan kalender, seperti SLO yang dilacak per bulan. CloudWatch Secara otomatis menyesuaikan kesehatan, anggaran, dan angka pencapaian berdasarkan jumlah hari dalam sebulan. Interval kalender lebih cocok untuk tujuan-tujuan bisnis yang diukur berdasarkan kalender yang sudah diselaraskan. Interval bergulir dihitung secara bergulir. Interval bergulir lebih cocok untuk melakukan pelacakan terhadap pengalaman pengguna terbaru dari aplikasi Anda. Periode adalah jangka waktu yang lebih pendek, dan banyak periode membentuk interval. Performa aplikasi dibandingkan dengan SLI selama masing-masing periode dalam interval. Untuk setiap periode, aplikasi ditentukan telah mencapai atau tidak mencapai performa yang diperlukan. Sebagai contoh, tujuan 99% dengan interval kalender satu hari dan periode 1 menit berarti bahwa aplikasi harus memenuhi atau mencapai ambang keberhasilan selama 99% dari periode 1 menit di siang hari. Jika ya, artinya SLO terpenuhi untuk hari itu. Hari berikutnya adalah interval evaluasi baru, dan aplikasi tersebut harus memenuhi atau mencapai ambang keberhasilan selama 99% dari periode 1 menit selama hari kedua untuk memenuhi SLO untuk hari kedua itu. SLI dapat didasarkan pada salah satu metrik aplikasi standar baru yang dikumpulkan Sinyal Aplikasi. Atau, itu bisa berupa ekspresi CloudWatch metrik atau metrik apa pun. Metrik aplikasi standar yang dapat Anda gunakan untuk SLI adalah Latency dan Availability . Availability mewakili respons yang berhasil dibagi dengan total permintaan. Ini dihitung sebagai (1 - Tingkat Kegagalan)*100 , di mana respons Kegagalan adalah kesalahan 5xx . Respons keberhasilan adalah respons tanpa kesalahan 5XX . Respons 4XX dianggap berhasil. Hitung anggaran kesalahan dan pencapaian untuk berbasis periode SLOs Ketika Anda melihat informasi tentang SLO, Anda melihat status kesehatan saat ini dan anggaran kesalahannya . Anggaran kesalahan adalah jumlah waktu dalam interval yang dapat menembus ambang batas tetapi tetap membiarkan SLO dipenuhi. Anggaran kesalahan total adalah jumlah total waktu pelanggaran yang dapat ditoleransi di seluruh interval. Sisa anggaran kesalahan adalah sisa jumlah waktu pelanggaran yang dapat ditoleransi selama interval saat ini. Ini setelah jumlah waktu pelanggaran yang telah terjadi telah dikurangi total anggaran kesalahan. Gambar berikut menggambarkan konsep anggaran pencapaian dan kesalahan untuk suatu tujuan dengan interval 30 hari, periode 1 menit, dan tujuan pencapaian 99%. 30 hari mencakup 43.200 periode 1 menit. 99% dari 43.200 adalah 42.768, jadi 42.768 menit selama sebulan harus sehat agar SLO terpenuhi. Sejauh ini dalam interval saat ini, 130 dari periode 1 menit berada kondisi tidak sehat. Menentukan keberhasilan dalam masing-masing periode Dalam masing-masing periode, data SLI akan dikumpulkan menjadi satu titik data berdasarkan statistik yang digunakan untuk SLI. Titik data ini mewakili durasi periode seluruhnya. Titik data tunggal itu dibandingkan dengan ambang batas SLI untuk menentukan apakah periode tersebut dalam kondisi sehat, atau tidak. Melihat periode yang tidak sehat selama rentang waktu saat ini di dasbor dapat mengingatkan para operator layanan Anda bahwa layanan perlu diprioritaskan. Jika periode ditentukan tidak sehat, seluruh panjang periode dihitung sebagai gagal terhadap anggaran kesalahan. Melacak anggaran kesalahan memungkinkan Anda mengetahui apakah layanan mencapai performa yang Anda inginkan dalam jangka waktu yang lebih lama. Pengecualian jendela waktu Pengecualian jendela waktu adalah blok waktu dengan tanggal mulai dan akhir yang ditentukan. Periode waktu ini dikecualikan dari metrik kinerja SLO dan Anda dapat menjadwalkan jendela pengecualian waktu satu kali atau berulang. Misalnya, pemeliharaan terjadwal. catatan Untuk berbasis periode SLOs, data SLI di jendela pengecualian dianggap sebagai tidak melanggar. Untuk berbasis permintaan SLOs, semua permintaan baik dan buruk di jendela pengecualian dikecualikan. Ketika interval untuk SLO berbasis permintaan sepenuhnya dikecualikan, metrik tingkat pencapaian default 100% diterbitkan. Anda hanya dapat menentukan jendela waktu dengan tanggal mulai di masa depan. Hitung anggaran kesalahan dan pencapaian berdasarkan permintaan SLOs Setelah Anda membuat SLO, Anda dapat mengambil laporan anggaran kesalahan untuk itu. Anggaran kesalahan adalah jumlah permintaan yang aplikasi Anda dapat tidak sesuai dengan tujuan SLO, dan masih memiliki aplikasi Anda memenuhi tujuan. Untuk SLO berbasis permintaan, anggaran kesalahan yang tersisa bersifat dinamis dan dapat meningkat atau menurun, tergantung pada rasio permintaan yang baik terhadap total permintaan Tabel berikut menggambarkan perhitungan untuk SLO berbasis permintaan dengan interval 5 hari dan 85% tujuan pencapaian. Dalam contoh ini, kami berasumsi tidak ada lalu lintas sebelum Hari 1. SLO tidak memenuhi tujuan pada Hari 10. Waktu Total permintaan Permintaan buruk Total permintaan akumulatif dalam 5 hari terakhir Akumulatif total permintaan bagus dalam 5 hari terakhir Pencapaian berbasis permintaan Total permintaan anggaran Permintaan anggaran yang tersisa Hari 1 10 1 10 9 9/10 = 90% 1.5 0,5 Hari 2 5 1 15 13 13/15= 86% 2.3 0,3 Hari 3 1 1 16 13 13/16= 81% 2.4 -0,6 Hari 4 24 0 40 37 37/40= 92% 6.0 3.0 Hari 5 20 5 60 52 52/60= 87% 9.0 1.0 Hari 6 6 2 56 47 47/56= 84% 8.4 -0,6 Hari 7 10 3 61 50 50/61= 82% 9.2 -1,8 Hari 8 15 6 75 59 59/75= 79% 11.3 -4,7 Hari 9 12 1 63 46 46/63= 73% 9.5 -7,5 Hari 10 5 57 40 40/57= 70% 8.5 -8,5 Pencapaian akhir selama 5 hari terakhir 70% Hitung laju pembakaran dan atur alarm laju pembakaran secara opsional Anda dapat menggunakan Sinyal Aplikasi untuk menghitung tingkat pembakaran untuk tujuan tingkat layanan Anda. Burn rate adalah metrik yang menunjukkan seberapa cepat layanan mengkonsumsi anggaran kesalahan, relatif terhadap tujuan pencapaian SLO. Ini dinyatakan sebagai faktor mutliple dari tingkat kesalahan dasar. Tingkat pembakaran dihitung sesuai dengan tingkat kesalahan dasar , yang tergantung pada tujuan pencapaian. Tujuan pencapaian adalah persentase dari periode waktu yang sehat atau permintaan yang berhasil yang harus dicapai untuk memenuhi tujuan SLO. Tingkat kesalahan dasar adalah (100% - persentase tujuan pencapaian), dan angka ini akan menggunakan anggaran kesalahan lengkap yang tepat pada akhir interval waktu SLO. Jadi SLO dengan tujuan pencapaian 99% akan memiliki tingkat kesalahan dasar 1%. Memantau laju pembakaran memberi tahu kita seberapa jauh kita dari tingkat kesalahan dasar. Sekali lagi mengambil contoh tujuan pencapaian 99%, berikut ini benar: Burn rate = 1 : Jika tingkat pembakaran tetap tepat pada tingkat kesalahan dasar sepanjang waktu, kami memenuhi tujuan SLO dengan tepat. Burn rate < 1 : Jika tingkat pembakaran lebih rendah dari tingkat kesalahan dasar, kami berada di jalur untuk melebihi tujuan SLO. Burn rate > 1 : Jika tingkat pembakaran lebih tinggi dari tingkat kesalahan dasar, kami memiliki kesempatan untuk gagal dalam tujuan SLO. Saat Anda membuat tingkat pembakaran untuk Anda SLOs, Anda juga dapat memilih untuk membuat CloudWatch alarm pada saat yang sama untuk memantau tingkat pembakaran. Anda dapat menetapkan ambang batas untuk tingkat pembakaran dan alarm dapat secara otomatis memberi tahu Anda jika metrik tingkat pembakaran melanggar ambang batas yang Anda tetapkan. Misalnya, tingkat pembakaran yang mendekati ambang batas dapat memberi tahu Anda bahwa SLO membakar anggaran kesalahan lebih cepat daripada yang dapat ditoleransi tim Anda dan tim Anda mungkin perlu memperlambat churn dalam aplikasi untuk memastikan bahwa tujuan kinerja jangka panjang terpenuhi. Membuat alarm akan menimbulkan biaya. Untuk informasi selengkapnya tentang CloudWatch harga, lihat CloudWatch Harga Amazon . Hitung laju pembakaran Untuk menghitung tingkat pembakaran, Anda harus menentukan jendela tampilan belakang . Jendela look-back adalah durasi waktu untuk mengukur tingkat kesalahan. burn rate = error rate over the look-back window / (100% - attainment goal) catatan Ketika tidak ada data untuk periode burn rate, Application Signals menghitung laju pembakaran berdasarkan pencapaian. Tingkat kesalahan dihitung sebagai rasio jumlah peristiwa buruk atas jumlah total peristiwa selama jendela tingkat pembakaran: Untuk berbasis periode SLOs, tingkat kesalahan dihitung sebagai periode buruk dibagi dengan total periode. Total periode mewakili keseluruhan periode selama jendela tampilan belakang. Untuk permintaan berbasis SLOs, ini adalah ukuran permintaan buruk dibagi dengan total permintaan. Jumlah total permintaan adalah jumlah permintaan selama jendela look-back. Jendela look-back harus kelipatan dari periode waktu SLO, dan harus kurang dari interval SLO. Tentukan ambang batas yang sesuai untuk alarm tingkat pembakaran Saat Anda mengonfigurasi alarm tingkat pembakaran, Anda harus memilih nilai untuk tingkat pembakaran sebagai ambang batas alarm. Nilai ambang batas ini tergantung pada panjang interval SLO dan jendela tampilan belakang, dan tergantung pada metode atau model mental mana yang ingin diadopsi oleh tim Anda. Ada dua metode utama yang tersedia untuk menentukan ambang batas. Metode 1: Tentukan persentase perkiraan total anggaran kesalahan yang bersedia dibakar tim Anda di jendela tampilan belakang. Jika Anda ingin khawatir ketika X% dari perkiraan anggaran kesalahan dihabiskan dalam jam lihat kembali tingkat pembakaran terakhir, ambang batas tingkat pembakaran adalah sebagai berikut: burn rate threshold = X% * SLO interval length / look-back window size Misalnya, 5% dari anggaran kesalahan 30 hari (720 jam) yang dihabiskan lebih dari satu jam membutuhkan tingkat pembakaran. 5% * 720 / 1 = 36 Oleh karena itu, jika jendela tampilan kembali tingkat pembakaran adalah 1 jam, kami menetapkan ambang batas laju pembakaran menjadi 36. Anda dapat menggunakan CloudWatch konsol untuk membuat alarm laju pembakaran menggunakan metode ini. Anda dapat menentukan angka X, dan ambang batas ditentukan menggunakan rumus di atas. Panjang interval SLO ditentukan berdasarkan jenis interval SLO: Untuk SLOs dengan interval bergulir, itu adalah panjang interval dalam jam. Untuk SLOs dengan interval berbasis kalender: Jika unit adalah hari atau minggu, itu adalah panjang interval dalam jam. Jika unit adalah satu bulan, kami mengambil 30 hari sebagai perkiraan panjang dan mengubahnya menjadi jam. Metode 2: Tentukan satuan waktul kelelahan anggaran untuk interval berikutnya Agar alarm memberi tahu Anda ketika tingkat kesalahan saat ini di jendela tampilan belakang terbaru menunjukkan bahwa waktu hingga kelelahan anggaran kurang dari X jam jauhnya (dengan asumsi anggaran yang tersisa saat ini 100%), Anda dapat menggunakan rumus berikut untuk menentukan ambang batas tingkat pembakaran. burn rate threshold = SLO interval length / X Kami menekankan bahwa waktu hingga habisnya anggaran (X) dalam rumus di atas mengasumsikan bahwa total anggaran yang tersisa saat ini 100%, dan oleh karena itu tidak memperhitungkan jumlah anggaran yang telah dibakar dalam interval ini. Kita juga bisa menganggapnya sebagai waktu sampai habis anggaran untuk interval berikutnya. Panduan untuk alarm laju pembakaran Sebagai contoh, mari kita ambil SLO dengan interval penggulungan 28 hari. Menyetel alarm tingkat pembakaran untuk SLO ini melibatkan dua langkah: Atur laju pembakaran dan jendela tampilan belakang. Kreta CloudWatch alarm yang memantau laju pembakaran. Untuk memulai, tentukan berapa banyak dari total anggaran kesalahan yang bersedia dibakar oleh layanan dalam jangka waktu tertentu. Dengan kata lain, tentukan tujuan Anda dengan menggunakan kalimat ini: “Saya ingin mendapatkan peringatan ketika X% dari total anggaran kesalahan saya dikonsumsi dalam M menit.” Misalnya, Anda mungkin ingin menetapkan tujuan untuk diperingatkan ketika 2% dari total anggaran kesalahan dikonsumsi dalam 60 menit. Untuk mengatur tingkat pembakaran, pertama-tama Anda menentukan jendela tampilan belakang. Jendela tampilan belakang adalah M, yang dalam contoh ini adalah 60 menit. Selanjutnya, Anda membuat CloudWatch alarm. Ketika Anda melakukannya, Anda harus menentukan ambang batas untuk tingkat pembakaran. Jika tingkat pembakaran melebihi ambang batas ini, alarm akan memberi tahu Anda. Untuk menemukan ambang batas, gunakan rumus berikut: burn rate threshold = X% * SLO interval length/ look-back window size Dalam contoh ini, X adalah 2 karena kami ingin diperingatkan jika 2% dari anggaran kesalahan dikonsumsi dalam 60 menit. Panjang interval adalah 40.320 menit (28 hari), dan 60 menit adalah jendela tampilan belakang, jadi jawabannya adalah: burn rate threshold = 2% * 40,320 / 60 = 13.44. Dalam contoh ini, Anda akan menetapkan 13.44 sebagai ambang alarm. Beberapa alarm dengan jendela berbeda Dengan mengatur alarm di beberapa jendela tampilan belakang, Anda dapat dengan cepat mendeteksi peningkatan tingkat kesalahan yang tajam dengan jendela pendek dan pada saat yang sama mendeteksi peningkatan tingkat kesalahan yang lebih kecil yang pada akhirnya menghabiskan anggaran kesalahan jika tetap tidak diperhatikan. Selain itu, Anda dapat mengatur alarm komposit pada tingkat pembakaran dengan jendela panjang dan pada tingkat pembakaran dengan jendela pendek (1/12 dari jendela panjang), dan diberi tahu hanya ketika kedua tingkat pembakaran melanggar ambang batas. Dengan cara ini, Anda dapat memastikan bahwa Anda mendapatkan peringatan hanya untuk situasi yang masih terjadi. Untuk informasi selengkapnya tentang alarm komposit di CloudWatch, lihat Menggabungkan alarm . catatan Anda dapat mengatur alarm metrik pada tingkat pembakaran saat Anda membuat laju pembakaran. Untuk menyetel alarm compoaite pada beberapa alarm laju pembakaran, Anda harus menggunakan instruksi di. Membuat sebuah alarm gabungan Satu strategi alarm komposit yang direkomendasikan dalam buku kerja Google Site Reliability Engineering mencakup tiga alarm komposit: Satu alarm komposit yang mengawasi sepasang alarm, satu dengan jendela satu jam dan satu lagi dengan jendela lima menit. Alarm komposit kedua yang mengawasi sepasang alarm, satu dengan jendela enam jam dan satu dengan jendela 30 menit. Alarm komposit ketiga yang mengawasi sepasang alarm, satu dengan jendela tiga hari dan satu dengan jendela enam jam. Langkah-langkah untuk melakukan pengaturan ini adalah sebagai berikut: Buat lima tingkat pembakaran, dengan jendela lima menit, 30 menit, satu jam, enam jam, dan tiga hari. Buat tiga pasang CloudWatch alarm berikut. Setiap pasangan mencakup satu jendela panjang dan satu jendela pendek yaitu 1/12 dari jendela panjang, dan ambang batas ditentukan dengan menggunakan langkah-langkah masuk. Tentukan ambang batas yang sesuai untuk alarm tingkat pembakaran Saat Anda menghitung ambang batas untuk setiap alarm pada pasangan, gunakan jendela tampilan belakang pasangan yang lebih panjang dalam perhitungan Anda. Alarm pada tingkat pembakaran 1 jam dan 5 menit (ambang batas ditentukan oleh 2% dari total anggaran) Alarm pada tingkat pembakaran 6 jam dan 30 menit (ambang batas ditentukan oleh 5% dari total anggaran) Alarm pada tingkat pembakaran 3 hari dan 6 jam (ambang batas ditentukan oleh 10% dari total anggaran) Untuk masing-masing pasangan ini, buat alarm komposit untuk mendapatkan peringatan ketika kedua alarm individu masuk ke status ALARM. Untuk informasi selengkapnya tentang membuat alarm komposit, lihat Membuat sebuah alarm gabungan . Misalnya, jika alarm Anda untuk pasangan pertama (jendela satu jam dan jendela lima menit) diberi nama OneHourBurnRate dan FiveMinuteBurnRate , aturan alarm CloudWatch komposit adalah ALARM(OneHourBurnRate) AND ALARM(FiveMinuteBurnRate) Strategi sebelumnya hanya mungkin untuk SLOs dengan panjang interval setidaknya tiga jam. Untuk SLOs dengan panjang interval yang lebih pendek, kami sarankan Anda memulai dengan sepasang alarm laju pembakaran di mana satu alarm memiliki jendela lihat ke belakang yang 1/12 dari jendela lihat-belakang alarm lainnya. Kemudian atur alarm komposit pada pasangan ini. Membuat SLO Kami menyarankan Anda mengatur latensi dan ketersediaan SLOs pada aplikasi penting Anda. Metrik yang dikumpulkan Sinyal Aplikasi ini selaras dengan tujuan bisnis bersama. Anda juga dapat mengatur SLOs CloudWatch metrik atau ekspresi matematika metrik apa pun yang menghasilkan satu deret waktu. Pertama kali Anda membuat SLO di akun Anda, CloudWatch secara otomatis membuat peran AWSServiceRoleForCloudWatchApplicationSignals terkait layanan di akun Anda, jika belum ada. Peran terkait layanan ini memungkinkan CloudWatch untuk mengumpulkan data CloudWatch Log, data jejak X-Ray, data CloudWatch metrik, dan data penandaan dari aplikasi di akun Anda. Untuk informasi selengkapnya tentang peran CloudWatch terkait layanan, lihat. Menggunakan peran terkait layanan untuk CloudWatch Saat Anda membuat SLO, Anda menentukan apakah itu SLO berbasis periode atau SLO berbasis permintaan. Setiap jenis SLO memiliki cara yang berbeda untuk mengevaluasi kinerja aplikasi Anda terhadap tujuan pencapaiannya. SLO berbasis periode menggunakan periode waktu yang ditentukan dalam interval waktu total yang ditentukan. Untuk setiap periode waktu, Sinyal Aplikasi menentukan apakah aplikasi memenuhi tujuannya. Tingkat pencapaian dihitung sebagai. number of good periods/number of total periods Misalnya, untuk SLO berbasis periode, memenuhi tujuan pencapaian 99,9% berarti bahwa dalam interval Anda, aplikasi Anda harus memenuhi tujuan kinerjanya selama setidaknya 99,9% dari periode waktu. SLO berbasis permintaan tidak menggunakan periode waktu yang telah ditentukan sebelumnya. Sebaliknya, SLO mengukur number of good requests/number of total requests selama interval. Kapan saja, Anda dapat menemukan rasio permintaan yang baik terhadap total permintaan untuk interval hingga stempel waktu yang Anda tentukan, dan mengukur rasio tersebut terhadap sasaran yang ditetapkan dalam SLO Anda. Topik Buat SLO berbasis periode Buat SLO berbasis permintaan Buat SLO berbasis periode Gunakan prosedur berikut untuk membuat SLO berbasis periode. Untuk membuat SLO berbasis periode Buka CloudWatch konsol di https://console.aws.amazon.com/cloudwatch/ . Pada panel navigasi, silakan pilih Tujuan Tingkat Layanan (SLO) . Pilih Buat SLO . Masukkan nama untuk SLO. Menyertakan nama layanan atau operasi, bersama kata kunci yang sesuai seperti latensi atau ketersediaan, akan membantu Anda mengidentifikasi apa yang ditunjukkan status SLO selama triase dengan cepat. Untuk Mengatur Indikator Tingkat Layanan(SLI) , lakukan salah satu hal berikut: Untuk mengatur SLO pada salah satu metrik aplikasi standar Latency atau Availability : Pilih Operasi Layanan . Pilih akun yang akan dipantau SLO ini. Pilih layanan yang akan dipantau oleh SLO ini. Pilih operasi yang akan dipantau oleh SLO ini. Untuk Pilih metode perhitungan , pilih Periode . Drop-down Pilih Layanan dan Pilih operasi diisi oleh layanan dan operasi yang telah aktif dalam 24 jam terakhir. Pilih Ketersediaan atau Latensi dan kemudian atur ambang batas. Untuk mengatur SLO pada CloudWatch metrik atau ekspresi matematika CloudWatch metrik apa pun: Pilih CloudWatch Metrik . Pilih Pilih CloudWatch metrik . Layar Pilih metrik muncul. Gunakan tab Jelajahi atau Kueri untuk menemukan metrik yang Anda inginkan, atau membuat ekspresi matematika metrik. Setelah Anda memilih metrik yang Anda inginkan, pilih tab Metrik bergrafik dan pilih Statistik dan Periode yang akan digunakan untuk SLO. Kemudian pilih Pilih metrik . Untuk informasi selengkapnya tentang metrik ini, silakan lihat Membuat sebuah grafik metrik dan Tambahkan ekspresi matematika ke CloudWatch grafik . Untuk Pilih metode perhitungan , pilih Periode . Untuk Atur kondisi , pilih operator perbandingan dan ambang batas untuk SLO yang akan digunakan sebagai indikator keberhasilan. Untuk mengatur SLO pada ketergantungan layanan pada salah satu metrik Latency aplikasi standar atau: Availability Pilih Ketergantungan Layanan . Di bawah Pilih layanan , pilih layanan yang akan dipantau oleh SLO ini. Berdasarkan layanan yang dipilih, di bawah Pilih operasi , Anda dapat memilih satu operasi tertentu atau memilih Semua operasi untuk menggunakan metrik dari semua operasi layanan ini yang memanggil ketergantungan. Di bawah Pilih dependensi , Anda dapat mencari dan memilih ketergantungan yang diperlukan yang ingin Anda ukur keandalannya. Setelah Anda memilih ketergantungan, Anda dapat melihat grafik yang diperbarui dan data historis berdasarkan ketergantungan. Jika Anda memilih Operasi Layanan atau Ketergantungan Layanan di langkah 5, atur panjang periode untuk SLO ini. Atur interval dan tujuan pencapaian untuk SLO. Untuk informasi selengkapnya tentang interval dan pencapaian tujuan dan bagaimana keduanya bekerja sama, silakan lihat Konsep-konsep SLO . (Opsional) Untuk Set SLO burn rate lakukan hal berikut: Atur panjang (dalam hitungan menit) jendela tampilan belakang untuk laju pembakaran. Untuk informasi tentang cara memilih panjang ini, lihat Panduan untuk alarm laju pembakaran . Untuk membuat lebih banyak tingkat pembakaran untuk SLO ini, pilih Tambahkan lebih banyak tingkat pembakaran dan atur jendela tampilan belakang untuk tingkat pembakaran tambahan. (Opsional) Buat alarm tingkat pembakaran dengan melakukan hal berikut: Di bawah Setel alarm laju pembakaran , pilih kotak centang untuk setiap laju pembakaran yang ingin Anda buat alarm. Untuk masing-masing alarm ini, lakukan hal berikut: Tentukan topik Amazon SNS yang akan digunakan untuk notifikasi saat alarm masuk ke status ALARM. Tetapkan ambang batas tingkat pembakaran atau tentukan persentase perkiraan total anggaran yang dibakar di jendela tampilan belakang terakhir yang ingin Anda tetapkan di bawah. Jika Anda menetapkan persentase perkiraan total anggaran yang dibakar, ambang batas tingkat pembakaran dihitung untuk Anda dan digunakan dalam alarm. Untuk memutuskan ambang batas apa yang akan ditetapkan atau untuk memahami bagaimana opsi ini digunakan untuk menghitung ambang batas tingkat pembakaran, lihat Tentukan ambang batas yang sesuai untuk alarm tingkat pembakaran . (Opsional) Atur satu atau lebih CloudWatch alarm atau ambang peringatan untuk SLO. CloudWatch alarm dapat menggunakan Amazon SNS untuk memberi tahu Anda secara proaktif jika aplikasi tidak sehat berdasarkan kinerja SLI-nya. Untuk membuat alarm, pilih salah satu kotak centang alarm dan masukkan atau buat topik Amazon SNS yang akan digunakan untuk notifikasi saat alarm masuk ke status ALARM . Untuk informasi selengkapnya tentang CloudWatch alarm, lihat Menggunakan CloudWatch alarm Amazon . Membuat alarm akan menimbulkan biaya. Untuk informasi selengkapnya tentang CloudWatch harga, lihat CloudWatch Harga Amazon . Jika Anda menetapkan ambang peringatan, itu muncul di layar Sinyal Aplikasi untuk membantu Anda mengidentifikasi SLOs yang berada dalam bahaya tidak terpenuhi, bahkan jika mereka saat ini sehat. Untuk mengatur ambang batas peringatan, masukkan nilai ambang batas di Ambang batas peringatan . Ketika anggaran kesalahan SLO lebih rendah dari ambang batas peringatan, SLO ditandai dengan Peringatan di beberapa layar Sinyal Aplikasi. Ambang batas peringatan juga muncul pada grafik anggaran kesalahan. Anda juga dapat membuat alarm peringatan SLO yang didasarkan pada ambang batas peringatan. (Opsional) Untuk Mengatur pengecualian jendela waktu SLO , lakukan hal berikut: Di bawah Jendela waktu Kecualikan , setel jendela waktu yang akan dikecualikan dari metrik kinerja SLO. Anda dapat memilih Tetapkan jendela waktu dan masuk ke jendela Mulai untuk setiap jam atau bulan atau Anda dapat memilih Atur jendela waktu dengan CRON dan masukkan ekspresi CRON. Di bawah Ulangi , atur apakah pengecualian jendela waktu ini berulang atau tidak. (Opsional) Di bawah Tambahkan alasan , Anda dapat memilih untuk memasukkan alasan pengecualian jendela waktu. Misalnya, pemeliharaan terjadwal. Pilih Tambahkan jendela waktu untuk menambahkan hingga 10 jendela pengecualian waktu. Untuk menambahkan tanda ke SLO ini, silakan pilih tab Tanda dan kemudian pilih Tambahkan tanda baru . Tanda dapat membantu Anda mengelola, mengidentifikasi, mengatur, dan memfilter sumber daya. Untuk informasi selengkapnya tentang penandaan, silakan lihat Menandai sumber daya AWS Anda . catatan Jika aplikasi yang terkait dengan SLO ini terdaftar AWS Service Catalog AppRegistry, Anda dapat menggunakan awsApplication tag untuk mengaitkan SLO ini dengan aplikasi itu. AppRegistry Untuk informasi lebih lanjut, lihat Apa itu AppRegistry? Pilih Buat SLO . Jika Anda juga memilih untuk membuat satu atau beberapa alarm, nama tombol berubah sehingga mencerminkan hal ini. Buat SLO berbasis permintaan Gunakan prosedur berikut untuk membuat SLO berbasis permintaan. Untuk membuat SLO berbasis permintaan Buka CloudWatch konsol di https://console.aws.amazon.com/cloudwatch/ . Pada panel navigasi, silakan pilih Tujuan Tingkat Layanan (SLO) . Pilih Buat SLO . Masukkan nama untuk SLO. Menyertakan nama layanan atau operasi, bersama kata kunci yang sesuai seperti latensi atau ketersediaan, akan membantu Anda mengidentifikasi apa yang ditunjukkan status SLO selama triase dengan cepat. Untuk Mengatur Indikator Tingkat Layanan(SLI) , lakukan salah satu hal berikut: Untuk mengatur SLO pada salah satu metrik aplikasi standar Latency atau Availability : Pilih Operasi Layanan . Pilih layanan yang akan dipantau oleh SLO ini. Pilih operasi yang akan dipantau oleh SLO ini. Untuk Pilih metode perhitungan , pilih Permintaan . Drop-down Pilih Layanan dan Pilih operasi diisi oleh layanan dan operasi yang telah aktif dalam 24 jam terakhir. Pilih Availability atau Latency . Jika Anda memilih Latency , atur ambang batas. Untuk mengatur SLO pada CloudWatch metrik atau ekspresi matematika CloudWatch metrik apa pun: Pilih CloudWatch Metrik . Untuk Tentukan permintaan target , lakukan hal berikut: Pilih apakah Anda ingin mengukur Permintaan Baik atau Permintaan Buruk . Pilih Pilih CloudWatch metrik . Metrik ini akan menjadi pembilang rasio permintaan target terhadap total permintaan. Jika Anda menggunakan metrik latensi, gunakan statistik Trimmed count (TC) . Jika ambang batas adalah 9 ms dan Anda menggunakan operator perbandingan kurang dari (<), maka gunakan threshold TC (:threshold - 1). Untuk informasi lebih lanjut tentang TC, lihat Sintaks . Layar Pilih metrik muncul. Gunakan tab Jelajahi atau Kueri untuk menemukan metrik yang Anda inginkan, atau membuat ekspresi matematika metrik. Untuk Tentukan permintaan total , pilih CloudWatch metrik yang ingin Anda gunakan untuk sumbernya. Metrik ini akan menjadi penyebut rasio permintaan target terhadap total permintaan. Layar Pilih metrik muncul. Gunakan tab Jelajahi atau Kueri untuk menemukan metrik yang Anda inginkan, atau membuat ekspresi matematika metrik. Setelah Anda memilih metrik yang Anda inginkan, pilih tab Metrik bergrafik dan pilih Statistik dan Periode yang akan digunakan untuk SLO. Kemudian pilih Pilih metrik . Jika Anda menggunakan metrik latensi yang memancarkan satu titik data per permintaan, gunakan statistik jumlah sampel untuk menghitung jumlah total permintaan. Untuk informasi selengkapnya tentang metrik ini, silakan lihat Membuat sebuah grafik metrik dan Tambahkan ekspresi matematika ke CloudWatch grafik . Untuk mengatur SLO pada ketergantungan layanan pada salah satu metrik Latency aplikasi standar atau: Availability Pilih Ketergantungan Layanan . Di bawah Pilih layanan , pilih layanan yang akan dipantau oleh SLO ini. Berdasarkan layanan yang dipilih, di bawah Pilih operasi , Anda dapat memilih satu operasi tertentu atau memilih Semua operasi untuk menggunakan metrik dari semua operasi layanan ini yang memanggil ketergantungan. Di bawah Pilih dependensi , Anda dapat mencari dan memilih ketergantungan yang diperlukan yang ingin Anda ukur keandalannya. Setelah Anda memilih ketergantungan, Anda dapat melihat grafik yang diperbarui dan data historis berdasarkan ketergantungan. Atur interval dan tujuan pencapaian untuk SLO. Untuk informasi selengkapnya tentang interval dan pencapaian tujuan dan bagaimana keduanya bekerja sama, silakan lihat Konsep-konsep SLO . (Opsional) Untuk Set SLO burn rate lakukan hal berikut: Atur panjang (dalam hitungan menit) jendela tampilan belakang untuk laju pembakaran. Untuk informasi tentang cara memilih panjang ini, lihat Panduan untuk alarm laju pembakaran . Untuk membuat lebih banyak tingkat pembakaran untuk SLO ini, pilih Tambahkan lebih banyak tingkat pembakaran dan atur jendela tampilan belakang untuk tingkat pembakaran tambahan. (Opsional) Buat alarm tingkat pembakaran dengan melakukan hal berikut: Di bawah Setel alarm laju pembakaran , pilih kotak centang untuk setiap laju pembakaran yang ingin Anda buat alarm. Untuk masing-masing alarm ini, lakukan hal berikut: Tentukan topik Amazon SNS yang akan digunakan untuk notifikasi saat alarm masuk ke status ALARM. Tetapkan ambang batas tingkat pembakaran atau tentukan persentase perkiraan total anggaran yang dibakar di jendela tampilan belakang terakhir yang ingin Anda tetapkan di bawah. Jika Anda menetapkan persentase perkiraan total anggaran yang dibakar, ambang batas tingkat pembakaran dihitung untuk Anda dan digunakan dalam alarm. Untuk memutuskan ambang batas apa yang akan ditetapkan atau untuk memahami bagaimana opsi ini digunakan untuk menghitung ambang batas tingkat pembakaran, lihat Tentukan ambang batas yang sesuai untuk alarm tingkat pembakaran . (Opsional) Atur satu atau lebih CloudWatch alarm atau ambang peringatan untuk SLO. CloudWatch alarm dapat menggunakan Amazon SNS untuk memberi tahu Anda secara proaktif jika aplikasi tidak sehat berdasarkan kinerja SLI-nya. Untuk membuat alarm, pilih salah satu kotak centang alarm dan masukkan atau buat topik Amazon SNS yang akan digunakan untuk notifikasi saat alarm masuk ke status ALARM . Untuk informasi selengkapnya tentang CloudWatch alarm, lihat Menggunakan CloudWatch alarm Amazon . Membuat alarm akan menimbulkan biaya. Untuk informasi selengkapnya tentang CloudWatch harga, lihat CloudWatch Harga Amazon . Jika Anda menetapkan ambang peringatan, itu muncul di layar Sinyal Aplikasi untuk membantu Anda mengidentifikasi SLOs yang berada dalam bahaya tidak terpenuhi, bahkan jika mereka saat ini sehat. Untuk mengatur ambang batas peringatan, masukkan nilai ambang batas di Ambang batas peringatan . Ketika anggaran kesalahan SLO lebih rendah dari ambang batas peringatan, SLO ditandai dengan Peringatan di beberapa layar Sinyal Aplikasi. Ambang batas peringatan juga muncul pada grafik anggaran kesalahan. Anda juga dapat membuat alarm peringatan SLO yang didasarkan pada ambang batas peringatan. (Opsional) Untuk Mengatur pengecualian jendela waktu SLO , lakukan hal berikut: Di bawah Jendela waktu Kecualikan , setel jendela waktu yang akan dikecualikan dari metrik kinerja SLO. Anda dapat memilih Tetapkan jendela waktu dan masuk ke jendela Mulai untuk setiap jam atau bulan atau Anda dapat memilih Atur jendela waktu dengan CRON dan masukkan ekspresi CRON. Di bawah Ulangi , atur apakah pengecualian jendela waktu ini berulang atau tidak. (Opsional) Di bawah Tambahkan alasan , Anda dapat memilih untuk memasukkan alasan pengecualian jendela waktu. Misalnya, pemeliharaan terjadwal. Pilih Tambahkan jendela waktu untuk menambahkan hingga 10 jendela pengecualian waktu. Untuk menambahkan tanda ke SLO ini, silakan pilih tab Tanda dan kemudian pilih Tambahkan tanda baru . Tanda dapat membantu Anda mengelola, mengidentifikasi, mengatur, dan memfilter sumber daya. Untuk informasi selengkapnya tentang penandaan, silakan lihat Menandai sumber daya AWS Anda . catatan Jika aplikasi yang terkait dengan SLO ini terdaftar AWS Service Catalog AppRegistry, Anda dapat menggunakan awsApplication tag untuk mengaitkan SLO ini dengan aplikasi itu. AppRegistry Untuk informasi lebih lanjut, lihat Apa itu AppRegistry? Pilih Buat SLO . Jika Anda juga memilih untuk membuat satu atau beberapa alarm, nama tombol berubah sehingga mencerminkan hal ini. Menampilkan dan melakukan penilaian awal pada status SLO Anda dapat dengan cepat melihat kesehatan Anda SLOs menggunakan Tujuan Tingkat Layanan atau opsi Layanan di CloudWatch konsol. Tampilan Layanan memberikan at-a-glance tampilan rasio layanan yang tidak sehat, dihitung berdasarkan SLOs yang telah Anda tetapkan. Untuk informasi selengkapnya tentang penggunaan opsi Layanan , silakan lihat Memantau kondisi kesehatan operasional aplikasi Anda dengan Sinyal Aplikasi . Tampilan Tujuan Tingkat Layanan memberikan sebuah tampilan makro organisasi Anda. Anda dapat melihat yang bertemu dan tidak terpenuhi secara SLOs keseluruhan. Ini memberi Anda gambaran tentang berapa banyak layanan dan operasi Anda yang berkinerja sesuai harapan Anda selama periode waktu yang lebih lama, sesuai dengan SLIs yang Anda pilih. Untuk melihat semua SLOs tampilan Tujuan Tingkat Layanan Buka CloudWatch konsol di https://console.aws.amazon.com/cloudwatch/ . Pada panel navigasi, silakan pilih Tujuan Tingkat Layanan (SLO) . Daftar Tujuan Tingkat Layanan (SLO) ditampilkan. Anda dapat dengan cepat melihat status Anda saat ini SLOs di kolom status SLI . Untuk mengurutkan SLOs sehingga semua yang tidak sehat berada di bagian atas daftar, pilih kolom status SLI sampai yang tidak sehat SLOs semuanya di atas. Tabel SLO memiliki kolom-kolom default berikut. Anda dapat menyesuaikan kolom-kolom mana saja yang ditampilkan dengan memilih ikon roda gigi yang ada di atas daftar. Untuk informasi lebih lanjut tentang tujuan SLIs, pencapaian, dan interval, lihat Konsep-konsep SLO . Nama SLO. Kolom Tujuan menampilkan persentase periode selama setiap interval yang harus berhasil memenuhi ambang batas SLI agar tujuan SLO terpenuhi. Ini juga menampilkan panjang interval untuk SLO tersebut. Status SLI akan menampilkan apakah status operasional aplikasi saat ini sedang dalam kondisi yang sehat atau tidak sehat. Jika ada periode selama rentang waktu yang dipilih saat ini tidak sehat untuk SLO, status SLI menampilkan Tidak Sehat . Jika SLO ini dikonfigurasi untuk memantau ketergantungan, kolom Dependency dan Remote Operation akan menampilkan detail tentang hubungan ketergantungan tersebut. Pencapaian akhir adalah tingkat pencapaian yang dicapai pada akhir rentang waktu yang dipilih. Urutkan berdasarkan kolom ini untuk melihat SLOs yang paling berisiko tidak terpenuhi. Delta pencapaian adalah perbedaan tingkat pencapaian antara awal dan akhir rentang waktu yang dipilih. Delta negatif berarti bahwa metrik kecenderungannya sedang ke arah bawah. Urutkan berdasarkan kolom ini untuk melihat tren terbaru dari SLOs. Anggaran kesalahan akhir (%) adalah persentase dari total waktu dalam periode yang dapat memiliki periode tidak sehat dan masih memiliki SLO yang berhasil dicapai. Jika Anda mengatur ini menjadi 5%, dan SLI sedang dalam kondisi tidak sehat dalam 5% atau kurang dari periode yang tersisa dalam interval, maka SLO masih berhasil dicapai. Delta anggaran kesalahan adalah perbedaan anggaran kesalahan antara awal dan akhir rentang waktu yang dipilih. Delta negatif berarti bahwa metrik sedang mengarah ke arah yang gagal. Anggaran kesalahan akhir (waktu) adalah jumlah waktu aktual dalam interval yang bisa tidak sehat dan masih memiliki SLO yang berhasil dicapai. Sebagai contoh, jika ini 14 menit, maka jika SLI tidak sehat selama kurang dari 14 menit selama interval yang tersisa, SLO akan tetap berhasil tercapai. Anggaran kesalahan akhir (permintaan) adalah jumlah permintaan dalam interval yang bisa tidak sehat dan SLO masih berhasil dicapai. Untuk berbasis permintaan SLOs, nilai ini dinamis dan dapat berfluktuasi karena jumlah permintaan kumulatif berubah seiring waktu. Kolom Layanan , Operasi , dan Tipe menampilkan informasi tentang layanan dan operasi apa yang diatur SLO ini. Untuk melihat grafik pencapaian dan kesalahan untuk SLO, pilih tombol radio di samping nama SLO. Grafik di bagian atas halaman menampilkan pencapaian SLO dan status Anggaran kesalahan . Sebuah grafik tentang metrik SLI yang dikaitkan dengan SLO ini juga ditampilkan. Untuk melakukan triase lebih lanjut SLO yang tidak memenuhi tujuannya, pilih nama layanan, nama operasi, atau nama ketergantungan yang terkait dengan SLO tersebut. Anda dibawa ke halaman detail di mana Anda dapat melakukan penilaian awal lebih lanjut. Untuk informasi selengkapnya, lihat Lihat detail aktivitas layanan dan kesehatan operasional dengan halaman detail layanan . Untuk mengubah rentang waktu grafik dan tabel pada halaman tersebut, pilih rentang waktu baru di dekat bagian atas layar. Sunting SLO yang ada Ikuti langkah-langkah ini untuk menyunting SLO yang ada. Saat Anda menyunting SLO, Anda hanya dapat mengubah ambang batas, interval, tujuan pencapaian, dan tag. Untuk mengubah aspek lain seperti layanan, operasi, atau metrik, buat SLO baru alih-alih menyunting yang sudah ada. Mengubah bagian dari konfigurasi inti SLO, seperti periode atau ambang batas, membatalkan semua titik data sebelumnya dan penilaian tentang pencapaian dan kondisi kesehatan. Ini secara efektif menghapus dan membuat kembali SLO. catatan Jika Anda menyunting SLO, alarm yang terkait dengan SLO tersebut tidak diperbarui secara otomatis. Anda mungkin perlu memperbarui alarm-alarm tersebut agar tetap sinkron dengan SLO. Cara menyunting SLO yang ada Buka CloudWatch konsol di https://console.aws.amazon.com/cloudwatch/ . Pada panel navigasi, silakan pilih Tujuan Tingkat Layanan (SLO) . Pilih tombol radio yang ada di samping SLO yang ingin Anda sunting, dan pilih Tindakan , Sunting SLO . Buat perubahan, lalu pilih Simpan perubahan . Menghapus SLO Ikuti langkah-langkah ini untuk menghapus SLO yang ada. catatan Saat Anda menghapus sebuah SLO, alarm yang terkait dengan SLO tersebut tidak akan dihapus secara otomatis. Anda harus menghapusnya sendiri. Untuk informasi selengkapnya, lihat Mengelola alarm-alarm . Cara menghapus SLO Buka CloudWatch konsol di https://console.aws.amazon.com/cloudwatch/ . Pada panel navigasi, silakan pilih Tujuan Tingkat Layanan (SLO) . Pilih tombol radio di samping SLO yang ingin Anda sunting, dan pilih Tindakan , Hapus SLO . Pilih Konfirmasi . Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Metrik khusus dengan Sinyal Aplikasi Pencarian Transaksi Apakah halaman ini membantu Anda? - Ya Terima kasih telah memberitahukan bahwa hasil pekerjaan kami sudah baik. Jika Anda memiliki waktu luang, beri tahu kami aspek apa saja yang sudah bagus, agar kami dapat menerapkannya secara lebih luas. Apakah halaman ini membantu Anda? - Tidak Terima kasih telah memberi tahu kami bahwa halaman ini perlu ditingkatkan. Maaf karena telah mengecewakan Anda. Jika Anda memiliki waktu luang, beri tahu kami bagaimana dokumentasi ini dapat ditingkatkan. | 2026-01-13T09:29:25 |
https://www.linkedin.com/products/one-network-enterprises-integrated-business-planning-execution/ | Integrated Business Planning &amp; Execution | LinkedIn Skip to main content LinkedIn One Network Enterprises 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 Integrated Business Planning & Execution Strategic Planning Software by One Network Enterprises See who's skilled in this Add as skill Learn more Report this product About The Integrated Business Planning & Execution solution suite is designed for today’s organizations with complex, globally sourced supply chains. It leverages One Network’s underlying cloud platform— the Digital Supply Chain Network™—to coordinate and synchronize end-customer demand across all internal operations and key trading partners, including contract manufacturers, suppliers, logistics providers, and retailers; it tracks, monitors, and plans continuously and in real time. The Integrated Business Planning & Execution solution includes services for Sales and Operations Planning (S&OP), Business Continuity and Risk Management, Sustainability. Media Products media viewer No more previous content One Network Control Tower Your Entire Supply Chain Digitized: From inbound supply to outbound order fulfillment and logistics, optimize and automate across your entire supply network and every trading partner. The NEO Platform’s intelligent agent technology delivers predictive and prescriptive analytics with real time information to help you lead your industry - for the highest service levels and product quality at lowest cost. Transform your business with the global leader in Supply Chain Control Towers: onenetwork.com No more next content Similar products Focus Focus Strategic Planning Software Aha! Roadmaps Aha! Roadmaps Strategic Planning Software DIGITAL PRODUCTS DIGITAL PRODUCTS Strategic Planning Software Cascade Cascade Strategic Planning Software WorkBoard WorkBoard Strategic Planning Software Stratsys platform for compliance and efficiency Stratsys platform for compliance and efficiency Strategic Planning Software Sign in to see more Show more Show less One Network Enterprises products NEO NEO Supply Chain Management Software Neo Platform Neo Platform Supply Chain Management Software One Network Master Data Management One Network Master Data Management Master Data Management (MDM) Software The Digital Supply Chain Network The Digital Supply Chain Network Supply Chain Management 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:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#posts-api | Pinterest API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Pinterest API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Discover by Keywords Posts API Collect by URL Discover by Profile URL Discover by Keywords Social Media APIs Pinterest API Scrapers Copy page Copy page Overview The Pinterest API Suite offers multiple types of APIs, each designed for specific data collection needs from Pinterest. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Discover by Keywords. Interesting Columns : name , following_count , website , follower_count . Posts API This API allows users to collect multiple posts based on a single input. Discovery functionality : - Discover by profile URL. - Discover by Keywords. Interesting Columns : title , content , user_name , likes . Profiles API Collect by URL This API allows users to retrieve detailed Pinterest profile information using the provided profile URL. Input Parameters : URL string required The Pinterest profile URL. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metrics : following_count , follower_count , boards_num , saved . Additional Information : last_updated , posts_page_url , discovery_input . This API allows users to collect detailed insights into a Pinterest profile, including user statistics, engagement metrics, and profile information. Discover by Keywords This API allows users to discover Pinterest profiles based on a specified keyword. Input Parameters : keyword string required The keyword to search for profiles. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metric s: following_count , follower_count , boards_num , saved. Additional Information : last_updated , posts_page_url , discovery_input . This API enables users to find Pinterest profiles related to a specific keyword, offering insights into user statistics, engagement, and profile details. Posts API Collect by URL This API allows users to collect detailed post data from a specific Pinterest post using the provided post URL. Input Parameters : URL string required The Pinterest post URL. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , post_type . For all data points, click here . User Details : user_name , user_url , user_id , followers . Post Metrics : likes , comments_num , comments , categories . Media & Attachments : image_video_url , video_length , attached_files . Hashtags & Discovery : hashtags , discovery_input . This API allows users to retrieve detailed insights into a specific Pinterest post, including user engagement, post content, media, and other related information. Discover by Profile URL This API allows users to retrieve posts from a specific Pinterest profile based on the provided profile URL. Input Parameters : URL string required The Pinterest profile URL from which to collect posts. num_of_posts number The number of posts to collect. If omitted, there is no limit. posts_to_not_include array An array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date ). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date ). Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users tso collect posts from a specific Pinterest profile, allowing for filtering by date, exclusion of specific posts, and retrieval of detailed post data including media, comments, and engagement metrics. Discover by Keywords This API allows users to discover Pinterest posts based on a specific keyword, enabling efficient content discovery. Input Parameters : keyword string required The keyword to search for posts, such as “food” or any other relevant term. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users to search for Pinterest posts based on a specific keyword, providing detailed insights into the content, engagement, media, and associated metrics for efficient discovery. Was this page helpful? Yes No Twitter Quora ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://git-scm.com/book/tl/v2/Mga-Git-na-Kasangkapan-Pagpipili-ng-Rebisyon | Git - Pagpipili ng Rebisyon 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. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 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 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 7.1 Mga Git na Kasangkapan - Pagpipili ng Rebisyon Sa ngayon, natutunan mo ang karamihan ng pang-araw-araw na mga utos at mga workflow na kailangan mong pamahalaan o pangalagaan ang Git na repositoryo para sa kontrol ng iyong source code. Nagawa mo na ang mga pangunahing gawain ng pagsubaybay at pag-commit ng mga file, at napakinabangan mo ang kapayarihan sa staging na lawak at magaan na paksa na pag-branch at pag-merge. Ngayon ikaw ay magsiyasat ng bilang sa sobrang makapangyarihan na bagay na magagawa ng Git na maaaring hindi mo na kinakailangang gamitin sa pang-araw-araw ngunit maaaring kailangan mo sa isang punto. Pagpipili ng Rebisyon Ang Git ay nagpapahintulot sa iyo upang sumangguni sa isang itinakdang mga commit o isang lawak ng mga commit sa maraming mga paraan. Hindi nila kinakailangan na halata ngunit nakakatulong upang malaman. Solong mga Rebisyon Maaari mong malinaw na i-refer ang anumang solong commit sa buong ito, 40-karakter na SHA-1 hash, ngunit may mga higit pa na pantaong-palakaibigan na mga paraan upang sumangguni rin sa mga commit. Ang seksyon na ito ng mga outline ng iba’t ibang mga paraan na maaari mong isangguni sa anumang commit. Ang Maikling SHA-1 Ang Git ay sapat na matalino upang malaman kung anong commit ang iyong nare-refer na kung bigyan mo ang mga unang ilang mga karakter ng SHA-1 hash, hangga’t ang bahagyang hash ay hindi bababa sa apat na mga karakter ang haba at hindi malabo; yan ay, walang ibang bagay sa database ng bagay na maaaring magkakaroon ng hash na nagmumula ng parehong prefix. Halimbawa, upang suriin ang tiyak na commit na kung saan ka kilala mo ang dinagdag na ilang mga pag-andar, maaari mong patakbuhin muna ang git log na utos upang hanapin ang commit: $ git log commit 734713bc047d87bf7eac9674765ae793478c50d3 Author: Scott Chacon <schacon@gmail.com> Date: Fri Jan 2 18:32:33 2009 -0800 fixed refs handling, added gc auto, updated tests commit d921970aadf03b3cf0e71becdaab3147ba71cdef Merge: 1c002dd... 35cfb2b... Author: Scott Chacon <schacon@gmail.com> Date: Thu Dec 11 15:08:43 2008 -0800 Merge commit 'phedders/rdocs' commit 1c002dd4b536e7479fe34593e72e6c6c1819e53b Author: Scott Chacon <schacon@gmail.com> Date: Thu Dec 11 14:58:32 2008 -0800 added some blame and merge stuff Sa kasong ito, sabihin mong interesado ka sa commit na kanino ang hash nagsisimula ng 1c002dd... . Maaari mong siyasatin ang commit na may anumang sumusunod na mga pagkakaiba-iba sa git show (ipagpalagay na mas maikling mga bersyon ay hindi malabo): $ git show 1c002dd4b536e7479fe34593e72e6c6c1819e53b $ git show 1c002dd4b536e7479f $ git show 1c002d Maaaring malaman ng Git ang isang maikli, natatanging pagpapaiklipara sa iyong SHA-1 na mga halaga. Kung ikaw ay nagpasa ng --abbrev-commit sa git log na utos, ang output ay gumamit ng mas maikling halaga ngunit panatilihin sila na katangi-tangi; ito ay mga default sa paggamit ng pitong mga karakter ngunit ginagawa nila ito na mas matagal kung kinakailangan upang mapanatiling hindi malinaw ang SHA-1: $ git log --abbrev-commit --pretty=oneline ca82a6d changed the version number 085bb3b removed unnecessary test code a11bef0 first commit Sa pangkalahatan, walo sa sampung mga karakter ay higit pa sa sapat upang maging natatanging sa loob ng isang proyekto. Halimbawa, sa Oktubre 2017, ang Linux na kernel (na kung saan ay isang medyo malaki na proyekto) ay may higit sa 700,000 na mga commit at halos anim na milyong na mga bagay, na may walang dalang mga bagay na magkatulad ang mga SHA-1 ay magkapareho sa unang 11 na mga karakter. Example 10. ISANG MAIKLING PAALALA TUNGKOL SA SHA-1 Maraming tao ay magiging nababahala sa isang punto na sila ay, sa pamamagitan ng sapalaran na pagkakataon, mayroong dalawang magkakaibang bagay sa kanilang repositoryo na ang hash ay pareho sa SHA-1 na halaga. Ano ngayon? Kung mangyari na ikaw ay mag-commit sa isang bagay na nag-hash sa parehong SHA-1 na halaga bilang isang nakaraang ibang bagay sa iyong repositoryo, Ang Git ay makakita ng nakaraan na bagay na nasa iyong Git na database, ipagpalagay na ito ay nakasulat na at muli lang gamitin ito. Kung subukan mong tingnan ang bagay na iyon muli sa isang punto, ikaw ay makakakuha lagi ng datos sa unang bagay. Gayunpaman, dapat mong malaman kung gaano katawa ang pagkawala sa sitwasyon na ito. Ang SHA-1 na digest ay 20 bytes o 160 bits. Ang bilang ng random na naka-hash na mga bagay na kinakailangan siguraduhin ang 50% na posibilidad ng isang banggaan ay mga 2 80 (ang formula para sa pagtukoy ng posibilidad ng banggaan ay p = (n(n-1)/2) * (1/2^160)) . 2 80 ay 1.2 x 10 24 o 1 milyon bilyon bilyon. Iyon ay 1,200 na beses ang bilang ng mga butil ng buhagin sa lupa. Narito ang isang halibawa na magbibigay sa iyo ng ideya kung ano ang kukuha nitong SHA-1 na banggaan Kung lahat sa 6.5 na bilyon na mga tayo sa Lupa ay nag-program, sa bawat segundo, sa bawat isa ay gumagawa ng code na katumbas sa buong Linux na kernel na kasaysayan(3.6 na milyong Git na mga bagay) at itinutulak into sa isang napakalaking Git na repositoryo, ito ay kukuha ng halos dalawang taon hanggang ang repositoryong ito ay maglalaman ng sapat na mga bagay upang magkaroon ng 50% na posibilidad sa isang SHA-1 na bagay na banggaan. Kaya naman, ang SHA-1 na banggaan ay mas malamang kaysa sa bawat miyembro sa iyong programming na koponan na inatake o napatay ng mga lobo sa hindi nauugnay na insidente sa parehong gabi. Mga Reperensiya ng Branch Isang tapat na paraan upang i-refer ang isang partikular na commit na kung itong commit na nasa tuktok na isang branch; sa ganitong kaso, maaari mo lamang gamitin ang pangalan ng branch sa anumang Git na utos na inaasahan ng isang reperensiya sa isang commit. Halimbawa, kung gusto mong suriin ang huling commit sa bagay sa branch, ang sumusunod na mga utos ay katumbas, ipagpalagay na ang topic1 na branch ay tumuturo sa commit sa ca82a6d... : $ git show ca82a6dff817ec66f44342007202690a93763949 $ git show topic1 Kung gusto mong makita kung saang tiyak na SHA-1 na branch tumuturo ito, o kung gusto mong makita ang kung anumang mga halimbawang ito na bumababa sa termino ng SHA-1s, maaari kang gumamit ng Git plumbing na kasangkapan na tinatawag na rev-parse . You can see Mga Panloob ng GIT for more information about plumbing tools; basically, rev-parse exists for lower-level operations and isn’t designed to be used in day-to-day operations. Gayunpaman, maaari itong makakatulong kung minsan kapag ikaw ay nangangailangan upang makita kung ano talaga ang nangyayari. Dito maaari kang magpatakbo ng rev-parse sa iyong branch. $ git rev-parse topic1 ca82a6dff817ec66f44342007202690a93763949 Mga Shortname ng RefLog Isa sa mga bagay ng Git ay gumawa ng background habang ikaw ay nagtratrabaho ng malayo ay magtago ng “reflog” — isang log na kung saan ang iyong HEAD at branch na mga reperensiya ay para sa huling ilang mga buwan. Maaari mong makita ang iyong reflog sa pamamagitan ng paggamit ng git reflog : $ git reflog 734713b HEAD@{0}: commit: fixed refs handling, added gc auto, updated d921970 HEAD@{1}: merge phedders/rdocs: Merge made by the 'recursive' stategy. 1c002dd HEAD@{2}: commit: added some blame and merge stuff 1c36188 HEAD@{3}: rebase -i (squash): updating HEAD 95df984 HEAD@{4}: commit: # This is a combination of two commits. 1c36188 HEAD@{5}: rebase -i (squash): updating HEAD 7e05da5 HEAD@{6}: rebase -i (pick): updating HEAD Sa tuwing iyong branch tip ay na-update sa anumang rason, ang Git ay nag-iimbak ng impormasyon para sa iyong temporaryong kasaysayan. Maaari mong gamitin ang iyong reflog na datos upang i-refer din ang mga lumang mga commit. Halimbawa, kung ikaw ay gustong makakita ng panglimang bago ang halaga sa HEAD ng iyong repositoryo, maaari mong gamitin ang @{5} na reperensiya na nakikita mo sa reflog output: $ git show HEAD@{5} Maaari mo ding gamitin ang syntax na ito upang makita kung saan ang branch ay ilang dami ng oras ang nakalipas. Halimbawa, para makita kung saan ang iyong master na branch kahapon, maaari kang mag-type ng $ git show master@{yesterday} Iyon ay magpapakita sa iyo kung saan ang tip ng iyong master na branch kahapon. Ang pamamaraan na ito ay gumagana lamang para sa datos na nasa iyong reflog pa, kaya ikaw ay hindi makagamit nito ng mga commit na mas luma pa sa ilang mga buwan. Upang makita ang reflog na impormasyon na naka-format tulad ng git log na output, maaari kang magpatakbo ng git log -g : $ git log -g master commit 734713bc047d87bf7eac9674765ae793478c50d3 Reflog: master@{0} (Scott Chacon <schacon@gmail.com>) Reflog message: commit: fixed refs handling, added gc auto, updated Author: Scott Chacon <schacon@gmail.com> Date: Fri Jan 2 18:32:33 2009 -0800 fixed refs handling, added gc auto, updated tests commit d921970aadf03b3cf0e71becdaab3147ba71cdef Reflog: master@{1} (Scott Chacon <schacon@gmail.com>) Reflog message: merge phedders/rdocs: Merge made by recursive. Author: Scott Chacon <schacon@gmail.com> Date: Thu Dec 11 15:08:43 2008 -0800 Merge commit 'phedders/rdocs' Mahalagang tandaan na ang reflog na impormasyon ay mahigpit na lokal — ito ay isang log lamang kung ano ang iyong nagawa sa iyong repositoryo. Ang mga reperensiya ay hindi pareho sa ibang kopya ng repositoryo; saka, pagkatapos ka mag-clone ng repositoryo, ikaw ay magkakarooon ng walang laman na reflog, na bilang walang aktibidad na naganap pa sa iyong repositoryo. Pagtatakbo ng git show HEAD@{2.months.ago} ay ipapakita sa iyo ang pagtutugma ng commit lamang kung ikaw ay nag-clone ng proyekto na hindi bababa sa dalawang buwan na nakalipas — kung na-clone mo itong mas kamakailan pa kaysa sa iyon, makikita mo lamang ang iyong unang lokal na commit. Tip Isipin ang reflog bilang bersyon ng Git sa kasaysayan ng shell Kung ikaw ay mayroong UNIX o Linux na karanasan, maaari mong isipin na ang iyong reflog bilang bersyon ng Git sa kasaysayan ng shell, na nagpapahiwatig na kung ano ang naroroon ay malinaw na may kaugnayan lamang para sa iyo at iyong “sesyon”, at walang kinalaman sa sinuman na maaaring nagtratrabaho sa parehong makina. Mga Reperensiya ng Kanunu-nunuan Ang iba pang pangunahing paraan upang tiyakin ang commit ay dumaan sa kanang kanunu-nunuan. Kung ikaw ay maglagay ng ^ (caret) sa katupusan ng reperensiya, ang Git ay naglulutas nito upang mangahulugang magulang sa commit na iyon. Ipagpalagay na tumugin ka sa kasaysayan ng iyong proyekto: $ git log --pretty=format:'%h %s' --graph * 734713b fixed refs handling, added gc auto, updated tests * d921970 Merge commit 'phedders/rdocs' |\ | * 35cfb2b Some rdoc changes * | 1c002dd added some blame and merge stuff |/ * 1c36188 ignore *.gem * 9b29157 add open3_detach to gemspec file list Pagkatapos, maaari mong makita ang nakaraaang commit sa pamamagitan sa pagtiyak ng HEAD^ , na ibig sabihin ay “ang magulang ng HEAD”: $ git show HEAD^ commit d921970aadf03b3cf0e71becdaab3147ba71cdef Merge: 1c002dd... 35cfb2b... Author: Scott Chacon <schacon@gmail.com> Date: Thu Dec 11 15:08:43 2008 -0800 Merge commit 'phedders/rdocs' Note Pag-alis ng caret sa Windows Sa Windows sa cmd.exe , ^ ay isang espesyal na karakter at nangangailangan upang tratuhin ng naiiba. Maaari mong doblehin ito o maglagay ng commit na reperensiya sa mga quote: $ git show HEAD^ # will NOT work on Windows $ git show HEAD^^ # OK $ git show "HEAD^" # OK Maaari mo ring tukuyin ang bilang pagkatapos ng ^ – halimbawa, ang d921970^2 ay ibig sabihin “ang ikalawang magulang sa d921970.” Ang syntax na ito ay kapaki-pakinabang lamang kung ang merge na mga commit, na may higit pa sa isang magulang. Ang unang magulang ay isang branch na ikaw ay nandoon noong ikaw ay nag-merge, at ang pangalawa ay ang commit na na-merge sa: $ git show d921970^ commit 1c002dd4b536e7479fe34593e72e6c6c1819e53b Author: Scott Chacon <schacon@gmail.com> Date: Thu Dec 11 14:58:32 2008 -0800 added some blame and merge stuff $ git show d921970^2 commit 35cfb2b795a55793d7cc56a6cc2060b4bb732548 Author: Paul Hedderly <paul+git@mjr.org> Date: Wed Dec 10 22:22:03 2008 +0000 Some rdoc changes Ang iba pang pangunahing kanunu-nunuan na pagtutukoy sa ~ (tilde). Ito rin ang tumutukoy sa unang magulang, kaya ang HEAD~ at HEAD^ ay magkatumbas. Ang pagkakaiba ay nagiging maliwanag kapag ikaw ang tumukoy ng isang numero. Ang HEAD~2 ay nangangahulugang “ang unang magulang sa unang magulang,” o “ang lolo o lola” — ito ay dumadaan sa unang mga magulang sa bilang sa maraming naitukoy. Halimbawa, sa kasaysayan na nakalista na mas maaga, ang HEAD~3 maaaring maging $ git show HEAD~3 commit 1c3618887afb5fbcbea25b7c013f4e2114448b8d Author: Tom Preston-Werner <tom@mojombo.com> Date: Fri Nov 7 13:47:59 2008 -0500 ignore *.gem Maaari itong maisulat na HEAD^^^ , na muli ang unang magulang sa unang magulang sa unang magulang: $ git show HEAD^^^ commit 1c3618887afb5fbcbea25b7c013f4e2114448b8d Author: Tom Preston-Werner <tom@mojombo.com> Date: Fri Nov 7 13:47:59 2008 -0500 ignore *.gem Maaari mo ring pagsamahin ang mga syntax na ito — maaari kang makakuha ng pangalawang magulang sa nakaraang reperensiya (ipagpapalagay na ito ay na-merge commit) sa pamamagitan ng paggamit ng HEAD~3^2 , at iba pa. Mga Lawak ng Commit Ngayon na magagawa mo na ang pagtukoy sa indibidwal na mga commit, tingnan natin kung paano magtukoy ng mga lawak sa mga commit. Ito ay partikular na kapaki-pakinabang para sa pagmamahala ng iyong mga branch — kung mayroon kang maraming mga branch, maaari mong gamitin ang lawak ng pagtutukoy upang sagutin ang mga tanong tulad ng, “Anong trabaho ang nasa branch na ito na hindi ko pa nai-merge sa aking pangunahing branch?” Dobleng Dot Ang pinaka-karaniwang na lawak na pagtutukoy ay ang doubleng-dot na syntax. Ito talaga ay nagtatanong sa Git na malutas ang lawak ng mga commit na mapupuntahan mula sa isang commit ngunit hindi maabot mula sa kabila. Halimbawa, sabihin na mayroon kang isang kasaysayan ng Git na mukhang ganito Halimbawa ng kasaysayan sa lawak ng pagpipilian. . Figure 137. Halimbawa ng kasaysayan sa lawak ng pagpipilian. Sabihin na gusto mong makita ang kung ano ang nasa iyong eksperimento na branch na hindi pa pinagsama sa iyong master na branch. Maaari kang magtanong sa Git upang ipakita sa iyo ang log ng mga commit na may master..experiment — ibig sabihin “ang lahat ng mga commit ay mapupuntahan mula sa eksperimento na hindi pa naabot mula sa master.” Para sa kapakanan ng kaiklian at kalinawan sa mga halimbawang ito, ang mga letra sa commit na mga bagay mula sa dayagram ay ginagamit sa lugar sa aktwal na log output sa pagkakasunod-sunod na sila ay magpakita: $ git log master..experiment D C Kung, sa kabila, ikaw ay gustong makita ang kabaligtaran — lahat ng mga commit sa master na wala sa experiment — maaari mong baligtarin ang mga pangalan ng branch. Ang experiment..master ay nagpapakita sa iyo ng lahat sa master na hindi maabot mula sa experiment : $ git log experiment..master F E Ito ay kapaki-pakinabang kung ikaw ay gustong magtago ng experiment branch na napapanahon at prebiyu sa kung ano ang nai-merge. Isa pang madalas gamitin sa syntax na ito ay tingnan kung ano ang iyong itutulak sa isang remote: $ git log origin/master..HEAD Ang utos na ito ay nagpapakita sa iyo sa anumang mga commit sa iyong kasalukuyang branch na wala pa sa master na branch sa iyong origin na remote. Kung ikaw ay magpatakbo ng git push ang iyong kasalukuyang branch ay nag-track sa origin/master , ang mga commit ay nailista sa pamamagitan ng git log origin/master..HEAD ay ang mga commit na iliipat sa server. Maaari mo ring iwanan ang isang bahagi ng syntax para magkaroon ng Git assume sa HEAD . Halimbawa, Maaari kang makakuha ng parehong mga resulta tulad ng sa nakaraang halimbawa sa pamamagitan nang pag-type ng git log origin/master.. — Git substitutes HEAD kung nawala ang isang panig. Maramihang mga Punto Ang dobleng-dot na syntax ay kapaki-pakinabang bilang isang shorthand, ngunit marahil gusto mong magtukoy ng higit pa sa dalawang mga branch upang ipahiwatig ang mga rebisyon, tulad ng nakikita kung ano ang mga commit na nasa ilang mga branch na wala sa branch na kasalukyang nasa iyo. Git allows you to do this by using either the ^ character or --not before any reference from which you don’t want to see reachable commits. Kaya naman, ang mga sumusunod na tatlong mga utos ay katumbas: $ git log refA..refB $ git log ^refA refB $ git log refB --not refA Ito ay maganda dahil kasama ang syntax na ito ay maaari kang magtukoy ng higit dalawang mga reperensiya sa iyong query, na kung saan ikaw ay hindi makagawa gamit ang dobleng-dot na syntax. Halimbawa, kung gusto mong makita ang lahat ng mga commit na maaaring mapuntahan mula sa refA o refB ngunit hindi mula sa refC , maaari mong gamitin ang alinman sa: $ git log refA refB ^refC $ git log refA refB --not refC Ginagawa ito para sa isang napakamakapangyarihan na rebisyong query na sistema na dapat makatulong sa iyo na para malaman kung ano ang nasa iyong mga branch. Triple na Dot Ang huling pangunahing na pagpili ng hanay na syntax ay ang tripleng-dot na syntax, na tumutukoy sa lahat ng mga commit na maaaring abutin sa alinman sa dalawang mga reperensiya ngunit hindi sa pamamagitan ng dalawang magkapareho. Tingnan uli ang halimbawa sa commit na kasaysayan sa Halimbawa ng kasaysayan sa lawak ng pagpipilian. . Kung gusto mong makita kung ano ang nasa master o experiment ngunit wala sa anumang karaniwang mga reperensiya, maaari kang magpatakbo ng: $ git log master...experiment F E D C Muli, ito ay nagbibigay sa iyo ng normal na log na output ngunit nagpapakita lamang sa commit na impormasyon para sa apat na mga commit, lumilitaw sa tradisyonal na commit na petsa ng pagkasunod-sunod. Isang karaniwang switch na gumagamit ng log na utos sa kasong ito ay --left-right , na kung saan ay nagpapakita kung saan na panig sa lawak ng bawat commit na nasa loob. Ito ay nakakatulong na makagawa ng output na mas kapaki-pakinabang: $ git log --left-right master...experiment < F < E > D > C Gamit ang mga kasangkapan, maaari mong mas madali maipaalam ni Get kung ano ang commit o mga commit na gusto mong siyasatin. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://l.facebook.com/l.php?u=https%3A%2F%2Fwww.instagram.com%2F&h=AT2nbAQgw-_I12x6Uj3oTNMu044hSnVN7yzk3wtbE4hEHyKRpuTtuNrhzFD7n-H70hqUe5MaB2UHwr4u011uH8BBrqTC-umL5k-D3RvP9x5q2Uzc7OEvhJgcPbC1wP0SlXkN_WqkpWJ7sJDi | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 새 계정 만들기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:29:25 |
https://www.linkedin.com/products/categories/application-performance-monitoring-software | Best Application Performance Monitoring (APM) 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 DevOps Engineer (24) Software Engineer (20) Site Reliability Engineer (15) Developer (11) Senior Software Engineer (8) See all products Find top products in Application Performance Monitoring (APM) Software category Software used to track application performance metrics and response time. - Quickly notify administrators of changes in baseline metrics - Measure end user experience, error rates, request rates, and availability - Provide data visualizations to assist in troubleshooting 93 results Cisco ThousandEyes Application Performance Monitoring (APM) Software by Cisco Instantly identify what is impacting user experiences across any domain—even those that you do not own or control. View product Datadog Application Performance Monitoring (APM) Software by Datadog Monitor infrastructure metrics, distributed traces, logs, and more in one unified platform with Datadog. View product Splunk Cloud Platform Application Performance Monitoring (APM) Software by Splunk Search, analyze, visualize and act on your data with a flexible and cost-effective data platform service. View product Elastic Observability Application Performance Monitoring (APM) Software by Elastic Elastic Observability gives your teams unified visibility across your entire ecosystem. Bring your logs, metrics, and APM traces together at scale in a single stack so you can monitor and react to events happening anywhere in your environment. Plus, it’s free and open. View product New Relic Application Performance Monitoring (APM) Software by New Relic Respond faster, optimize better, and build more perfect software. Monitor your entire stack on a single platform. 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 Sumo Logic Application Performance Monitoring (APM) Software by Sumo Logic Sumo Logic helps make the digital world faster, reliable and more secure by unifying insights to ignite action through the power of logs with its AI-powered SaaS Log Analytics Platform. View product Citrix Analytics (Performance Observability) Application Performance Monitoring (APM) Software by Citrix Citrix Analytics delivers actionable data and proactive insights to dramatically reduce mean time to detect (MTTD), mean time to resolve (MTTR), and root cause analysis (RCA), resulting in lifted user experience and reliability. The extensive variety of endpoint devices and connectivity options, such as Wi-Fi or LTE, escape the reach of conventional back-end monitoring, a gap that is effectively bridged by Citrix Analytics. In addition, uberAgent monitoring delivers lightweight agent insights and visibility of physical, virtual client, and server operating systems. Built into the Citrix platform, the granular analysis of application processes, web apps, network, and operating system metrics equips engineers and architects with the metrics they need for a better IT environment. View product New Relic APM Application Performance Monitoring (APM) Software by New Relic New Relic invented cloud APM for application engineers. Today it is a leader in observability and source of truth for all engineers to make decisions with data across their entire software stack and the software life cycle. There are an estimated 25 million engineers in the world across more than 25 distinct functions. As every company becomes a software company, engineers are using New Relic to gather real-time insights and trending data about the performance of their software so they can be more resilient and deliver exceptional customer experiences. Only New Relic provides an all-in-one platform that is built and sold as a unified experience. With New Relic, customers get access to a secure telemetry cloud for all metrics, events, logs, and traces; powerful full-stack analysis tools; and predictable user-based pricing. View product AppDynamics Application Performance Monitoring (APM) Software by AppDynamics Streamline the visualization of each component across complex application infrastructures to improve the user experience with performance monitoring. View product IBM Instana Application Performance Monitoring (APM) Software by IBM Data, AI & Automation DevOps, SRE, Platform, ITOps, and Developer teams face increasing challenges to ensure optimal application performance while operating with greater speed and efficiency. The process of modernization is already demanding, and observability shouldn't add to the complexity. Fortunately, with IBM Instana, real-time observability becomes effortless and accessible to all. Experience quick results and stay ahead of the dynamic complexities in today's and tomorrow's environments. From mobile to mainframe, Instana supports a vast range of over 250 technologies and continues to expand. Discover the power of Instana today and elevate your observability strategy. 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:25 |
https://git-scm.com/book/tl/v2/Pagsisimula-Pag-install-ng-Git | Git - Pag-install ng 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. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 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 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 1.5 Pagsisimula - Pag-install ng Git Pag-install ng Git Bago ka magsimulang gumamit ng Git, dapat mo itong i-install sa iyong kompyuter. Kahit pa na naka-install na ito, marahil ay magandang ideya pa rin na i-update ito sa pinakabagong bersyon. Maaari kang mag-install nito bilang isang package o sa pamamagitan ng ibang installer, o mag-download ng source code at i-compile mo ito nang ikaw lang. Ang aklat na ito ay isinulat gamit ang Git na bersyon 2.0.0 . Kahit na ang karamihan sa mga kautusan na gagamitin natin ay gagana pa rin sa napakalumang bersyon ng Git, ang iilan sa mga ito ay maaaring hindi o maaaring may medyong kaibahan kung gumamit ka ng lumang bersyon. Dahil ang Git ay sobrang mahusay sa pag-preserve ng backwards compatibility, kahit anung bersyon pagkatapos ng 2.0 ay gagana pa rin. Pag-install sa Linux Kung gusto mong i-install ang mga pangunahing kagamitan ng Git sa Linux sa pamamagitan ng isang binary na installer, maaari mo itong gawin sa pangunahing package-management na kagamitan na kalakip ng iyong distribusyon. Kung ikaw ay nasa Fedora bilang halimbawa (o kahit anong kaparehong RPM-based na distro gaya ng RHEL o CentOS), maaari mong gamitin ang dnf : $ sudo dnf install git-all Kung ikaw ay nasa Debian-based na distribusyon gaya ng Ubuntu, subukan ang apt-get : $ sudo apt-get install git-all Para sa karagdagang mga opsyon, mayroong mga hakbang sa pag-install sa iilang iba-ibang mga Unix Flavors sa Git na website, sa http://git-scm.com/download/linux . Pag-instal sa Mac Mayroong iba’t ibang pamamaraan ng pag-install ng Git sa Mac. Ang pinakamadali ay marahil ang pag-install ng Xcode Command Line Tools. Sa Mavericks (10.0) o mas mataas pa, maaari mo itong magawa sa simpleng pagpapatakbo ng git mula sa Terminal sa unang pagkakataon. $ git --version Kung hindi mo pa ito na-install, ito ay mag-prompt sa iyo na i-install ito. Kung gusto mo ang isang mas bago na bersyon, maaari mo rin itong i-install sa pamamagitan ng isang binary na installer. Ang macOS Git na installer ay naka-maintain at mai-download mula sa Git na website, sa http://git-scm.com/download/mac . Figure 7. Git macOS na Installer. Maari mo rin itong i-install bilang bahagi ng GitHub para sa Mac na pag-install. Ang kanilang GUI Git na kagamitan ay mayroong ding opsyon na mag-install na command line na mga kagamitan. Maaari mong i-download ang kagamitan na ito mula sa Github para sa Mac na website, sa http://mac.github.com . Pag-install sa Windows Mayroon ding maraming pamamaraan ng pag-install ng Git sa Windows. Ang pinaka-opisyal na build ay mai-download mula sa Git na website. Pumunta lang sa http://git-scm.com/download/win at ito ay awtomatikong mag-download. Tandaan na ito ay isang proyekto na tinatawag na Git para sa Windows, kung saan hiwalay sa mismong Git; para sa karagdagang impormasyon tungkol dito, pumunta sa https://git-for-windows.github.io/ . Para makakuha ng automated na pag-install maaari mong gamitin ang Git Chocolatey package . Tandaan na ang Chocolatey na package ay pinangasiwaan ng komunidad. Isa pang madaling paraan para ma-install ang Git ay sa pamamagitan ng pag-install ng GitHub para sa Windows. Ang installer ay naglakip ng command line na bersyon ng Git, pati na rin ang GUI. Maaari din itong gumana kasabay ang Powershell, at nag set-up ng matatag na credential caching at magaling na CRLF na mga setting. Matutunan pa natin ang tungkol sa mga bagay na iyon mga ilang sandali, ngunit sapat na sabihin natin na iyon ang mga bagay na gugustuhin mo. Maaari mo itong i-download mula GitHub para sa Windows na website, sa http://windows.github.com . Pag-install mula sa Source May iilang mga tao ang gustong mag-install ng Git mula sa source, dahil makukuha mo ang pinakabagong bersyon. Ang mga binary na installer ay maaaring huli ng kaunti, ngunit ang Git ay nag-mature na sa nakaraang mga taon, ito ay wala nang masyadong kaibahan. Kung gusto mo pa ring mag-install ng Git mula sa source, kakailanganin mo ang sumusunod na mga library kung saan ang Git ay nakadepende: autotools, curl, zlib, openssl, expat, at libiconv. Halimbawa, kung ikaw ay nasa isang sistema na mayroong dnf (gaya ng Fedora) o apt-get (gaya ng Debian-based na sistema), maaari mong gamitin ang isa sa mga command na ito para mag-install ng minimal na dependencies para sa pag-compile at pag-install ng Git na mga binaries. $ sudo dnf install dh-autoreconf curl-devel expat-devel gettext-devel \ openssl-devel perl-devel zlib-devel $ sudo apt-get install dh-autoreconf libcurl4-gnutls-dev libexpat1-dev \ gettext libz-dev libssl-dev Para magawa mo ang pagdagdag ng dokumentasyon sa iba’t ibang format (doc, html, info), ang mga karagdagang dependencies na ito ay kinakailangan (Tandaan: ang mga gumagamit ng RHEL at RHEL-derivatives gaya ng CentOS at Scientific Linux ay kinakailangang i-enable ang EPEL na repository para ma-download ang docbook2X na package): $ sudo dnf install asciidoc xmlto docbook2X getopt $ sudo apt-get install asciidoc xmlto docbook2x getopt Bukod dito, kung ikaw ay gumagamit ng Fedora/RHEL/RHEL-derivatives, kailangan mong gawin ito $ sudo ln -s /usr/bin/db2x_docbook2texi /usr/bin/docbook2x-texi dahil sa mga kaibahan ng binary name. Kung mayroon ka na sa lahat ng kinakailangang mga dependecies, maaari ka nang magpatuloy at kumuha ng pinakabagong tagged na release tarball mula sa iilang mga lugar. Maaari mo itong makuha sa kernel.org na site, sa https://www.kernel.org/pub/software/scm/git , o sa mirror na nasa GitHub na website, sa https://github.com/git/git/releases . Karaniwang mas malinaw kung ano ang pinakabagong bersyon sa GitHub na pahina, ngunit ang kernel.org na pahina ay mayroon ding mga release signatures kung gusto mong i-verify ang iyong download. Pagkatapos, ay mag-compile at mag-install: $ tar -zxf git-2.0.0.tar.gz $ cd git-2.0.0 $ make configure $ ./configure --prefix=/usr $ make all doc info $ sudo make install install-doc install-html install-info Pagkatapos magawa ito, maaari mo ring kunin ang Git sa Git mismo para sa mga updates: $ git clone git://git.kernel.org/pub/scm/git/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:25 |
https://babelfish.gitbook.io/the-babelfish-gitbook/ | Welcome! | BabelFish.Money bars BabelFish.Money search circle-xmark Ctrl k Welcome! Getting Started 💡 What is BabelFish ⚖️ What does Babelfish Solve 💫 Cross-Chain Multiverse 📊 Balancing Curves 👥 The Team & The Dao 🗺️ Roadmap ❓ FAQ ❗ Risk Tokens 🪙 Staking ⏰ Early unstaking 📜 Governance 🐡 Tokenomics Tutorials & guides 🏦 Connecting Your Wallet 🪐 Bridge 🌉 Using BabelFish Bridge 🚀 Rules for Turbocharging Rootstock's Stablecoin Liquidity Pilot Campaign ✅ Voting 🖥️ Voting Power 🛠️ Troubleshooting 📊 XUSD Statistics Content & Social Media 🗣️ Social Media 📺 Community Calls 🧑🔬 Join us 🏁 Bounties gitbook Powered by GitBook block-quote On this page chevron-down copy Copy chevron-down Welcome! Welcome DeFi Hitchhiker! We are glad that your DeFi-journey brought you to Babelfish! If you still have any questions after your visit here, please do not hesitate to connect with your fellow travelers through our social media . Our community is there to help and support each other and we welcome you with open arms. Next What is BabelFish chevron-right Last updated 3 years ago | 2026-01-13T09:29:25 |
https://www.linkedin.com/products/notionhq-notion?similarProducts=true&trk=products_details_guest_similar_products_section_sign_in#main-content | Notion | LinkedIn Skip to main content LinkedIn Notion 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 Notion Knowledge Management Software by Notion See who's skilled in this Add as skill Learn more Report this product About Notion is the AI workspace where teams and agents get more done together. Assign the task, and your Agents will get to work alongside your team in one connected workspace. Together, you’ll create docs, manage projects, find answers across your apps, and automate repetitive tasks to spend less time on busywork and more time on your life’s work. Media Products media viewer No more previous content This is Notion Notion is a single space where you can think, write, and plan. Capture thoughts, manage projects, or even run an entire company — and do it exactly the way you want. Wiki Create a destination for your team to find all the the information they need - from vacation policies to company directories. Project Management Track your work any way you want - with tables, Kanban boards, calendars, and lists. Notion databases are so customizable, you can build your own tools to match any workflow. Notes & Docs Keep all your documents together, tagged, and easily searchable. Meeting notes are just one example. You can format your docs exactly the way you want, and share them with the right folks with one click. Build & Publish You can create whatever you need with Notion - like this job board. It's a snap to publish a page like this to the web so that anyone can see it. No need to spend the time wrangling with a website builder when you can put up a simple site that's also instantly editable. No more next content Featured customers of Notion Pernod Ricard Beverage Manufacturing 907,762 followers Kaiser Permanente Hospitals and Health Care 1,049,984 followers PayPal Software Development 1,615,662 followers Volvo Group Motor Vehicle Manufacturing 2,223,520 followers Accor Hospitality 2,470,557 followers NVIDIA Computer Hardware Manufacturing 4,566,091 followers TIME Book and Periodical Publishing 2,475,910 followers Discord Software Development 467,975 followers Toyota Motor Corporation Motor Vehicle Manufacturing 2,293,377 followers Ramp Financial Services 261,454 followers Mitsubishi Heavy Industries Industrial Machinery Manufacturing 280,462 followers Vercel Software Development 194,602 followers Capgemini IT Services and IT Consulting 8,651,141 followers OpenAI Research Services 9,664,902 followers Figma Design Services 1,953,092 followers KPMG Accounting 5,197,789 followers Affirm Financial Services 329,011 followers Konfío Financial Services 87,349 followers Andreessen Horowitz Venture Capital and Private Equity Principals 617,860 followers SKIMS Retail Apparel and Fashion 266,763 followers Show more Show less Similar products Jira Jira Project Management Software Trello Trello Project Management Software GitHub Issues GitHub Issues Project Management Software Zoho Projects Zoho Projects Project Management Software Asana Asana Project Management Software Zoho Sprints Zoho Sprints Project Management Software Sign in to see more Show more Show less Notion products Notion Calendar Notion Calendar Calendar Software Notion Mail Notion Mail Email 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:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#param-url-4 | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://docs.aws.amazon.com/ko_kr/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-common-scenarios.html | CloudWatch 에이전트를 사용하는 일반적인 시나리오 - Amazon CloudWatch CloudWatch 에이전트를 사용하는 일반적인 시나리오 - Amazon CloudWatch 설명서 Amazon CloudWatch 사용자 가이드 다른 사용자로 CloudWatch 에이전트 실행 CloudWatch 에이전트가 희소 로그 파일을 처리하는 방법 CloudWatch 에이전트가 수집한 지표에 사용자 지정 측정기준 추가 CloudWatch 에이전트가 수집한 지표 집계 또는 롤업 CloudWatch 에이전트로 고분해능 지표 수집 다른 계정에 지표, 로그, 추적 전송 CloudWatch 에이전트와 이전 CloudWatch Logs 에이전트 간 타임스탬프 차이 OpenTelemetry 수집기 구성 파일 추가 CloudWatch 에이전트를 사용하는 일반적인 시나리오 이 섹션에서는 CloudWatch 에이전트에 대한 일반적인 구성 및 사용자 지정 태스크를 완료하는 방법을 설명하는 다양한 시나리오를 제공합니다. 주제 다른 사용자로 CloudWatch 에이전트 실행 CloudWatch 에이전트가 희소 로그 파일을 처리하는 방법 CloudWatch 에이전트가 수집한 지표에 사용자 지정 측정기준 추가 CloudWatch 에이전트가 수집한 지표 집계 또는 롤업 CloudWatch 에이전트로 고분해능 지표 수집 다른 계정에 지표, 로그, 추적 전송 CloudWatch 에이전트와 이전 CloudWatch Logs 에이전트 간 타임스탬프 차이 OpenTelemetry 수집기 구성 파일 추가 다른 사용자로 CloudWatch 에이전트 실행 Linux 서버에서 CloudWatch는 기본적으로 루트 사용자로 실행됩니다. 에이전트를 다른 사용자로 실행하려면 CloudWatch 에이전트 구성 파일의 agent 섹션에 있는 run_as_user 파라미터를 사용합니다. 이 옵션은 Linux 서버에서만 사용할 수 있습니다. 이미 루트 사용자로 에이전트를 실행 중인데 다른 사용자를 사용하도록 변경하려면 다음 절차 중 하나를 사용하세요. Linux를 실행하는 EC2 인스턴스에서 CloudWatch 에이전트를 다른 사용자로 실행하려면 새 CloudWatch 에이전트 패키지를 다운로드하여 설치합니다. 새 Linux 사용자를 생성하거나 RPM 또는 DEB 파일이 생성한 기본 사용자 cwagent 를 사용합니다. 다음 중 한 가지 방법으로 이 사용자에 대한 자격 증명을 제공합니다. .aws/credentials 파일이 루트 사용자의 홈 디렉터리에 있는 경우 CloudWatch 에이전트를 실행하는 데 사용할 사용자의 자격 증명 파일을 생성해야 합니다. 이 자격 증명 파일은 /home/ username /.aws/credentials 입니다. 그런 다음 common-config.toml 에 있는 shared_credential_file 파라미터 값을 자격 증명 파일의 경로 이름으로 설정합니다. 자세한 내용은 AWS Systems Manager를 사용하여 CloudWatch 에이전트 설치 섹션을 참조하세요. .aws/credentials 파일이 루트 사용자의 홈 디렉터리에 없는 경우 다음 중 하나를 수행할 수 있습니다. CloudWatch 에이전트를 실행하는 데 사용할 사용자의 자격 증명 파일을 생성합니다. 이 자격 증명 파일은 /home/ username /.aws/credentials 입니다. 그런 다음 common-config.toml 에 있는 shared_credential_file 파라미터 값을 자격 증명 파일의 경로 이름으로 설정합니다. 자세한 내용은 AWS Systems Manager를 사용하여 CloudWatch 에이전트 설치 섹션을 참조하세요. 자격 증명 파일을 생성하는 대신 인스턴스에 IAM 역할을 연결합니다. 에이전트는 이 역할을 자격 증명 공급자로 사용합니다. CloudWatch 에이전트 구성 파일에서 agent 섹션에 다음 줄을 추가합니다. "run_as_user": " username " 필요에 따라 구성 파일을 추가로 수정합니다. 자세한 내용은 CloudWatch 에이전트 구성 파일 생성 섹션을 참조하세요. 사용자에게 필수 권한을 부여하세요. 사용자는 수집할 로그 파일에 대한 읽기(r) 권한이 있어야 하며 로그 파일 경로의 모든 디렉터리에 대해 실행(x) 권한이 있어야 합니다. 방금 수정한 구성 파일로 에이전트를 시작합니다. sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a fetch-config -m ec2 -s -c file: configuration-file-path Linux를 실행하는 온프레미스 서버에서 CloudWatch 에이전트를 다른 사용자로 실행하려면 새 CloudWatch 에이전트 패키지를 다운로드하여 설치합니다. 새 Linux 사용자를 생성하거나 RPM 또는 DEB 파일이 생성한 기본 사용자 cwagent 를 사용합니다. 이 사용자의 자격 증명을 사용자가 액세스할 수 있는 경로(예: /home/ username /.aws/credentials )에 저장합니다. common-config.toml 에 있는 shared_credential_file 파라미터 값을 자격 증명 파일의 경로 이름으로 설정합니다. 자세한 내용은 AWS Systems Manager를 사용하여 CloudWatch 에이전트 설치 섹션을 참조하세요. CloudWatch 에이전트 구성 파일에서 agent 섹션에 다음 줄을 추가합니다. "run_as_user": " username " 필요에 따라 구성 파일을 추가로 수정합니다. 자세한 내용은 CloudWatch 에이전트 구성 파일 생성 단원을 참조하세요. 사용자에게 필수 권한을 부여하세요. 사용자는 수집할 로그 파일에 대한 읽기(r) 권한이 있어야 하며 로그 파일 경로의 모든 디렉터리에 대해 실행(x) 권한이 있어야 합니다. 방금 수정한 구성 파일로 에이전트를 시작합니다. sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a fetch-config -m ec2 -s -c file: configuration-file-path CloudWatch 에이전트가 희소 로그 파일을 처리하는 방법 희소 파일은 빈 블록과 실제 내용이 모두 포함된 파일입니다. 희소 파일은 블록을 구성하는 실제 null 바이트 대신 빈 블록을 나타내는 간단한 정보를 디스크에 작성하여 디스크 공간을 보다 효율적으로 사용합니다. 이렇게 하면 일반적으로 희소 파일의 실제 크기가 명백한 크기보다 훨씬 작아집니다. 그러나 CloudWatch 에이전트는 희소 파일을 일반 파일 처리 방법과 다르게 처리하지 않습니다. 에이전트가 희소 파일을 읽을 때 빈 블록은 null 바이트로 채워진 “실제” 블록으로 처리됩니다. 이 때문에 CloudWatch 에이전트는 희소 파일의 외관상 크기만큼의 바이트를 CloudWatch에 게시합니다. 희소 파일을 게시하도록 CloudWatch 에이전트를 구성하면 예상보다 높은 CloudWatch 비용이 발생할 수 있으므로 그렇게 하지 않는 것이 좋습니다. 예를 들어 Linux의 /var/logs/lastlog 는 일반적으로 희소 파일이므로 CloudWatch에 게시하지 않는 것이 좋습니다. CloudWatch 에이전트가 수집한 지표에 사용자 지정 측정기준 추가 에이전트에 의해 수집되는 지표에 태그와 같은 사용자 지정 측정기준을 추가하려면 해당 지표를 나열하는 에이전트 구성 파일의 섹션에 append_dimensions 필드를 추가하세요. 예를 들어, 구성 파일의 다음 예제 섹션에서는 stackName 의 값이 포함된 Prod 라는 사용자 지정 측정기준을 에이전트에 의해 수집된 cpu 및 disk 지표에 추가합니다. "cpu": { "resources":[ "*" ], "measurement":[ "cpu_usage_guest", "cpu_usage_nice", "cpu_usage_idle" ], "totalcpu":false, "append_dimensions": { "stackName":"Prod" } }, "disk": { "resources":[ "/", "/tmp" ], "measurement":[ "total", "used" ], "append_dimensions": { "stackName":"Prod" } } 에이전트 구성 파일을 변경할 때마다 에이전트를 다시 시작하여 변경 사항을 적용해야 합니다. CloudWatch 에이전트가 수집한 지표 집계 또는 롤업 에이전트에 의해 수집되는 지표를 집계하거나 롤업하려면 에이전트 구성 파일의 해당 지표에 대한 섹션에 aggregation_dimensions 필드를 추가하세요. 예를 들어, 다음 구성 파일 조각은 AutoScalingGroupName 측정기준에서 지표를 롤업합니다. 각 Auto Scaling 그룹의 모든 인스턴스에서 지표가 집계되어 전체적으로 표시될 수 있습니다. "metrics": { "cpu": { ...} "disk": { ...} "aggregation_dimensions" : [["AutoScalingGroupName"]] } Auto Scaling 그룹 이름에서 롤업할 뿐 아니라 InstanceId 및 InstanceType 측정기준 각각의 조합을 따라 롤업하려면 다음을 추가합니다. "metrics": { "cpu": { ...} "disk": { ...} "aggregation_dimensions" : [["AutoScalingGroupName"], ["InstanceId", "InstanceType"]] } 대신 지표를 하나의 모음에 롤업하려면 [] 를 사용합니다. "metrics": { "cpu": { ...} "disk": { ...} "aggregation_dimensions" : [[]] } 에이전트 구성 파일을 변경할 때마다 에이전트를 다시 시작하여 변경 사항을 적용해야 합니다. CloudWatch 에이전트로 고분해능 지표 수집 metrics_collection_interval 필드는 수집되는 지표의 시간 간격을 초 단위로 지정합니다. 이 필드에 60 미만의 값을 지정하면 지표가 고분해능 지표로 수집됩니다. 예를 들어, 모든 지표가 고해상도 지표이며 10초마다 수집되어야 하는 경우 agent 섹션의 metrics_collection_interval 에서 글로벌 지표 수집 간격 값으로 10을 지정합니다. "agent": { "metrics_collection_interval": 10 } 또는 다음 예에서는 cpu 지표는 1초마다 수집되도록 설정하고 다른 모든 지표는 1분마다 수집되도록 설정합니다. "agent": { "metrics_collection_interval": 60 }, "metrics": { "metrics_collected": { "cpu": { "resources":[ "*" ], "measurement":[ "cpu_usage_guest" ], "totalcpu":false, "metrics_collection_interval": 1 }, "disk": { "resources":[ "/", "/tmp" ], "measurement":[ "total", "used" ] } } } 에이전트 구성 파일을 변경할 때마다 에이전트를 다시 시작하여 변경 사항을 적용해야 합니다. 다른 계정에 지표, 로그, 추적 전송 CloudWatch 에이전트가 지표, 로그, 추적을 다른 계정에 전송하도록 하려면 전송 서버의 에이전트 구성 파일에서 role_arn 파라미터를 지정합니다. role_arn 값은 에이전트가 데이터를 대상 계정에 전송할 때 사용하는 대상 계정의 IAM 역할을 지정합니다. 지표 또는 로그를 대상 계정에 전달할 때는 이 역할을 통해 전송 계정이 대상 계정의 해당 역할을 맡을 수 있습니다. 에이전트 구성 파일에 지표를 보낼 때 사용할 문자열, 로그를 보낼 때 사용할 문자열, 추적을 보낼 때 사용할 문자열 등 role_arn 문자열을 별도로 지정할 수도 있습니다. 구성 파일의 agent 섹션 부분에 대한 다음의 예에서는 데이터를 다른 계정에 보낼 때 CrossAccountAgentRole 을 사용하도록 에이전트를 설정합니다. { "agent": { "credentials": { "role_arn": "arn:aws:iam::123456789012:role/CrossAccountAgentRole" } }, ..... } 또는 다음 예에서는 지표, 로그 및 추적 전송에 사용할 전송 계정에 대해 서로 다른 역할을 설정합니다. "metrics": { "credentials": { "role_arn": "RoleToSendMetrics" }, "metrics_collected": { .... "logs": { "credentials": { "role_arn": "RoleToSendLogs" }, .... 필요한 정책 에이전트 구성 파일에서 role_arn 을 지정할 때 전송 및 대상 계정의 IAM 역할에 특정 정책이 있는지도 확인해야 합니다. 전송 계정과 대상 계정의 역할에는 모두 CloudWatchAgentServerPolicy 가 있어야 합니다. 이 정책을 역할에 지정하는 방법에 대한 자세한 내용은 사전 조건 단원을 참조하세요. 전송 계정의 역할은 다음의 정책을 포함해야 합니다. 역할을 편집할 때 IAM 콘솔의 [ 권한(Permissions) ] 탭에서 이 정책을 추가합니다. JSON { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "sts:AssumeRole" ], "Resource": [ "arn:aws:iam:: 111122223333 :role/ agent-role-in-target-account " ] } ] } 대상 계정의 역할에는 전송 계정에서 사용하는 IAM 역할을 인식하도록 다음 정책이 포함되어야 합니다. 역할을 편집할 때 IAM 콘솔의 [ 신뢰 관계(Trust relationships) ] 탭에서 이 정책을 추가합니다. 이 역할은 전송 계정에서 사용한 정책의 agent-role-in-target-account 에 지정된 역할입니다. JSON { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": [ "arn:aws:iam:: 111122223333 :role/ role-in-sender-account " ] }, "Action": "sts:AssumeRole" } ] } CloudWatch 에이전트와 이전 CloudWatch Logs 에이전트 간 타임스탬프 차이 CloudWatch 에이전트는 이전 CloudWatch Logs 에이전트와 비교했을 때 타임스탬프 형식에 대해 다른 기호 집합을 지원합니다. 이러한 차이는 다음 표에 표시됩니다. 두 에이전트 모두에서 지원하는 기호 CloudWatch 에이전트에서만 지원하는 기호 이전 CloudWatch Logs 에이전트에서만 지원하는 기호 %A, %a, %b, %B, %d, %f, %H, %l, %m, %M, %p, %S, %y, %Y, %Z, %z %-d, %-l, %-m, %-M, %-S %c,%j, %U, %W, %w 새 CloudWatch 에이전트에서 지원하는 기호의 의미에 대한 자세한 내용은 Amazon CloudWatch 사용 설명서 의 CloudWatch 에이전트 구성 파일: 로그 섹션 단원을 참조하세요. CloudWatch Logs 에이전트에서 지원하는 기호에 대한 자세한 내용은 Amazon CloudWatch Logs 사용 설명서 의 에이전트 구성 파일 단원을 참조하세요. OpenTelemetry 수집기 구성 파일 추가 CloudWatch 에이전트는 자체 구성 파일과 함께 추가 OpenTelemetry 수집기 구성 파일을 지원합니다. 이 기능을 사용하면 CloudWatch 에이전트 구성을 통해 CloudWatch 에이전트 기능(예: CloudWatch Application Signals 또는 Container Insights)을 사용하고, 단일 에이전트를 활용하여 기존 OpenTelemetry 수집기 구성을 가져올 수 있습니다. CloudWatch 에이전트가 자동으로 생성한 파이프라인과의 병합 충돌을 방지하려면, OpenTelemetry 수집기 구성의 각 구성 요소 및 파이프라인에 사용자 지정 접미사를 추가하는 것이 좋습니다. receivers: otlp/custom-suffix: protocols: http: exporters: awscloudwatchlogs/custom-suffix: log_group_name: "test-group" log_stream_name: "test-stream" service: pipelines: logs/custom-suffix: receivers: [otlp/custom-suffix] exporters: [awscloudwatchlogs/custom-suffix] CloudWatch 에이전트를 구성하려면 fetch-config 옵션을 사용하여 CloudWatch 에이전트를 시작하고, CloudWatch 에이전트의 구성 파일을 지정합니다. CloudWatch 에이전트에는 하나 이상의 CloudWatch 에이전트 구성 파일이 필요합니다. /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a fetch-config -c file:/tmp/agent.json -s 그런 다음, append-config 옵션을 사용하여 OpenTelemetry 수집기 구성 파일을 지정합니다. /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a append-config -c file:/tmp/otel.yaml -s 에이전트는 시작 시 2가지 구성 파일을 병합하고, 해결된 구성을 로깅합니다. javascript가 브라우저에서 비활성화되거나 사용이 불가합니다. AWS 설명서를 사용하려면 Javascript가 활성화되어야 합니다. 지침을 보려면 브라우저의 도움말 페이지를 참조하십시오. 문서 규칙 관련 원격 측정과 함께 CloudWatch 에이전트 사용 CloudWatch 에이전트 자격 증명 기본 설정 이 페이지의 내용이 도움이 되었습니까? - 예 칭찬해 주셔서 감사합니다! 잠깐 시간을 내어 좋았던 부분을 알려 주시면 더 열심히 만들어 보겠습니다. 이 페이지의 내용이 도움이 되었습니까? - 아니요 이 페이지에 작업이 필요하다는 점을 알려 주셔서 감사합니다. 실망시켜 드려 죄송합니다. 잠깐 시간을 내어 설명서를 향상시킬 수 있는 방법에 대해 말씀해 주십시오. | 2026-01-13T09:29:25 |
https://docs.aws.amazon.com/zh_cn/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-common-scenarios.html | CloudWatch 代理的常见场景 - Amazon CloudWatch CloudWatch 代理的常见场景 - Amazon CloudWatch 文档 Amazon CloudWatch 用户指南 以不同用户身份运行 CloudWatch 代理 CloudWatch 代理如何处理稀疏日志文件 将自定义维度添加到 CloudWatch 代理收集的指标 汇总或累积 CloudWatch 代理收集的指标 使用 CloudWatch 代理收集高精度指标 向不同账户发送指标、日志和跟踪信息 CloudWatch 代理与旧版 CloudWatch Logs 代理之间的时间戳差异 追加 OpenTelemetry 收集器配置文件 CloudWatch 代理的常见场景 本节为您提供不同的场景，概述如何完成 CloudWatch 代理的常见配置和自定义任务。 主题 以不同用户身份运行 CloudWatch 代理 CloudWatch 代理如何处理稀疏日志文件 将自定义维度添加到 CloudWatch 代理收集的指标 汇总或累积 CloudWatch 代理收集的指标 使用 CloudWatch 代理收集高精度指标 向不同账户发送指标、日志和跟踪信息 CloudWatch 代理与旧版 CloudWatch Logs 代理之间的时间戳差异 追加 OpenTelemetry 收集器配置文件 以不同用户身份运行 CloudWatch 代理 在 Linux 服务器上，CloudWatch 默认以根用户身份运行。要让代理以不同用户身份运行，请在 CloudWatch 代理配置文件的 agent 部分中使用 run_as_user 参数。该选项仅在 Linux 服务器上可用。 如果已使用 root 用户运行代理并希望更改为使用不同的用户，请使用以下过程之一。 在运行 Linux 的 EC2 实例上以不同用户身份运行 CloudWatch 代理 下载并安装新的 CloudWatch 代理软件包。 创建新的 Linux 用户，或使用 RPM 或 DEB 文件创建的默认用户（名为 cwagent ）。 使用以下方式之一为该用户提供凭证： 如果文件 .aws/credentials 存在于根用户的主目录中，您必须为要用于运行 CloudWatch 代理的用户创建一个凭证文件。该凭证文件是 /home/ username /.aws/credentials 。然后，将 common-config.toml 中的 shared_credential_file 参数值设置为凭证文件的路径名。有关更多信息，请参阅 使用 AWS Systems Manager 安装 CloudWatch 代理 。 如果根用户的主目录中不存在文件 .aws/credentials ，您可以执行下列操作之一： 为要用于运行 CloudWatch 代理的用户创建一个凭证文件。该凭证文件是 /home/ username /.aws/credentials 。然后，将 common-config.toml 中的 shared_credential_file 参数值设置为凭证文件的路径名。有关更多信息，请参阅 使用 AWS Systems Manager 安装 CloudWatch 代理 。 将 IAM 角色附加到实例，而不是创建凭证文件。代理将该角色作为凭证提供程序。 在 CloudWatch 代理配置文件中，在 agent 部分中添加以下行： "run_as_user": " username " 根据需要，对该配置文件进行其他修改。有关更多信息，请参阅 创建 CloudWatch 代理配置文件 。 为用户提供所需的权限。用户必须拥有要收集的日志文件的 Read (r) 权限，并且必须对日志文件路径中的每个目录具有 Execute (x) 权限。 使用刚修改的配置文件启动代理。 sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a fetch-config -m ec2 -s -c file: configuration-file-path 在运行 Linux 的本地部署服务器上以不同用户身份运行 CloudWatch 代理 下载并安装新的 CloudWatch 代理软件包。 创建新的 Linux 用户，或使用 RPM 或 DEB 文件创建的默认用户（名为 cwagent ）。 将该用户的凭证存储到用户可访问的路径中，例如 /home/ username /.aws/credentials 。 将 common-config.toml 中的 shared_credential_file 参数值设置为凭证文件的路径名。有关更多信息，请参阅 使用 AWS Systems Manager 安装 CloudWatch 代理 。 在 CloudWatch 代理配置文件中，在 agent 部分中添加以下行： "run_as_user": " username " 根据需要，对该配置文件进行其他修改。有关更多信息，请参阅 创建 CloudWatch 代理配置文件 。 为用户提供所需的权限。用户必须拥有要收集的日志文件的 Read (r) 权限，并且必须对日志文件路径中的每个目录具有 Execute (x) 权限。 使用刚修改的配置文件启动代理。 sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a fetch-config -m ec2 -s -c file: configuration-file-path CloudWatch 代理如何处理稀疏日志文件 稀疏文件是具有空块和真实内容的文件。稀疏文件通过将表示空块的简短信息（而不是构成此块的实际 Null 字节）写入磁盘，以更有效地使用磁盘空间。这使得稀疏文件的实际大小通常比其表观大小小得多。 但是，CloudWatch 代理对稀疏文件的处理方式与对普通文件的处理方式不同。当代理读取稀疏文件时，空块被视为填充 Null 字节的“真实”块。因此，CloudWatch 代理向 CloudWatch 发布的字节数与稀疏文件的表观大小相同。 配置 CloudWatch 代理来发布稀疏文件可能会导致高于预期 CloudWatch 成本，因此我们建议不要这样做。例如，Linux 中的 /var/logs/lastlog 通常是一个非常稀疏的文件，我们建议您不要将其发布到 CloudWatch。 将自定义维度添加到 CloudWatch 代理收集的指标 要将自定义维度 (如标签) 添加到该代理收集的指标中，请将 append_dimensions 字段添加到代理配置文件中列出这些指标的部分。 例如，以下示例配置文件部分将一个名为 stackName 且值为 Prod 的自定义维度添加到该代理收集的 cpu 和 disk 指标中。 "cpu": { "resources":[ "*" ], "measurement":[ "cpu_usage_guest", "cpu_usage_nice", "cpu_usage_idle" ], "totalcpu":false, "append_dimensions": { "stackName":"Prod" } }, "disk": { "resources":[ "/", "/tmp" ], "measurement":[ "total", "used" ], "append_dimensions": { "stackName":"Prod" } } 切记，每次更改代理配置文件时，您必须重新启动该代理以使更改生效。 汇总或累积 CloudWatch 代理收集的指标 要汇总或累积该代理收集的指标，请将 aggregation_dimensions 字段添加到代理配置文件中与该指标对应的部分。 例如，以下配置文件片段累积 AutoScalingGroupName 维度上的指标。每个 Auto Scaling 组的所有实例中的指标将进行汇总，可以将这些指标作为一个整体进行查看。 "metrics": { "cpu": { ...} "disk": { ...} "aggregation_dimensions" : [["AutoScalingGroupName"]] } 除了累积 Auto Scaling 组名称以外，如果还希望累积各个 InstanceId 和 InstanceType 维度的组合，请添加以下内容。 "metrics": { "cpu": { ...} "disk": { ...} "aggregation_dimensions" : [["AutoScalingGroupName"], ["InstanceId", "InstanceType"]] } 要将指标累积到一个集合中，请使用 [] 。 "metrics": { "cpu": { ...} "disk": { ...} "aggregation_dimensions" : [[]] } 切记，每次更改代理配置文件时，您必须重新启动该代理以使更改生效。 使用 CloudWatch 代理收集高精度指标 metrics_collection_interval 字段指定收集的指标的时间间隔 (以秒为单位)。如果为该字段指定小于 60 的值，则将指标作为高精度指标进行收集。 例如，如果所有指标均应为高精度指标并且每 10 秒收集一次，请在 agent 部分中指定 10 作为 metrics_collection_interval 的值，以用作全局指标收集间隔。 "agent": { "metrics_collection_interval": 10 } 或者，以下示例将 cpu 指标设置为每秒收集一次，将所有其他指标设置为每分钟收集一次。 "agent": { "metrics_collection_interval": 60 }, "metrics": { "metrics_collected": { "cpu": { "resources":[ "*" ], "measurement":[ "cpu_usage_guest" ], "totalcpu":false, "metrics_collection_interval": 1 }, "disk": { "resources":[ "/", "/tmp" ], "measurement":[ "total", "used" ] } } } 切记，每次更改代理配置文件时，您必须重新启动该代理以使更改生效。 向不同账户发送指标、日志和跟踪信息 要让 CloudWatch 代理将指标、日志或跟踪信息发送到其他账户，请在发送服务器上的代理配置文件中指定 role_arn 参数。 role_arn 值指定在将数据发送到目标账户时代理使用的目标账户中的 IAM 角色。在指标或日志传递到目标账户时，此角色使发送账户能够在目标账户中担任相应的角色。 您还可以在代理配置文件中指定多个单独的 role_arn 字符串：一个用于发送指标，一个用于发送日志，还有一个用于发送跟踪信息。 配置文件的 agent 部分的以下部分示例将代理设置为在将数据发送到其他账户时使用 CrossAccountAgentRole 。 { "agent": { "credentials": { "role_arn": "arn:aws:iam::123456789012:role/CrossAccountAgentRole" } }, ..... } 或者，以下示例为发送账户设置不同的角色，以用于发送指标、日志和跟踪信息： "metrics": { "credentials": { "role_arn": "RoleToSendMetrics" }, "metrics_collected": { .... "logs": { "credentials": { "role_arn": "RoleToSendLogs" }, .... 必需策略 在代理配置文件中指定 role_arn 时，还必须确保发送和目标账户的 IAM 角色具有某些策略。发送账户和目标账户中的角色都应具有 CloudWatchAgentServerPolicy 。有关将该策略分配给角色的更多信息，请参阅 先决条件 。 发送账户中的角色还必须包含以下策略。编辑角色时，您可以将此策略添加到 IAM 控制台的 Permissions（权限） 选项卡。 JSON { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "sts:AssumeRole" ], "Resource": [ "arn:aws:iam:: 111122223333 :role/ agent-role-in-target-account " ] } ] } 目标账户中的角色必须包含以下策略，以便它识别发送账户使用的 IAM 角色。编辑角色时，您可以将此策略添加到 IAM 控制台的 True relationships（信任关系） 选项卡。此角色是在发送账户使用的策略的 agent-role-in-target-account 中指定的角色。 JSON { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": [ "arn:aws:iam:: 111122223333 :role/ role-in-sender-account " ] }, "Action": "sts:AssumeRole" } ] } CloudWatch 代理与旧版 CloudWatch Logs 代理之间的时间戳差异 与更早的 CloudWatch Logs 代理相比，CloudWatch 代理支持将一组不同的符号集用于时间戳格式。这些差异如下表所示。 两种代理均支持的符号 仅 CloudWatch 代理支持的符号 仅更早的 CloudWatch Logs 代理支持的符号 %A、%a、%b、%B、%d、%f、%H、%l、%m、%M、%p、%S、%y、%Y、%Z、z %-d、%-l、%-m、%-M、%-S %c、%j、%U、%W、%w 有关较新的 CloudWatch 代理支持的符号的含义的更多信息，请参阅 Amazon CloudWatch 用户指南 中的 CloudWatch 代理配置文件：日志部分 。有关 CloudWatch Logs 代理支持的符号的信息，请参阅 Amazon CloudWatch Logs 用户指南 中的 代理配置文件 。 追加 OpenTelemetry 收集器配置文件 除了自己的配置文件外，CloudWatch 代理还支持补充的 OpenTelemetry 收集器配置文件。此功能允许通过 CloudWatch 代理配置使用 CloudWatch Application Signals 或 Container Insights 等 CloudWatch 代理功能，并借助单个代理引入现有的 OpenTelemetry 收集器配置。 为防止与 CloudWatch 代理自动创建的管道发生合并冲突，我们建议为 OpenTelemetry 收集器配置中的每个组件和管道添加自定义后缀。 receivers: otlp/custom-suffix: protocols: http: exporters: awscloudwatchlogs/custom-suffix: log_group_name: "test-group" log_stream_name: "test-stream" service: pipelines: logs/custom-suffix: receivers: [otlp/custom-suffix] exporters: [awscloudwatchlogs/custom-suffix] 要配置 CloudWatch 代理，请使用 fetch-config 选项启动 CloudWatch 代理并指定 CloudWatch 代理的配置文件。CloudWatch 代理至少需要一个 CloudWatch 代理配置文件。 /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a fetch-config -c file:/tmp/agent.json -s 接下来，在指定 OpenTelemetry 收集器配置文件时使用 append-config 选项。 /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a append-config -c file:/tmp/otel.yaml -s 代理会在启动时合并两个配置文件并记录已解析的配置。 Javascript 在您的浏览器中被禁用或不可用。 要使用 Amazon Web Services 文档，必须启用 Javascript。请参阅浏览器的帮助页面以了解相关说明。 文档惯例 将 CloudWatch 代理与相关遥测结合使用 CloudWatch 代理凭证首选项 此页面对您有帮助吗？- 是 感谢您对我们工作的肯定！ 如果不耽误您的时间，请告诉我们做得好的地方，让我们做得更好。 此页面对您有帮助吗？- 否 感谢您告诉我们本页内容还需要完善。很抱歉让您失望了。 如果不耽误您的时间，请告诉我们如何改进文档。 | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#content-area | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#profile-api | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://git-scm.com/book/tl/v2/Pagsisimula-Isang-Maikling-Kasaysayan-ng-Git | Git - Isang Maikling Kasaysayan ng 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. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 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 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 1.2 Pagsisimula - Isang Maikling Kasaysayan ng Git Isang Maikling Kasaysayan ng Git Gaya ng napakaraming mga magagandang bagay sa buhay, ang Git ay nagsimula sa malikhaing pagkawasak at mainit na kontrobersiya. Ang Linux na kernel ay isang open source software na proyekto na may lubhang malaking pakay. Halos sa buong buhay ng Linux kernel na maintenance (1991-2002), mga pagbabago sa software ay pinasa-pasa sa paligid bilang mga patches at mga naka-archive na mga files. Sa 2002, ang Linux kernel na proyekto ay nagsisimulang gumamit ng isang pribadong DVCS na tinatawag na BitKeeper. Sa 2005, ang relasyon sa pagitan ng komunidad ng naglikha ng Linux na kernel at ang komersyal na kumpanya na gumawa ng BitKeeper ay nasira, at ang libre-sa-gasto na estado ng kagamitan ay tinanggal. Ito ang nagbigay diin sa development na komunidad ng Linux (at lalong-lalo na si Linux Torvalds, ang naglikha ng Linux) na gumawa ng kanilang sariling kagamitan ayon sa mga iilang mga aralin na natutunan nila habang gumagamit ng BitKeeper. Ang ilan sa mga layunin ng bagong sistema ay ang sumusunod: Bilis Simpleng disenyo Malakas na suporta sa non-linear na pagdedevelop (libu-libong mga parallel na branches) Ganap na ipinamamahagi Mabisang magagamit sa malalaking mga proyekto gaya ng Linux kernel (bilis at laki ng datos) Mula nang pagsilang nito noong 2005, ang Git ay nagbago at nag-mature para madaling magamit at naglakip pa rin sa mga inisyal na mga katangiang ito. Ito ay lubhang napakabilis, sadyang mabisa sa mga malalaking proyekto, at mayroon itong kahanga-hangang branching na sistema para sa non-linear na pagdedevelop (Tingnan ang Pag-branch ng Git ). prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://git-scm.com/book/cs/v2/GitHub-Maintaining-a-Project | Git - Maintaining a Project 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. Úvod 1.1 Správa verzí 1.2 Stručná historie systému Git 1.3 Základy systému Git 1.4 Příkazový řádek 1.5 Instalace systému Git 1.6 První nastavení systému Git 1.7 Získání nápovědy 1.8 Shrnutí 2. Základy práce se systémem Git 2.1 Získání repozitáře Git 2.2 Nahrávání změn do repozitáře 2.3 Zobrazení historie revizí 2.4 Návrat do předchozího stavu 2.5 Práce se vzdálenými repozitáři 2.6 Používání značek 2.7 Aliasy v Gitu 2.8 Shrnutí 3. Větve v systému Git 3.1 Větve v kostce 3.2 Základy větvení a slučování 3.3 Správa větví 3.4 Postupy při práci s větvemi 3.5 Vzdálené větve 3.6 Přeskládání 3.7 Shrnutí 4. Git na serveru 4.1 Protokoly 4.2 Zprovoznění Gitu na serveru 4.3 Generování veřejného klíče SSH 4.4 Nastavení serveru 4.5 Démon Git 4.6 Chytrý HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti hostování u třetí strany 4.10 Shrnutí 5. Distribuovaný Git 5.1 Distribuované pracovní postupy 5.2 Přispívání do projektu 5.3 Správa projektu 5.4 Shrnutí 6. GitHub 6.1 Zřízení účtu a úprava konfigurace 6.2 Přispívání do projektu 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Shrnutí 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 Ladění v systému Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Shrnutí 8. Customizing Git 8.1 Git Configuration 8.2 Atributy Git 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Shrnutí 9. Git a ostatní systémy 9.1 Git as a Client 9.2 Migrating to Git 9.3 Shrnutí 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Balíčkové soubory 10.5 The Refspec 10.6 Přenosové protokoly 10.7 Správa a obnova dat 10.8 Environment Variables 10.9 Shrnutí 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 Shrnutí 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 6.3 GitHub - Maintaining a Project Maintaining a Project Now that we’re comfortable contributing to a project, let’s look at the other side: creating, maintaining and administering your own project. Vytvoření nového repozitáře Let’s create a new repository to share our project code with. Start by clicking the “New repository” button on the right-hand side of the dashboard, or from the {plus} button in the top toolbar next to your username as seen in The “New repository” dropdown. . Figure 110. The “Your repositories” area. Figure 111. The “New repository” dropdown. This takes you to the “new repository” form: Figure 112. The “new repository” form. All you really have to do here is provide a project name; the rest of the fields are completely optional. For now, just click the “Create Repository” button, and boom – you have a new repository on GitHub, named <user>/<project_name> . Since you have no code there yet, GitHub will show you instructions for how to create a brand-new Git repository, or connect an existing Git project. We won’t belabor this here; if you need a refresher, check out Základy práce se systémem Git . Now that your project is hosted on GitHub, you can give the URL to anyone you want to share your project with. Every project on GitHub is accessible over HTTP as https://github.com/<user>/<project_name> , and over SSH as git@github.com:<user>/<project_name> . Git can fetch from and push to both of these URLs, but they are access-controlled based on the credentials of the user connecting to them. Note It is often preferable to share the HTTP based URL for a public project, since the user does not have to have a GitHub account to access it for cloning. Users will have to have an account and an uploaded SSH key to access your project if you give them the SSH URL. The HTTP one is also exactly the same URL they would paste into a browser to view the project there. Přidávání spolupracovníků If you’re working with other people who you want to give commit access to, you need to add them as “collaborators”. If Ben, Jeff, and Louise all sign up for accounts on GitHub, and you want to give them push access to your repository, you can add them to your project. Doing so will give them “push” access, which means they have both read and write access to the project and Git repository. Click the “Settings” link at the bottom of the right-hand sidebar. Figure 113. The repository settings link. Then select “Collaborators” from the menu on the left-hand side. Then, just type a username into the box, and click “Add collaborator.” You can repeat this as many times as you like to grant access to everyone you like. If you need to revoke access, just click the “X” on the right-hand side of their row. Figure 114. Repository collaborators. Managing Pull Requests Now that you have a project with some code in it and maybe even a few collaborators who also have push access, let’s go over what to do when you get a Pull Request yourself. Pull Requests can either come from a branch in a fork of your repository or they can come from another branch in the same repository. The only difference is that the ones in a fork are often from people where you can’t push to their branch and they can’t push to yours, whereas with internal Pull Requests generally both parties can access the branch. For these examples, let’s assume you are “tonychacon” and you’ve created a new Arduino code project named “fade”. Email Notifications Someone comes along and makes a change to your code and sends you a Pull Request. You should get an email notifying you about the new Pull Request and it should look something like Email notification of a new Pull Request. . Figure 115. Email notification of a new Pull Request. There are a few things to notice about this email. It will give you a small diffstat — a list of files that have changed in the Pull Request and by how much. It gives you a link to the Pull Request on GitHub. It also gives you a few URLs that you can use from the command line. If you notice the line that says git pull <url> patch-1 , this is a simple way to merge in a remote branch without having to add a remote. We went over this quickly in Získání vzdálených větví (checkout) . If you wish, you can create and switch to a topic branch and then run this command to merge in the Pull Request changes. The other interesting URLs are the .diff and .patch URLs, which as you may guess, provide unified diff and patch versions of the Pull Request. You could technically merge in the Pull Request work with something like this: $ curl http://github.com/tonychacon/fade/pull/1.patch | git am Collaborating on the Pull Request As we covered in The GitHub Flow , you can now have a conversation with the person who opened the Pull Request. You can comment on specific lines of code, comment on whole commits or comment on the entire Pull Request itself, using GitHub Flavored Markdown everywhere. Every time someone else comments on the Pull Request you will continue to get email notifications so you know there is activity happening. They will each have a link to the Pull Request where the activity is happening and you can also directly respond to the email to comment on the Pull Request thread. Figure 116. Responses to emails are included in the thread. Once the code is in a place you like and want to merge it in, you can either pull the code down and merge it locally, either with the git pull <url> <branch> syntax we saw earlier, or by adding the fork as a remote and fetching and merging. If the merge is trivial, you can also just hit the “Merge” button on the GitHub site. This will do a “non-fast-forward” merge, creating a merge commit even if a fast-forward merge was possible. This means that no matter what, every time you hit the merge button, a merge commit is created. As you can see in Merge button and instructions for merging a Pull Request manually. , GitHub gives you all of this information if you click the hint link. Figure 117. Merge button and instructions for merging a Pull Request manually. If you decide you don’t want to merge it, you can also just close the Pull Request and the person who opened it will be notified. Pull Request Refs If you’re dealing with a lot of Pull Requests and don’t want to add a bunch of remotes or do one time pulls every time, there is a neat trick that GitHub allows you to do. This is a bit of an advanced trick and we’ll go over the details of this a bit more in The Refspec , but it can be pretty useful. GitHub actually advertises the Pull Request branches for a repository as sort of pseudo-branches on the server. By default you don’t get them when you clone, but they are there in an obscured way and you can access them pretty easily. To demonstrate this, we’re going to use a low-level command (often referred to as a “plumbing” command, which we’ll read about more in Plumbing and Porcelain ) called ls-remote . This command is generally not used in day-to-day Git operations but it’s useful to show us what references are present on the server. If we run this command against the “blink” repository we were using earlier, we will get a list of all the branches and tags and other references in the repository. $ git ls-remote https://github.com/schacon/blink 10d539600d86723087810ec636870a504f4fee4d HEAD 10d539600d86723087810ec636870a504f4fee4d refs/heads/master 6a83107c62950be9453aac297bb0193fd743cd6e refs/pull/1/head afe83c2d1a70674c9505cc1d8b7d380d5e076ed3 refs/pull/1/merge 3c8d735ee16296c242be7a9742ebfbc2665adec1 refs/pull/2/head 15c9f4f80973a2758462ab2066b6ad9fe8dcf03d refs/pull/2/merge a5a7751a33b7e86c5e9bb07b26001bb17d775d1a refs/pull/4/head 31a45fc257e8433c8d8804e3e848cf61c9d3166c refs/pull/4/merge Of course, if you’re in your repository and you run git ls-remote origin or whatever remote you want to check, it will show you something similar to this. If the repository is on GitHub and you have any Pull Requests that have been opened, you’ll get these references that are prefixed with refs/pull/ . These are basically branches, but since they’re not under refs/heads/ you don’t get them normally when you clone or fetch from the server — the process of fetching ignores them normally. There are two references per Pull Request - the one that ends in /head points to exactly the same commit as the last commit in the Pull Request branch. So if someone opens a Pull Request in our repository and their branch is named bug-fix and it points to commit a5a775 , then in our repository we will not have a bug-fix branch (since that’s in their fork), but we will have pull/<pr#>/head that points to a5a775 . This means that we can pretty easily pull down every Pull Request branch in one go without having to add a bunch of remotes. Now, you could do something like fetching the reference directly. $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD This tells Git, “Connect to the origin remote, and download the ref named refs/pull/958/head .” Git happily obeys, and downloads everything you need to construct that ref, and puts a pointer to the commit you want under .git/FETCH_HEAD . You can follow that up with git merge FETCH_HEAD into a branch you want to test it in, but that merge commit message looks a bit weird. Also, if you’re reviewing a lot of pull requests, this gets tedious. There’s also a way to fetch all of the pull requests, and keep them up to date whenever you connect to the remote. Open up .git/config in your favorite editor, and look for the origin remote. It should look a bit like this: [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* That line that begins with fetch = is a “refspec.” It’s a way of mapping names on the remote with names in your local .git directory. This particular one tells Git, "the things on the remote that are under refs/heads should go in my local repository under refs/remotes/origin ." You can modify this section to add another refspec: [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* That last line tells Git, “All the refs that look like refs/pull/123/head should be stored locally like refs/remotes/origin/pr/123 .” Now, if you save that file, and do a git fetch : $ git fetch # … * [new ref] refs/pull/1/head -> origin/pr/1 * [new ref] refs/pull/2/head -> origin/pr/2 * [new ref] refs/pull/4/head -> origin/pr/4 # … Now all of the remote pull requests are represented locally with refs that act much like tracking branches; they’re read-only, and they update when you do a fetch. This makes it super easy to try the code from a pull request locally: $ git checkout pr/2 Checking out files: 100% (3769/3769), done. Branch pr/2 set up to track remote branch pr/2 from origin. Switched to a new branch 'pr/2' The eagle-eyed among you would note the head on the end of the remote portion of the refspec. There’s also a refs/pull/#/merge ref on the GitHub side, which represents the commit that would result if you push the “merge” button on the site. This can allow you to test the merge before even hitting the button. Pull Requests on Pull Requests Not only can you open Pull Requests that target the main or master branch, you can actually open a Pull Request targeting any branch in the network. In fact, you can even target another Pull Request. If you see a Pull Request that is moving in the right direction and you have an idea for a change that depends on it or you’re not sure is a good idea, or you just don’t have push access to the target branch, you can open a Pull Request directly to it. When you go to open a Pull Request, there is a box at the top of the page that specifies which branch you’re requesting to pull to and which you’re requesting to pull from. If you hit the “Edit” button at the right of that box you can change not only the branches but also which fork. Figure 118. Manually change the Pull Request target fork and branch. Here you can fairly easily specify to merge your new branch into another Pull Request or another fork of the project. Mentions and Notifications GitHub also has a pretty nice notifications system built in that can come in handy when you have questions or need feedback from specific individuals or teams. In any comment you can start typing a @ character and it will begin to autocomplete with the names and usernames of people who are collaborators or contributors in the project. Figure 119. Start typing @ to mention someone. You can also mention a user who is not in that dropdown, but often the autocompleter can make it faster. Once you post a comment with a user mention, that user will be notified. This means that this can be a really effective way of pulling people into conversations rather than making them poll. Very often in Pull Requests on GitHub people will pull in other people on their teams or in their company to review an Issue or Pull Request. If someone gets mentioned on a Pull Request or Issue, they will be “subscribed” to it and will continue getting notifications any time some activity occurs on it. You will also be subscribed to something if you opened it, if you’re watching the repository or if you comment on something. If you no longer wish to receive notifications, there is an “Unsubscribe” button on the page you can click to stop receiving updates on it. Figure 120. Unsubscribe from an Issue or Pull Request. The Notifications Page When we mention “notifications” here with respect to GitHub, we mean a specific way that GitHub tries to get in touch with you when events happen and there are a few different ways you can configure them. If you go to the “Notification center” tab from the settings page, you can see some of the options you have. Figure 121. Notification center options. The two choices are to get notifications over “Email” and over “Web” and you can choose either, neither or both for when you actively participate in things and for activity on repositories you are watching. Web Notifications Web notifications only exist on GitHub and you can only check them on GitHub. If you have this option selected in your preferences and a notification is triggered for you, you will see a small blue dot over your notifications icon at the top of your screen as seen in Notification center. . Figure 122. Notification center. If you click on that, you will see a list of all the items you have been notified about, grouped by project. You can filter to the notifications of a specific project by clicking on its name in the left hand sidebar. You can also acknowledge the notification by clicking the checkmark icon next to any notification, or acknowledge all of the notifications in a project by clicking the checkmark at the top of the group. There is also a mute button next to each checkmark that you can click to not receive any further notifications on that item. All of these tools are very useful for handling large numbers of notifications. Many GitHub power users will simply turn off email notifications entirely and manage all of their notifications through this screen. Email Notifications Email notifications are the other way you can handle notifications through GitHub. If you have this turned on you will get emails for each notification. We saw examples of this in Comments sent as email notifications and Email notification of a new Pull Request. . The emails will also be threaded properly, which is nice if you’re using a threading email client. There is also a fair amount of metadata embedded in the headers of the emails that GitHub sends you, which can be really helpful for setting up custom filters and rules. For instance, if we look at the actual email headers sent to Tony in the email shown in Email notification of a new Pull Request. , we will see the following among the information sent: To: tonychacon/fade <fade@noreply.github.com> Message-ID: <tonychacon/fade/pull/1@github.com> Subject: [fade] Wait longer to see the dimming effect better (#1) X-GitHub-Recipient: tonychacon List-ID: tonychacon/fade <fade.tonychacon.github.com> List-Archive: https://github.com/tonychacon/fade List-Post: <mailto:reply+i-4XXX@reply.github.com> List-Unsubscribe: <mailto:unsub+i-XXX@reply.github.com>,... X-GitHub-Recipient-Address: tchacon@example.com Výstup obsahuje řadu zajímavých informací. If you want to highlight or re-route emails to this particular project or even Pull Request, the information in Message-ID gives you all the data in <user>/<project>/<type>/<id> format. If this were an issue, for example, the <type> field would have been “issues” rather than “pull”. The List-Post and List-Unsubscribe fields mean that if you have a mail client that understands those, you can easily post to the list or “Unsubscribe” from the thread. That would be essentially the same as clicking the “mute” button on the web version of the notification or “Unsubscribe” on the Issue or Pull Request page itself. It’s also worth noting that if you have both email and web notifications enabled and you read the email version of the notification, the web version will be marked as read as well if you have images allowed in your mail client. Special Files There are a couple of special files that GitHub will notice if they are present in your repository. README The first is the README file, which can be of nearly any format that GitHub recognizes as prose. For example, it could be README , README.md , README.asciidoc , etc. If GitHub sees a README file in your source, it will render it on the landing page of the project. Many teams use this file to hold all the relevant project information for someone who might be new to the repository or project. This generally includes things like: What the project is for How to configure and install it An example of how to use it or get it running The license that the project is offered under How to contribute to it Since GitHub will render this file, you can embed images or links in it for added ease of understanding. CONTRIBUTING The other special file that GitHub recognizes is the CONTRIBUTING file. If you have a file named CONTRIBUTING with any file extension, GitHub will show Opening a Pull Request when a CONTRIBUTING file exists. when anyone starts opening a Pull Request. Figure 123. Opening a Pull Request when a CONTRIBUTING file exists. The idea here is that you can specify specific things you want or don’t want in a Pull Request sent to your project. This way people may actually read the guidelines before opening the Pull Request. Project Administration Generally there are not a lot of administrative things you can do with a single project, but there are a couple of items that might be of interest. Changing the Default Branch If you are using a branch other than “master” as your default branch that you want people to open Pull Requests on or see by default, you can change that in your repository’s settings page under the “Options” tab. Figure 124. Change the default branch for a project. Simply change the default branch in the dropdown and that will be the default for all major operations from then on, including which branch is checked out by default when someone clones the repository. Transferring a Project If you would like to transfer a project to another user or an organization in GitHub, there is a “Transfer ownership” option at the bottom of the same “Options” tab of your repository settings page that allows you to do this. Figure 125. Transfer a project to another GitHub user or Organization. This is helpful if you are abandoning a project and someone wants to take it over, or if your project is getting bigger and want to move it into an organization. Not only does this move the repository along with all its watchers and stars to another place, it also sets up a redirect from your URL to the new place. It will also redirect clones and fetches from Git, not just web requests. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#param-url-3 | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#param-end-date | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#param-num-of-posts | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://news.fuse.io/fuse-node-sale-is-live-launching-the-next-chapter-of-state-of-the-art-zkevm-l2/ | Fuse Ember Update: Pre-sale is Closed, Public Node Sale is LIVE! Skip to content fuse.io Docs Console University fuse.io Docs Console University Search fuse.io Docs Console University fuse.io Docs Console University About Blog Latest news and updates Community Support & Contribute Telegram Youtube LinkedIn Twitter Github Discord Ambassador Program Join Fuse Force Brand Kit Brand assets Jobs Explore opportunities Network Intro to Fuse EVM-compatible, Layer-2 Blockchain Get Fuse Explore the ways to get the native Fuse Network token Ecosystem Web3 Tools for Business Ignite Apply for Funding & Grants Developers Network Status Network performance and status RPC Providers Build crypto apps that scale Documentation Build on Fuse Solutions Account Abstraction Remove Complex Blockchain Actions Web3 Payments Cost-Effective Everyday Payments Gaming Coming soon... Wallet as a Service Integrate Web3 in Minutes Mobile stack Create Branded Mobile Wallets Case Studies Real world use cases built on Fuse Mystic Valley Freedom Wallet Sanduk Zneakrz Tools Staking FUSE on-chain staking Bridge Move assets to Fuse DEX Voltage Finance & VOLT Mobile App NFTs Mint Digital Collectibles on Artrific Fuse Explorer Query Transactions & Activity Safe Leading Platform to Manage Digital Assets Governance Shape the Future of Fuse About Network Developers Solutions Tools Blog Latest news and updates Community Support & Contribute Ambassador Program Join Fuse Force Brand Kit Brand assets Jobs Explore opportunities Telegram Youtube LinkedIn Github Twitter Discord Intro to Fuse EVM-compatible, Layer-2 Blockchain Get Fuse Explore the ways to get the native Fuse Network token Ecosystem Web3 Tools for Business Ignite Apply for Funding & Grants Network Status Network performance and status RPC Providers Build crypto apps that scale Documentation Build on Fuse Get Started Quick Start Fuse Basics FuseBox Tutorials Explore our APIs Smart Wallets API Trade API Notifications API GraphQL API Account Abstraction Remove Complex Blockchain Actions Web3 Payments Cost-Effective Everyday Payments Gaming Coming soon... Wallet as a Service Integrate Web3 in Minutes Mobile stack Create Branded Mobile Wallets Real world case studies Mystic Valley Ticketing and Event Payments Freedom Wallet Bridging RWAs for Businesses Sanduk Send and receive digital dollars Zneakrz Frictionless e-commerce Staking FUSE on-chain staking Bridge Move assets to Fuse DEX Voltage Finance & VOLT Mobile App NFTs Mint Digital Collectibles on Artrific Fuse Explorer Query Transactions & Activity Safe Leading Platform to Manage Digital Assets Governance Shape the Future of Fuse EN FR JP CN Subscribe Fuse Console Blog Fuse Ember Update: Pre-sale is Closed, Public Node Sale is LIVE! Featured , News February 11, 2025 Fuse Ember Update: Pre-sale is Closed, Public Node Sale is LIVE! The Fuse Ember Node Sale is officially live on https://www.fuse.io/node-sale This marks an important step in Fuse’s journey as we prepare for the migration to Layer 2 (L2) , powered by Polygon CDK , with support from key infrastructure partners like QuickNode and Avail . The node sale will strengthen governance, improve tokenomics, and support Fuse’s long-term growth. This node sale is designed to establish a new governance structure ahead of the L2 migration starting in April. It also introduces changes to Fuse’s tokenomics to support long-term sustainability and incentivize active participation in the network. 42 million Fuse tokens from the Fuse Foundation treasury have been allocated to provide yield for node operators over the next three years , ensuring consistent rewards while securing the network. Key Tokenomics Updates As part of the Fuse Ember Node Sale, we’re introducing fundamental changes to Fuse’s tokenomics, designed to create a more sustainable, deflationary, and growth-oriented economy. Here’s the story behind these changes: Over the past few months, we’ve re-evaluated how Fuse’s economic model can better serve long-term holders and the future of the network. This led to three major decisions: Setting a Max Supply Cap: For the first time in Fuse’s history, we’ve introduced a maximum supply cap of 400 million FUSE . This ensures predictability, scarcity, and long-term value for holders, eliminating concerns about uncontrolled token inflation. Eliminating Inflation: Since 2019, Fuse had a 5% annual inflation rate —a common mechanism in many blockchain networks. However, we believe the future of Fuse doesn’t rely on inflation-driven growth. So, we’ve officially reduced the inflation rate from 5% to 0% , making Fuse a fully deflationary asset moving forward. Rewarding Node Operators from Treasury Funds: To support the next three years of network growth, we’re allocating 42 million FUSE tokens from the Fuse treasury to fund node operator rewards . This approach ensures that rewards are backed by existing supply, rather than new token emissions—further reinforcing the deflationary model. Our closed presale has successfully concluded with participation from major long-term holders, including Collider Ventures, Tectona, Spark, Aleph, TRGC, and Blockchain Founders Fund . Notably, presale participants could only invest using FUSE tokens , effectively removing a significant portion of the circulating supply. This strategic move reduces sell pressure and strengthens Fuse’s tokenomics as we transition to the new L2 network. 🚫 No VC Unlocks : Unlike many projects, there are no future unlocks that could dilute token value. 📉 Reduced Circulating Supply : With treasury-backed rewards and presale supply absorption, Fuse’s circulating supply is tighter than ever. 🔒 Deflationary Model : No inflation, capped supply, and sustainable rewards—all designed for long-term growth. Backed by Strong Ecosystem Support We are proud to announce that our early, new partners & backers already closed the pre-sale: Collider Ventures, Blockchain Founders Fund, Tectona, Spark Capital, TRGC, Hashkey. Additionally, many of Fuse’s largest holders and validators participated, showing strong confidence in the network’s growth. What’s Ahead in 2025 April: Migration to L2 begins with a 1:1 Fuse token swap. Integration with major DeFi protocols and infrastructure partners: Polygon, QuickNode, LayerZero, Avail, Stargate, Thirdweb, The Graph, and 150+ more. Launch of a revenue-sharing model and business subscription services. Expansion of stablecoin payment solutions like web3 debit card and on/ramp options. Partnering with Polygon, on ZK bridging with Agglayer. Adding private payments enabled by ZK. Introducing a new version of our AA stack enabling recurring payments and other new features powered by Safe account. New SDK’s for mobile native cross-platform AA. Onboarding of new node operators to enhance decentralization globally. We are building the Stripe of Web3 – Great time to join us before nodes are fully sold! Secure your node today to participate in network governance, earn rewards, and support the future of Fuse. The Fuse Node Sale is live at fuse.io/node-sale . Join the Fuse journey today and help shape the future of payments. Twitter | Telegram | Discord | Announcements More Articles Fuse at Six: Full-State Migration Update and a New Phase of Growth On July 29, 2019, Fuse minted its first block with a simple belief: everyday finance should be open, transparent, and available to November 7, 2025 The First Visa Card on Fuse – Solid Card (Powered by Bridge & VISA) We’re thrilled to announce a major milestone for the Fuse ecosystem. The first-ever Visa card built on Fuse. Meet the Solid Card, October 21, 2025 Need the latest? Our newsletter is full of free resources, updates, special events and Web3 insights. Sign up below Email Sign Up Youtube GitHub Twitter Telegram Discord Docs Getting Started Fuse Network Mobile Stack Voltage Finance Fuse Network Mobile Stack Voltage Finance Under the hood Explorer Documentation Fuse Staking Governance Service status Explorer Documentation Fuse Staking Governance Service status General Brand Kit Jobs Ambassador Program Brand Kit Jobs Ambassador Program Subscribe to our newsletter © 2026 Fuse. All Rights Reserved. Need the latest? Our newsletter is full of free resources, updates, special events and Web3 insights. Sign up below Thank you! Something went wrong. x This Site Is Protected By Shield Security → | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#param-what-to-collect | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://docs.aws.amazon.com/fr_fr/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-configure-related-telemetry.html | Configuration des noms CloudWatch d'agent, de service et d'environnement pour les entités associées - Amazon CloudWatch Configuration des noms CloudWatch d'agent, de service et d'environnement pour les entités associées - Amazon CloudWatch Documentation Amazon CloudWatch Guide de l’utilisateur Les traductions sont fournies par des outils de traduction automatique. En cas de conflit entre le contenu d'une traduction et celui de la version originale en anglais, la version anglaise prévaudra. Configuration des noms CloudWatch d'agent, de service et d'environnement pour les entités associées L' CloudWatch agent peut envoyer des métriques et des journaux contenant des données d'entité pour soutenir le volet Explore de la CloudWatch console. Le nom du service ou le nom de l'environnement peut être configuré par la configuration JSON de l'CloudWatch agent . Note La configuration de l’agent peut être remplacée. Pour plus de détails sur la manière dont l’agent détermine quelles données envoyer pour les entités associées, consultez Utilisation de l' CloudWatch agent avec la télémétrie associée . Pour les métriques, le paramètre peut être défini au niveau de l’agent, des métriques ou du plugin. Pour les journaux, il peut être défini au niveau de l’agent, des journaux ou du fichier. La configuration la plus spécifique est toujours utilisée. Par exemple, si la configuration existe au niveau de l’agent et au niveau des métriques, les métriques utiliseront la configuration des métriques, et tout le reste (journaux) utilisera la configuration de l’agent. L’exemple suivant montre différentes manières de configurer le nom du service et le nom de l’environnement. { "agent": { "service.name": "agent-level-service", "deployment.environment": "agent-level-environment" }, "metrics": { "service.name": "metric-level-service", "deployment.environment": "metric-level-environment", "metrics_collected": { "statsd": { "service.name": "statsd-level-service", "deployment.environment": "statsd-level-environment", }, "collectd": { "service.name": "collectdd-level-service", "deployment.environment": "collectd-level-environment", } } }, "logs": { "service.name": "log-level-service", "deployment.environment": "log-level-environment", "logs_collected": { "files": { "collect_list": [ { "file_path": "/opt/aws/amazon-cloudwatch-agent/logs/amazon-cloudwatch-agent.log", "log_group_name": "amazon-cloudwatch-agent.log", "log_stream_name": "amazon-cloudwatch-agent.log", "service.name": "file-level-service", "deployment.environment": "file-level-environment" } ] } } } } JavaScript est désactivé ou n'est pas disponible dans votre navigateur. Pour que vous puissiez utiliser la documentation AWS, Javascript doit être activé. Vous trouverez des instructions sur les pages d'aide de votre navigateur. Conventions de rédaction Configurer et configurer la collecte de métriques Prometheus sur les instances Amazon EC2 Démarrez l' CloudWatch agent Cette page vous a-t-elle été utile ? - Oui Merci de nous avoir fait part de votre satisfaction. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer ce qui vous a plu afin que nous puissions nous améliorer davantage. Cette page vous a-t-elle été utile ? - Non Merci de nous avoir avertis que cette page avait besoin d'être retravaillée. Nous sommes désolés de ne pas avoir répondu à vos attentes. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer comment nous pourrions améliorer cette documentation. | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#collect-by-url-3 | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
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%91%ce%bd%ce%b1%ce%ba%ce%b5%cf%86%ce%b1%ce%bb%ce%b1%ce%af%cf%89%cf%83%ce%b7 | 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.10 Το Git στον διακομιστή - Ανακεφαλαίωση Ανακεφαλαίωση Έχετε αρκετές επιλογές για το πώς να δημιουργήσετε και λειτουργήσετε ένα απομακρυσμένο αποθετήριο Git έτσι ώστε να μπορείτε να συνεργάζεστε με άλλους ή να κοινοποιείτε την εργασία σας. Το να έχετε δικό σας διακομιστή σάς δίνει μεγάλο έλεγχο και σας επιτρέπει να τρέχετε τον διακομιστή εντός του firewall σας, αλλά η εγκατάσταση και συντήρηση ενός τέτοιου διακομιστή γενικά απαιτεί αρκετό χρόνο. Αν τοποθετήσετε τα δεδομένα σας σε έναν φιλοξενούμενο διακομιστή, η εγκατάσταση και η συντήρηση είναι εύκολες· ωστόσο, πρέπει να σας επιτρέπεται να έχετε τον κώδικά σας σε διακομιστές τρίτων και ορισμένοι οργανισμοί δεν το επιτρέπουν. Θα πρέπει να είναι αρκετά απλό να προσδιορίσετε ποια λύση ή ποιος συνδυασμός λύσεων είναι κατάλληλα για σας και τον οργανισμό σας. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#param-url-1 | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#collect-by-url-2 | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://www.linkedin.com/legal/user-agreement?session_redirect=%2Fservices%2Fproducts%2Fsalesforce-lightning-platform%2F&trk=registration-frontend_join-form-user-agreement | User Agreement | LinkedIn Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Effective on November 3, 2025 Our mission is to connect the world’s professionals to allow them to be more productive and successful. Our services are designed to promote economic opportunity for our members by enabling you and millions of other professionals to meet, exchange ideas, learn, and find opportunities or employees, work, and make decisions in a network of trusted relationships. Table of Contents: Introduction Obligations Rights and Limits Disclaimer and Limit of Liability Termination Governing Law and Dispute Resolution General Terms LinkedIn “Dos and Don’ts” Complaints Regarding Content How To Contact Us Introduction 1.1 Contract When you use our Services you agree to all of these terms. Your use of our Services is also subject to our Cookie Policy and our Privacy Policy, which covers how we collect, use, share, and store your personal information. By creating a LinkedIn account or accessing or using our Services (described below), you are agreeing to enter into a legally binding contract with LinkedIn (even if you are using third party credentials or using our Services on behalf of a company). If you do not agree to this contract (“Contract” or “User Agreement”), do not create an account or access or otherwise use any of our Services. If you wish to terminate this Contract at any time, you can do so by closing your account and no longer accessing or using our Services. As a Visitor or Member of our Services, the collection, use, and sharing of your personal data is subject to our Privacy Policy , our Cookie Policy and other documents referenced in our Privacy Policy , and updates. You acknowledge and have read our Privacy Policy . Services This Contract applies to LinkedIn.com, LinkedIn-branded apps, and other LinkedIn-related sites, apps, communications, and other services that state that they are offered under this Contract (“Services”), including the offsite collection of data for those Services, such as via our ads and the “Apply with LinkedIn” and “Share with LinkedIn” plugins. LinkedIn and other Key Terms You are entering into this Contract with LinkedIn (also referred to as “we” and “us”). Designated Countries . We use the term “Designated Countries” to refer to countries in the European Union (EU), European Economic Area (EEA), and Switzerland. If you reside in the “Designated Countries”, you are entering into this Contract with LinkedIn Ireland Unlimited Company (“LinkedIn Ireland”) and LinkedIn Ireland will be the controller of your personal data provided to, or collected by or for, or processed in connection with our Services. If you reside outside of the “Designated Countries”, you are entering into this Contract with LinkedIn Corporation (“LinkedIn Corp.”) and LinkedIn Corp. will be the controller of (or business responsible for) your personal data provided to, or collected by or for, or processed in connection with our Services. Affiliates . Affiliates are companies controlling, controlled by or under common control with us, including, for example, LinkedIn Ireland, LinkedIn Corporation, LinkedIn Singapore and Microsoft Corporation or any of its subsidiaries (e.g., Github, Inc.). Social Action . Actions that members take on our services such as likes, comments, follows, sharing content. Content . Content includes, for example, feed posts, feedback, comments, profiles, articles (and contributions), group posts, job postings, messages (including InMails), videos, photos, audio, and/or PDFs. 1.2 Members and Visitors This Contract applies to Members and Visitors. When you register and join the LinkedIn Services, you become a “Member”. If you have chosen not to register for our Services, you may access certain features as a “Visitor.” 1.3 Changes We may make changes to this Contract. We may modify this Contract, our Privacy Policy and our Cookie Policy from time to time. If we materially change these terms or if we are legally required to provide notice, we will provide you notice through our Services, or by other means, to provide you the opportunity to review the changes before they become effective. However, we may not always provide prior notice of changes to these terms (1) when those changes are legally required to be implemented with immediate effect, or (2) when those changes relate to a newly launched service or feature. We agree that changes cannot be retroactive. If you object to any of these changes, you may close your account . Your continued use of our Services after we publish or send a notice about our changes to these terms means that you are consenting to the updated terms as of their effective date. 2. Obligations 2.1 Service Eligibility Here are some promises that you make to us in this Contract: You’re eligible to enter into this Contract and you are at least our “Minimum Age.” The Services are not for use by anyone under the age of 16. To use the Services, you agree that: (1) you must be the "Minimum Age" (described below) or older; (2) you will only have one LinkedIn account, which must be in your real name; and (3) you are not already restricted by LinkedIn from using the Services. Creating an account with false information is a violation of our terms, including accounts registered on behalf of others or persons under the age of 16. “Minimum Age” means 16 years old. However, if law requires that you must be older in order for LinkedIn to lawfully provide the Services to you without parental consent (including using your personal data) then the Minimum Age is such older age. Learn More 2.2 Your Account You will keep your password a secret You will not share your account with anyone else and will follow our policies and the law. Members are account holders. You agree to: (1) protect against wrongful access to your account (e.g., use a strong password and keep it confidential); (2) not share or transfer your account or any part of it (e.g., sell or transfer the personal data of others by transferring your connections); and (3) follow the law, our list of Dos and Don’ts (below), and our Professional Community Policies . Learn More You are responsible for anything that happens through your account unless you close it or report misuse. As between you and others (including your employer), your account belongs to you. However, if the Services were purchased by another party for you to use in connection with your work for them (e.g., Recruiter seat or LinkedIn Learning subscription bought by your employer), the party paying for such Service has the right to control access to and get reports on your use of such paid Service; however, they do not have rights to your personal account. 2.3 Payment You’ll honor your payment obligations and you are okay with us storing your payment information. You understand that there may be fees and taxes that are added to our prices. Refunds are subject to our policy, and we may modify our prices and those modified prices will apply prospectively. If you buy any of our paid Services, you agree to pay us the applicable fees and taxes and you agree to the additional terms specific to the paid Services. Failure to pay these fees will result in the termination of your paid Services. Also, you agree that: Your purchase may be subject to foreign exchange fees or differences in prices based on location (e.g., exchange rates). We may store and continue billing your payment method (e.g., credit card), even after it has expired, to avoid interruptions in your paid Services and to use it to pay for other Services you may buy. If your primary payment method fails, we may automatically charge a secondary payment method, if you have provided one. You may update or change your payment method. Learn more If you purchase a subscription, your payment method automatically will be charged at the start of each subscription period for the fees and taxes applicable to that period. To avoid future charges, cancel before the renewal date. Learn how to cancel or suspend your paid subscription Services. We may modify our prices effective prospectively upon reasonable notice to the extent allowed under the law. All of your paid Services are subject to LinkedIn’s refund policy . We may calculate taxes payable by you based on the billing information that you provide us. You can get a copy of your invoice through your LinkedIn account settings under “ Purchase History ”. 2.4 Notices and Messages You’re okay with us providing notices and messages to you through our websites, apps, and contact information. If your contact information is out of date, you may miss out on important notices. You agree that we will provide notices and messages to you in the following ways: (1) within the Services or (2) sent to the contact information you provided us (e.g., email, mobile number, physical address). You agree to keep your contact information up to date. Please review your settings to control and limit the types of messages you receive from us. 2.5 Sharing When you share information on our Services, others can see, copy and use that information. Our Services allow sharing of information (including content) in many ways, such as through your profile, posts, articles, group posts, links to news articles, job postings, messages, and InMails. Depending on the feature and choices you make, information that you share may be seen by other Members, Visitors, or others (on or off of the Services). Where we have made settings available, we will honor the choices you make about who can see content or other information (e.g., message content to your addressees, sharing content only to LinkedIn connections, restricting your profile visibility from search tools, or opting not to notify others of your LinkedIn profile update). For job searching activities, we default to not notifying your connections or the public. So, if you apply for a job through our Services or opt to signal that you are interested in a job, our default is to share it only with the job poster. To the extent that laws allow this, we are not obligated to publish any content or other information on our Services and can remove it with or without notice. 3. Rights and Limits 3.1. Your License to LinkedIn You own all of your original content that you provide to us, but you also grant us a non-exclusive license to it. We’ll honor the choices you make about who gets to see your content, including how it can be used for ads. As between you and LinkedIn, you own your original content that you submit or post to the Services. You grant LinkedIn and our Affiliates the following non-exclusive license to the content and other information you provide (e.g., share, post, upload, and/or otherwise submit) to our Services: A worldwide, transferable and sublicensable right to use, copy, modify, distribute, publicly perform and display, host, and process your content and other information without any further consent, notice and/or compensation to you or others. These rights are limited in the following ways: You can end this license for specific content by deleting such content from the Services, or generally by closing your account, except (a) to the extent you (1) shared it with others as part of the Services and they copied, re-shared it or stored it, (2) we had already sublicensed others prior to your content removal or closing of your account, or (3) we are required by law to retain or share it with others, and (b) for the reasonable time it takes to remove the content you delete from backup and other systems. We will not include your content in advertisements for the products and services of third parties to others without your separate consent (including sponsored content). However, without compensation to you or others, ads may be served near your content and other information, and your social actions may be visible and included with ads, as noted in the Privacy Policy. If you use a Service feature, we may mention that with your name or photo to promote that feature within our Services, subject to your settings. We will honor the audience choices for shared content (e.g., “Connections only”). For example, if you choose to share your post to "Anyone on or off LinkedIn” (or similar): (a) we may make it available off LinkedIn; (b) we may enable others to publicly share onto third-party services (e.g., a Member embedding your post on a third party service); and/or (c) we may enable search tools to make that public content findable though their services. Learn More While we may edit and make format changes to your content (such as translating or transcribing it, modifying the size, layout or file type, and removing or adding labels or metadata), we will take steps to avoid materially modifying the meaning of your expression in content you share with others. Because you own your original content and we only have non-exclusive rights to it, you may choose to make it available to others, including under the terms of a Creative Commons license . You and LinkedIn agree that if content includes personal data, it is subject to our Privacy Policy. You and LinkedIn agree that we may access, store, process, and use any information (including content and/or personal data) that you provide in accordance with the terms of the Privacy Policy and your choices (including settings). By submitting suggestions or other feedback regarding our Services to LinkedIn, you agree that LinkedIn can use and share (but does not have to) such feedback for any purpose without compensation to you. You promise to only provide content and other information that you have the right to share and that your LinkedIn profile will be truthful. You agree to only provide content and other information that does not violate the law or anyone’s rights (including intellectual property rights). You have choices about how much information to provide on your profile but also agree that the profile information you provide will be truthful. LinkedIn may be required by law to remove certain content and other information in certain countries. 3.2 Service Availability We may change or limit the availability of some features, or end any Service. We may change, suspend or discontinue any of our Services. We may also limit the availability of features, content and other information so that they are not available to all Visitors or Members (e.g., by country or by subscription access). We don’t promise to store or show (or keep showing) any information (including content) that you’ve shared. LinkedIn is not a storage service. You agree that we have no obligation to store, maintain or provide you a copy of any content or other information that you or others provide, except to the extent required by applicable law and as noted in our Privacy Policy. 3.3 Other Content, Sites and Apps Your use of others’ content and information posted on our Services, is at your own risk. Others may offer their own products and services through our Services, and we aren’t responsible for those third-party activities. Others’ Content: By using the Services, you may encounter content or other information that might be inaccurate, incomplete, delayed, misleading, illegal, offensive, or otherwise harmful. You agree that we are not responsible for content or other information made available through or within the Services by others, including Members. While we apply automated tools to review much of the content and other information presented in the Services, we cannot always prevent misuse of our Services, and you agree that we are not responsible for any such misuse. You also acknowledge the risk that others may share inaccurate or misleading information about you or your organization, and that you or your organization may be mistakenly associated with content about others, for example, when we let connections and followers know you or your organization were mentioned in the news. Members have choices about this feature . Others’ Products and Services: LinkedIn may help connect you to other Members (e.g., Members using Services Marketplace or our enterprise recruiting, jobs, sales, or marketing products) who offer you opportunities (on behalf of themselves, their organizations, or others) such as offers to become a candidate for employment or other work or offers to purchase products or services. You acknowledge that LinkedIn does not perform these offered services, employ those who perform these services, or provide these offered products. You further acknowledge that LinkedIn does not supervise, direct, control, or monitor Members in the making of these offers, or in their providing you with work, delivering products or performing services, and you agree that (1) LinkedIn is not responsible for these offers, or performance or procurement of them, (2) LinkedIn does not endorse any particular Member’s offers, and (3) LinkedIn is not an agent or employment agency on behalf of any Member offering employment or other work, products or services. With respect to employment or other work, LinkedIn does not make employment or hiring decisions on behalf of Members offering opportunities and does not have such authority from Members or organizations using our products. For Services Marketplace , (a) you must be at least 18 years of age to procure, offer, or perform services, and (b) you represent and warrant that you have all the required licenses and will provide services consistent with the relevant industry standards and our Professional Community Policies . Others’ Events: Similarly, LinkedIn may help you register for and/or attend events organized by Members and connect with other Members who are attendees at such events. You agree that (1) LinkedIn is not responsible for the conduct of any of the Members or other attendees at such events, (2) LinkedIn does not endorse any particular event listed on our Services, (3) LinkedIn does not review and/or vet any of these events or speakers, and (4) you will adhere to the terms and conditions that apply to such events. 3.4 Limits We have the right to limit how you connect and interact on our Services. LinkedIn reserves the right to limit your use of the Services, including the number of your connections and your ability to contact other Members. LinkedIn reserves the right to restrict, suspend, or terminate your account if you breach this Contract or the law or are misusing the Services (e.g., violating any of the Dos and Don’ts or Professional Community Policies ). We can also remove any content or other information you shared if we believe it violates our Professional Community Policies or Dos and Don’ts or otherwise violates this Contract. Learn more about how we moderate content. 3.5 Intellectual Property Rights We’re providing you notice about our intellectual property rights. LinkedIn reserves all of its intellectual property rights in the Services. Trademarks and logos used in connection with the Services are the trademarks of their respective owners. LinkedIn, and “in” logos and other LinkedIn trademarks, service marks, graphics and logos used for our Services are trademarks or registered trademarks of LinkedIn. 3.6 Recommendations and Automated Processing We use data and other information about you to make and order relevant suggestions and to generate content for you and others. Recommendations: We use the data and other information that you provide and that we have about Members and content on the Services to make recommendations for connections, content, ads, and features that may be useful to you. We use that data and other information to recommend and to present information to you in an order that may be more relevant for you. For example, that data and information may be used to recommend jobs to you and you to recruiters and to organize content in your feed in order to optimize your experience and use of the Services. Keeping your profile accurate and up to date helps us to make these recommendations more accurate and relevant. Learn More Generative AI Features: By using the Services, you may interact with features we offer that automate content generation for you. The content that is generated might be inaccurate, incomplete, delayed, misleading or not suitable for your purposes. Please review and edit such content before sharing with others. Like all content you share on our Services, you are responsible for ensuring it complies with our Professional Community Policies , including not sharing misleading information. The Services may include content automatically generated and shared using tools offered by LinkedIn or others off LinkedIn. Like all content and other information on our Services, regardless of whether it's labeled as created by “AI”, be sure to carefully review before relying on it. 4. Disclaimer and Limit of Liability 4.1 No Warranty This is our disclaimer of legal liability for the quality, safety, or reliability of our Services. LINKEDIN AND ITS AFFILIATES MAKE NO REPRESENTATION OR WARRANTY ABOUT THE SERVICES, INCLUDING ANY REPRESENTATION THAT THE SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, AND PROVIDE THE SERVICES (INCLUDING CONTENT, OUTPUT AND INFORMATION) ON AN “AS IS” AND “AS AVAILABLE” BASIS. TO THE FULLEST EXTENT PERMITTED UNDER APPLICABLE LAW, LINKEDIN AND ITS AFFILIATES DISCLAIM ANY IMPLIED OR STATUTORY WARRANTY, INCLUDING ANY IMPLIED WARRANTY OF TITLE, ACCURACY, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. If you plan to use content, output and information for any reason, it is your responsibility to verify its accuracy and fitness for your purposes, because any content, output and information on the service may not reflect accurate, complete, or current information. 4.2 Exclusion of Liability These are the limits of legal liability we may have to you. TO THE FULLEST EXTENT PERMITTED BY LAW (AND UNLESS LINKEDIN HAS ENTERED INTO A SEPARATE WRITTEN AGREEMENT THAT OVERRIDES THIS CONTRACT), LINKEDIN AND ITS AFFILIATES, WILL NOT BE LIABLE IN CONNECTION WITH THIS CONTRACT FOR LOST PROFITS OR LOST BUSINESS OPPORTUNITIES, REPUTATION (E.G., OFFENSIVE OR DEFAMATORY STATEMENTS), LOSS OF DATA (E.G., DOWN TIME OR LOSS, USE OF, OR CHANGES TO, YOUR INFORMATION OR CONTENT) OR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL OR PUNITIVE DAMAGES. LINKEDIN AND ITS AFFILIATES WILL NOT BE LIABLE TO YOU IN CONNECTION WITH THIS CONTRACT FOR ANY AMOUNT THAT EXCEEDS (A) THE TOTAL FEES PAID OR PAYABLE BY YOU TO LINKEDIN FOR THE SERVICES DURING THE TERM OF THIS CONTRACT, IF ANY, OR (B) US $1000. 4.3 Basis of the Bargain; Exclusions The limitations of liability in this Section 4 are part of the basis of the bargain between you and LinkedIn and shall apply to all claims of liability (e.g., warranty, tort, negligence, contract and law) even if LinkedIn or its affiliates has been told of the possibility of any such damage, and even if these remedies fail their essential purpose. THESE LIMITATIONS OF LIABILITY DO NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY OR FOR FRAUD, GROSS NEGLIGENCE OR INTENTIONAL MISCONDUCT, OR IN CASES OF NEGLIGENCE, WHERE A MATERIAL OBLIGATION HAS BEEN BREACHED. A MATERIAL OBLIGATION BEING AN OBLIGATION WHICH FORMS A PREREQUISITE TO OUR DELIVERY OF SERVICES AND ON WHICH YOU MAY REASONABLY RELY, BUT ONLY TO THE EXTENT THAT THE DAMAGES WERE DIRECTLY CAUSED BY THE BREACH AND WERE FORESEEABLE UPON CONCLUSION OF THIS CONTRACT AND TO THE EXTENT THAT THEY ARE TYPICAL IN THE CONTEXT OF THIS CONTRACT. 5. Termination We can each end this Contract, but some rights and obligations survive. Both you and LinkedIn may terminate this Contract at any time with notice to the other. On termination, you lose the right to access or use the Services. The following shall survive termination: Our rights to use and disclose your feedback; Section 3 (subject to 3.1.1); Sections 4, 6, 7, and 8.2 of this Contract; and Any amounts owed by either party prior to termination remain owed after termination. You can visit our Help Center to learn about how to close your account 6. Governing Law and Dispute Resolution In the unlikely event we end up in a legal dispute, depending on where you live, you and LinkedIn agree to resolve it in California courts using California law, Dublin, Ireland courts using Irish law, or as otherwise provided in this section. If you live in the Designated Countries, the laws of Ireland govern all claims related to LinkedIn's provision of the Services, but this shall not deprive you of the mandatory consumer protections under the law of the country to which we direct your Services where you have habitual residence. With respect to jurisdiction, you and LinkedIn agree to choose the courts of the country to which we direct your Services where you have habitual residence for all disputes arising out of or relating to this User Agreement, or in the alternative, you may choose the responsible court in Ireland. If you are a business user within the scope of Article 6(12) of the EU Digital Markets Act (“DMA”) and have a dispute arising out of or in connection with Article 6(12) of the DMA, you may also utilize the alternative dispute resolution mechanism available in the Help Center . For others outside of Designated Countries, including those who live outside of the United States: You and LinkedIn agree that the laws of the State of California, U.S.A., excluding its conflict of laws rules, shall exclusively govern any dispute relating to this Contract and/or the Services. You and LinkedIn both agree that all claims and disputes can be litigated only in the federal or state courts in Santa Clara County, California, USA, and you and LinkedIn each agree to personal jurisdiction in those courts. You may have additional rights of redress and appeal for some decisions made by LinkedIn that impact you. 7. General Terms Here are some important details about the Contract. If a court with authority over this Contract finds any part of it unenforceable, you and we agree that the court should modify the terms to make that part enforceable while still achieving its intent. If the court cannot do that, you and we agree to ask the court to remove that unenforceable part and still enforce the rest of this Contract. This Contract (including additional terms that may be provided by us when you engage with a feature of the Services) is the only agreement between us regarding the Services and supersedes all prior agreements for the Services. If we don't act to enforce a breach of this Contract, that does not mean that LinkedIn has waived its right to enforce this Contract. You may not assign or transfer this Contract (or your membership or use of Services) to anyone without our consent. However, you agree that LinkedIn may assign this Contract to its affiliates or a party that buys it without your consent. There are no third-party beneficiaries to this Contract. You agree that the only way to provide us legal notice is at the addresses provided in Section 10. 8. LinkedIn “Dos and Don’ts” LinkedIn is a community of professionals. This list of “Dos and Don’ts” along with our Professional Community Policies limits what you can and cannot do on our Services, unless otherwise explicitly permitted by LinkedIn in a separate writing (e.g., through a research agreement). 8.1. Dos You agree that you will: Comply with all applicable laws, including, without limitation, privacy laws, intellectual property laws, anti-spam laws, export control laws, laws governing the content shared, and other applicable laws and regulatory requirements; Provide accurate contact and identity information to us and keep it updated; Use your real name on your profile; and Use the Services in a professional manner. 8.2. Don’ts You agree that you will not : Create a false identity on LinkedIn, misrepresent your identity, create a Member profile for anyone other than yourself (a real person), or use or attempt to use another’s account (such as sharing log-in credentials or copying cookies); Develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services, including profiles and other data from the Services; Override any security feature or bypass or circumvent any access controls or use limits of the Services (such as search results, profiles, or videos); Copy, use, display or distribute any information (including content) obtained from the Services, whether directly or through third parties (such as search tools or data aggregators or brokers), without the consent of the content owner (such as LinkedIn for content it owns); Disclose information that you do not have the consent to disclose (such as confidential information of others (including your employer); Violate the intellectual property rights of others, including copyrights, patents, trademarks, trade secrets or other proprietary rights. For example, do not copy or distribute (except through the available sharing functionality) the posts or other content of others without their permission, which they may give by posting under a Creative Commons license; Violate the intellectual property or other rights of LinkedIn, including, without limitation, (i) copying or distributing our learning videos or other materials, (ii) copying or distributing our technology, unless it is released under open source licenses; or (iii) using the word “LinkedIn” or our logos in any business name, email, or URL except as provided in the Brand Guidelines ; Post (or otherwise share) anything that contains software viruses, worms, or any other harmful code; Reverse engineer, decompile, disassemble, decipher or otherwise attempt to derive the source code for the Services or any related technology that is not open source; Imply or state that you are affiliated with or endorsed by LinkedIn without our express consent (e.g., representing yourself as an accredited LinkedIn trainer); Rent, lease, loan, trade, sell/re-sell or otherwise monetize the Services or related data or access to the same, without LinkedIn’s consent; Deep-link to our Services for any purpose other than to promote your profile or a Group on our Services, without LinkedIn’s consent; Use bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages, create, comment on, like, share, or re-share posts, or otherwise drive inauthentic engagement; Engage in “framing”, “mirroring”, or otherwise simulating the appearance or function of the Services; Overlay or otherwise modify the Services or their appearance (such as by inserting elements into the Services or removing, covering, or obscuring an advertisement included on the Services); Interfere with the operation of, or place an unreasonable load on, the Services (e.g., spam, denial of service attack, viruses, manipulating algorithms); Violate the Professional Community Policies , certain third party terms where applicable, or any additional terms concerning a specific Service that are provided when you sign up for or start using such Service; Use our Services to do anything that is unlawful, misleading, discriminatory, fraudulent or deceitful (e.g. manipulated media that wrongfully depicts a person saying or doing something they did not say or do); and/or Misuse our reporting or appeals process, including by submitting duplicative, fraudulent or unfounded reports, complaints or appeals. 9. Complaints Regarding Content Contact information for complaints about content provided by our Members. We ask that you report content and other information that you believe violates your rights (including intellectual property rights), our Professional Community Policies or otherwise violates this Contract or the law. To the extent we can under law, we may remove or restrict access to content, features, services, or information, including if we believe that it’s reasonably necessary to avoid harm to LinkedIn or others, violates the law or is reasonably necessary to prevent misuse of our Services. We reserve the right to take action against serious violations of this Contract, including by implementing account restrictions for significant violations. We respect the intellectual property rights of others. We require that information shared by Members be accurate and not in violation of the intellectual property rights or other rights of third parties. We provide a policy and process for complaints concerning content shared, and/or trademarks used, by our Members. 10. How To Contact Us Our Contact information. Our Help Center also provides information about our Services. For general inquiries, you may contact us online . For legal notices or service of process, you may write us at these addresses . LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (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)) Language | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#param-posts-to-not-include-1 | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/attach-iam-role.html | Attach an IAM role to an instance - Amazon Elastic Compute Cloud Attach an IAM role to an instance - Amazon Elastic Compute Cloud Documentation Amazon EC2 User Guide Attach an IAM role to an instance You can create an IAM role and attach it to an instance during or after launch. You can also replace or detach IAM roles. To attach an IAM role to an instance at launch using the Amazon EC2 console, expand Advanced details . For IAM instance profile , select the IAM role. Note If you created your IAM role using the IAM console, the instance profile was created for you and given the same name as the role. If you created your IAM role using the AWS CLI, API, or an AWS SDK, you might have given your instance profile a different name than the role. You can attach an IAM role to an instance that is running or stopped. If the instance already has an IAM role attached, you must replace it with the new IAM role. Console To attach an IAM role to an instance Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/ . In the navigation pane, choose Instances . Select the instance. Choose Actions , Security , Modify IAM role . For IAM role , select the IAM instance profile. Choose Update IAM role . AWS CLI To attach an IAM role to an instance Use the associate-iam-instance-profile command to attach the IAM role to the instance. When you specify the instance profile, you can use either the Amazon Resource Name (ARN) of the instance profile, or you can use its name. aws ec2 associate-iam-instance-profile \ --instance-id i-1234567890abcdef0 \ --iam-instance-profile Name=" TestRole-1 " PowerShell To attach an IAM role to an instance Use the Register-EC2IamInstanceProfile cmdlet. Register-EC2IamInstanceProfile ` -InstanceId i-1234567890abcdef0 ` -IamInstanceProfile_Name TestRole-1 To replace the IAM role on an instance that already has an attached IAM role, the instance must be running. You can do this if you want to change the IAM role for an instance without detaching the existing one first. For example, you can do this to ensure that API actions performed by applications running on the instance are not interrupted. Console To replace an IAM role for an instance Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/ . In the navigation pane, choose Instances . Select the instance. Choose Actions , Security , Modify IAM role . For IAM role , select the IAM instance profile. Choose Update IAM role . AWS CLI To replace an IAM role for an instance If required, use the describe-iam-instance-profile-associations command to get the association ID. aws ec2 describe-iam-instance-profile-associations \ --filters Name=instance-id,Values= i-1234567890abcdef0 \ --query IamInstanceProfileAssociations.AssociationId Use the replace-iam-instance-profile-association command. Specify the association ID for the existing instance profile and the ARN or name of the new instance profile. aws ec2 replace-iam-instance-profile-association \ --association-id iip-assoc-0044d817db6c0a4ba \ --iam-instance-profile Name=" TestRole-2 " PowerShell To replace an IAM role for an instance If required, use the Get-EC2IamInstanceProfileAssociation cmdlet to get the association ID. (Get-EC2IamInstanceProfileAssociation -Filter @ { Name="instance-id"; Values=" i-0636508011d8e966a "}).AssociationId Use the Set-EC2IamInstanceProfileAssociation cmdlet. Specify the association ID for the existing instance profile and the ARN or name of the new instance profile. Set-EC2IamInstanceProfileAssociation ` -AssociationId iip-assoc-0044d817db6c0a4ba ` -IamInstanceProfile_Name TestRole-2 You can detach an IAM role from an instance that is running or stopped. Console To detach an IAM role from an instance Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/ . In the navigation pane, choose Instances . Select the instance. Choose Actions , Security , Modify IAM role . For IAM role , choose No IAM Role . Choose Update IAM role . When promoted for confirmation, enter Detach , and then choose Detach . AWS CLI To detach an IAM role from an instance If required, use describe-iam-instance-profile-associations to get the association ID for the IAM instance profile to detach. aws ec2 describe-iam-instance-profile-associations \ --filters Name=instance-id,Values= i-1234567890abcdef0 \ --query IamInstanceProfileAssociations.AssociationId Use the disassociate-iam-instance-profile command. aws ec2 disassociate-iam-instance-profile --association-id iip-assoc-0044d817db6c0a4ba PowerShell To detach an IAM role from an instance If required, use Get-EC2IamInstanceProfileAssociation to get the association ID for the IAM instance profile to detach. (Get-EC2IamInstanceProfileAssociation -Filter @ { Name="instance-id"; Values="i-0636508011d8e966a"}).AssociationId Use the Unregister-EC2IamInstanceProfile cmdlet. Unregister-EC2IamInstanceProfile -AssociationId iip-assoc-0044d817db6c0a4ba Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Permissions to attach a role to an instance Update management Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:29:25 |
https://www.fuse.io/es/edison | Edison Fuse Turns Six: Future-Proofing the Entire Network Network Intro to Fuse EVM-compatible, Layer-2 Blockchain Get Fuse Explore the ways to get the native Fuse Network token Ecosystem Web3 Tools for Business Ignite Apply for Funding & Grants Tools Staking Stake FUSE for Rewards Bridge Bridge Assets To & From Fuse Safe Leading Platform to Manage Digital Assets Products Fuse Ember Integrate Web3 in Minutes Edison AI Agent Integrate Web3 in Minutes Gaming Coming soon... FuseBox Integrate Web3 in Minutes Case Studies Real World Case Studies Mystic Valley Freedom Wallet Sanduk Zneakrz Developers Documentation Build on Fuse RPC Providers Build crypto apps that scale Fuse Explorer Query Transactions & Activity Network Status Network performance and status Developers Documentation Build on Fuse RPC Providers Build crypto apps that scale Fuse Explorer Query Transactions & Activity Network Status Network performance and status Tools Ecosystem Web3 Tools for Business NFTs Mint Digital Collectibles on Artrific Community Support & Contribute Telegram Youtube LinkedIn Twitter Github Discord Governance Shape the Future of Fuse About Fuse Blog Latest news and updates Brand Kit Brand assets Jobs Explore opportunities Network Products Developers Ecosystem About Intro to Fuse EVM-compatible, Layer-2 Blockchain Ignite Apply for Funding & Grants Staking Stake FUSE for Rewards Bridge Bridge Assets To & From Fuse Safe Leading Platform to Manage Digital Assets Edison AI Agent Integrate Web3 in Minutes FuseBox Integrate Web3 in Minutes Case studies Real World Case Studies Real world case studies Mystic Valley Ticketing and Event Payments Freedom Wallet Bridging RWAs for Businesses Sanduk Send and receive digital dollars Zneakrz Frictionless e-commerce Documentation Learn about Fuse and get started with guides and tools for building on Fuse RPC Providers Build crypto apps that scale Fuse Explorer Query Transactions & Activity Network Status Network performance and status Get Started Quick Start Fuse Basics FuseBox Tutorials Explore our APIs Smart Wallets API Trade API Notifications API GraphQL API Ecosystem Web3 Tools for Business Community Support & Contribute Governance Shape the Future of Fuse Telegram Youtube LinkedIn Github Twitter Discord Get Fuse Explore the ways to get the native Fuse Network token Fuse Blog Latest news and updates Brand Kit Brand assets Jobs Explore opportunities EN FR JP CN Docs Ember Points Fuse Console edison Bridge the gap between Blockchain and AI Our AI agent Edison will help you build your idea from A to Z Get Started What can Edison do for you? Experience the power of blockchain without the complexity. Ask the Fuse AI Agent to handle your Fuse Network transactions, manage assets, and navigate DeFi services. Try Edison now Learn more Mint a branded Stablecoin Create your own price-stable token on Fuse Create a payment link Accept crypto payments with simple links Create an Airdrop Distribute tokens to your community easily Research a token Get insights on any token on the Fuse ecosystem Replacing clunky no-code interfaces so you could focus on your business Edison will guide you through all the tools and services on fuse. Automate simple and complicated tasks for customer service billing and marketing Learn more Build anything you want Deploy contracts Abstract away complexity Simplify user onboarding and transactions Branded stablecoins Index and query blockchain data Build powerful dApp experiences Wallet as a service Deploy smart contracts with ease Monitor and manage deployments Online commerce Private nodes for your dApp Fast and reliable connectivity Loyalty programs Launch your own stablecoin Full control over token operations Composable yield Account abstraction standard Better UX for web3 users Automations Design token distributions Execute airdrops at scale Security & Cost cutting Track on-chain events Get real-time notifications Join the Waitlist Leave your email to be notified when the Edison launches Thanks, we’ll keep you updated! Oops! Something went wrong while submitting the form. YouTube Github Twitter Telegram Discord Docs Getting started Fuse Network Mobile Stack Voltage Finance Web3 Glossary Charge Under the hood Explorer Documentation Fuse Staking Governance Service Status General Brand Kits Jobs Ambassador Program FAQ Subscribe to our newsletter © 2024 Fuse. All Rights Reserved | 2026-01-13T09:29:25 |
https://docs.aws.amazon.com/de_de/AmazonCloudWatch/latest/monitoring/create-cloudwatch-agent-configuration-file-wizard.html | Erstellen Sie die CloudWatch Agenten-Konfigurationsdatei mit dem Assistenten - Amazon CloudWatch Erstellen Sie die CloudWatch Agenten-Konfigurationsdatei mit dem Assistenten - Amazon CloudWatch Dokumentation Amazon CloudWatch Benutzer-Leitfaden Erforderliche Anmeldeinformationen Führen Sie den Assistenten zur CloudWatch Agentenkonfiguration aus CloudWatch Vordefinierte Metriksätze für Agenten Die vorliegende Übersetzung wurde maschinell erstellt. Im Falle eines Konflikts oder eines Widerspruchs zwischen dieser übersetzten Fassung und der englischen Fassung (einschließlich infolge von Verzögerungen bei der Übersetzung) ist die englische Fassung maßgeblich. Erstellen Sie die CloudWatch Agenten-Konfigurationsdatei mit dem Assistenten Der Assistent für die Agentenkonfigurationsdatei amazon-cloudwatch-agent-config-wizard ,, stellt eine Reihe von Fragen, um Ihnen bei der Konfiguration des CloudWatch Agenten für Ihre Bedürfnisse zu helfen. In diesem Abschnitt werden die für die Konfigurationsdatei erforderlichen Anmeldeinformationen beschrieben. Es wird beschrieben, wie der Assistent für die CloudWatch Agentenkonfiguration ausgeführt wird. Außerdem werden die Metriken beschrieben, die im Assistenten vordefiniert sind. Erforderliche Anmeldeinformationen Der Assistent kann die zu verwendenden Anmeldeinformationen und die AWS Region automatisch erkennen, wenn Sie die AWS Anmeldeinformationen und die Konfigurationsdateien vor dem Start des Assistenten eingerichtet haben. Weitere Informationen zu diesen Dateien finden Sie unter Konfigurations- und Anmeldeinformationsdateien im AWS Systems Manager -Benutzerhandbuch . In der AWS Anmeldeinformationsdatei sucht der Assistent nach Standardanmeldedaten und sucht auch nach einem AmazonCloudWatchAgent Abschnitt wie dem folgenden: [AmazonCloudWatchAgent] aws_access_key_id = my_access_key aws_secret_access_key = my_secret_key Der Assistent zeigt die Standard-Anmeldeinformationen, die Anmeldeinformationen aus AmazonCloudWatchAgent und die Option Others an. Sie können auswählen, welche Anmeldeinformationen verwendet werden sollen. Bei Wahl von Others (Andere), können Sie Anmeldeinformationen eingeben. Verwenden Sie für my_access_key und my_secret_key die Schlüssel des IAM-Benutzers, der über Schreibberechtigungen für den Systems Manager Parameter Store verfügt. In der AWS Konfigurationsdatei können Sie die Region angeben, an die der Agent Metriken sendet, falls es sich um eine andere Region als den [default] Abschnitt handelt. Standardmäßig werden die Metriken in der Region veröffentlicht, in der sich die EC2 Amazon-Instance befindet. Wenn die Metriken in einer anderen Region veröffentlicht werden sollen, geben Sie hier die Region an. Im folgenden Beispiel werden die Metriken in der Region us-west-1 veröffentlicht. [AmazonCloudWatchAgent] region = us-west-1 Führen Sie den Assistenten zur CloudWatch Agentenkonfiguration aus Um die CloudWatch Agenten-Konfigurationsdatei zu erstellen Starten Sie den Assistenten zur CloudWatch Agentenkonfiguration, indem Sie Folgendes eingeben: sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-config-wizard Führen Sie auf einem Server mit Windows Server die folgenden Befehle aus, um den Assistenten zu starten: cd "C:\Program Files\Amazon\AmazonCloudWatchAgent" .\amazon-cloudwatch-agent-config-wizard.exe Beantworten Sie die Fragen zum Anpassen der Konfigurationsdatei für Ihren Server. Wenn Sie die Konfigurationsdatei lokal speichern, wird die Konfigurationsdatei config.json in /opt/aws/amazon-cloudwatch-agent/bin/ auf Linux-Servern und in C:\Program Files\Amazon\AmazonCloudWatchAgent auf Windows Server-Servern gespeichert. Anschließend können Sie diese Datei auf andere Server kopieren, auf denen der Agent installiert werden soll. Wenn Sie Systems Manager zum Installieren und Konfigurieren des Agenten verwenden, müssen Sie mit Yes (Ja) antworten, wenn Sie gefragt werden, ob Sie die Datei in Systems Manager Parameter Store speichern möchten. Sie können sich auch dafür entscheiden, die Datei im Parameter Store zu speichern, auch wenn Sie den SSM-Agent nicht zur Installation des CloudWatch Agenten verwenden. Zum Speichern der Datei in Parameter Store müssen Sie eine IAM-Rolle mit ausreichenden Berechtigungen verwenden. CloudWatch Vordefinierte Metriksätze für Agenten Der Assistent ist mit vordefinierten Metrikkategorien mit unterschiedlichen Detailebenen konfiguriert. Diese Metrikkategorien werden in den folgenden Tabellen dargestellt. Weitere Informationen zu diesen Metriken finden Sie unter Vom CloudWatch Agenten gesammelte Metriken . Anmerkung Parameter Store unterstützt Parameter in den Stufen „Standard“ und „Advanced“. Diese Parameterebenen beziehen sich nicht auf die Ebenen „Basic“, „Standard“ und „Advanced“ der Metrikdetails, die in diesen Tabellen beschrieben werden. EC2 Amazon-Instances, auf denen Linux läuft Detailstufe Enthaltene Metriken Basic Mem: mem_used_percent Disk: disk_used_percent Die disk -Metriken wie disk_used_percent haben eine Dimension für Partition , was bedeutet, dass die Anzahl der generierten benutzerdefinierten Metriken von der Anzahl der Partitionen abhängt, die Ihrer Instance zugeordnet sind. Die Anzahl der Festplattenpartitionen hängt davon ab, welches AMI Sie verwenden, und wie viele Amazon-EBS-Volumes Sie an den Server anfügen. Standard CPU: cpu_usage_idle , cpu_usage_iowait , cpu_usage_user , cpu_usage_system Disk: disk_used_percent , disk_inodes_free Diskio: diskio_io_time Mem: mem_used_percent Swap: swap_used_percent Advanced CPU: cpu_usage_idle , cpu_usage_iowait , cpu_usage_user , cpu_usage_system Disk: disk_used_percent , disk_inodes_free Diskio: diskio_io_time , diskio_write_bytes , diskio_read_bytes , diskio_writes , diskio_reads Mem: mem_used_percent Netstat: netstat_tcp_established , netstat_tcp_time_wait Swap: swap_used_percent On-Premises-Server mit Linux Detailstufe Enthaltene Metriken Basic Disk: disk_used_percent Diskio: diskio_write_bytes , diskio_read_bytes , diskio_writes , diskio_reads Mem: mem_used_percent Net: net_bytes_sent , net_bytes_recv , net_packets_sent , net_packets_recv Swap: swap_used_percent Standard CPU: cpu_usage_idle , cpu_usage_iowait Disk: disk_used_percent , disk_inodes_free Diskio: diskio_io_time , diskio_write_bytes , diskio_read_bytes , diskio_writes , diskio_reads Mem: mem_used_percent Net: net_bytes_sent , net_bytes_recv , net_packets_sent , net_packets_recv Swap: swap_used_percent Advanced CPU: cpu_usage_guest , cpu_usage_idle , cpu_usage_iowait , cpu_usage_steal , cpu_usage_user , cpu_usage_system Disk: disk_used_percent , disk_inodes_free Diskio: diskio_io_time , diskio_write_bytes , diskio_read_bytes , diskio_writes , diskio_reads Mem: mem_used_percent Net: net_bytes_sent , net_bytes_recv , net_packets_sent , net_packets_recv Netstat: netstat_tcp_established , netstat_tcp_time_wait Swap: swap_used_percent EC2 Amazon-Instances, auf denen Windows Server ausgeführt wird Anmerkung Die in dieser Tabelle aufgeführten Metriknamen zeigen an, wie die Metrik in der Konsole angezeigt wird. Der tatsächliche Name der Metrik enthält möglicherweise nicht das erste Wort. Der tatsächliche Metrikname für LogicalDisk % Free Space lautet beispielsweise nur % Free Space . Detailstufe Enthaltene Metriken Basic Memory: Memory % Committed Bytes In Use LogicalDisk: LogicalDisk % Free Space Standard Memory: Memory % Committed Bytes In Use Paging: Paging File % Usage Processor: Processor % Idle Time , Processor % Interrupt Time , Processor % User Time PhysicalDisk: PhysicalDisk % Disk Time LogicalDisk: LogicalDisk % Free Space Advanced Memory: Memory % Committed Bytes In Use Paging: Paging File % Usage Processor: Processor % Idle Time , Processor % Interrupt Time , Processor % User Time LogicalDisk: LogicalDisk % Free Space PhysicalDisk: PhysicalDisk % Disk Time , PhysicalDisk Disk Write Bytes/sec , PhysicalDisk Disk Read Bytes/sec , PhysicalDisk Disk Writes/sec , PhysicalDisk Disk Reads/sec TCP: TCPv4 Connections Established , TCPv6 Connections Established On-Premises-Server mit Windows Server Anmerkung Die in dieser Tabelle aufgeführten Metriknamen zeigen an, wie die Metrik in der Konsole angezeigt wird. Der tatsächliche Name der Metrik enthält möglicherweise nicht das erste Wort. Der tatsächliche Metrikname für LogicalDisk % Free Space lautet beispielsweise nur % Free Space . Detailstufe Enthaltene Metriken Basic Paging: Paging File % Usage Processor: Processor % Processor Time LogicalDisk: LogicalDisk % Free Space PhysicalDisk: PhysicalDisk Disk Write Bytes/sec , PhysicalDisk Disk Read Bytes/sec , PhysicalDisk Disk Writes/sec , PhysicalDisk Disk Reads/sec Memory: Memory % Committed Bytes In Use Network Interface: Network Interface Bytes Sent/sec , Network Interface Bytes Received/sec , Network Interface Packets Sent/sec , Network Interface Packets Received/sec Standard Paging: Paging File % Usage Processor: Processor % Processor Time , Processor % Idle Time , Processor % Interrupt Time LogicalDisk: LogicalDisk % Free Space PhysicalDisk: PhysicalDisk % Disk Time , PhysicalDisk Disk Write Bytes/sec , PhysicalDisk Disk Read Bytes/sec , PhysicalDisk Disk Writes/sec , PhysicalDisk Disk Reads/sec Memory: Memory % Committed Bytes In Use Network Interface: Network Interface Bytes Sent/sec , Network Interface Bytes Received/sec , Network Interface Packets Sent/sec , Network Interface Packets Received/sec Advanced Paging: Paging File % Usage Processor: Processor % Processor Time , Processor % Idle Time , Processor % Interrupt Time , Processor % User Time LogicalDisk: LogicalDisk % Free Space PhysicalDisk: PhysicalDisk % Disk Time , PhysicalDisk Disk Write Bytes/sec , PhysicalDisk Disk Read Bytes/sec , PhysicalDisk Disk Writes/sec , PhysicalDisk Disk Reads/sec Memory: Memory % Committed Bytes In Use Network Interface: Network Interface Bytes Sent/sec , Network Interface Bytes Received/sec , Network Interface Packets Sent/sec , Network Interface Packets Received/sec TCP: TCPv4 Connections Established , TCPv6 Connections Established JavaScript ist in Ihrem Browser nicht verfügbar oder deaktiviert. Zur Nutzung der AWS-Dokumentation muss JavaScript aktiviert sein. Weitere Informationen finden auf den Hilfe-Seiten Ihres Browsers. Dokumentkonventionen Erstellen Sie die CloudWatch Agenten-Konfigurationsdatei Beispiele für Konfigurationsdateien Hat Ihnen diese Seite geholfen? – Ja Vielen Dank, dass Sie uns mitgeteilt haben, dass wir gute Arbeit geleistet haben! Würden Sie sich einen Moment Zeit nehmen, um uns mitzuteilen, was wir richtig gemacht haben, damit wir noch besser werden? Hat Ihnen diese Seite geholfen? – Nein Vielen Dank, dass Sie uns mitgeteilt haben, dass diese Seite überarbeitet werden muss. Es tut uns Leid, dass wir Ihnen nicht weiterhelfen konnten. Würden Sie sich einen Moment Zeit nehmen, um uns mitzuteilen, wie wir die Dokumentation verbessern können? | 2026-01-13T09:29:25 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=fr | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 � | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#param-posts-to-not-include | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#param-start-date | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://git-scm.com/book/fr/v2/Git-sur-le-serveur-GitWeb | Git - GitWeb 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.7 Git sur le serveur - GitWeb GitWeb Après avoir réglé les accès de base en lecture/écriture et en lecture seule pour vos projets, vous souhaiterez peut-être mettre en place une interface web simple de visualisation. Git fournit un script CGI appelé GitWeb qui est souvent utilisé à cette fin. Figure 49. L’interface web de visualisation Gitweb. Si vous souhaitez vérifier à quoi GitWeb ressemblerait pour votre projet, Git fournit une commande pour démarrer une instance temporaire de serveur si vous avez un serveur léger tel que lighttpd ou webrick sur votre système. Sur les machines Linux, lighttpd est souvent pré-installé et vous devriez pouvoir le démarrer en tapant git instaweb dans votre répertoire de travail. Si vous utilisez un Mac, Ruby est installé de base avec Léopard, donc webrick est une meilleure option. Pour démarrer instaweb avec un gestionnaire autre que lighttpd , vous pouvez le lancer avec l’option --httpd . $ git instaweb --httpd=webrick [2009-02-21 10:02:21] INFO WEBrick 1.3.1 [2009-02-21 10:02:21] INFO ruby 1.8.6 (2008-03-03) [universal-darwin9.0] Cette commande démarre un serveur HTTP sur le port 1234 et lance automatiquement un navigateur Internet qui ouvre la page d’accueil. C’est vraiment très simple. Pour arrêter le serveur, il suffit de lancer la même commande, mais avec l’option --stop : $ git instaweb --httpd=webrick --stop Si vous souhaitez fournir l’interface web en permanence sur le serveur pour votre équipe ou pour un projet opensource que vous hébergez, il sera nécessaire d’installer le script CGI pour qu’il soit appelé par votre serveur web. Quelques distributions Linux ont un package gitweb qu’il suffira d’installer via apt ou dnf , ce qui est une possibilité. Nous détaillerons tout de même rapidement l’installation manuelle de GitWeb. Premièrement, le code source de Git qui fournit GitWeb est nécessaire pour pouvoir générer un script CGI personnalisé : $ git clone git://git.kernel.org/pub/scm/git/git.git $ cd git/ $ make GITWEB_PROJECTROOT="/opt/git" prefix=/usr gitweb SUBDIR gitweb SUBDIR ../ make[2]: `GIT-VERSION-FILE' is up to date. GEN gitweb.cgi GEN static/gitweb.js $ sudo cp -Rf gitweb /var/www/ Notez que vous devez indiquer où trouver les dépôts Git au moyen de la variable GITWEB_PROJECTROOT . Maintenant, il faut paramétrer dans Apache l’utilisation de CGI pour ce script, en spécifiant un nouveau VirtualHost : <VirtualHost *:80> ServerName gitserver DocumentRoot /var/www/gitweb <Directory /var/www/gitweb> Options ExecCGI +FollowSymLinks +SymLinksIfOwnerMatch AllowOverride All order allow,deny Allow from all AddHandler cgi-script cgi DirectoryIndex gitweb.cgi </Directory> </VirtualHost> Une fois de plus, GitWeb peut être géré par tout serveur web capable de prendre en charge CGI ou Perl. La mise en place ne devrait pas être plus difficile avec un autre serveur. Après redémarrage du serveur, vous devriez être capable de visiter https://gitserveur/ pour visualiser vos dépôts en ligne. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#param-url | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://git-scm.com/book/tl/v2/Pag-branch-ng-Git-Pag-rebase | Git - Pag-rebase 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. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 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 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 3.6 Pag-branch ng Git - Pag-rebase Pag-rebase Sa Git, mayroong dalawang pangunahing mga paraan upang pagsamahin ang mga pagbabago mula sa isang branch patungo sa iba: ang merge at ang rebase . Sa seksyong ito matututo ka kung ano ang pag-rebase, paano ito gawin, bakit ito ay isang medyo kahanga-hangang kasangkapan, at sa anong kaso mo hindi gugustuhing gamitin ito. Ang Pangunahing Rebase Kung ikaw ay pupunta pabalik sa kamakailang halimbawa mula sa Batayan ng Pag-merge , maaari mong tingnan na nahiwalay mo ang iyong trabaho at gumawa ng mga commit sa dalawang magkaibang mga branch. Figure 35. Simpleng divergent na kasaysayan Ang pinakamadaling paraan upang mapagsama ang mga branch, bilang nasakop na natin, ay ang merge na utos. Ito ay gumagawa ng isang three-way na merge sa pagitan ng dalawang pinakabagong mga snapshot ng branch ( C3 at C4 ) at ang pinakakamakailang karaniwang ninuno ng dalawa ( C2 ), kaya gumagawa ng isang panibagong snapshot (at commit). Figure 36. Pag-merge upang mapagsama ang nahiwalay na kasaysayan ng trabaho Subalit, mayroong ibang paraan: maaari mong kunin ang patch ng pagbabago na napakilala sa C4 at ilapat muli ito sa itaas ng C3 . Sa Git, ito ay tinatawag na rebasing . Gamit ang rebase na utos, maaari mong kunin ang lahat ng mga pagbabago na na-commit sa isang branch at i-replay ang mga ito sa iba pa. Sa halimbawang ito, papatakbuhin mo ang sumusunod: $ git checkout experiment $ git rebase master First, rewinding head to replay your work on top of it... Applying: added staged command Gumagana ito sa pamamagitan ng pagpunta sa karaniwang ninuno ng dalawang mga branch (yung isa ay kung saan nandoon ka at yung isa ay kung saan ka magre-rebase), kukunin ang diff na napakilala sa bawat commit ng branch kung saan nandoon ka, isi-save ang mga diff na iyon sa pansamantalang mga file, iri-reset ang kasalukuyang branch sa parehong commit bilang branch na iyong iri-rebase, at sa huli ay ilalapat ang bawat pagbabago. Figure 37. Pag-rebase ng pagbabago na napakilala sa C4 patungo sa C3 Sa puntong ito, maaari kang pumunta pabalik sa master na branch at gumawa ng fast-forward na merge. $ git checkout master $ git merge experiment Figure 38. Pag-fast-forward ng master na branch Ngayon, ang snapshot na itinuro ng C4' ay eksaktong kapareho sa isa na itinuro ng C5 sa merge na halimbawa. Walang pagkakaiba sa resulta ng integrasyon, ngunit ang pag-rebase ay ginagawang mas malinis ang kasaysayan. Kung iyong susuriin ang log ng isang na-rebase na branch, magmumukha itong isang linear na kasaysayan: lumalabas na ang lahat ng trabaho ay nangyari na nakaserye, kahit ito ay orihinal na nangyari na nakahilera. Kadalasan, gagawin mo ito upang siguraduhing ang iyong mga commit ay nalapat nang malinis sa isang remote na branch — marahil sa isang proyekto kung saan sinusubukan mong mag-ambag ngunit iyong hindi mo na pinapanatili. Sa kasong ito, gagawin mo ang iyong trabaho sa isang branch at pagkatapos ay iri-rebase ang iyong trabaho sa origin/master kapag ikaw ay handa nang isumite ang iyong mga patch sa pangunahing proyekto. Sa paraan iyon, ang tagapanatili ay hindi na kailangang gumawa ng anumang pagsasama na trabaho — isang fast-forward o isang malinis na paglapat lamang. Tandaan na ang snapshot na itinuro ng huling commit na nagtapos sa iyo, kung ito ay ang huli sa na-rebase na mga commit para sa isang rebase o ang huling merge na commit pagkatapos ng isang merge, ay ang parehong snapshot - ang kasaysayan lamang ang naiiba. Ang pag-rebase ay iri-replay ang mga pagbabago mula sa isang linya ng trabaho patungo sa iba sa pagkakaayos base sa kanilang pagpakilala, samantalang ang pag-merge ay kinukuha ang mga endpoint at sama-samang imi-merge ang mga ito. Maraming Kagiliw-giliw na mga Rebase Maaari ka ring magkaroon ng iyong rebase na replay sa anuman maliban sa rebase na target na branch. Gamitin ang isang kasaysayan katulad ng Isang kasaysayan na may isang paksa na naka-branch off sa ibang paksa na branch , bilang halimbawa. Ikaw ay nag-branch ng isang paksa na branch ( server ) upang magdagdag ng ilang server-side na functionality sa iyong proyekto, at gumawa ng isang commit. Pagkatapos, ikaw ay nag-branch off nito upang gawin ang mga pagbabago sa client-side ( client ) at nag-commit ng ilang beses. Sa wakas, ikaw ay bumalik sa iyong server na branch at gumawa ng ilang mga commit. Figure 39. Isang kasaysayan na may isang paksa na naka-branch off sa ibang paksa na branch Ipagpalagay na ikaw na nakapagpasya na gusto mong i-merge ang iyong client-side na mga pagbabago sa iyong mainline para sa isang release, ngunit gusto mong pigilan ang mga pagbabago ng server-side hanggang ito ay mas lalo pang nasubukan. Maaari mong kunin ang mga pagbabago na wala sa server ( C8 at C9 ) at i-replay ang mga ito sa iyong master na branch gamit ang --onto na opsyon ng git rebase : $ git rebase --onto master server client Ang ibig talagang sabihin nito ay, “Kunin ang client na branch, alamin ang mga patch mula nung humiwalay ito mula sa server na branch, at i-replay ang mga patch na ito sa client na branch animo ito ay direktang nakabase sa master na branch.” Ito ay medyo kumplikado, ngunit ang resulta ay talagang kamangha-mangha. Figure 40. Pag-rebase ng isang paksa na naka-branch off sa ibang paksa na branch Ngayon maaari ka nang mag-fast-forward sa iyong master na branch (tingnan ang Pag-fast-forward ng iyong master na branch upang isama ang mga pagbabago sa kliyente na branch ): $ git checkout master $ git merge client Figure 41. Pag-fast-forward ng iyong master na branch upang isama ang mga pagbabago sa kliyente na branch Sabihin nating ikaw ay nakapagpasyang mag-pull din sa iyong server na branch. Maaari mong i-rebase ang server na branch sa master na branch nang hindi kailangang unang mag-check out nito sa pamamagitan ng pagpapatakbo ng git rebase <basebranch> <topicbranch> — na nagchi-check out ng paksa na branch (sa kasong ito, server ) para sa iyo at iri-replay ito sa base na branch ( master ): $ git rebase master server Ito ay iri-replay ang iyong server na trabaho sa itaas ng iyong master na trabaho, na ipinapakita sa Pag-rebase ng iyong server na branch sa itaas ng iyong master na branch . Figure 42. Pag-rebase ng iyong server na branch sa itaas ng iyong master na branch Pagkatapos, maaari mong i-fast-forward ang base na branch ( master ): Then, you can fast-forward the base branch ( master ): $ git checkout master $ git merge server Maaari mong tanggalin ang client at server na mga branch dahil lahat ang trabaho ay napagsama-sama na at hindi mo na kailangan ang mga ito, iniiwan ang iyong kasaysayan para sa buong proseso na nagmumukhang katulad ng Huling kasaysayan ng commit : $ git branch -d client $ git branch -d server Figure 43. Huling kasaysayan ng commit Ang mga Panganib ng Pag-rebase Ahh, ngunit ang kaligayahan ng pag-rebase ay mayroon ding kakulangan, na maaaring mabuo sa isang linya: Huwag mag-rebase ng mga commit na umiiral sa labas ng iyong repositoryo. Kung susundin mo ang patnubay na iyon, magiging maayos ka. Kung hindi, kasusuklaman ka ng mga tao, at kakamuhian ka ng iyong mga kaibigan at pamilya. Kapag ikaw ay nag-rebase ng mga bagay, ikaw ay lumilisan sa umiiral na mga commit at gumagawa ng mga panibago na kahawig ngunit naiiba. Kung magpu-push ka ng mga commit saanman at ang iba ay magpu-pull down ng mga ito at magbabase sa trabaho nito, at pagkatapos ay isusulat mo muli ang mga commit na iyon gamit ang git rebase at i-push muli ang mga ito, ang iyong mga katulong ay kailangang mag merge muli ng kanilang trabaho at ang mga bagay ay magugulo kapag sinubukan mong mag-pull sa kanilang trabaho patungo pabalik sa iyo. Tumingin tayo sa isang halimbawa kung papaano ang pag-rebase ng trabaho na iyong ginawang publiko ay maaaring magsanhi ng mga problema. Ipagpalagay na ikaw ay nag-clone mula sa isang sentral na server at pagkatapos ay gumawa ng ilang trabaho sa iyon. Ang iyong kasaysayan ng commit ay magmumukhang katulad nito: Figure 44. Mag-clone ng isang repositoryo, at magbase ng ilang trabaho nito Ngayon, may iba pang gumagawa ng higit pang trabaho na nagsasama ng isang merge, at nagpu-push ng trabahong iyon sa sentral na server. Kinuha mo ito at nag-merge ng bagong remote na branch sa iyong trabaho, ginagawang magkamukha nito ang iyong kasaysayan: Figure 45. Kumuha ng maraming mga commit, at i-merge ang mga ito sa iyong trabaho Susunod, ang tao na nag-push ng na-merge na trabaho ay nagpasyang bumalik at sa halip ay mag-rebase ng kanilang trabaho; gumawa sila ng isang git push --force upang sapawan ang kasaysayan sa server. Ikaw ngayon ay nag-fetch mula sa server na iyon, hinihila pababa ang mga bagong commit. Figure 46. May isang tao na nagpu-push ng na-rebase na mga commit, iniiwanan ang mga commit kung saan mo binase ang iyong trabaho Ngayon kayong dalawa ay nasa mahirap na kalagayan. Kung gagawa ka ng isang git pull , ikaw ay lilikha ng isang merge na commit na naglalaman ng parehong mga linya ng kasaysayan, at ang iyong repositoryo ay magmumukhang katulad nito: Figure 47. Ikaw ay muling nag-merge sa parehong trabaho patungo sa isang panibagong merge na commmit Kung magpapatakbo ka ng isang git log kapag ang iyong kasaysayan ay magmumukhang katulad nito, makikita mo ang dalawang mga commit na mayroong parehong may-akda, petsa, at mensahe, na kung saan ay nakalilito. At saka, kung ipu-push mo ang kasaysayang ito pabalik sa server, ipapakilala mo ulit ang lahat ng mga na-rebase na commit na iyon sa sentral na server, na kung saan ay tuluyan pang nakakalito sa mga tao. Medyo ligtas magpalagay na ang ibang developer ay hindi gusto ang C4 at C6 sa kasaysayan; iyan ang dahilan kung bakit sila nag-rebase sa simula pa lang. Mag-rebase Kung Ikaw ay Mag-rebase Kung talagang natagpuan mo iyong sarili sa sitwasyong katulad nito, ang Git ay may ilang higit pang salamangka na maaaring makatulong sa iyo. Kung may tao sa iyong team na sapilitang nagpu-push ng mga pagbabago na nag-o-overwrite ng trabaho kung saan nakabase ang iyong mga ginawa, ang iyong hamon ay ang malaman kung ano ang sa iyo at kung ano ang nasulat muli nila. Lumilitaw na sa karagdagan sa checksum ng commit SHA-1, ang Git ay nagkakalkula rin ng isang checksum na nakabase lamang sa patch na napakilala sa commit. Ito ay tinatawag na isang “patch-id”. Kung ikaw ay magpu-pull down ng trabaho na muling isinulat at iri-rebase ito sa itaas ng bagong mga commit mula sa iyong kasosyo, ang Git ay kadalasang matagumpay na nalalaman kung ano ang katangi-tanging sa iyo at ilalapat ang mga ito pabalik sa itaas ng bagong branch. Halimbawa, sa nakaraang sitwasyon, kung sa halip na gumawa ng isang merge kapag tayo ay nasa May isang tao na nagpu-push ng na-rebase na mga commit, iniiwanan ang mga commit kung saan mo binase ang iyong trabaho papatakbuhin natin ang git rebase teamone/master , ang Git ay: Tutukuyin kung anong trabaho ang katangi-tangi sa ating branch (C2, C3, C4, C6, C7) Tutukuyin kung ano ang hindi merge na mga commit (C2, C3, C4) Tutukuyin kung ano ang hindi naisulat muli sa target na branch (C2 at C3 lamang, dahil ang C4 ay kaparehong patch sa C4') Ilalapat ang mga commit na iyon sa itaas ng teamone/master Kaya sa halip sa resulta na nakikita natin sa Ikaw ay muling nag-merge sa parehong trabaho patungo sa isang panibagong merge na commmit , tayo ay magtatapos na may bagay na mas katulad sa Pag-rebase sa itaas ng na-force-push na rebase ng trabaho . Figure 48. Pag-rebase sa itaas ng na-force-push na rebase ng trabaho Ito ay gumagana lamang kung ang C4 at C4' na ginawa ng iyong kasosyo ay halos eksaktong magkatugma na patch. Kung hindi ay ang rebase ay hindi makakapagsabi na ito ay isang kopya at magdaragdag ng ibang katulad ng C4 na patch (na marahil ay mabibigong malinis na maglapat, dahil ang mga pagbabago ay marahil nandoon na). Maaari mo ring pasimplihin ito sa pamamagitan ng isang git pull --rebase sa halip na isang normal na git pull . O maaari mong manu-manong gawin ito gamit ang isang git fetch na sinusundan ng isang git rebase teamone/master sa kasong ito. Kung ikaw ay gumagamit ng git pull at gustong i- --rebase ang default, maaari mong itakda ang halaga ng pull.rebase na config gamit ang kagaya ng git config --global pull.rebase true . Kung ituturing mo ang pag-rebase bilang isang paraan upang maglinis at magtrabaho sa mga commit bago mo i-push ang mga ito, at kung ikaw ay magri-rebase lamang ng mga commit na hindi pampublikong magagamit, ikaw ay magiging maayos lamang. Kung ikaw ay magri-rebase ng mga commit na pampublikong nai-push na, at ang mga tao ay bumabase ng kanilang trabaho sa mga commit na iyon, ikaw ay maaaring mapasabak sa isang nakakabigong panganib, at suklam ng iyong mga kasamahan sa koponan. Kung ikaw o isang kasosyo ay nakatuklas na kinakailangan ito sa isang punto, siguraduhing ang lahat ay nakakaalam kung paano patakbuhin ang git pull --rebase upang subukang mas pasimplehin pa ang sakit nito pagkatapos. Rebase vs. Merge Ngayong nakita mo na ang pag-rebase at pag-merge na kumikilos, baka ikaw ay nagtataka kung ano ang mas mabuti. Bago natin maaaring sagutin ito, umatras muna tayo at pag-usapan ang tungkol sa ibig sabihin ng kasaysayan. Isang pananaw nito ay ang iyong kasaysayan ng commit sa repositoryo ay isang rekord kung ano ang tunay na nangyari. Ito ay isang makasaysayang dokumento, mahalaga sa sarili nitong karapatan, at hindi dapat mabago. Mula sa anggulong ito, ang pagbabago sa kasaysayan ng commit ay halos lapastangan sa diyos; ikaw ay nagsisinungaling tungkol sa kung ano ang tunay na naganap. Kaya ano kung mayroong isang magulong serye ng merge na mga commit? Iyon ang nangyari, at ang repositoryo ay kailangang i-preserba iyon para sa angkan. Ang humahadlang na pananaw ay ang kasaysayan ng commit ay ang istorya kung papaano nagawa ang iyong proyekto. Hindi mo iaambag ang unang draft ng isang aklat, at ang manwal para sa kung papaano panatilihin ang iyong software ay nararapat na ingatan ang pag-edit. Ito ang kampo na gumagamit ng mga kasangkapan katulad ng rebase at filter-branch upang magtalakay sa istorya sa paraan na pinakamainam para sa mga mambabasa sa hinaharap. Ngayon, sa tanong kung alin sa pag-merge o pag-rebase ang mas mabuti: sana makita mo na ito ay hindi ganoon ka simple. Ang Git ay isang makapangyarihan na kasangkapan, at nagpapahintulot sa iyo upang gumawa ng maraming mga bagay at gamit ang iyong kasaysayan, ngunit bawat koponan at bawat proyekto ay magkakaiba. Ngayon na alam mo na kung paano gumagana ang dalawang bagay na ito, nakasalalay sa iyo na magpasya kung ano ang pinakamainam para sa iyong partikular na sitwasyon. Sa karaniwan ang paraan upang makakuha ng pinakamabuti sa dalawang mundo ay ang pag-rebase ng mga lokal na pagbabago na ginawa mo ngunit hindi pa naibahagi bago mo i-push ang mga ito upang linisin ang iyong istorya, ngunit huwag mag-rebase ng kahit ano na na-push mo kahit saan. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/tiktok#discover-by-search-url | TikTok API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs TikTok API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profile API Collect by URL Discover by Search URL Posts API Collect by URL Discover by Profile URL Discover by Keywords Discover by Discover URL Comments API Collect by URL Social Media APIs TikTok API Scrapers Copy page Copy page Overview The TikTok API Suite offers multiple types of APIs, each designed for specific data collection needs from TikTok. Below is an overview of how these APIs connect and interact, based on the available features: Profile API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Direct URL of the search Interesting Columns : nickname , awg_engagement_rate , followers , likes Posts API This API allows users to collect multiple posts based on a single input URL. Discovery functionality : - Direct URL of the TikTok profile - Discover by keywords - Direct URL of the discovery Interesting Columns : url , share_count , description , hashtags Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : url , comment_text , commenter_url , num_likes Profile API Collect by URL This API allows users to retrieve detailed TikTok profile information using the provided profile URL. Input Parameters : URL string required The TikTok profile URL. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API allows users to retrieve detailed TikTok profile information, including engagement metrics, privacy settings, and top videos, offering insights into user activity and profile data. Discover by Search URL This API allows users to discover TikTok profiles based on a specific search URL and country, providing detailed profile information. Input Parameters : search_url string required The TikTok search URL. country string required The country from which to perform the search. Output Structure : Includes comprehensive data points: Profile Details : account_id , nickname , biography , bio_link , predicted_lang , is_verified , followers , following , likes , videos_count , create_time , id , url , profile_pic_url , profile_pic_url_hd , and more. For all data points, click here . Engagement Metrics : awg_engagement_rate , comment_engagement_rate , like_engagement_rate , like_count , digg_count . Privacy & Settings : is_private , relation , open_favorite , comment_setting , duet_setting , stitch_setting , is_ad_virtual , room_id , is_under_age_18 . Discovery & Top Videos : region , top_videos , discovery_input . This API enables users to discover TikTok profiles based on search criteria, offering insights into user activity, engagement, privacy settings, and top content. It helps facilitate efficient discovery and analysis of TikTok users. Posts API Collect by URL This API enables users to collect detailed data from TikTok posts by providing a post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information: : tt_chain_token , secu_id Discover by Profile URL This API allows users to retrieve posts from a TikTok profile based on a provided profile URL, with filtering options for the number of posts, date range, and post exclusions. Input Parameters : URL string required The TikTok profile URL. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. start_date string Start date for filtering posts (format: mm-dd-yyyy). Should be lower than end_date . end_date string End date for filtering posts (format: mm-dd-yyyy). Should be greater than start_date . what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , official_item , original_item , shortcode , video_url , music , cdn_url , width , carousel_images , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover and retrieve detailed information about posts from a specific TikTok profile, including post-specific metrics, profile details of the creator, and tagged users. It supports efficient content discovery and post analysis. Discover by Keywords This API allows users to search for TikTok posts based on specific keywords or hashtags, offering a powerful tool for discovering relevant content across TikTok’s platform. Input Parameters : search_keyword string required The keyword or hashtag to search for within TikTok posts. num_of_posts number The number of posts to collect. If not provided, there is no limit. posts_to_not_include array An array of post IDs to exclude from the collection. what_to_collect string Specify the type of posts to collect (e.g., “post” or “reel”). Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API allows users to discover posts on TikTok that match specific keywords or hashtags, providing insights into post details, profile information, and media. It’s a great tool for exploring trends, content, and users on TikTok. Discover by Discover URL This API allows users to collect detailed post data from a specific TikTok discover URL. Input Parameters : URL string required The TikTok discover URL from which posts will be retrieved. Output Structure : Includes comprehensive data points: Post Details : post_id , description , create_time , digg_count , share_count , collect_count , comment_count , play_count , video_duration , hashtags , original_sound , post_type , discovery_input , official_item , original_item , and more. For all data points, click here . Profile Details : profile_id , profile_username , profile_url , profile_avatar , profile_biography , account_id , profile_followers , is_verified . Tagged Users and Media : tagged_user , carousel_images . Additional Information : tt_chain_token , secu_id . This API provides detailed insights into TikTok posts discovered via the discover URL, allowing for easy access to trending content, user profiles, and post metadata for analysis and exploration. Comments API Collect by URL This API allows users to collect detailed comment data from a specific TikTok post using the provided post URL. Input Parameters : URL string required The TikTok post URL. Output Structure : Includes comprehensive data points: Post Details : post_url , post_id , post_date_created . For all data points, click here . Comment Details : date_created , comment_text , num_likes , num_replies , comment_id , comment_url . Commenter Details : commenter_user_name , commenter_id , commenter_url . This API provides detailed insights into TikTok post comments, including comment-specific metrics and information about the commenters, enabling effective comment analysis and interaction tracking. Was this page helpful? Yes No LinkedIn Reddit ⌘ I linkedin youtube github Powered by | 2026-01-13T09:29:25 |
https://git-scm.com/book/cs/v2/Git-na-serveru-Mo%c5%benosti-hostov%c3%a1n%c3%ad-u-t%c5%99et%c3%ad-strany | Git - Možnosti hostování u třetí strany 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. Úvod 1.1 Správa verzí 1.2 Stručná historie systému Git 1.3 Základy systému Git 1.4 Příkazový řádek 1.5 Instalace systému Git 1.6 První nastavení systému Git 1.7 Získání nápovědy 1.8 Shrnutí 2. Základy práce se systémem Git 2.1 Získání repozitáře Git 2.2 Nahrávání změn do repozitáře 2.3 Zobrazení historie revizí 2.4 Návrat do předchozího stavu 2.5 Práce se vzdálenými repozitáři 2.6 Používání značek 2.7 Aliasy v Gitu 2.8 Shrnutí 3. Větve v systému Git 3.1 Větve v kostce 3.2 Základy větvení a slučování 3.3 Správa větví 3.4 Postupy při práci s větvemi 3.5 Vzdálené větve 3.6 Přeskládání 3.7 Shrnutí 4. Git na serveru 4.1 Protokoly 4.2 Zprovoznění Gitu na serveru 4.3 Generování veřejného klíče SSH 4.4 Nastavení serveru 4.5 Démon Git 4.6 Chytrý HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti hostování u třetí strany 4.10 Shrnutí 5. Distribuovaný Git 5.1 Distribuované pracovní postupy 5.2 Přispívání do projektu 5.3 Správa projektu 5.4 Shrnutí 6. GitHub 6.1 Zřízení účtu a úprava konfigurace 6.2 Přispívání do projektu 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Shrnutí 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 Ladění v systému Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Shrnutí 8. Customizing Git 8.1 Git Configuration 8.2 Atributy Git 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Shrnutí 9. Git a ostatní systémy 9.1 Git as a Client 9.2 Migrating to Git 9.3 Shrnutí 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Balíčkové soubory 10.5 The Refspec 10.6 Přenosové protokoly 10.7 Správa a obnova dat 10.8 Environment Variables 10.9 Shrnutí 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 Shrnutí 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.9 Git na serveru - Možnosti hostování u třetí strany Možnosti hostování u třetí strany Pokud nechcete vynakládat práci spojenou se zprovozněním vlastního severu pro Git, máte několik možností pro hostování svých gitových projektů na specializovaných externích serverech. Toto řešení vám nabízí celou řadu výhod. Hostingové místo lze zprovoznit většinou velmi rychle a snadno. A nemusíte se zabývat údržbou nebo sledováním serveru. Veřejné hostingové místo můžete chtít pro svůj open-source kód použít dokonce i v případech, kdy interně provozujete svůj vlastní server. Pro open-source komunitu může být snadnější váš projekt najít a zapojit se do něj. V dnešní době můžete vybírat z velkého počtu možností hostingu. Každá má jiné klady a zápory. Aktualizovaný seznam si můžete prohlédnout na stránce GitHosting , která je součástí hlavních wiki stránek pro Git. V kapitole GitHub si podrobně probereme používání GitHubu, protože jde o nejrozsáhlejší hostovací server pro Git a protože asi budete potřebovat spolupracovat s projekty, které jsou na něm hostovány. Ale pokud si nechcete zprovoznit svůj vlastní server pro Git, můžete si vybrat z tuctu dalších možností. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://git-scm.com/book/tr/v2/Git-Temelleri-Komut-K%c4%b1sayolu-Alias-Ayarlama | Git - Komut Kısayolu (Alias) Ayarlama 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 2.7 Git Temelleri - Komut Kısayolu (Alias) Ayarlama Komut Kısayolu (Alias) Ayarlama Temel Git ile ilgili bu bölümü bitirmeden önce Git deneyiminizi daha basit, daha kolay ve daha tanıdık hale getirebilecek küçük bir ipucu vereceğiz: komut kısayolları. Bu kitapta kısayol konusuna detaylıca girmeyeceğiz veya ilerleyen bölümlerde bunları kullandığınızı varsaymayacağız, ancak yine de nasıl kullanacağınızı bilmenizde fayda var. Eğer komutunuzun tamamını yazmazsanız, Git bir kısaltma yaptığınızı otomatik olarak anlayamaz. Git komutlarının tamamını uzun uzun yazmak istemiyorsanız, git config komutunu kullanarak, dilediğiniz komut için kolaylıkla bir kısayol ayarlayabilirsiniz. Aşağıda kısayol olarak atamak isteyebileceğiniz birkaç örnek verilmiştir: $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status İlk örnekte git commit yerine git ci komutunu ayarlıyorsunuz. Artık git ci yazarsanız Git bunu git commit olarak düşünecektir. Git’i kullanmaya devam ettikçe muhtemelen diğer komutları da sıklıkla kullanacaksınız. Yeni kısayollar oluşturmaktan çekinmeyin. Bu tekniği aynı zamanda Git’te mevcut olmayan, ama olması gerektiğini düşündüğünüz komutların oluşturulmasında da kullanabilirsiniz. Örneğin, bir dosyayı izlemden (stage) kaldırırken karşılaştığınız "kullanılabilirlik" sorununu düzeltmek için Git’e kendi izlemden kaldırma komutunuzu ekleyebilirsiniz: $ git config --global alias.unstage 'reset HEAD --' Bu yeni tanımlanan komut, aşağıdaki iki komutun işini tek başına yapacaktır. $ git unstage fileA $ git reset HEAD -- fileA Böylesi daha temiz görünüyor. Bir last komutu eklemek de çok yaygındır. Şunun gibi: $ git config --global alias.last 'log -1 HEAD' Böylelikle son işlemi kolayca görebilirsiniz: $ git last commit 66938dae3329c7aebe598c2246a8e6af90d04646 Author: Josh Goebel <dreamer3@example.com> Date: Tue Aug 26 19:48:51 2008 +0800 test for current head Signed-off-by: Scott Chacon <schacon@example.com> Gördüğünüz gibi Git, yeni komutu her neyin kısayolu olarak ayarlarsanız onunla değiştirir. Ancak Git alt komutları yerine, harici bir komut da çalıştırmak isteyebilirsiniz. Bu durumda komuta ! karakteriyle başlamalısınız. Eğer Git’te çalışan kendi komutlarınızı yazmak istiyorsanız bu epey kullanışlıdır. Hadi git visual komutunu çalıştıracak gitk kısayolunu atamayı gösterelim: $ git config --global alias.visual '!gitk' prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://git-scm.com/book/uz/v2/Git-%d1%81%d0%b5%d1%80%d0%b2%d0%b5%d1%80%d0%b4%d0%b0-%d0%a5%d1%83%d0%bb%d0%be%d1%81%d0%b0%d0%bb%d0%b0%d1%80 | 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 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.10 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:25 |
https://docs.aws.amazon.com/es_es/AmazonCloudWatch/latest/monitoring/Solution-NVIDIA-GPU-On-EC2.html | Solución de CloudWatch: carga de trabajo de GPU NVIDIA en Amazon EC2 - Amazon CloudWatch Solución de CloudWatch: carga de trabajo de GPU NVIDIA en Amazon EC2 - Amazon CloudWatch Documentación Amazon CloudWatch Guía del usuario Requisitos Ventajas Configuración del agente de CloudWatch para esta solución Implementar el agente para su solución Crear el panel de soluciones de GPU NVIDIA Solución de CloudWatch: carga de trabajo de GPU NVIDIA en Amazon EC2 Esta solución lo ayuda a configurar la recopilación de métricas lista para usar mediante agentes de CloudWatch para las cargas de trabajo de GPU NVIDIA que se ejecutan en instancias de EC2. Además, lo ayuda a configurar un panel de CloudWatch preconfigurado. Para obtener información general sobre todas las soluciones de observabilidad de CloudWatch, consulte Soluciones de observabilidad de CloudWatch . Temas Requisitos Ventajas Configuración del agente de CloudWatch para esta solución Implementar el agente para su solución Crear el panel de soluciones de GPU NVIDIA Requisitos Esta solución es adecuada para las siguientes condiciones: Recursos informáticos: Amazon EC2 Compatible con hasta 500 GPU en todas las instancias de EC2 en una determinadaRegión de AWS Versión más reciente del agente de CloudWatch SSM Agent instalado en la instancia de EC2 La instancia de EC2 debe tener instalado un controlador NVIDIA. Los controladores NVIDIA están preinstalados en algunas Imágenes de máquina de Amazon (AMI). De lo contrario, puede instalar el controlador de forma manual. Para obtener más información, consulte Instalar los controladores NVIDIA en instancias de Linux . nota AWS Systems Manager (SSM Agent) está preinstalado en algunas Imágenes de máquina de Amazon (AMI) proporcionadas por AWS y terceros de confianza. Si el agente no está instalado, puede instalarlo manualmente mediante el procedimiento correspondiente al tipo de sistema operativo. Instalación y desinstalación manual del SSM Agent en instancias de EC2 para Linux Instalación y desinstalación manual del SSM Agent en instancias de EC2 para macOS Instalación y desinstalación manual del SSM Agent en instancias de EC2 para Windows Server Ventajas La solución ofrece supervisión NVIDIA, lo que proporciona información valiosa para los siguientes casos de uso: Analice el uso de GPU y de memoria para detectar cuellos de botella en el rendimiento o la necesidad de recursos adicionales. Supervise la temperatura y el consumo de energía para garantizar que las GPU funcionen dentro de límites seguros. Evalúe el rendimiento del codificador para las cargas de trabajo de video de la GPU. Compruebe la conectividad PCIe para conocer la generación y el ancho esperados. Supervise las velocidades de reloj de la GPU para detectar problemas de escala y limitación. A continuación se detallan las principales ventajas de la solución: Automatiza la recopilación de métricas para NVIDIA mediante la configuración del agente de CloudWatch, lo que elimina la instrumentación manual. Proporciona un panel de CloudWatch consolidado y preconfigurado para las métricas de NVIDIA. El panel administrará automáticamente las métricas de las nuevas instancias de EC2 de NVIDIA configuradas con la solución, incluso si esas métricas no existían cuando creó el panel por primera vez. La siguiente imagen muestra un ejemplo del panel para esta solución: Costos Esta solución crea y utiliza recursos en su espacio de trabajo. Se cobrará por el uso estándar, que incluye lo siguiente: Las métricas recopiladas por el agente de CloudWatch se cobran como métricas personalizadas. La cantidad de métricas que utiliza esta solución depende de la cantidad de hosts de EC2. Cada host de EC2 configurado para la solución publica un total de 17 métricas por GPU. Un panel personalizado. Operaciones de API solicitadas por el agente de CloudWatch para publicar las métricas. Con la configuración predeterminada de esta solución, el agente de CloudWatch llama a PutMetricData una vez por minuto para cada host de EC2. Esto significa que la API PutMetricData se llamará 30*24*60=43,200 en un mes de 30 días para cada host de EC2. Para obtener más información sobre los precios de CloudWatch, consulte Precios de Amazon CloudWatch . La calculadora de precios puede ayudarlo a estimar los costos mensuales aproximados del uso de esta solución. Para usar la calculadora de precios para estimar los costos mensuales de la solución Abra la calculadora de precios de Amazon CloudWatch . En Elegir una región , seleccione la región en la que desea implementar la solución. En la sección Métricas , en Número de métricas , ingrese 17 * average number of GPUs per EC2 host * number of EC2 instances configured for this solution . En la sección API , en Número de solicitudes de API , ingrese 43200 * number of EC2 instances configured for this solution . De forma predeterminada, el agente CloudWatch realiza una operación PutMetricData por minuto para cada host de EC2. En la sección Paneles y alarmas , en Número de paneles , escriba 1 . Puede ver sus costos mensuales estimados en la parte inferior de la calculadora de precios. Configuración del agente de CloudWatch para esta solución El agente de CloudWatch es un software que se ejecuta de forma continua y autónoma en sus servidores y en entornos contenerizados. Recopila métricas, registros y trazas de su infraestructura y aplicaciones y los envía a CloudWatch y X-Ray. Para obtener más información sobre el agente de CloudWatch, consulte Recopile las métricas, registros y rastros con el agente de CloudWatch . La configuración del agente de esta solución recopila un conjunto de métricas para ayudarlo a empezar a supervisar y observar su GPU NVIDIA. El agente de CloudWatch se puede configurar para recopilar más métricas de GPU NVIDIA que las que muestra el panel de forma predeterminada. Para ver una lista de todas las métricas de GPU NVIDIA que puede recopilar, consulte Recopilación de métricas de GPU NVIDIA . Configuración del agente de CloudWatch para esta solución Las métricas que el agente recopiló se definen en la configuración del agente. La solución proporciona configuraciones de agentes para recopilar las métricas recomendadas con las dimensiones adecuadas para el panel de la solución. Utilice la siguiente configuración de agente de CloudWatch en instancias EC2 con GPU NVIDIA. La configuración se almacenará como parámetro en Parameter Store de SSM, como se detalla más adelante en Paso 2: almacene el archivo de configuración recomendado del agente de CloudWatch en Parameter Store de Systems Manager . { "metrics": { "namespace": "CWAgent", "append_dimensions": { "InstanceId": "$ { aws:InstanceId}" }, "metrics_collected": { "nvidia_gpu": { "measurement": [ "utilization_gpu", "temperature_gpu", "power_draw", "utilization_memory", "fan_speed", "memory_total", "memory_used", "memory_free", "pcie_link_gen_current", "pcie_link_width_current", "encoder_stats_session_count", "encoder_stats_average_fps", "encoder_stats_average_latency", "clocks_current_graphics", "clocks_current_sm", "clocks_current_memory", "clocks_current_video" ], "metrics_collection_interval": 60 } } }, "force_flush_interval": 60 } Implementar el agente para su solución Existen varios métodos de instalación del agente de CloudWatch, según el caso de uso. Recomendamos usar Systems Manager para esta solución. Proporciona una experiencia de consola y simplifica la administración de una flota de servidores administrados en una sola cuenta de AWS. Las instrucciones de esta sección utilizan Systems Manager y están pensadas para cuando el agente de CloudWatch no se esté ejecutando con las configuraciones existentes. Puede comprobar si el agente de CloudWatch se está ejecutando, siguiendo los pasos que se indican en Verifique que el agente de CloudWatch esté en ejecución . Si ya ejecuta el agente de CloudWatch en los hosts de EC2 en los que se implementa la carga de trabajo y administra las configuraciones del agente, puede omitir las instrucciones de esta sección y seguir el mecanismo de implementación existente para actualizar la configuración. Asegúrese de combinar la configuración de agente de la GPU NVIDIA con la configuración de agente existente y, a continuación, implemente la configuración combinada. Si utiliza Systems Manager para almacenar y administrar la configuración del agente de CloudWatch, puede combinar la configuración con el valor del parámetro existente. Para obtener más información, consulte Managing CloudWatch agent configuration files . nota El uso de Systems Manager para implementar las siguientes configuraciones de agente de CloudWatch reemplazará o sobrescribirá cualquier configuración de agente de CloudWatch existente en las instancias de EC2. Puede modificar esta configuración para adaptarla a su entorno o caso de uso únicos. Las métricas definidas en la configuración son las mínimas requeridas para el panel proporcionado por la solución. El proceso de implementación consta de los siguientes pasos: Paso 1: asegúrese de que las instancias de EC2 de destino disponen de los permisos de IAM necesarios. Paso 2: almacene el archivo de configuración recomendado del agente en Parameter Store de Systems Manager. Paso 3: instale el agente de CloudWatch en una o más instancias de EC2 mediante una pila de CloudFormation. Paso 4: verifique que la configuración del agente sea correcta. Paso 1: asegúrese de que las instancias de EC2 de destino disponen de los permisos de IAM necesarios Debe conceder permiso a Systems Manager para instalar y configurar el agente de CloudWatch. También debe conceder permiso al agente de CloudWatch para publicar la telemetría de su instancia de EC2 en CloudWatch. Asegúrese de que el rol de IAM adjuntado a la instancia tenga adjuntas las políticas de IAM CloudWatchAgentServerPolicy y AmazonSSMManagedInstanceCore . Después de crear el rol, adjunte el rol a sus instancias de EC2. Para adjuntar un rol a una instancia de EC2, siga los pasos que se indican en Adjuntar un rol de IAM a una instancia . Paso 2: almacene el archivo de configuración recomendado del agente de CloudWatch en Parameter Store de Systems Manager Parameter Store simplifica la instalación del agente de CloudWatch en una instancia de EC2 al almacenar y administrar los parámetros de configuración de forma segura, lo que elimina la necesidad de valores de codificación rígida. Esto garantiza un proceso de implementación más seguro y flexible, lo que permite una administración centralizada y facilita las actualizaciones de las configuraciones en varias instancias. Siga los pasos a continuación para almacenar el archivo de configuración del agente de CloudWatch recomendado como parámetro en Parameter Store. Para crear el archivo de configuración del agente de CloudWatch como parámetro Abra la consola de AWS Systems Manager en https://console.aws.amazon.com/systems-manager/ . Compruebe que la región seleccionada en la consola sea la región en la que se ejecuta la carga de trabajo de la GPU NVIDIA. Desde el panel de navegación, elija Administración de aplicaciones , Parameter Store . Siga estos pasos para crear un nuevo parámetro para la configuración. Elija Create parameter . En el cuadro Nombre , ingrese un nombre que utilizará para hacer referencia al archivo de configuración del agente de CloudWatch en pasos posteriores. Por ejemplo, AmazonCloudWatch-NVIDIA-GPU-Configuration . (Opcional) En el cuadro Descripción , escriba una descripción para el parámetro. En Capa de parámetros , elija Estándar . En Type , elija String . En Tipo de datos , elija texto . En el cuadro Valor , pegue el bloque JSON correspondiente que aparece en Configuración del agente de CloudWatch para esta solución . Elija Create parameter . Paso 3: instale el agente de CloudWatch y aplique la configuración mediante una plantilla de CloudFormation Puede usar AWS CloudFormation para instalar el agente y configurarlo para que use la configuración del agente de CloudWatch que creó en los pasos anteriores. Para instalar y configurar el agente de CloudWatch para esta solución Abra el asistente de CloudFormation Creación rápida de pilas mediante este enlace: https://console.aws.amazon.com/cloudformation/home?#/stacks/quickcreate?templateURL=https://aws-observability-solutions-prod-us-east-1.s3.us-east-1.amazonaws.com/CloudWatchAgent/CFN/v1.0.0/cw-agent-installation-template-1.0.0.json . Compruebe que la región seleccionada en la consola sea la región en la que se ejecuta la carga de trabajo de la GPU NVIDIA. En Nombre de la pila , ingrese un nombre para identificar esta pila, como CWAgentInstallationStack . En la sección Parámetros , especifique los siguientes parámetros: En CloudWatchAgentConfigSSM , ingrese el nombre del parámetro de Systems Manager para la configuración del agente que creó anteriormente, por ejemplo AmazonCloudWatch-NVIDIA-GPU-Configuration . Para seleccionar las instancias de destino, tiene dos opciones. En el caso de InstanceIds , especifique una lista delimitada por comas de una lista de ID de instancia en los que desee instalar el agente de CloudWatch con esta configuración. Puede enumerar una sola instancia o varias instancias. Si realiza una implementación a escala, puede especificar la TagKey y el TagValue correspondiente para dirigirse a todas las instancias de EC2 con esta etiqueta y valor. Si especifica una TagKey , debe especificar el TagValue correspondiente. (En el caso de un grupo de escalado automático, especifique aws:autoscaling:groupName para TagKey y especifique el nombre del grupo de escalado automático para que TagValue se implemente en todas las instancias del grupo de escalado automático). Revise la configuración y, a continuación, seleccione Crear pila . Si quiere editar primero el archivo de plantilla para personalizarlo, seleccione la opción Cargar un archivo de plantilla en el Asistente de creación de pilas para cargar la plantilla editada. Para obtener más información, consulte Creación de una pila en la consola de CloudFormation . nota Una vez completado este paso, este parámetro de Systems Manager se asociará a los agentes de CloudWatch que se ejecuten en las instancias de destino. Esto significa que: Si se elimina el parámetro de Systems Manager, el agente se detendrá. Si se edita el parámetro de Systems Manager, los cambios de configuración se aplicarán automáticamente al agente con la frecuencia programada, que es de 30 días por defecto. Si desea aplicar inmediatamente los cambios a este parámetro de Systems Manager, debe volver a ejecutar este paso. Para obtener más información sobre asociaciones, consulte Trabajo con asociaciones en Systems Manager . Paso 4: verifique que la configuración del agente sea correcta Puede comprobar si el agente de CloudWatch está instalado siguiendo los pasos que se indican en Verifique que el agente de CloudWatch esté en ejecución . Si el agente de CloudWatch no está instalado ni en ejecución, asegúrese de haber configurado todo correctamente. Asegúrese de haber adjuntado un rol con los permisos correctos a la instancia EC2, tal y como se describe en Paso 1: asegúrese de que las instancias de EC2 de destino disponen de los permisos de IAM necesarios . Asegúrese de haber configurado correctamente el JSON para el parámetro de Systems Manager. Siga los pasos de Solución de problemas de la instalación del agente de CloudWatch con CloudFormation . Si todo está configurado correctamente, debería ver las métricas de la GPU NVIDIA publicadas en CloudWatch. Puede comprobar la consola de CloudWatch para verificar que se estén publicando. Para verificar que las métricas de la GPU NVIDIA se publican en CloudWatch Abra la consola de CloudWatch en https://console.aws.amazon.com/cloudwatch/ . Elija Métricas , Todas las métricas . Asegúrese de haber seleccionado la región en la que implementó la solución y elija Namespaces personalizados , CWAgent . Busque las métricas mencionadas en Configuración del agente de CloudWatch para esta solución , por ejemplo nvidia_smi_utilization_gpu . Si ve los resultados de estas métricas, significa que las métricas se están publicando en CloudWatch. Crear el panel de soluciones de GPU NVIDIA El panel proporcionado por esta solución presenta las métricas de las GPU NVIDIA mediante la agregación y presentación de las métricas de todas las instancias. El panel muestra un desglose de los principales contribuyentes (los 10 principales por widget de métrica) para cada métrica. Esto lo ayuda a identificar rápidamente los valores atípicos o las instancias que contribuyen de manera significativa a las métricas observadas. Para crear el panel, puede usar las siguientes opciones: Use la consola de CloudWatch para crear el panel. Utilice la consola de AWS CloudFormation para implementar el panel. Descargue la infraestructura de AWS CloudFormation como código e intégrela como parte de su automatización de integración continua (CI). Al utilizar la consola de CloudWatch para crear un panel, puede obtener una vista previa del panel antes de crearlo y que se le cobre por ello. nota El panel creado con CloudFormation en esta solución muestra las métricas de la región en la que se implementa la solución. Asegúrese de crear la pila CloudFormation en la región en la que se publican las métricas de su GPU NVIDIA. Si especificó un namespace personalizado que no sea CWAgent en la configuración del agente de CloudWatch, tendrá que cambiar la plantilla CloudFormation del panel para sustituir CWAgent por el namespace personalizado que esté utilizando. Para crear el panel mediante la consola de CloudWatch Abra la consola de CloudWatch en Crear panel mediante este enlace: https://console.aws.amazon.com/cloudwatch/home?#dashboards?dashboardTemplate=NvidiaGpuOnEc2&referrer=os-catalog . Compruebe que la región seleccionada en la consola sea la región en la que se ejecuta la carga de trabajo de la GPU NVIDIA. Ingrese el nombre del panel, luego seleccione Crear panel . Para diferenciar fácilmente este panel de otros paneles similares de otras regiones, recomendamos incluir el nombre de la región en el nombre del panel, por ejemplo NVIDIA-GPU-Dashboard-us-east-1 . Obtenga una vista previa del panel y seleccione Guardar para crearlo. Para crear el panel de control mediante CloudFormation Abra el asistente de CloudFormation Creación rápida de pilas mediante este enlace: https://console.aws.amazon.com/cloudformation/home?#/stacks/quickcreate?templateURL=https://aws-observability-solutions-prod-us-east-1.s3.us-east-1.amazonaws.com/NVIDIA_GPU_EC2/CloudWatch/CFN/v1.0.0/dashboard-template-1.0.0.json . Compruebe que la región seleccionada en la consola sea la región en la que se ejecuta la carga de trabajo de la GPU NVIDIA. En Nombre de la pila , ingrese un nombre para identificar esta pila, como NVIDIA-GPU-DashboardStack . En la sección Parámetros , especifique el nombre del panel en el parámetro DashboardName . Para diferenciar fácilmente este panel de otros paneles similares de otras regiones, recomendamos incluir el nombre de la región en el nombre del panel, por ejemplo NVIDIA-GPU-Dashboard-us-east-1 . Reconozca las capacidades de acceso para las transformaciones en Capacidades y transformaciones . Tenga en cuenta que CloudFormation no agrega ningún recurso de IAM. Revise la configuración y, a continuación, seleccione Crear pila . Cuando el estado de la pila sea CREATE_COMPLETE , elija la pestaña Recursos situada debajo de la pila creada y, a continuación, elija el enlace situado en ID físico para ir al panel. También puede acceder al panel en la consola de CloudWatch seleccionando Paneles en el panel de navegación izquierdo de la consola y buscando el nombre del panel en Paneles personalizados . Si desea editar el archivo de plantilla para personalizarlo para cualquier propósito, puede usar la opción Cargar un archivo de plantilla en Crear asistente de pilas para cargar la plantilla editada. Para obtener más información, consulte Creación de una pila en la consola de CloudFormation . Puede utilizar este enlace para descargar la plantilla: https://aws-observability-solutions-prod-us-east-1.s3.us-east-1.amazonaws.com/NVIDIA_GPU_EC2/CloudWatch/CFN/v1.0.0/dashboard-template-1.0.0.json . Introducción al panel de GPU NVIDIA Estas son algunas tareas que puede probar con el nuevo panel de GPU NVIDIA. Estas tareas permiten comprobar que el panel funciona correctamente y le proporcionan experiencia práctica al usarlo para supervisar sus GPU NVIDIA. A medida que las vaya probando, se familiarizará con la navegación por el panel y la interpretación de las métricas visualizadas. Revisar el uso de la GPU En la sección Uso , busque los widgets Uso de GPU y Uso de memoria . Estos muestran el porcentaje de tiempo que la GPU se utiliza activamente para realizar cálculos y el porcentaje de memoria global que se lee o escribe, respectivamente. Un uso elevado podría indicar posibles cuellos de botella de rendimiento o la necesidad de recursos adicionales de la GPU. Analizar el uso de memoria de la GPU En la sección Memoria , busque los widgets Memoria total , Memoria usada y Memoria libre . Estos proporcionan información sobre la capacidad total de memoria de las GPU y la cantidad de memoria que se consume o está disponible actualmente. La presión de la memoria puede provocar problemas de rendimiento o errores por falta de memoria, por lo que es importante supervisar estas métricas y garantizar que haya suficiente memoria disponible para sus cargas de trabajo. Supervisar la temperatura y el consumo de energía En la sección Temperatura/energía , busque los widgets Temperatura de GPU y Consumo de energía . Estas métricas son esenciales para garantizar que las GPU funcionen dentro de los límites térmicos y de potencia seguros. Identificar el rendimiento del codificador En la sección Codificador , busque los widgets Recuento de sesiones del codificador , FPS promedio y Latencia promedio . Estas métricas son pertinentes si ejecuta cargas de trabajo de codificación de video en sus GPU. Supervise estas métricas para asegurarse de que sus codificadores funcionan de manera óptima e identifique cualquier posible cuello de botella o problema de rendimiento. Compruebe el estado del enlace PCIe En la sección PCIe , busque los widgets Generación de enlace PCIe y Ancho de enlace PCIe . Estas métricas proporcionan información sobre el enlace PCIe que conecta la GPU al sistema host. Asegúrese de que el enlace funcione con la generación y el ancho esperados para evitar posibles limitaciones de rendimiento debido a los cuellos de botella del PCIe. Revisar los relojes de la GPU En la sección Reloj , busque los widgets Reloj gráfico , Reloj SM , Reloj de memoria y Reloj de video . Estas métricas muestran las frecuencias de funcionamiento actuales de varios componentes de la GPU. La supervisión de estos relojes puede ayudar a identificar posibles problemas relacionados con la escala del reloj de la GPU o la limitación de la frecuencia, que podrían afectar el rendimiento. JavaScript está desactivado o no está disponible en su navegador. Para utilizar la documentación de AWS, debe estar habilitado JavaScript. Para obtener más información, consulte las páginas de ayuda de su navegador. Convenciones del documento Carga de trabajo de NGINX en EC2 Carga de trabajo de Kafka en EC2 ¿Le ha servido de ayuda esta página? - Sí Gracias por hacernos saber que estamos haciendo un buen trabajo. Si tiene un momento, díganos qué es lo que le ha gustado para que podamos seguir trabajando en esa línea. ¿Le ha servido de ayuda esta página? - No Gracias por informarnos de que debemos trabajar en esta página. Lamentamos haberle defraudado. Si tiene un momento, díganos cómo podemos mejorar la documentación. | 2026-01-13T09:29:25 |
https://docs.aws.amazon.com/pt_br/AmazonCloudWatch/latest/monitoring/Solution-NVIDIA-GPU-On-EC2.html#Solution-NVIDIA-GPU-Agent-Config | Solução do CloudWatch: workload da GPU da NVIDIA no Amazon EC2 - Amazon CloudWatch Solução do CloudWatch: workload da GPU da NVIDIA no Amazon EC2 - Amazon CloudWatch Documentação Amazon CloudWatch Guia do usuário Requisitos Benefícios Configuração do agente do CloudWatch para esta solução Implantação do agente para a sua solução Criação do painel da solução com a GPU da NVIDIA Solução do CloudWatch: workload da GPU da NVIDIA no Amazon EC2 Esta solução auxilia na configuração da coleta de métricas prontas para uso com agentes do CloudWatch para workloads da GPU da NVIDIA que estão sendo executadas em instâncias do EC2. Além disso, a solução ajuda na configuração de um painel do CloudWatch configurado previamente. Para obter informações gerais sobre todas as soluções de observabilidade do CloudWatch, consulte Soluções de observabilidade do CloudWatch . Tópicos Requisitos Benefícios Configuração do agente do CloudWatch para esta solução Implantação do agente para a sua solução Criação do painel da solução com a GPU da NVIDIA Requisitos Esta solução é aplicável nas seguintes condições: Computação: Amazon EC2 Fornecimento de suporte para até 500 GPUs em todas as instâncias do EC2 em uma Região da AWS específica Versão mais recente do agente do CloudWatch SSM Agent instalado na instância do EC2 A instância do EC2 deve ter um driver da NVIDIA instalado. Os drivers da NVIDIA são instalados previamente em algumas imagens de máquina da Amazon (AMIs). Caso contrário, é possível instalar o driver manualmente. Para obter mais informações, consulte Instalação de drivers NVIDIA em instâncias Linux . nota O AWS Systems Manager (SSM Agent) está instalado previamente em algumas imagens de máquinas da Amazon (AMIs) fornecidas pela AWS e por entidades externas confiáveis. Se o agente não estiver instalado, você poderá instalá-lo manualmente usando o procedimento adequado para o seu tipo de sistema operacional. Instalar e desinstalar o SSM Agent manualmente em instâncias do EC2 para Linux Instalar e desinstalar o SSM Agent manualmente em instâncias do EC2 para macOS Instalar e desinstalar o SSM Agent manualmente em instâncias do EC2 para Windows Server Benefícios A solução disponibiliza monitoramento da NVIDIA, fornecendo insights valiosos para os seguintes casos de uso: Análise do uso da GPU e da memória para identificar gargalos de performance ou a necessidade de obtenção de recursos adicionais. Monitoramento da temperatura e do consumo de energia para garantir que as GPUs operem dentro dos limites seguros. Avaliação da performance do codificador para workloads de vídeo na GPU. Verificação da conectividade PCIe para garantir que atendam à geração e à largura esperadas. Monitoramento das velocidades do relógio da GPU para identificar problemas de ajuste de escala ou de controle de utilização. A seguir, apresentamos as principais vantagens da solução: Automatiza a coleta de métricas para a NVIDIA usando a configuração do agente do CloudWatch, o que elimina a necessidade de instrumentação manual. Fornece um painel do CloudWatch consolidado e configurado previamente para as métricas da NVIDIA. O painel gerenciará automaticamente as métricas das novas instâncias do EC2 para a NVIDIA que foram configuradas usando a solução, mesmo que essas métricas não estejam disponíveis no momento de criação do painel. A imagem apresentada a seguir é um exemplo do painel para esta solução. Custos Esta solução cria e usa recursos em sua conta. A cobrança será realizada com base no uso padrão, que inclui o seguinte: Todas as métricas coletadas pelo agente do CloudWatch são cobradas como métricas personalizadas. O número de métricas usadas por esta solução depende do número de hosts do EC2. Cada host do EC2 configurado para a solução publica um total de 17 métricas por GPU. Um painel personalizado. As operações da API solicitadas pelo agente do CloudWatch para publicar as métricas. Com a configuração padrão para esta solução, o agente do CloudWatch chama a operação PutMetricData uma vez por minuto para cada host do EC2. Isso significa que a API PutMetricData será chamada 30*24*60=43,200 em um mês com 30 dias para cada host do EC2. Para obter mais informações sobre os preços do CloudWatch, consulte Preço do Amazon CloudWatch . A calculadora de preços pode ajudar a estimar os custos mensais aproximados para o uso desta solução. Como usar a calculadora de preços para estimar os custos mensais da solução Abra a calculadora de preços do Amazon CloudWatch . Em Escolher uma região , selecione a região em que você gostaria de implantar a solução. Na seção Métricas , em Número de métricas , insira 17 * average number of GPUs per EC2 host * number of EC2 instances configured for this solution . Na seção APIs , em Número de solicitações de API , insira 43200 * number of EC2 instances configured for this solution . Por padrão, o agente do CloudWatch executa uma operação PutMetricData a cada minuto para cada host do EC2. Na seção Painéis e alarmes , em Número de painéis , insira 1 . É possível visualizar os custos mensais estimados na parte inferior da calculadora de preços. Configuração do agente do CloudWatch para esta solução O agente do CloudWatch é um software que opera de maneira contínua e autônoma em seus servidores e em ambientes com contêineres. Ele coleta métricas, logs e rastreamentos da infraestrutura e das aplicações e os envia para o CloudWatch e para o X-Ray. Para obter mais informações sobre o agente do CloudWatch, consulte Coleta de métricas, logs e rastreamentos usando o agente do CloudWatch . Nesta solução, a configuração do agente coleta um conjunto de métricas para ajudar você a começar a monitorar e realizar a observabilidade da GPU da NVIDIA. O agente do CloudWatch pode ser configurado para coletar mais métricas da GPU da NVIDIA do que as que são exibidas por padrão no painel. Para obter uma lista de todas as métricas da GPU da NVIDIA que você pode coletar, consulte Colete métricas de GPU NVIDIA . Configuração do agente para esta solução As métricas coletadas pelo agente são definidas na configuração do agente. A solução fornece configurações do agente para a coleta das métricas recomendadas com dimensões adequadas para o painel da solução. Use a configuração do agente do CloudWatch apresentada a seguir em instâncias do EC2 equipadas com GPUs da NVIDIA. A configuração será armazenada como um parâmetro no Parameter Store do SSM, conforme detalhado posteriormente em Etapa 2: armazenar o arquivo de configuração recomendado do agente do CloudWatch no Systems Manager Parameter Store . { "metrics": { "namespace": "CWAgent", "append_dimensions": { "InstanceId": "$ { aws:InstanceId}" }, "metrics_collected": { "nvidia_gpu": { "measurement": [ "utilization_gpu", "temperature_gpu", "power_draw", "utilization_memory", "fan_speed", "memory_total", "memory_used", "memory_free", "pcie_link_gen_current", "pcie_link_width_current", "encoder_stats_session_count", "encoder_stats_average_fps", "encoder_stats_average_latency", "clocks_current_graphics", "clocks_current_sm", "clocks_current_memory", "clocks_current_video" ], "metrics_collection_interval": 60 } } }, "force_flush_interval": 60 } Implantação do agente para a sua solução Existem várias abordagens para instalar o agente do CloudWatch, dependendo do caso de uso. Recomendamos o uso do Systems Manager para esta solução. Ele fornece uma experiência no console e simplifica o gerenciamento de uma frota de servidores gerenciados em uma única conta da AWS. As instruções apresentadas nesta seção usam o Systems Manager e são destinadas para situações em que o agente do CloudWatch não está em execução com as configurações existentes. É possível verificar se o agente do CloudWatch está em execução ao seguir as etapas apresentadas em Verificar se o atendente do CloudWatch está em execução . Se você já estiver executando o agente do CloudWatch nos hosts do EC2 nos quais a workload está implantada e gerenciando as configurações do agente, pode pular as instruções apresentadas nesta seção e usar o mecanismo de implantação existente para atualizar a configuração. Certifique-se de combinar a configuração do agente da GPU da NVIDIA com a configuração do agente existente e, em seguida, implante a configuração combinada. Se você estiver usando o Systems Manager para armazenar e gerenciar a configuração do agente do CloudWatch, poderá combinar a configuração com o valor do parâmetro existente. Para obter mais informações, consulte Managing CloudWatch agent configuration files . nota Ao usar o Systems Manager para implantar as configurações do agente do CloudWatch apresentadas a seguir, qualquer configuração existente do agente do CloudWatch nas suas instâncias do EC2 será substituída ou sobrescrita. É possível modificar essa configuração para atender às necessidades do ambiente ou do caso de uso específico. As métricas definidas na configuração representam o requisito mínimo necessário para o painel fornecido pela solução. O processo de implantação inclui as seguintes etapas: Etapa 1: garantir que as instâncias do EC2 de destino têm as permissões do IAM necessárias. Etapa 2: armazenar o arquivo de configuração recomendado do agente no Systems Manager Parameter Store. Etapa 3: instalar o agente do CloudWatch em uma ou mais instâncias do EC2 usando uma pilha do CloudFormation. Etapa 4: verificar se a configuração do agente foi realizada corretamente. Etapa 1: garantir que as instâncias do EC2 de destino têm as permissões do IAM necessárias Você deve conceder permissão para o Systems Manager instalar e configurar o agente do CloudWatch. Além disso, é necessário conceder permissão para que o agente do CloudWatch publique a telemetria da instância do EC2 para o CloudWatch. Certifique-se de que o perfil do IAM anexado à instância tenha as políticas do IAM CloudWatchAgentServerPolicy e AmazonSSMManagedInstanceCore associadas. Após criar o perfil, associe-o às suas instâncias do EC2. Para anexar um perfil a uma instância do EC2, siga as etapas apresentadas em Attach an IAM role to an instance . Etapa 2: armazenar o arquivo de configuração recomendado do agente do CloudWatch no Systems Manager Parameter Store O Parameter Store simplifica a instalação do agente do CloudWatch em uma instância do EC2 ao armazenar e gerenciar os parâmetros de configuração de forma segura, eliminando a necessidade de valores com codificação rígida. Isso garante um processo de implantação mais seguro e flexível ao possibilitar o gerenciamento centralizado e as atualizações simplificadas para as configurações em diversas instâncias. Use as etapas apresentadas a seguir para armazenar o arquivo de configuração recomendado do agente do CloudWatch como um parâmetro no Parameter Store. Como criar o arquivo de configuração do agente do CloudWatch como um parâmetro Abra o console AWS Systems Manager em https://console.aws.amazon.com/systems-manager/ . Verifique se a região selecionada no console corresponde à região em que a workload da GPU da NVIDIA está em execução. No painel de navegação, escolha Gerenciamento de aplicações e, em seguida, Parameter Store . Siga as etapas apresentadas a seguir para criar um novo parâmetro para a configuração. Escolha Criar Parâmetro . Na caixa Nome , insira um nome que será usado para referenciar o arquivo de configuração do agente do CloudWatch nas etapas posteriores. Por exemplo, . AmazonCloudWatch-NVIDIA-GPU-Configuration (Opcional) Na caixa Descrição , digite uma descrição para o parâmetro. Em Camadas de parâmetros , escolha Padrão . Para Tipo , escolha String . Em Tipo de dados , selecione texto . Na caixa Valor , cole o bloco em JSON correspondente que foi listado em Configuração do agente para esta solução . Escolha Criar Parâmetro . Etapa 3: instalar o agente do CloudWatch e aplicar a configuração usando um modelo do CloudFormation É possível usar o AWS CloudFormation para instalar o agente e configurá-lo para usar a configuração do agente do CloudWatch criada nas etapas anteriores. Como instalar e configurar o agente do CloudWatch para esta solução Abra o assistente para criar pilha de forma rápida do CloudFormation usando este link: https://console.aws.amazon.com/cloudformation/home?#/stacks/quickcreate?templateURL=https://aws-observability-solutions-prod-us-east-1.s3.us-east-1.amazonaws.com/CloudWatchAgent/CFN/v1.0.0/cw-agent-installation-template-1.0.0.json . Verifique se a região selecionada no console corresponde à região em que a workload da GPU da NVIDIA está em execução. Em Nome da pilha , insira um nome para identificar esta pilha, como CWAgentInstallationStack . Na seção Parâmetros , especifique o seguinte: Para CloudWatchAgentConfigSSM , insira o nome do parâmetro do Systems Manager para a configuração do agente que você criou anteriormente, como AmazonCloudWatch-NVIDIA-GPU-Configuration . Para selecionar as instâncias de destino, você tem duas opções. Para InstanceIds , especifique uma lista delimitada por vírgulas de IDs de instâncias nas quais você deseja instalar o agente do CloudWatch com esta configuração. É possível listar uma única instância ou várias instâncias. Se você estiver realizando implantações em grande escala, é possível especificar a TagKey e o TagValue correspondente para direcionar todas as instâncias do EC2 associadas a essa etiqueta e a esse valor. Se você especificar uma TagKey , é necessário especificar um TagValue correspondente. (Para um grupo do Auto Scaling, especifique aws:autoscaling:groupName para a TagKey e defina o nome do grupo do Auto Scaling para a TagValue para realizar a implantação em todas as instâncias do grupo do Auto Scaling.) Analise as configurações e, em seguida, escolha Criar pilha . Se você desejar editar o arquivo de modelo previamente para personalizá-lo, selecione a opção Fazer upload de um arquivo de modelo no Assistente de criação de pilha para fazer o upload do modelo editado. Para obter mais informações, consulte Criar uma pilha no console do CloudFormation . nota Após a conclusão desta etapa, este parâmetro do Systems Manager será associado aos agentes do CloudWatch em execução nas instâncias de destino. Isto significa que: Se o parâmetro do Systems Manager for excluído, o agente será interrompido. Se o parâmetro do Systems Manager for editado, as alterações de configuração serão aplicadas automaticamente ao agente na frequência programada, que, por padrão, é de 30 dias. Se você desejar aplicar imediatamente as alterações a este parâmetro do Systems Manager, você deverá executar esta etapa novamente. Para obter mais informações sobre as associações, consulte Working with associations in Systems Manager . Etapa 4: verificar se a configuração do agente foi realizada corretamente É possível verificar se o agente do CloudWatch está instalado ao seguir as etapas apresentadas em Verificar se o atendente do CloudWatch está em execução . Se o agente do CloudWatch não estiver instalado e em execução, certifique-se de que todas as configurações foram realizadas corretamente. Certifique-se de ter anexado um perfil com as permissões adequadas para a instância do EC2, conforme descrito na Etapa 1: garantir que as instâncias do EC2 de destino têm as permissões do IAM necessárias . Certifique-se de ter configurado corretamente o JSON para o parâmetro do Systems Manager. Siga as etapas em Solução de problemas de instalação do atendente do CloudWatch com o CloudFormation . Se todas as configurações estiverem corretas, as métricas da GPU da NVIDIA serão publicadas no CloudWatch e estarão disponíveis para visualização. É possível verificar no console do CloudWatch para assegurar que as métricas estão sendo publicadas corretamente. Como verificar se as métricas da GPU da NVIDIA estão sendo publicadas no CloudWatch Abra o console do CloudWatch, em https://console.aws.amazon.com/cloudwatch/ . Escolha Métricas e, depois, Todas as métricas . Certifique-se de ter selecionado a região na qual a solução foi implantada, escolha Namespaces personalizados e, em seguida, selecione CWAgent . Pesquise pelas métricas mencionadas em Configuração do agente para esta solução , como nvidia_smi_utilization_gpu . Caso encontre resultados para essas métricas, isso significa que elas estão sendo publicadas no CloudWatch. Criação do painel da solução com a GPU da NVIDIA O painel fornecido por esta solução apresenta métricas das GPUs da NVIDIA ao agregar e apresentar as métricas em todas as instâncias. O painel mostra um detalhamento dos principais colaboradores (que corresponde aos dez principais por widget de métrica) para cada métrica. Isso ajuda a identificar rapidamente discrepâncias ou instâncias que contribuem significativamente para as métricas observadas. Para criar o painel, é possível usar as seguintes opções: Usar o console do CloudWatch para criar o painel. Usar o console do AWS CloudFormation para implantar o painel. Fazer o download do código de infraestrutura como código do AWS CloudFormation e integrá-lo como parte da automação de integração contínua (CI). Ao usar o console do CloudWatch para criar um painel, é possível visualizá-lo previamente antes de criá-lo e incorrer em custos. nota O painel criado com o CloudFormation nesta solução exibe métricas da região em que a solução está implantada. Certifique-se de que a pilha do CloudFormation seja criada na mesma região em que as métricas da GPU da NVIDIA são publicadas. Se você especificou um namespace personalizado diferente de CWAgent na configuração do agente do CloudWatch, será necessário alterar o modelo do CloudFormation para o painel, substituindo CWAgent pelo namespace personalizado que você está usando. Como criar o painel usando o console do CloudWatch Abra o console do CloudWatch e acesse Criar painel usando este link: https://console.aws.amazon.com/cloudwatch/home?#dashboards?dashboardTemplate=NvidiaGpuOnEc2&referrer=os-catalog . Verifique se a região selecionada no console corresponde à região em que a workload da GPU da NVIDIA está em execução. Insira o nome do painel e, em seguida, escolha Criar painel . Para diferenciar este painel de painéis semelhantes em outras regiões com facilidade, recomendamos incluir o nome da região no nome do painel, por exemplo, NVIDIA-GPU-Dashboard-us-east-1 . Visualize previamente o painel e escolha Salvar para criá-lo. Como criar o painel usando o CloudFormation Abra o assistente para criar pilha de forma rápida do CloudFormation usando este link: https://console.aws.amazon.com/cloudformation/home?#/stacks/quickcreate?templateURL=https://aws-observability-solutions-prod-us-east-1.s3.us-east-1.amazonaws.com/NVIDIA_GPU_EC2/CloudWatch/CFN/v1.0.0/dashboard-template-1.0.0.json . Verifique se a região selecionada no console corresponde à região em que a workload da GPU da NVIDIA está em execução. Em Nome da pilha , insira um nome para identificar esta pilha, como NVIDIA-GPU-DashboardStack . Na seção Parâmetros , especifique o nome do painel no parâmetro DashboardName . Para diferenciar este painel de painéis semelhantes em outras regiões com facilidade, recomendamos incluir o nome da região no nome do painel, por exemplo, NVIDIA-GPU-Dashboard-us-east-1 . Confirme as funcionalidades de acesso relacionadas às transformações na seção Capacidades e transformações . Lembre-se de que o CloudFormation não adiciona recursos do IAM. Analise as configurações e, em seguida, escolha Criar pilha . Quando o status da pilha mostrar CREATE_COMPLETE , selecione a guia Recursos na pilha criada e, em seguida, escolha o link exibido em ID físico para acessar o painel. Como alternativa, é possível acessar o painel diretamente no console do CloudWatch ao selecionar Painéis no painel de navegação do console à esquerda e localizar o nome do painel na seção Painéis personalizados . Se você desejar editar o arquivo de modelo para personalizá-lo para atender a uma necessidade específica, é possível usar a opção Fazer upload de um arquivo de modelo no Assistente de criação de pilha para fazer o upload do modelo editado. Para obter mais informações, consulte Criar uma pilha no console do CloudFormation . É possível usar este link para fazer download do modelo: https://aws-observability-solutions-prod-us-east-1.s3.us-east-1.amazonaws.com/NVIDIA_GPU_EC2/CloudWatch/CFN/v1.0.0/dashboard-template-1.0.0.json . Como começar a usar o painel da GPU da NVIDIA A seguir, apresentamos algumas tarefas que você pode realizar para explorar o novo painel da GPU da NVIDIA. Essas tarefas permitem a validação do funcionamento correto do painel e fornecem uma experiência prática ao usá-lo para monitorar as GPUs da NVIDIA. À medida que realiza as tarefas, você se familiarizará com a navegação no painel e com a interpretação das métricas visualizadas. Análise da utilização da GPU Na seção Utilização , localize os widgets de Utilização da GPU e Utilização da memória . Eles mostram, respectivamente, a porcentagem de tempo em que a GPU está sendo ativamente usada para cálculos e a porcentagem de uso da memória global para leitura ou gravação. Uma utilização elevada pode indicar possíveis gargalos de performance ou a necessidade de obtenção de recursos adicionais de GPU. Análise do uso de memória da GPU Na seção Memória , localize os widgets Memória total , Memória usada e Memória livre . Esses widgets fornecem insights sobre a capacidade total de memória das GPUs, além de indicar a quantidade de memória que, no momento, está sendo consumida ou disponível. A pressão de memória pode acarretar em problemas de performance ou erros por falta de memória, portanto, é fundamental monitorar essas métricas e garantir que a workload tenha memória suficiente disponível. Monitoramento da temperatura e do consumo de energia Na seção Temperatura/Potência , localize os widgets de Temperatura da CPU e Consumo de energia . Essas métricas são essenciais para garantir que as GPUs estejam operando dentro dos limites seguros de temperatura e consumo de energia. Identificação da performance do codificador Na seção Codificador , localize os widgets de Contagem de sessões do codificador , Média de FPS e Latência média . Essas métricas são relevantes se você estiver executando workloads de codificação de vídeo em suas GPUs. O monitoramento dessas métricas é fundamental para garantir a operação ideal dos codificadores e identificar possíveis gargalos ou problemas de performance. Verificação do status do link do PCIe Na seção PCIe , localize os widgets de Geração do link do PCIe e de Largura do link do PCIe . Essas métricas fornecem informações sobre o link do PCIe que estabelece conexão entre a GPU e o sistema de host. Certifique-se de que o link esteja operando com a geração e a largura esperadas para evitar possíveis limitações de performance causadas por gargalos do PCIe. Análise dos relógios da GPU Na seção Relógio , localize os widgets de Relógio de gráficos , Relógio de SM , Relógio de memória e Relógio de vídeo . Essas métricas apresentam as frequências operacionais atuais dos diversos componentes da GPU. O monitoramento desses relógios pode ajudar a identificar possíveis problemas com o ajuste de escala ou com o controle de utilização do relógio da GPU, que podem impactar a performance. O Javascript está desativado ou não está disponível no seu navegador. Para usar a documentação da AWS, o Javascript deve estar ativado. Consulte as páginas de Ajuda do navegador para obter instruções. Convenções do documento Workload do NGINX no EC2 Workload do Kafka no EC2 Essa página foi útil? - Sim Obrigado por nos informar que estamos fazendo um bom trabalho! Se tiver tempo, conte-nos sobre o que você gostou para que possamos melhorar ainda mais. Essa página foi útil? - Não Obrigado por nos informar que precisamos melhorar a página. Lamentamos ter decepcionado você. Se tiver tempo, conte-nos como podemos melhorar a documentação. | 2026-01-13T09:29:25 |
https://www.linkedin.com/uas/login?session_redirect=%2Fproducts%2Ftechnarts-numerus&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:25 |
https://git-scm.com/book/cs/v2/GitHub-Shrnut%c3%ad | Git - Shrnutí 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. Úvod 1.1 Správa verzí 1.2 Stručná historie systému Git 1.3 Základy systému Git 1.4 Příkazový řádek 1.5 Instalace systému Git 1.6 První nastavení systému Git 1.7 Získání nápovědy 1.8 Shrnutí 2. Základy práce se systémem Git 2.1 Získání repozitáře Git 2.2 Nahrávání změn do repozitáře 2.3 Zobrazení historie revizí 2.4 Návrat do předchozího stavu 2.5 Práce se vzdálenými repozitáři 2.6 Používání značek 2.7 Aliasy v Gitu 2.8 Shrnutí 3. Větve v systému Git 3.1 Větve v kostce 3.2 Základy větvení a slučování 3.3 Správa větví 3.4 Postupy při práci s větvemi 3.5 Vzdálené větve 3.6 Přeskládání 3.7 Shrnutí 4. Git na serveru 4.1 Protokoly 4.2 Zprovoznění Gitu na serveru 4.3 Generování veřejného klíče SSH 4.4 Nastavení serveru 4.5 Démon Git 4.6 Chytrý HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti hostování u třetí strany 4.10 Shrnutí 5. Distribuovaný Git 5.1 Distribuované pracovní postupy 5.2 Přispívání do projektu 5.3 Správa projektu 5.4 Shrnutí 6. GitHub 6.1 Zřízení účtu a úprava konfigurace 6.2 Přispívání do projektu 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Shrnutí 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 Ladění v systému Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Shrnutí 8. Customizing Git 8.1 Git Configuration 8.2 Atributy Git 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Shrnutí 9. Git a ostatní systémy 9.1 Git as a Client 9.2 Migrating to Git 9.3 Shrnutí 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Balíčkové soubory 10.5 The Refspec 10.6 Přenosové protokoly 10.7 Správa a obnova dat 10.8 Environment Variables 10.9 Shrnutí 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 Shrnutí 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 6.6 GitHub - Shrnutí Shrnutí Teď už jste uživatelem GitHubu. Umíte vytvořit účet, spravovat organizaci, vytvářet repozitáře a odesílat do nich (push), přispívat do projektů jiných lidí a přijímat příspěvky od ostatních. V další kapitole se naučíte používat mocnější nástroje a naleznete v ní tipy pro zvládnutí složitějších situací, což z vás udělá mistra Gitu. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:25 |
https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/LogsAnomalyDetection.html | Log anomaly detection - Amazon CloudWatch Logs Log anomaly detection - Amazon CloudWatch Logs Documentation Amazon CloudWatch User Guide Severity and priority of anomalies and patterns Anomaly visibility time Suppressing an anomaly Frequently asked questions Log anomaly detection You can detect anomalies in your log data in two ways: by creating a log anomaly detector for continuous monitoring, or by using the anomaly detection command in CloudWatch Logs Insights queries for on-demand analysis. A log anomaly detector scans the log events ingested into a log group and finds anomalies in the log data automatically. Anomaly detection uses machine-learning and pattern recognition to establish baselines of typical log content. For on-demand analysis, you can use the anomaly detection command in CloudWatch Logs Insights queries to identify unusual patterns in time-series data. For more information about query-based anomaly detection, see Using anomaly detection in CloudWatch Logs Insights . After you create an anomaly detector for a log group, it trains using the past two weeks of log events in the log group for training. The training period can take up to 15 minutes. After the training is complete, it begins to analyze incoming logs to identify anomalies, and the anomalies are displayed in the CloudWatch Logs console for you to examine. CloudWatch Logs pattern recognition extracts log patterns by identifying static and dynamic content in your logs. Patterns are useful for analyzing large log sets because a large number of log events can often be compressed into a few patterns. For example, see the following sample of three log events. 2023-01-01 19:00:01 [INFO] Calling DynamoDB to store for ResourceID: 12342342k124-12345 2023-01-01 19:00:02 [INFO] Calling DynamoDB to store for ResourceID: 324892398123-1234R 2023-01-01 19:00:03 [INFO] Calling DynamoDB to store for ResourceID: 3ff231242342-12345 In the previous sample, all three log events follow one pattern: <Date-1> <Time-2> [INFO] Calling DynamoDB to store for resource id <ResourceID-3> Fields within a pattern are called tokens . Fields that vary within a pattern, such as a request ID or timestamp, are referred to as dynamic tokens . Each different value found for a dynamic token is called a token value . If CloudWatch Logs can infer the type of data that a dynamic token represents, it displays the token as < string - number > . The string is a description of the type of data that the token represents. The number shows where in the pattern this token appears, compared to the other dynamic tokens. CloudWatch Logs assigns the string part of the name based on analyzing the content of the log events that contain it. If CloudWatch Logs can't infer the type of data that a dynamic token represents, it displays the token as <Token- number >, and number indicates where in the pattern this token appears, compared to the other dynamic tokens. Common examples of dynamic tokens include error codes, IP addresses, timestamps, and request IDs. Logs anomaly detection uses these patterns to find anomalies. After the anomaly detector model training period, logs are evaluated against known trends. The anomaly detector flags significant fluctuations as anomalies. This chapter describes how to enable anomaly detection, view anomalies, create alarms for log anomaly detectors, and metrics that log anomaly detectors publish. It also describes how to encrypt anomaly detector and its results with AWS Key Management Service. Creating log anomaly detectors doesn't incur charges. Severity and priority of anomalies and patterns Each anomaly found by a log anomaly detector is assigned a priority . Each pattern found is assigned a severity . Priority is automatically computed, and is based on both the severity level of the pattern and the amount of deviation from expected values. For example, if a certain token value suddenly increases by 500%, that anomaly might be designated as HIGH priority even if its severity is NONE . Severity is based only on keywords found in the patterns such as FATAL , ERROR , and WARN . If none of these keywords are found, the severity of a pattern is marked as NONE . Anomaly visibility time When you create an anomaly detector, you specify the maximum anomaly visibility period for it. This is the number of days that the anomaly is displayed in the console and is returned by the ListAnomalies API operation. After this time period has elapsed for an anomaly, if it continues to happen, it's automatically accepted as regular behavior and the anomaly detector model stops flagging it as an anomaly. If you don't adjust the visibility time when you create an anomaly detector, 21 days is used as the default. Suppressing an anomaly After an anomaly has been found, you can choose to suppress it temporarily or permanently. Suppressing an anomaly causes the anomaly detector to stop flagging this occurrence as an anomaly for the amount of time that you specify. When you suppress an anomaly, you can choose to suppress only that specific anomaly, or suppress all anomalies related to the pattern that the anomaly was found in. You can still view suppressed anomalies in the console. You can also choose to stop suppressing them. Frequently asked questions Does AWS use my data to train machine-learning algorithms for AWS use or for other customers? No. The anomaly detection model created by the training is based on the log events in a log group and is used only within that log group and that AWS account. What types of log events work well with anomaly detection? Log anomaly detection is well-suited for: Application logs and other types of logs where most log entries fit typical patterns. Log groups with events that contain a log level or severity keywords such as INFO , ERROR , and DEBUG are especially well-suited to log anomaly detection. Log anomaly detection is not suited for: Log events with extremely long JSON structures, such as CloudTrail Logs. Pattern analysis analyzes only up to the first 1500 characters of a log line, so any characters beyond that limit are skipped. Audit or access logs, such as VPC flow logs, will also have less success with anomaly detection. Anomaly detection is meant to find application issues, so it might not be well-suited for network or access anomalies. To help you determine whether an anomaly detector is suited to a certain log group, use CloudWatch Logs pattern analysis to find the number of patterns in the log events in the group. If the number of patterns is no more than about 300, anomaly detection might work well. For more information about pattern analysis, see Pattern analysis . What gets flagged as an anomaly? The following occurrences can cause a log event to be flagged as an anomaly: A log event with a pattern not seen before in the log group. A significant variation to a known pattern. A new value for a dynamic token that has a discrete set of usual values. A large change in the number of occurrences of a value for a dynamic token. While all the preceding items might be flagged as anomalies, they don't all mean that the application is performing poorly. For example, a higher-than-usual number of 200 success values might be flagged as an anomaly. In cases like this, you might consider suppressing these anomalies that don't indicate problems. What happens with sensitive data that is being masked? Any parts of log events that are masked as sensitive data are not scanned for anomalies. For more information about masking sensitive data, see Help protect sensitive log data with masking . Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Troubleshooting scheduled queries Using anomaly detection in CloudWatch Logs Insights Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:29:25 |
https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/LogsAnomalyDetection.html | Log anomaly detection - Amazon CloudWatch Logs Log anomaly detection - Amazon CloudWatch Logs Documentation Amazon CloudWatch User Guide Severity and priority of anomalies and patterns Anomaly visibility time Suppressing an anomaly Frequently asked questions Log anomaly detection You can detect anomalies in your log data in two ways: by creating a log anomaly detector for continuous monitoring, or by using the anomaly detection command in CloudWatch Logs Insights queries for on-demand analysis. A log anomaly detector scans the log events ingested into a log group and finds anomalies in the log data automatically. Anomaly detection uses machine-learning and pattern recognition to establish baselines of typical log content. For on-demand analysis, you can use the anomaly detection command in CloudWatch Logs Insights queries to identify unusual patterns in time-series data. For more information about query-based anomaly detection, see Using anomaly detection in CloudWatch Logs Insights . After you create an anomaly detector for a log group, it trains using the past two weeks of log events in the log group for training. The training period can take up to 15 minutes. After the training is complete, it begins to analyze incoming logs to identify anomalies, and the anomalies are displayed in the CloudWatch Logs console for you to examine. CloudWatch Logs pattern recognition extracts log patterns by identifying static and dynamic content in your logs. Patterns are useful for analyzing large log sets because a large number of log events can often be compressed into a few patterns. For example, see the following sample of three log events. 2023-01-01 19:00:01 [INFO] Calling DynamoDB to store for ResourceID: 12342342k124-12345 2023-01-01 19:00:02 [INFO] Calling DynamoDB to store for ResourceID: 324892398123-1234R 2023-01-01 19:00:03 [INFO] Calling DynamoDB to store for ResourceID: 3ff231242342-12345 In the previous sample, all three log events follow one pattern: <Date-1> <Time-2> [INFO] Calling DynamoDB to store for resource id <ResourceID-3> Fields within a pattern are called tokens . Fields that vary within a pattern, such as a request ID or timestamp, are referred to as dynamic tokens . Each different value found for a dynamic token is called a token value . If CloudWatch Logs can infer the type of data that a dynamic token represents, it displays the token as < string - number > . The string is a description of the type of data that the token represents. The number shows where in the pattern this token appears, compared to the other dynamic tokens. CloudWatch Logs assigns the string part of the name based on analyzing the content of the log events that contain it. If CloudWatch Logs can't infer the type of data that a dynamic token represents, it displays the token as <Token- number >, and number indicates where in the pattern this token appears, compared to the other dynamic tokens. Common examples of dynamic tokens include error codes, IP addresses, timestamps, and request IDs. Logs anomaly detection uses these patterns to find anomalies. After the anomaly detector model training period, logs are evaluated against known trends. The anomaly detector flags significant fluctuations as anomalies. This chapter describes how to enable anomaly detection, view anomalies, create alarms for log anomaly detectors, and metrics that log anomaly detectors publish. It also describes how to encrypt anomaly detector and its results with AWS Key Management Service. Creating log anomaly detectors doesn't incur charges. Severity and priority of anomalies and patterns Each anomaly found by a log anomaly detector is assigned a priority . Each pattern found is assigned a severity . Priority is automatically computed, and is based on both the severity level of the pattern and the amount of deviation from expected values. For example, if a certain token value suddenly increases by 500%, that anomaly might be designated as HIGH priority even if its severity is NONE . Severity is based only on keywords found in the patterns such as FATAL , ERROR , and WARN . If none of these keywords are found, the severity of a pattern is marked as NONE . Anomaly visibility time When you create an anomaly detector, you specify the maximum anomaly visibility period for it. This is the number of days that the anomaly is displayed in the console and is returned by the ListAnomalies API operation. After this time period has elapsed for an anomaly, if it continues to happen, it's automatically accepted as regular behavior and the anomaly detector model stops flagging it as an anomaly. If you don't adjust the visibility time when you create an anomaly detector, 21 days is used as the default. Suppressing an anomaly After an anomaly has been found, you can choose to suppress it temporarily or permanently. Suppressing an anomaly causes the anomaly detector to stop flagging this occurrence as an anomaly for the amount of time that you specify. When you suppress an anomaly, you can choose to suppress only that specific anomaly, or suppress all anomalies related to the pattern that the anomaly was found in. You can still view suppressed anomalies in the console. You can also choose to stop suppressing them. Frequently asked questions Does AWS use my data to train machine-learning algorithms for AWS use or for other customers? No. The anomaly detection model created by the training is based on the log events in a log group and is used only within that log group and that AWS account. What types of log events work well with anomaly detection? Log anomaly detection is well-suited for: Application logs and other types of logs where most log entries fit typical patterns. Log groups with events that contain a log level or severity keywords such as INFO , ERROR , and DEBUG are especially well-suited to log anomaly detection. Log anomaly detection is not suited for: Log events with extremely long JSON structures, such as CloudTrail Logs. Pattern analysis analyzes only up to the first 1500 characters of a log line, so any characters beyond that limit are skipped. Audit or access logs, such as VPC flow logs, will also have less success with anomaly detection. Anomaly detection is meant to find application issues, so it might not be well-suited for network or access anomalies. To help you determine whether an anomaly detector is suited to a certain log group, use CloudWatch Logs pattern analysis to find the number of patterns in the log events in the group. If the number of patterns is no more than about 300, anomaly detection might work well. For more information about pattern analysis, see Pattern analysis . What gets flagged as an anomaly? The following occurrences can cause a log event to be flagged as an anomaly: A log event with a pattern not seen before in the log group. A significant variation to a known pattern. A new value for a dynamic token that has a discrete set of usual values. A large change in the number of occurrences of a value for a dynamic token. While all the preceding items might be flagged as anomalies, they don't all mean that the application is performing poorly. For example, a higher-than-usual number of 200 success values might be flagged as an anomaly. In cases like this, you might consider suppressing these anomalies that don't indicate problems. What happens with sensitive data that is being masked? Any parts of log events that are masked as sensitive data are not scanned for anomalies. For more information about masking sensitive data, see Help protect sensitive log data with masking . Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Troubleshooting scheduled queries Using anomaly detection in CloudWatch Logs Insights Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:29:25 |
https://docs.aws.amazon.com/es_es/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-configure-related-telemetry.html | Configuración de los nombres de entorno y servicio del agente de CloudWatch para las entidades relacionadas - Amazon CloudWatch Configuración de los nombres de entorno y servicio del agente de CloudWatch para las entidades relacionadas - Amazon CloudWatch Documentación Amazon CloudWatch Guía del usuario Configuración de los nombres de entorno y servicio del agente de CloudWatch para las entidades relacionadas El agente de CloudWatch puede enviar métricas y registros con datos de entidades para admitir el panel Explorar lo relacionado en la consola de CloudWatch. El nombre del servicio o el nombre del entorno se pueden configurar mediante la configuración JSON del agente de CloudWatch . nota La configuración del agente puede anularse. Para obtener más información sobre la manera en que el agente decide qué datos enviar a las entidades relacionadas, consulte Uso del agente de CloudWatch con la telemetría relacionada . En cuanto a las métricas, se puede configurar en el nivel del agente, de las métricas o del complemento. En el caso de los registros, se puede configurar en el nivel del agente, de los registros o de los archivos. Siempre se utiliza la configuración más específica. Por ejemplo, si la configuración existe en el nivel del agente y de las métricas, las métricas utilizarán la configuración las métricas, y todo lo demás (registros) utilizará la configuración del agente. En el siguiente ejemplo, se muestran diferentes formas de configurar el nombre del servicio y el nombre del entorno. { "agent": { "service.name": "agent-level-service", "deployment.environment": "agent-level-environment" }, "metrics": { "service.name": "metric-level-service", "deployment.environment": "metric-level-environment", "metrics_collected": { "statsd": { "service.name": "statsd-level-service", "deployment.environment": "statsd-level-environment", }, "collectd": { "service.name": "collectdd-level-service", "deployment.environment": "collectd-level-environment", } } }, "logs": { "service.name": "log-level-service", "deployment.environment": "log-level-environment", "logs_collected": { "files": { "collect_list": [ { "file_path": "/opt/aws/amazon-cloudwatch-agent/logs/amazon-cloudwatch-agent.log", "log_group_name": "amazon-cloudwatch-agent.log", "log_stream_name": "amazon-cloudwatch-agent.log", "service.name": "file-level-service", "deployment.environment": "file-level-environment" } ] } } } } JavaScript está desactivado o no está disponible en su navegador. Para utilizar la documentación de AWS, debe estar habilitado JavaScript. Para obtener más información, consulte las páginas de ayuda de su navegador. Convenciones del documento Configuración de la recopilación de métricas de Prometheus en instancias de Amazon EC2 Inicie el agente de CloudWatch ¿Le ha servido de ayuda esta página? - Sí Gracias por hacernos saber que estamos haciendo un buen trabajo. Si tiene un momento, díganos qué es lo que le ha gustado para que podamos seguir trabajando en esa línea. ¿Le ha servido de ayuda esta página? - No Gracias por informarnos de que debemos trabajar en esta página. Lamentamos haberle defraudado. Si tiene un momento, díganos cómo podemos mejorar la documentación. | 2026-01-13T09:29:25 |
https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/LogsAnomalyDetection.html | Log anomaly detection - Amazon CloudWatch Logs Log anomaly detection - Amazon CloudWatch Logs Documentation Amazon CloudWatch User Guide Severity and priority of anomalies and patterns Anomaly visibility time Suppressing an anomaly Frequently asked questions Log anomaly detection You can detect anomalies in your log data in two ways: by creating a log anomaly detector for continuous monitoring, or by using the anomaly detection command in CloudWatch Logs Insights queries for on-demand analysis. A log anomaly detector scans the log events ingested into a log group and finds anomalies in the log data automatically. Anomaly detection uses machine-learning and pattern recognition to establish baselines of typical log content. For on-demand analysis, you can use the anomaly detection command in CloudWatch Logs Insights queries to identify unusual patterns in time-series data. For more information about query-based anomaly detection, see Using anomaly detection in CloudWatch Logs Insights . After you create an anomaly detector for a log group, it trains using the past two weeks of log events in the log group for training. The training period can take up to 15 minutes. After the training is complete, it begins to analyze incoming logs to identify anomalies, and the anomalies are displayed in the CloudWatch Logs console for you to examine. CloudWatch Logs pattern recognition extracts log patterns by identifying static and dynamic content in your logs. Patterns are useful for analyzing large log sets because a large number of log events can often be compressed into a few patterns. For example, see the following sample of three log events. 2023-01-01 19:00:01 [INFO] Calling DynamoDB to store for ResourceID: 12342342k124-12345 2023-01-01 19:00:02 [INFO] Calling DynamoDB to store for ResourceID: 324892398123-1234R 2023-01-01 19:00:03 [INFO] Calling DynamoDB to store for ResourceID: 3ff231242342-12345 In the previous sample, all three log events follow one pattern: <Date-1> <Time-2> [INFO] Calling DynamoDB to store for resource id <ResourceID-3> Fields within a pattern are called tokens . Fields that vary within a pattern, such as a request ID or timestamp, are referred to as dynamic tokens . Each different value found for a dynamic token is called a token value . If CloudWatch Logs can infer the type of data that a dynamic token represents, it displays the token as < string - number > . The string is a description of the type of data that the token represents. The number shows where in the pattern this token appears, compared to the other dynamic tokens. CloudWatch Logs assigns the string part of the name based on analyzing the content of the log events that contain it. If CloudWatch Logs can't infer the type of data that a dynamic token represents, it displays the token as <Token- number >, and number indicates where in the pattern this token appears, compared to the other dynamic tokens. Common examples of dynamic tokens include error codes, IP addresses, timestamps, and request IDs. Logs anomaly detection uses these patterns to find anomalies. After the anomaly detector model training period, logs are evaluated against known trends. The anomaly detector flags significant fluctuations as anomalies. This chapter describes how to enable anomaly detection, view anomalies, create alarms for log anomaly detectors, and metrics that log anomaly detectors publish. It also describes how to encrypt anomaly detector and its results with AWS Key Management Service. Creating log anomaly detectors doesn't incur charges. Severity and priority of anomalies and patterns Each anomaly found by a log anomaly detector is assigned a priority . Each pattern found is assigned a severity . Priority is automatically computed, and is based on both the severity level of the pattern and the amount of deviation from expected values. For example, if a certain token value suddenly increases by 500%, that anomaly might be designated as HIGH priority even if its severity is NONE . Severity is based only on keywords found in the patterns such as FATAL , ERROR , and WARN . If none of these keywords are found, the severity of a pattern is marked as NONE . Anomaly visibility time When you create an anomaly detector, you specify the maximum anomaly visibility period for it. This is the number of days that the anomaly is displayed in the console and is returned by the ListAnomalies API operation. After this time period has elapsed for an anomaly, if it continues to happen, it's automatically accepted as regular behavior and the anomaly detector model stops flagging it as an anomaly. If you don't adjust the visibility time when you create an anomaly detector, 21 days is used as the default. Suppressing an anomaly After an anomaly has been found, you can choose to suppress it temporarily or permanently. Suppressing an anomaly causes the anomaly detector to stop flagging this occurrence as an anomaly for the amount of time that you specify. When you suppress an anomaly, you can choose to suppress only that specific anomaly, or suppress all anomalies related to the pattern that the anomaly was found in. You can still view suppressed anomalies in the console. You can also choose to stop suppressing them. Frequently asked questions Does AWS use my data to train machine-learning algorithms for AWS use or for other customers? No. The anomaly detection model created by the training is based on the log events in a log group and is used only within that log group and that AWS account. What types of log events work well with anomaly detection? Log anomaly detection is well-suited for: Application logs and other types of logs where most log entries fit typical patterns. Log groups with events that contain a log level or severity keywords such as INFO , ERROR , and DEBUG are especially well-suited to log anomaly detection. Log anomaly detection is not suited for: Log events with extremely long JSON structures, such as CloudTrail Logs. Pattern analysis analyzes only up to the first 1500 characters of a log line, so any characters beyond that limit are skipped. Audit or access logs, such as VPC flow logs, will also have less success with anomaly detection. Anomaly detection is meant to find application issues, so it might not be well-suited for network or access anomalies. To help you determine whether an anomaly detector is suited to a certain log group, use CloudWatch Logs pattern analysis to find the number of patterns in the log events in the group. If the number of patterns is no more than about 300, anomaly detection might work well. For more information about pattern analysis, see Pattern analysis . What gets flagged as an anomaly? The following occurrences can cause a log event to be flagged as an anomaly: A log event with a pattern not seen before in the log group. A significant variation to a known pattern. A new value for a dynamic token that has a discrete set of usual values. A large change in the number of occurrences of a value for a dynamic token. While all the preceding items might be flagged as anomalies, they don't all mean that the application is performing poorly. For example, a higher-than-usual number of 200 success values might be flagged as an anomaly. In cases like this, you might consider suppressing these anomalies that don't indicate problems. What happens with sensitive data that is being masked? Any parts of log events that are masked as sensitive data are not scanned for anomalies. For more information about masking sensitive data, see Help protect sensitive log data with masking . Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Troubleshooting scheduled queries Using anomaly detection in CloudWatch Logs Insights Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:29:25 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.