Conform with umbrella app, distillery and edeliver about conform

[coryodaniel]

I'm having the same issue using Conform 2.1.1 and Distillery 0.10.1. I found another issue where it seems to be solved, but I could not get it to work either. My release VSN directory is missing the schema and conf files. See attached screen shots.

distillery and conform non-umbrella

distillery and conform umbrella

[coryodaniel]

I have tried this with the master branches of conform and distillery and still have no luck.

[coryodaniel]

@akurkin you may want to hop over to this ticket if you are experiencing issues!

[coryodaniel]

@akurkin Would you mind taking a peek at this PR to see if it solves your problem? ->

#94

[akurkin]

@coryodaniel sure, I'm more than happy to try it out :) hopefully will get back to it this week. Does your change fixes the way mix tasks work or should I manually place schema files in apps?

[coryodaniel]

@akurkin changes the plugin that the release mix task uses. It'll grab each of the conform configs/schemas and merge them together to make one for the whole umbrella. It only ends up in the release since its generated.

[akurkin]

@coryodaniel I've tried last week, it turned out at a first glance that generated sys.config was in different format than in the one generated by distillery from master branch. I.e. it contained all files merged, but they were merged but not flatten. Too bad I didn't save the output file, I'm going to give a shot one more time and hopefully provide more useful info.

[bitwalker]

@akurkin Were you able to confirm if there was an issue?

[akurkin]

@bitwalker @coryodaniel today we've tried converting configs for all in-umbrella apps using latest conform and distillery releases, and all worked smoothly - merging configs into one (at rel/<app>/var/sys.config) and then starting an app, so I think this issue can be closed, thanks much for hard work on this, seems a really big step forward for making it easier to run and release elixir apps! 🙇 👏 🐝

the next steps left for us to figure out how to put symlinks of .conf files into generated release, so that configuration can be separated from release (perhaps via plugin functionality in distillery?) - so please let me know if you have any thoughts, otherwise I think this issue can be closed

[bitwalker]

@akurkin You can simply use the RELEASE_CONFIG_DIR environment variable to have the release look in a different location for the configs - no need to symlink :)