README.md in sigh-0.6.0 vs README.md in sigh-0.8.0

- old
+ new

@@ -49,14 +49,10 @@ ------- <h5 align="center"><code>sigh</code> is part of <a href="https://fastlane.tools">fastlane</a>: connect all deployment tools into one streamlined workflow.</h5> -### spaceship version - -If you're feeling adventurous and want to test the new `sigh` beta with [spaceship](https://spaceship.airforce), update using `sudo gem update sigh --pre`. More information in the [release notes](https://github.com/KrauseFx/sigh/releases/tag/1.0.0.beta5). - # Features - **Download** the latest provisioning profile for your app - **Renew** a provisioning profile, when it has expired - **Repair** a provisioning profile, when it is broken @@ -109,10 +105,14 @@ To generate the profile in a specific directory: sigh -o "~/Certificates/" +To download all your provisioning profiles use + + sigh download_all + For a list of available commands run sigh --help ### Advanced @@ -127,18 +127,23 @@ If you need the provisioning profile to be renewed regardless of its state use the `--force` option. This gives you a profile with the maximum lifetime. `--force` will also add all available devices to this profile. sigh --force -By default, ```sigh``` will include all certificates on development profiles, and first certificate on other types. If you need to specify which certificate to use you can either use the environment variable `SIGH_CERTIFICATE`, or pass the name or expiry date of the certificate as argument: +By default, `sigh` will include all certificates on development profiles, and first certificate on other types. If you need to specify which certificate to use you can either use the environment variable `SIGH_CERTIFICATE`, or pass the name or expiry date of the certificate as argument: sigh -c "SunApps GmbH" -Or identify be expire date if you're using the same names for multiple certificates +# Repair - sigh -d "Nov 11, 2017" +`sigh` can automatically repair all your existing provisioning profiles which are expired or just invalid. +All you have to do is + + sigh repair + + # Resign If you generated your `ipa` file but want to apply a different code signing onto the ipa file, you can use `sigh resign`: @@ -174,20 +179,19 @@ Choose signing certificate to use: - `SIGH_CERTIFICATE` (The name of the certificate to use) - `SIGH_CERTIFICATE_ID` (The ID of the certificate) -- `SIGH_CERTIFICATE_EXPIRE_DATE` (The expire date of the certificate) As always, run `sigh --help` to get a list of all variables. If you're using [cert](https://github.com/KrauseFx/cert) in combination with [fastlane](https://github.com/KrauseFx/fastlane) the signing certificate will automatically be selected for you. (make sure to run `cert` before `sigh`) `sigh` will store the `UDID` of the generated provisioning profile in the environment: `SIGH_UDID`. # How does it work? -```sigh``` will access the ```iOS Dev Center``` to download, renew or generate the ```.mobileprovision``` file. Check out the full source code: [developer_center.rb](https://github.com/KrauseFx/sigh/blob/master/lib/sigh/developer_center.rb). +```sigh``` will access the ```iOS Dev Center``` to download, renew or generate the ```.mobileprovision``` file. It uses [spaceship](https://spaceship.airforce) to communicate with Apple's web services. ## How is my password stored? ```sigh``` uses the [password manager](https://github.com/KrauseFx/CredentialsManager) from `fastlane`. Take a look the [CredentialsManager README](https://github.com/KrauseFx/CredentialsManager) for more information.