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

Dynamic CLI setup for Windows #118

Closed
kaustubhgupta opened this issue Jul 12, 2021 · 12 comments
Closed

Dynamic CLI setup for Windows #118

kaustubhgupta opened this issue Jul 12, 2021 · 12 comments

Comments

@kaustubhgupta
Copy link

💥 Proposal

As per issue #94 discussions, contributors are looking forward to windows support, and the termos package we are using is only implemented for Linux machines.

Till the time we release a proper windows version, the contributors should be able to contribute to the code base. What if I tell you that you can do your development in a Linux environment and still use windows machines? No, I am not talking about dual boot or virtualization. It's WSL!

Windows subsystem for Linux (WSL) is a compatibility layer for running Linux binary executables natively on Windows 10, Windows 11, and Windows Server 2019. I think most of the Windows developers are using Windows 10 and it would be great news for them to use WSL as their development environment.

I am using WSL2 for quite some time and I tried testing dynamic cli. It worked like a charm.

image

I can create a quick demo resource/ text tutorial on setting up dynamic cli on Windows machines.

Let me know your thoughts. CC: @GouravSardana @sakshatl

@github-actions
Copy link

Hi👋 thanks for creating your first issue for IOSF, Will get back to you soon !.

@lainq
Copy link
Contributor

lainq commented Jul 12, 2021

Yes, WSL is of course a great solution. But, we can't force our contributors to download pretty heavy software just to contribute to the project(1.82 GB is pretty heavy). But, contributors can use WSL if they wish to 🙂 . Thank you for recommending a solution 🤗 🙂

@kaustubhgupta
Copy link
Author

Yes, WSL is of course a great solution. But, we can't force our contributors to download pretty heavy software just to contribute to the project(1.82 GB is pretty heavy). But, contributors can use WSL if they wish to 🙂 . Thank you for recommending a solution 🤗 🙂

WSL is not much heavy, plus this is not only limited to dynamic CLI but it will support them in future projects also

@lainq
Copy link
Contributor

lainq commented Jul 12, 2021

Yes, WSL is of course a great solution. But, we can't force our contributors to download pretty heavy software just to contribute to the project(1.82 GB is pretty heavy). But, contributors can use WSL if they wish to 🙂 . Thank you for recommending a solution 🤗 🙂

WSL is not much heavy, plus this is not only limited to dynamic CLI but it will support them in future projects also

Yes, that's also true 🙂

@GouravSardana
Copy link
Member

For now we can adopt this plan but i don't think this will work longer. We have to remove the dependencies which is dependent upon OS

@GouravSardana
Copy link
Member

Hey @kaustubhgupta , Are you working on this?

@kaustubhgupta
Copy link
Author

I didn't got the confirmation on this, that's why I was waiting. Should I make this resource? If yes, then where to put this file and under which section should I link it in the readme.

P.S: Not related to the issue, I am not able to join the telegram group. The link is not working for me.

@GouravSardana
Copy link
Member

Yup, You can get started on this. You can put in the installment section. Please mention only for windows. Other than that follow the above thing (pip install ...)

Try this link - https://t.me/joinchat/FjyKgz1w3ppiZjI1

@kaustubhgupta
Copy link
Author

Yup, You can get started on this. You can put in the installment section. Please mention only for windows. Other than that follow the above thing (pip install ...)

Try this link - https://t.me/joinchat/FjyKgz1w3ppiZjI1

okay, I will pull up the PR soon.

@kaustubhgupta
Copy link
Author

Update: It might take a little longer time, I am quite busy these days.

@GouravSardana
Copy link
Member

Take your time

@kaustubhgupta
Copy link
Author

Closing this issue here, can be continued in #123

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

No branches or pull requests

3 participants