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
I added the Action for doing a release to PyPI on tagged push, but we need the secret set up for physrisk-api as for physrisk. PIease can you check you are happy with the approach (i.e. same publishing for physrisk-api as physrisk-lib) and if so add the secrets?
I'll be at office hours, so maybe discuss then.
Thanks,
Joe
The text was updated successfully, but these errors were encountered:
By the way, the reason for the publish to PyPI is so that OS-C members can host API internally as well as accessing physrisk internally. Companies tend to have their 'walled-garden' repos with some access to the public. An internal process can then take the package and wrap it (e.g. as Docker image) for internal deployment. @Floflow is looking into this by the way.
Hi @erikerlandson; hi @negillett,
I added the Action for doing a release to PyPI on tagged push, but we need the secret set up for physrisk-api as for physrisk. PIease can you check you are happy with the approach (i.e. same publishing for physrisk-api as physrisk-lib) and if so add the secrets?
I'll be at office hours, so maybe discuss then.
Thanks,
Joe
The text was updated successfully, but these errors were encountered: