Conversation
|
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 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 |
|
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 |
Work-in-progress to make the habitat frontend deployable via habitat
This plan will:
leverage-api