Support Build & Setup Environment Variables
See original GitHub issueIn my case I have a postCreateCommand
that clones another organization repo. This works great under Codespaces but is hanging when using this project. I think what I see is that 🏃 start container
will stop here.
Cloning into '/workspaces/mysharedrepo'...
Username for 'https://github.com/':
And never move from that spot. The lifecycle script is doing something like this.
git clone "https://${GITHUB_TOKEN}@github.com/myorg/mysharedrepo.git" /workspaces/mysharedrepo
cd /workspaces/mysharedrepo
Any recommendations to get that working?
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Set environment variables to configure builds
To set environment variables for local builds, you append the --env flag to the pack command for each environment variable.
Read more >Create and Modify Environment Variables on Windows
To create or modify environment variables on Windows 10: On the Windows taskbar, right-click the Windows icon and select System. In the Settings...
Read more >How To Set Environment Variables
Setting environment variables in Windows using the GUI is hidden behind several layers of settings dialogs. To open the respective interface you ...
Read more >Build environment variables
Identify environment variables available in the build environment, set your own environment variables, and use environment variables during builds.
Read more >Configuring Environment Variables and Secrets
Click on Environment in the left pane, and then click on Add Environment Variable. Service environment. Enter the Key and Value for your...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You can start with passing env to both. Then if an issue is reported with this behavior, we can split it up.
Would it make sense to have the
env:
variables be accessible to both the build and start stages? That might help here.