Version: 2022.2
언어: 한국어
패키지 문서화
기능 집합

패키지 공유

패키지 액세스를 일부 사용자들로 제한하거나, 폐색망 조직에 패키지 레지스트리 서버를 설정하려는 경우 자체 패키지 레지스트리 서버를 설정할 수 있습니다.

When you have finished developing your package and you want to share it with other users, you have several options:

Compressed file You can distribute a zip file to other Unity users. That way, they can decompress the zip file to a local folder on their own computer and install the package from disk.
Tarball You can distribute a tarball to other Unity users. That way, they can install the package from the local tarball directly.
Git URL 지원되는 프로토콜 중 하나를 사용하여 Git 저장소에 링크를 배포할 수 있습니다. 그러면 사용자들이 Git URL을 사용하여 패키지를 설치할 수 있습니다. 이때 Unity 패키지 관리자는 GitHub, GitLab 등과 같은 Git 저장소 호스팅 서비스를 사용하여 패키지를 페치할 수 있습니다.
Scoped Registry You can set up a package registry server to host your package and then publish it to that registry using the npm publish command. Your package’s consumers can then set up a scoped registry configuration in their project to fetch your custom packages from your own package registry.

Unity Package Manager supports registries based on the npm protocol. Make sure that whatever registry server you choose implements the /-/v1/search or /-/all endpoints.

Warning: When you set up your own package registry server, make sure you use only those features that are compatible with Unity’s Scoped Registries. For example, Unity doesn’t support namespaces using the @scope notation that npm supports.

Most of the time, anonymous access within a local network is adequate to fulfill your security requirements. However, if you want more control over who accesses packages via scoped registries, you can enable npm authentication for specific users. Your package’s customers can then configure their scoped registries to use their npm authentication tokens.

추가 리소스

패키지 문서화
기능 집합