Fix issue with environmental variables.

[nkabir]

Moving config.interpolate() before schema check to support interpolated variables in configuration file to address issue #107

All tests pass.

[ghost]

@nkabir thanks for this PR. As we say in #106, @ellmetha and I aren't maintaining this project anymore. @robvdl stepped in but he isn't sure if he'd be able to do it on his own. Would you be interested in stepping in?

[codecov-io]

Codecov Report

Merging #108 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #108   +/-   ##
=======================================
  Coverage   93.45%   93.45%           
=======================================
  Files          45       45           
  Lines        1269     1269           
=======================================
  Hits         1186     1186           
  Misses         83       83

Impacted Files	Coverage Δ
lxdock/conf/config.py	98.91% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b0f098...56fbc42. Read the comment docs.

[nkabir]

Sure. It would be helpful to have one or more people that have a history with the project to be available for occasional questions. It's a nice library and fits my needs quite well. I don't anticipate needing new features but would consider it a shame if it went unmaintained. If @robvdl will also be involved, we may be able to keep it alive.

[ghost]

@nkabir great, you're in!

I'll be available if you have questions or want to release a version, but otherwise I'm not planning on reviewing incoming PR.

[nkabir]

Understood. That should be fine. Thank you for a great library!

[robvdl]

Hi @nkabir thanks for your PR, and welcome aboard.

I plan on getting a bit more involved after Christmas as I have just one more week of work and then a month off, I only just got access myself just like you.

[nkabir]

Looking forward to it, @robvdl

[robvdl]

Although I did see this commit and it's pretty small and it's probably fine, I was going to try to merge it over the weekend. We should probably at least try to avoid self merging things into master, unless we merge into a develop branch it's OK.

One of the first things I wanted to change is not mark the project as unmaintained anymore.

We need to come up with some plans of how to go forward, what outstanding issues need to be resolved, or which ones don't make sense and just need to be answered.

I am pretty sure there is an IRC channel too, since we use IRC at work all day anyway, I will make a habit of being on there at least during work hours in NZ.

We should probably continue the conversation in #106 rather than here.

By the way @hsoft some people at work were excited to see a new maintainer to vagrant lxc, good luck with your work on that. I know they use a very custom version of vagrant and vagrant LXC now and are really excited to see vagrant LXC being worked on again, I doubt they want to be on this custom version.