We built a library (SDK) for iOS. The source code of the library is closed (proprietary). The output we want to release is iOS frameworks, API documentation, setup guide, license file but NO source code.
We are discussing different ways to release it to the public.
1) One way is to create a public git repository hosted in Github and push all the output in it.
2) Another way is to host these files on our own server.
Is there any benefit of hosting it on GitHub over hosting it on our own servers? I know git is to manage source files but in this case, there is no source file that we want to publish, it is just the output. Is there any general rule to release iOS close source SDKs?. I tried many IOS and Git training resources to find a solution for this. Unluckily I couldn't able to. I am inclined more towards hosting the SDK (as zips) in our own server. I believe it is always the latest SDK you market on your website and not the older SDK.
댓글 1개
게시글 목록
| 번호 | 제목 |
|---|---|
| 1891 | |
| 1879 | |
| 1874 | |
| 1873 | |
| 1867 | |
| 1866 | |
| 1862 | |
| 1861 | |
| 1855 | |
| 1854 | |
| 1853 | |
| 1851 | |
| 1850 | |
| 1849 | |
| 1848 | |
| 1847 | |
| 1841 | |
| 1840 | |
| 1835 | |
| 1833 | |
| 1825 | |
| 1824 | |
| 1820 | |
| 1819 | |
| 1814 | |
| 1811 | |
| 1810 | |
| 1809 | |
| 1808 | |
| 1805 |
댓글 작성
댓글을 작성하시려면 로그인이 필요합니다.
로그인하기