You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running services locally doesn't work out of the box.
PS E:\Ynput\ayon-kitsu> cd services/processor
PS E:\Ynput\ayon-kitsu\services\processor> ./manage.ps1 run
&: E:\Ynput\ayon-kitsu\services\processor\manage.ps1:39:7
Line |
39 | & poetry run python -m processor
| ~~~~~~
| The term 'poetry' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the
| name, or if a path was included, verify that the path is correct and try again.
Expected Behavior:
IMO, having more options in manage script where I can run install that brings poetry and venv.
More info about how to run the service on developer machine and will it conflict with the service running on ASH.
It's important to note (please, @iLLiCiTiT correct me) that the services themselves are not directly uploaded to the server. Instead, their Docker files are created and then uploaded to Docker Hub whenever there is a new GitHub release. This is why services with the -dev.x postfix in their version number do not work—there are no Docker files available for these interim versions.
Version
1.0.0
What platform you are running on?
Windows
Steps To Reproduce:
shown above.
> cd services/processor
> ./manage.ps1 run
Are there any labels you wish to add?
I have added the relevant labels to the bug report.
Relevant log output:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior:
Running services locally doesn't work out of the box.
Expected Behavior:
IMO, having more options in
manage
script where I can runinstall
that bringspoetry
andvenv
.More info about how to run the service on developer machine and will it conflict with the service running on ASH.
It's important to note (please, @iLLiCiTiT correct me) that the services themselves are not directly uploaded to the server. Instead, their Docker files are created and then uploaded to Docker Hub whenever there is a new GitHub release. This is why services with the
-dev.x
postfix in their version number do not work—there are no Docker files available for these interim versions.Version
1.0.0
What platform you are running on?
Windows
Steps To Reproduce:
shown above.
Are there any labels you wish to add?
Relevant log output:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered: