패키지 액세스를 일부 사용자들로 제한하거나, 폐색망 조직에 패키지 레지스트리 서버를 설정하려는 경우 자체 패키지 레지스트리 서버를 설정할 수 있습니다.
패키지 개발을 마친 후 다른 사용자들에게 공유하려는 경우 다음과 같은 여러 옵션을 이용할 수 있습니다.
|Tarball||You can distribute a zip or tarball to other Unity users. That way, they can either install the package from the local tarball directly or decompress the zip or tarball to a local folder on their own computer and install it from there.|
|Git URL||You can distribute a link to your Git repository, using one of the supported protocols. Then users can install your package using its Git URL, because the Unity Package Manager can fetch packages from Git repository hosting services like GitHub and GitLab.|
|Scoped Registry||You can set up a package registry server to host your package and then publish it to that registry using npm’s 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
Warning: When you set up your own package registry server, make sure you only use features that are compatible with Unity’s Scoped Registries. For example, Unity doesn’t support namespaces using the
Most of the time, anonymous access within a local network is sufficient 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.