|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 5215 | minor | always | 09-17-12 09:44 | 09-20-12 11:19 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.31 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.32 | ||
|
|
|||||
| Summary: | 0005215: host-deploy with resinctl --host | ||||
| Description: |
(rep by Gerrit Janssen) Suppose I configure all cluster members to scan a local directory for virtual hosts by using the host-deploy tag. Is that cluster-safe ? I mean, when you push the app to the cluster with "resinctl deploy", it's obvious that this is a single app that needs to be deployed to all cluster members. But, when you use host-deploy it will be each server individually that will be discovering the new virtual host whenever they scan their local directory (and so possibly not even at the same time). Does that work in combination with "resinctl deploy --host hostname" ? Will the locally discovered host be visible at the cluster level and will they all be seen as the same virtual host ? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||