Skip to content

Habitat plan#29

Open
themightychris wants to merge 3 commits intoLever-age:developfrom
themightychris:develop
Open

Habitat plan#29
themightychris wants to merge 3 commits intoLever-age:developfrom
themightychris:develop

Conversation

@themightychris
Copy link
Copy Markdown

@themightychris themightychris commented Dec 28, 2016

Work-in-progress to make the habitat frontend deployable via habitat

This plan will:

  • Install frontend files
  • Supervise leverage-api
    • Configure
    • Launch
  • Supervise nginx
    • Configure
    • Launch

@themightychris themightychris mentioned this pull request Dec 28, 2016
4 tasks
@lottspot
Copy link
Copy Markdown
Contributor

I don't love having these files managed directly in the frontend repository since they concern deployment rather than development (not to mention they concern an experimental deployment rather than the production deployment). I think I would prefer to see these files checked in to a dedicated repository.

@lottspot lottspot mentioned this pull request Dec 28, 2016
3 tasks
@themightychris
Copy link
Copy Markdown
Author

@lottspot at this point i'm not really looking for these PRs to actually be merged, I just want to see what I can get working in these branches and have a place to discuss and take notes

Once we have a good pattern though, I suspect there might be a case to be made that all repos include a way to deploy their goods. Every project having separate code and deployment repos sounds like it could get messy, but I guess it depends on how recipe patterns shake out

@lottspot
Copy link
Copy Markdown
Contributor

Ok.. not sure I agree about the marriage of application code and deployment boilerplate, but we can discuss further at a time and within a channel that makes more sense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants