Research if Linux deployment script can be deployed with WSL #1002
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#1002
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This could potentially fix the #948 and #915
Research:
It is very easy to run Linux scripts with WSL, and it is actually a common standard for docker projects for CI/CD purposes. For example, some projects only use Linux scripts and run them with WSL. That way you could rely on only Linux scripts.
Since docker desktop (Windows) is already running on WSL with the VM (docker-desktop), the dependency is already included in the project. All we need to do is to create another OS preferebly Debian (for compatibility reasons with docker) and run the DeployTrigger.sh.
The question is rather, in what scale should we utilize WSL with Debian for our gain?
Should it only be installed during deployment (And uninstalled right after?), or is there a reason to install it in the installation script and use it for more things.
After discussion with peers we believe the right option is to install it during deployment and keep it installed, since it would be a little unnecessary to keep installing it each deploy.
Initially it looked as if this solution would work fine, this was until it was discovered that the VM will not be able to run a SSH to a remote server because of NAT settings and WSL constraints to establishing an SSH connection. The research suggests that it is possible but would need alot more additional work, uncertain if its worth the effort to be able to deploy from Windows machine.
After the problems with WSL it was decided to take a second look at the WIP PR for windows deployment script which spawned this issue, the problems were identified and solved. I think this issue can be closed without a review because its not relevant.