I wonder if somebody could provide me with some insights on the difference between
APP/bin/APP start and
APP/bin/APP foreground, apart from the obvious (daemon like behaviour vs direct output).
We have some strange behaviour in our app when ran with ‘start’ (from using edeliver) rather than with foreground. More specific, we have some tasks running with Quantum and when using
start they are registered and run multiple times (typically twice) and they also use old stale code (an outdated Ecto schema). When starting the app with
foreground everything runs fine.
For now we only see this behaviour on our staging server, but since staging and prod are almost identical we are stressing deploying to production.