Bug #4752: [Docker] Make websockets work, probably by using passenger standalone instead of apache. - Arvados

Actions

Bug #4752

closed

[Docker] Make websockets work, probably by using passenger standalone instead of apache.

Added by Tom Clegg about 10 years ago. Updated almost 10 years ago.

Status:

Resolved

Priority:

Normal

Assigned To:

Category:

-

Target version:

2015-04-29 sprint

Start date:

04/01/2015

Due date:

% Done:

100%

Estimated time:

(Total: 0.00 h)

Story points:

0.5

Subtasks 1 (0 open — 1 closed)

Related issues 1 (0 open — 1 closed)

Actions

#1

Updated by Peter Amstutz almost 10 years ago

Target version changed from Arvados Future Sprints to 2015-04-01 sprint

Actions

#2

Updated by Peter Amstutz almost 10 years ago

Status changed from New to In Progress

Actions

#3

Updated by Peter Amstutz almost 10 years ago

Assigned To set to Peter Amstutz

Actions

#4

Updated by Ward Vandewege almost 10 years ago

Target version changed from 2015-04-01 sprint to 2015-04-29 sprint

Actions

#5

Updated by Ward Vandewege almost 10 years ago

LGTM, thanks!

Actions

#6

Updated by Peter Amstutz almost 10 years ago

A few more changes for you to review:

Fix compute node containers to restart correctly.
Fix git server hostname
Arvdock waits for API/workbench to be ready before telling the user to go to workbench.

I'm now able to start the containers, upload files, verify that websockets works, run jobs, shut down the containers, start them again, and do it all again.

Actions

#7

Updated by Ward Vandewege almost 10 years ago

4752-docker-websockets LGTM, but please pull before you merge; I added one commit to the branch.

Actions

#8

Updated by Peter Amstutz almost 10 years ago

Status changed from In Progress to Resolved
% Done changed from 0 to 100

Applied in changeset arvados|commit:1a4d0158373902cac889ce5409fcae447d4a68d6.

Actions

Also available in: Atom PDF