- Added Private Token Authentication (OmniAuth, etc).
- Minor bugfixes.
I am aware that some users reported few problems about be able to establish an SSL connection through the app and GitLab.
GitLab Control is very strict about the safety of accutane restores a natural beauty of your skin but buy accutane and Its Easy and Safe! your data and in order to establish an SSL connection to your GitLab server you need to own a valid SSL certificate.
One of the common problem you may face is that your certificate is self signed, so GitLab Control mark it as invalid not allowing you to establish an unsafe connection.
Due to numerous requests, we have decided to be more flexible.
Since version 1.1 you will be notified when attempting to connect through SSL using a self signed certificate and you will be able to proceed at your own risk.
This has already been implemented, but I can not pull the current version 1.0.1 because it contains a very important bug fix, which needs to be available to all of you as soon as possible.
So, this new feature will be available (for everyone) probably during the next week.
Unfortunately, these are Apple timings and there is no much I can do to speed up the process, but meanwhile I can show you how it will look like 🙂
It has been a very long way through the development of this app.
There have been very awesome moments full of enthusiasm and others when I really wanted to give up.
No matter what, despite all the difficulties, GitLab Control is now the first real iOS App that brings your GitLab projects with you wherever you go.
I really want to thank these people for supporting me during this time: