Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Clarification: stack parameter + stacks

See original GitHub issue

Is it possible to let the play-with-docker live site also use a stack from a repository from my GitHub account? Apparently the paths passed to stack parameter are resolved relative to https://github.com/play-with-docker/stacks.

Issue Analytics

State:
Created 6 years ago
Comments:10 (5 by maintainers)

Top GitHub Comments

1reaction

marcosnilscommented, Dec 5, 2017

Yes, just send the full url of the raw file from your git repo in the stack parameter

0reactions

strarsiscommented, Dec 5, 2017

@marcosnils: It is already closed 😄

Top Results From Across the Web

Stacks: Parameter Tutorial

Tutorial: How do the major Stacks parameters control the de novo formation of stacks and loci? This tutorial will describe how three major...

StackInstance - AWS CloudFormation

A list of parameters from the stack set template whose values have been overridden in this stack instance. Type: Array of Parameter objects....

V2 stack_output vs stack_output_external clarification #556

stack_output now seems to be able to reference stacks from a different environment. Is this true? stack_output_external seems to have been ...

Technical Appendix E. Derivation of Stack Parameter Data

2.1.2 Emission and Stack Height Data in AFS. AFS tracks data in a hierarchy with four levels: (1) facilities; (2) stacks, the locations...

Stack Config - Sceptre

Outputs from stacks with custom names can't be resolved using the standard stack output resolver. Outputs should be resolved using the stack output...