We are still iterating on what to call these concepts. In this situation the upstream-url should be your floxpkgs repository. Likely this is your current directory and the CLI should be reading the git repo’s origin and offering that as the default value for “upstream-url”.
For some background on what problem this option is trying to address: you may have only ssh transport access to write to your floxpkgs repo, but it might be publicly readable, in which case the “upstream-url” should be how people consuming your software can access it. We are redesigning this portion to provide a better set of defaults and improve how we explain the concept.
Currently I invoke flox publish in the scmpuff directory which contains the derivation I want to publish to my flox catalog. If I call flox publish ----publish-to https://github.com/etorreborre/floxpkgs.git then my scmpuff repository origin URL is detected as the upstream-url. Could you please describe what you think is the full proper command line invocation with all the parameters that I should use?
Also I just saw that the tutorial on publishing still refers to a remote-url
from the repository that defines a package (lets take your scmpuff as an example)
flox publish -A scmpuff
will detect your current directory as a git repository (therefore defaulting --upstream-url to your origin remote.
The upstream-url is part of the published metadata to allow rebuilding of the published package from source.
--publish-to defines where these metadata files will be stored (since you need to access them somehow after all).
Normally this should point to your floxpkgs repository
flox will guess the repository from your published repositories origin url:
So to come back to your question,
to publish scmpuff you only need to run flox publish in the scmpuff repo.
the --publish-to and --upstream-url are confiremend interactively in that case.
If a single command is what you need it would be
flox publish -A scmpuff --upstream-url git+ssh://email@example.com/etorreborre/scmpuff.git --publish-to git+ssh://firstname.lastname@example.org/etorreborre/floxpkgs
As @tomberek said the API is still experimental and were trying to find a good way to specify defaults without long cli invocations and repetitive/error prone interactive entries, stay tuned
just a quick heads up that ‘flox publish’ has been reworked and the updates will be in the next release (0.0.7) which is expected very soon now. We’ll make an announcement here in discourse once it is available.