Building a central Go modules repository: GoCenter’s back to the future. @jfrog @ankushchadha111 GopherCon 2019 Lightning Talk Ankush Chadha About me • Dev Manager, Community & Partner Engineering

Starting Apache Karaf Cave Server 2. Repository 2.1. Create 2.2. List 2.3. Repository and OBR service 2.4. Destroy 2.5. What’s next 3. Populate repository 3.1. Upload a single artifact 3.2. Populate Populate from an external repository 4. Proxy repository 5. OBR commands 6. HTTP wrapper service 6.1. OBR metadata access 6.2. OSGi bundles access 7. Administration Overview Apache Karaf Cave is OSGi Bundle Repository (OBR) and Karaf Features Repository (KFR). OBR provides a service that can automatically install a bundle, with its deployment dependencies, from a bundle repository. Apache Karaf

Apache Karaf Cave Server 2. Repository 2.1. Create 2.2. List 3. Populate repository 3.1. Upload a single artifact 3.2. Populate from an external repository 4. Proxy repository 5. HTTP wrapper service service 5.1. Repository metadata access 6. Maven wrapper service 7. Administration 7.1. JMX 7.2. REST Overview Apache Karaf Cave is an Apache Karaf sub-project. Cave is an implementation of the OSGi OSGi Repository specification, providing additional features such as a complete Maven repository support, a REST API for management, support of remote repository proxy. Cave deals with the requirements

Summary Git Basics Getting a Git Repository Initializing a Repository in an Existing Directory Cloning an Existing Repository Recording Changes to the Repository Checking the Status of Your Files The HTTP Protocols The SSH Protocol The Git Protocol Getting Git on a Server Putting the Bare Repository on a Server Small Setups Generating Your SSH Public Key Setting Up the Server Git Daemon Smart Pull Requests GitHub Flavored Markdown Keep your GitHub public repository up-to-date Maintaining a Project Creating a New Repository Adding Collaborators Managing Pull Requests Mentions and Notifications

Summary Git Basics Getting a Git Repository Initializing a Repository in an Existing Directory Cloning an Existing Repository Recording Changes to the Repository Checking the Status of Your Files The HTTP Protocols The SSH Protocol The Git Protocol Getting Git on a Server Putting the Bare Repository on a Server Small Setups Generating Your SSH Public Key Setting Up the Server Git Daemon Smart Pull Requests GitHub Flavored Markdown Keep your GitHub public repository up-to-date Maintaining a Project Creating a New Repository Adding Collaborators Managing Pull Requests Mentions and Notifications

Getting a Git Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Recording Changes to the Repository . . . . of cases you’ll encounter most often. After reading this chapter, you should be able to clone a repository, see what has happened in the history of the project, modify files, and contribute changes. If clients don’t just check out the latest snapshot of the files; rather, they fully mirror the repository, including its full history. Thus, if any server dies, and these systems were collaborating via

formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot

formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot

formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot

formats and makes it easy for translators to contribute. The translations should be kept within same repository as source code and translation process should closely follow development. There is no plan in Weblate. Project Project information like instructions for translators or information about VCS repository. If translation format supports it, you can also follow links to source code which contains translated Component configuration for detailed description of the fields): Field Value Source code repository URL of the VCS repository with your project File mask po/*.po Base file for new translations po/hello.pot