-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Umbrella - versioning - release updates #33
Comments
I've setup a fork of the oxo_umbrella to see if it was the project. |
Cleaned down. Repeated. I've put the committed_at version stamp on each of the child applications.
Perhaps obviously, this works. The miracle of sleep. I can see myself bumping the minor release when I push to production, but each minor for each feature I push to staging to preview, seems for a manual task to remember, a step I'd prefer not to take. So if I may adapt the question, is this a sane approach? If I've not altered the core application, it's getting a version bump anyway this way. My gut is saying roll with this till it's problem, along with a PR to the readme for umbrella's specifically. Thoughts? Footnotes Other considerations for umbrella is the npm like tasks in deploy and upgrade. Either alias or append paths.
|
Notes for myself; others, this article has a nice tweak on the version numbering.
Then in mix files
I'm not certain that's better, easier, but maybe not as traceable compared to git log bits. Perhaps ideal for the top level or child, but not both. |
I'm experimenting with a clean-ish umbrella app. Two apps, the core ( domain & db ) and a phoenix web app. A straight up initial deploy works fine and pushing produces suitable log noise to the effect it's released successfully and unpacked, made the 'release' permanent.
I'm using the git log version number in the umbrella project. The apps are fixed at 0.0.1 etc.
If I do a html change for example then push all as expected, log below. At this point, refreshing the app, there is no change. If I issue a /etc/init.d/briskoda_platform stop and start it loads, but still the old code.
This is the tail of the output:
Looks good.
If I touch the individual apps mix.exs to be 0.0.1 > 0.0.2 I get the appropriate appup file but again no hot reload.
At this point a manual stop and start works, the new code boots.
At this point having gone over things; issues here; issues on distillery; code etc, I'm at a loss for what I've missed. This is the greatest clue but those steps are covered of by the gatling process.
mix release --upgrade --upfrom=0.0.1484065140 --warnings-as-errors --env=prod
Anyone else got a simple umbrella app hot reloading?
The text was updated successfully, but these errors were encountered: