915 Windows deployment script #948
No reviewers
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K!948
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "915-Windows-deployment-script"
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?
Added the Windows deployment script and changed the Unix script to match the coding conventions.
Also changed the names.
Relevant issue: #915
Review
Question before merge ready:
Should we try it out on a windows machine in order to actually know that it works?
Yes, try it and post result from server logs.
Tried to execute the script on my Windows PC and it could not find the path.
Apparently Windows require special permissions of some sort to SSH with the private.key, we will talk to Henrik about the key because we suspect that it is a private key, but we should probably have a public key.
915 Windows deployment scriptto WIP: 915 Windows deployment scriptA discussion has been taking place about if it would be a simple fix to use the docker WSL (Windows Subsystem for Linux), we already have it since docker is running WSL. It could work out fine in order for Windows users to be able to deploy.
I will create a separate issue on this.
WIP: 915 Windows deployment scriptto 915 Windows deployment scriptTried this out by running a test script on the server from my Windows machine which worked.
I don't see how this would work differently than deploying the deploy script, this will be somewhat awkward to test since you need the SSH-key to verify it.