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

Feature Request - Portable Version #205

Open
raspyweather opened this issue Feb 28, 2019 · 7 comments
Open

Feature Request - Portable Version #205

raspyweather opened this issue Feb 28, 2019 · 7 comments

Comments

@raspyweather
Copy link

It would be a very useful feature to use this application in a portable version without installation, as it is not possible to use this software in many companies as admin rights are required to run the installer.

@neuhausneuhaus
Copy link

By a portable version do you mean a web app, or being able to run Swell from something like npx?

@raspyweather
Copy link
Author

I meant something that doesn't require installation with admin rights as thats a problem for many developers in companies.
But yes a web app, electron app or something with npx would totally do it.

@8D-k
Copy link

8D-k commented Nov 16, 2021

Adding a Dockerfile to Swell's repo may be a workaround to assist many who otherwise may not have admin rights. Admin rights over a container image or virtual machine are generally easier to obtain in many situations rather than than admin rights over a full machine in a controlled IT environment.

A fuller direct addressing of this Issue will be to have a full portable package installation generated much like Deno's packages. Make a single swell.exe executable file packaged by this project which can simply start without external dependencies on the target system. This would address the issue raised in a completely portable manner.

Portable in this context means to have non-admin rights on the system running Swell and requiring no dependency installation after downloading project packages. Potentially a *.zip file with a *.exe inside of the *.zip file, and no need to download anything further aside from what is included. Potentially a *.zip file with *.exe and several configuration files, plugins folder, and so forth. Correct handling here if there are resources including libraries which routinely need updated.

@8D-k
Copy link

8D-k commented Nov 16, 2021

@cgefx or others active in recent development to speak up.
What scope is currently under consideration for a fix to this issue? Thank you for any insight

@8D-k
Copy link

8D-k commented Nov 17, 2021

@raspyweather Do you know which direction the project is hoping to take on this?

@raspyweather
Copy link
Author

Sadly no :(

@cgefx
Copy link
Contributor

cgefx commented Nov 18, 2021

Adding a Dockerfile to Swell's repo may be a workaround to assist many who otherwise may not have admin rights. Admin rights over a container image or virtual machine are generally easier to obtain in many situations rather than than admin rights over a full machine in a controlled IT environment.

A fuller direct addressing of this Issue will be to have a full portable package installation generated much like Deno's packages. Make a single swell.exe executable file packaged by this project which can simply start without external dependencies on the target system. This would address the issue raised in a completely portable manner.

Portable in this context means to have non-admin rights on the system running Swell and requiring no dependency installation after downloading project packages. Potentially a *.zip file with a *.exe inside of the *.zip file, and no need to download anything further aside from what is included. Potentially a *.zip file with *.exe and several configuration files, plugins folder, and so forth. Correct handling here if there are resources including libraries which routinely need updated.

there was talk about containerizing Swell in the last planning meeting, though in the context of development workflow. We'll look into this at the next one and see if there's anything there in terms of portability for production releases.

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

4 participants