doc: update RAEDME of dspot-web mojo

[borisbaldassari]

Refactor dspot-web to include dspot-mojo, a web interface for dspot + descartes demonstration.

[monperrus]

thanks for the pr.

the diff seems incorrect (too many changes + conflict), merge/rebase and recreate the PR?

[borisbaldassari]

Hey Martin,
Ok, I don't know what happened. Will do that end of next week (we have our Crossminer review Tuesday) and will let you know.

[monperrus]

cool! Git is sometimes mysterious :-)

[borisbaldassari]

Hey Martin, I believe the last commit should solve the merge issue. Please let me know if it works better now. Thanks, cheers! :-)

[coveralls]

Pull Request Test Coverage Report for Build 2496

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 22 unchanged lines in 3 files lost coverage.
• Overall coverage decreased (-0.4%) to 83.167%

---

Files with Coverage Reduction	New Missed Lines	%
dspot/src/main/java/eu/stamp_project/dspot/common/test_framework/AbstractTestFrameworkDecorator.java	3	28.57%
dspot/src/main/java/eu/stamp_project/dspot/common/test_framework/TestFramework.java	3	88.37%
dspot/src/main/java/eu/stamp_project/dspot/amplifier/SimpleInputAmplDistributor.java	16	75.76%

Totals
Change from base Build 2492:	-0.4%
Covered Lines:	4921
Relevant Lines:	5917

---

💛 - Coveralls

[monperrus]

Thanks.

On the demo machine:

root@dovh1$ hypnotoad
bash: hypnotoad: command not found
debian@dovh1:~$ hypnotoad
bash: hypnotoad: command not found

Where is hypnotoad?

[borisbaldassari]

Hypnotoad is part of the Mojolicious app, and is available as the dspot user. FYI the dspot web demo runs under the dspot user.

[monperrus]

OK, I can see it when I su dspot, thanks.

Next step, where is script/dspot_web on the machine?

[borisbaldassari]

It's in the dspot hierarchy, as cloned in the home of dspot user. Complete path should be something like ~/dspot/dspot-web/v2-mojo/script/dspot_web. Sorry for not being clear enough, do you want to setup a call to clarify everything smoothly and quickly? 😁 Le lun. 17 févr. 2020 à 19:51, Martin Monperrus <notifications@github.com> a écrit :

…

OK, I can see it when I su dspot, thanks. Next step, where is script/dspot_web on the machine? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#941?email_source=notifications&email_token=ABMT733LDPWUADL2XHCARH3RDLMB7A5CNFSM4KS5GEEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL7LX3Q#issuecomment-587119598>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMT735QUWMMDKUFOX5VV5DRDLMB7ANCNFSM4KS5GEEA> .

[monperrus]

~/dspot/dspot-web/v2-mojo/script/dspot_web yes! modified the README in this PR.

About the worker: how to stop it? how to check that it's up and running?'

[borisbaldassari]

The easiest way to check if the worker is running is to go to the admin UI at [1].
[1] https://dspot-demo.stamp-project.eu/admin/minion

From the sysadmin perspective, the worker is running inside a screen on the dspot server. To see it just run screen -r to re-attache the screen and you should see the worker running (it's a foreground process so there should be lines printed on stdout).

[monperrus]

Thanks, updated with this info b8fbe74

https://dspot-demo.stamp-project.eu/admin/minion says that it's working.

However, on the server, screen -r gives nothing, either as user dspot or as root.

Any idea?

[borisbaldassari]

However, on the server, screen -r gives nothing, either as user dspot or as root.

It should be run as user dspot, not root. And it should definitely work. It may be because I was connected and the screen process was indeed attached. In that case simply run screen -dr in order to detach it before re-attaching it.
I disconnected myself in any case so a simple screen -r should work now.

[monperrus]

OK, thanks a lot Boris for the last doc update.