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

Version control the scripts and workflows #87

Open
thoth291 opened this issue Oct 1, 2020 · 2 comments
Open

Version control the scripts and workflows #87

thoth291 opened this issue Oct 1, 2020 · 2 comments
Labels

Comments

@thoth291
Copy link

thoth291 commented Oct 1, 2020

Let's assume that one can use GitLab for auth to PLynx (look at this issue #78 ).
Then instantly would be great to have all the scripts version controlled in appropriate repos, instead of being scattered somewhere in some separate database.
This would also help to reuse codes within PLynx with other projects and frameworks.

Any thoughts?

@thoth291
Copy link
Author

thoth291 commented Oct 1, 2020

I can also see this as a good idea to tie Plynx workflows as CI/CD for some operations and workflows - this way one could develop for Plynx purely in gitlab and use Plynx only for some grand tests.

@khaxis
Copy link
Collaborator

khaxis commented Oct 13, 2020

Hi Anar, sorry didn't your issues before. Thanks for the feedback!

Yes, have been thinking about it. It needs some development and probably an external service following plynx paradigms.

One option is to create a new Hub plugin. It's the panel on the left side. Currently there are only two plugins: the one that uses the database, the other one is serving a static list. The idea is to make this plugin to scan git repo(s).

Alternative is to have a git operation, that clones a repo using it's url and hash. A little ugly might seem, but that's what I was doing before

@khaxis khaxis added the feature label Oct 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants