Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create SDK repository #1251

Closed
nitrosx opened this issue Jun 12, 2024 · 5 comments
Closed

Create SDK repository #1251

nitrosx opened this issue Jun 12, 2024 · 5 comments

Comments

@nitrosx
Copy link
Contributor

nitrosx commented Jun 12, 2024

Create SDK repository

Summary

At each new release of SciCat BE, we want to auto generate all the supported SDKs in a separate repositories.
The objective is to always have the SDK (bindings, libraries) up to date to the most recent and stable version of SciCat

Expected Behaviour

Create a new repository in SciCat project named SDK, also known as bindings or libraries.

@nitrosx nitrosx moved this to Todo in SDK repositories Jun 12, 2024
@nitrosx nitrosx moved this from Todo to Accepted in SDK repositories Jun 12, 2024
@nitrosx nitrosx moved this from Accepted to Ready in SDK repositories Jun 12, 2024
@nitrosx nitrosx moved this from Ready to Done in SDK repositories Jun 12, 2024
@dylanmcreynolds
Copy link
Contributor

Does this mean you want one repo with python, javascript, rust, etc?

@dylanmcreynolds
Copy link
Contributor

Related to SciCatProject/pyscicat#59

@dylanmcreynolds
Copy link
Contributor

I think that pyscicat is the natural place for the python version.

@Ingvord
Copy link
Contributor

Ingvord commented Jul 23, 2024

We will need to store source code for compiled languages some where. Having source code for these is very much appreciated by the developers.

Also for these having independent repo would be more preferred, as every language has its own eco system which is easier to maintain independently

@nitrosx
Copy link
Contributor Author

nitrosx commented Oct 31, 2024

Not needed for now.
SDK are generated and stored as artifacts at every merge to Master. They are also published to NPM.js and PYPI at every release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants