Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

azavea / tilegarden Public

Notifications You must be signed in to change notification settings
Fork 7
Star 98

Code
Issues 26
Pull requests 20
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

WIP: Make deployment scripts handle multi-environment deployment#140

Open

KlaasH wants to merge 4 commits intodevelopazavea/tilegarden:developfrom feature/multi-environment-deploymentazavea/tilegarden:feature/multi-environment-deploymentCopy head branch name to clipboard

+150-54

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Aug 4, 2019

Set up docker-compose and deploy scripts to use env-specific env files
KlaasH
committed
Remove default env file from docker-compose
KlaasH
committed
Add an ENVIRON variable and use it to set deployment name
KlaasH
committed
Adjust Terraform for multi-env setup
KlaasH
committed

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.