7/30/2023 0 Comments Shipit permissions![]() For example if your app settings URL is, the bot user should be acme-shipit. It should be the App "slug" with the suffix. Every GitHub App have an associated user which acts as the author of the App actions through the API, for example when an App merges a Pull Request. Github.bot_login The login of the App user. Then look at the URL it should follow this pattern. Github.installation_id The ID of your GitHub App installation, it can be found under Organization Settings > Installed GitHub Apps > Configure. Github.app_id The GitHub App ID, it can be found under General > About Redis_url Should point to a working Redis database. Host Should specify the domain of your shipit instance, e.g. It is used for signing session cookies etc. Secret_key_base Should be generated automatically by Rails. Id: Iv1.bf2c2c45b449bfd9 secret: ef694cd6e45223075d78d138ef014049052665f1 teams:ĭomain: # The domain name of your GitHub Enterprise instance, leave it empty if you use Secret_key_base: some-long-string host: redis_url: "redis://redis-host " github:Īpp_id: 42 installation_id: 43 bot_login: "my-app " webhook_secret: some-secret-value private_key: | -BEGIN RSA PRIVATE KEY- MIIEpAIBAAKCAQEA7iUQC2uUq/gtQg0gxtyaccuicYgmq1LUr1mOWbmwM1Cv63+S 73qo8h87FX+YyclY5fZF6SMXIys02JOkImGgbnvEOLcHnImCYrWs03msOzEIO/pG M0YedAPtQ2MEiLIu4y8htosVxeqfEOPiq9kQgFxNKyETzjdIA9q1md8sofuJUmPv ibacW1PecuAMnn+P8qf0XIDp7uh6noB751KvhCaCNTAPtVE9NZ18OmNG9GOyX/pu pQHIrPgTpTG6KlAe3r6LWvemzwsMtuRGU+K+KhK9dFIlSE+v9rA32KScO8efOh6s Gu3rWorV4iDu14U62rzEfdzzc63YL94sUbZxbwIDAQABAoIBADLJ8r8MxZtbhYN1 u0zOFZ45WL6v09dsBfITvnlCUeLPzYUDIzoxxcBFittN6C744x3ARS6wjimw+EdM TZALlCSb/sA9wMDQzt7wchhz9Zh2H5RzDu+2f54sjDh38KqancdT8PO2fAFGxX/b qicOVyeZB9gv6MJtJc20olBbuXAeBNfcDABF9oxF+0i+Ssg7B4VXiqgcjtGbr/Og qRll7AqyTArVx2圎cVfZxeZ4zGnigzcJq4te7yYpxzwk+RxblkPh54Yt4WxZ+8DI Rsn3r6ajlpwzpwvsJFU2Txq7xBTzGQMFmy/Pnjk83kP2cogxB2+tRyjITGqTwD8b gg9PFCkCgYEA+7u8A0l0Cz6p0SI6c7ftVePVRiIhpawWN7og/wEmI6zUjm/3rA+R hrhaVKuOD8QF/HdDsqTck5gjGAjTmJz6r33/cl1Tz+pr62znsrB4r0yMKvQbKN81 WGaWOsi2+ZXqLNv5h5wpUF0MTKlXHeKnwP5kuEvGwVn6WURFCh6PhLMCgYEA8i5e JjulJVGyd5HuoY3xyO7E6DjidsqRnVRq+hYpORjnHvTmSwe4+tH4ha2p9Kv2Y6k3 C1NYY/fSMQoYCCRaYyJleI+la/9tsZqAmtms4ZB8KhFmPHf9fW75i6G0xKWyZ8K+ E2Ft/UaEiM282593cguV6+Kt5uExnyPxLLK4FlUCgYEAwRJ/JGI8/7bjFkTTYheq j5q75BufhOrU6471acAe2XPgXxLfefdC3Xodxh0CS3NESBvNL4Ikr4sbN37lk4Kq /th7iOKtuqUIeru/hZy2I3VpeDRbdGCmEJQ2GwYA2LKztg5Nd0Y9paaIHXAwIfrK QUqcQ4HTAk8ZpUeoUBeaaeMCgYANLmbjb9WiPVsYVPIHCwHA7PX8qbPxwT7BsGmO KQyfVfKmZa/vH4F67Vi4deZNMdrcO8aKMEQcVM2065a5QrlEsgeR00eupB1lUEJ1 qylUsZeAdqf43JMIc7TTW77KATa/nQLZbTEeWus1wvTngztuEqFbUGAks9cOkVc8 FpIcbQKBgQDVIL8gPLmn0f+4oLF8MBC+oxtKpz14X5iJ1saGFkzW5I+nIEskpS0S qtirnTCnJFGdCrFwctnxiuiCmyGwpBYdjIfHyvYAHnqAtMnESzCUyeSFZiquVW5W MvbMmDPoV27XOHU9kIq6NXtfrkpufiyo6/VEYWozXalxKLNuqLYfPQ= -END RSA PRIVATE KEY- oauth: The config/secrets.yml file will hold your secrets, by default it is ignored by git, so it's up to you to decide how secrets are deployed in production, as Rails doesn't enforce any method. Once it's created, make sure it's installed on your organization via the Install App menu on the side. Installing the GitHub App on your organization Issues: Read & write (to allow closing related issues on merge).Contents: Read & write (to allow merging).Webhook secret (optional): Fill it with some randomly generated string, and keep it in clear on the side, you'll need it later. Webhook URL: It must be set to /webhooks, e.g. User authorization callback URL: It must be set to /github/auth/github/callback, e.g. Homepage URL: The URL where Shipit will be deployed, e.g. You can create a new one for your organization at, or for a regular user. Shipit needs a GitHub App to authenticate users, receive Webhooks and access the API. Run this command: rails _7.0_ new shipit -skip-action-cable -skip-turbolinks -skip-action-mailer -skip-active-storage -skip-webpack-install -skip-action-mailbox -skip-action-text -m.If you don't have Rails installed, run this command: gem install rails -v 7.0. ![]() Shipit provides you with a Rails template. Shipit requires a database (MySQL, PostgreSQL or SQLite3), Redis, and Ruby 2.6 or superior. In the future we'd like to provide it fully packaged inside a Docker container, but it hasn't been done yet. At this point Shipit is mostly a Rails engine, so setting it up in production requires some Rails development knowledge.ĭeploying and hosting a Rails application is not trivial, and this document assumes you know how to do it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |