Hi Evan,
It gives 404 with no more errors in logfiles. Of course, it's in production mode.
I've just tried to simulate it:
- removed all ebin/*.beam, moved existing src/view/x/y.html to /tmp
- rebar compile
- init.sh start
- app returns HTTP 404 for the specified page (this is OK)
- now /tmp/y.html moved back to src/view/x/y.html
- rebar compile, ebin/appname_view_x_y.beam exists
- init.sh reload
- "loading routes from bla bla bla..." appears in log
- app still returns HTTP 404 for /x/y URI
- init.sh attach; l(appname_view_x_y) gives {ok, appname_view_x_y}, but still HTTP 404 on the web
- boss_load:reload_all() by hand on eshell -- still no errors, and {module, appname_view_x_y} IS member of the returned array!
...I really don't know what's wrong, but it seems that even if the module is loaded correctly, it won't get rendered and reports (if the error handling routes are disabled) well known message [The requested template ("src/view/home/dashboard.{dtl,html,txt,jade,eex}") was not found. Additionally, no handler was found for processing 404 errors. You probably want to modify ../weberp/priv/weberp.routes to prevent errors like this one."].
After '
./init.sh restart', everything works again. It's a regular CB from your github, thus no hacks:
$ git describe master
v0.8.7-39-g05e20a7...we only use model_manager other than default but I don't think this is the problem.
Tom