(🚧 WIP 🚧)
If you use official package of the Unity Package manager. It should import them directly from the Unity Server.
If you want, you can create your own server (Look later on the suject).
They are also other solutions propose by the community.

Found an article that explain a way of doing it:
https://medium.com/@markushofer/run-your-own-unity-package-server-b4fe9995704e

That not what I want to do but that could be useful if someone need.

Changelog

Info on the log and where to access info

[0.0.0] - yyyy-mm-dd

Title of the log

• List of the new change 1
• List of the new change 1

WIp

• https://www.youtube.com/watch?v=bdsODjVhJP8

Saw that the quality of the following video were not great.
People disliked it.
So I unlisted them.
But the are some good info in it so i keep them here, in case some on need them.

In previous workshop and project, I have always the same question(s).

1. Check that git is install
2. Check that git\bin path is in your "environment variable"
3. Change your "credential manager"
   • Press window
   • Search "credential manager"
   • Go in Windows Credentials
   • Remove all old, other users or not use credentials linked to Git.
4. Push your code in git, or else.
5. Window ask you your password and will save it in credential manager
6. Done 🍻.

If it is not enough, you can use this commands:

• git config credential.helper "" To remove the window helper that fit the password for you
• git config credential.helper cache to reactivate the window helper.

git config --get remote.origin.url

https://docs.unity3d.com/Manual/upm-ui-tarball.html

• https://forum.unity.com/threads/package-perproject-assets.642292/
• https://twitter.com/FreyaHolmer/status/1270735204404076548

I realized in my code a pattern that I am using.

1. Create a interface package that resume what you expect from a technology.
2. Create a code that use this interface for the tool you create.
3. Create some code that convert the complex native code into this interface package you provided.

Leading your tool box to be less dependent of the native update of the api you are following.

C:\Program Files\Unity\Hub\Editor\2020.1.0b4\Editor\Data\Resources\PackageManager\Editor

https://docs.unity3d.com/Packages/[email protected]/manual/index.html?_ga=2.241698434.1064320143.1589955333-2089392457.1586257174

• https://forum.unity.com/threads/setup-for-scoped-registries-private-registries.573934/
• https://docs.npmjs.com/misc/scope)

• https://forum.unity.com/threads/git-support-on-package-manager.573673/
• https://forum.unity.com/threads/git-support-on-package-manager.573673/page-3#post-4405291

https://docs.unity3d.com/Packages/[email protected]/manual/index.html

Layer and tag are linked to the user project so if you use it in your project you need to provide information to the user that he need to configure that and that before your tool work. How should we deal with that situation ?

Nomenclature of Unity with version:
https://docs.unity3d.com/2020.2/Documentation/Manual/upm-semver.html

For three weeks, we did a workshop with the Belgian students of Technocité call Magic Doors.

The workshop was a success, I am planning to re-iterate the experiment.
This post is a postmortem to make a review of how it happens.
And how to improve the next workshop.

Source: Laetitia

https://openupm.com/

• https://forum.unity.com/members/favo-yang.40971/
• https://medium.com/openupm/how-to-maintain-upm-package-part-1-7b4daf88d4c4

Tutorial on the package manager are so rare...
And good / complete one are rarer.

So if I find some, I will add them here.

Draft

Check that you have Unity 2018+ Install

Install Git on your PC

Add git to Environment System

Create a git repository GitLab or GitHub

Clone the repository in your project

Create a package in Unity

1. Create a folder
2. Create Package.json and complete informations
3. Create a folder "Runtime"
4. Create an assembly "country.organisation.packagename.Runtime
5. Put your asset in the assembly

Push the code online

Re-covert it in project

Find a full tutorial here:
Hello Package