Merge devenv.sh with webodm.sh and allow --media to be used during development

[NicksonYap]

How did you install WebODM? (Docker, natively, ...)?

Docker

What's your browser and operating system? (Copy/paste the output of https://www.whatismybrowser.com/)

Chrome 72 on Linux Ubuntu 16.04 https://whatismybrowser.com/w/L9HHM9Q

What is the problem?

Cloned latest repo at 3d3c6164f618c5ee452013f593b8ee9e278b59af

After running successfully: ./devenv.sh start

Error in webpage:

Console output/steps: consoleoutput.txt

What should be the expected behavior?

Should be a normal login page

How can we reproduce this? (What steps did you do to trigger the problem? What parameters are you using for processing? If possible please include a copy of your dataset uploaded on Google Drive or Dropbox. Be detailed)

Just clone new repo, run:

./webodm.sh start (works normally)
./webodm.sh stop 
 ./devenv.sh start

Produces the error shown in screenshot above

The following is my SSD partitioning

I had issue when using exFAT (unable to create symlink)

[NicksonYap]

I found the way to fix

I was aware this issue is related with the fact that envdev.sh does not work well with webdom.sh start --media_dir XXXXX

So when resetting docker I have deleted containers and images, but forgot to delete volumes.

docker volume rm webodm_appmedia 
docker volume rm webodm_dbdata

So the actual issue is that envdev.sh should work with--media_dir XXXXXor that the development should be able to be activated with webdom.sh start --media_dir XXXXX --dev

[pierotofy]

Hey @NicksonYap :hand: thanks for sharing your findings! You are correct in that the devenv.sh script could probably be merged with webodm.sh via a --dev flag. I will leave this issue open and mark it as an improvement.

[pierotofy]

This is now done (in febsprint branch).