Closes #2 (closed).
Introduces an interface to manage multiple triggers manually. The user now has an option to:
- Create new custom triggers;
- Edit triggers (including alias and URL);
- Run triggers on demand and receive a quick feedback (green light: all good, red light and error code: something's wrong);
- Delete triggers.
After the experimental result data is considered complete (not partial anymore), all the triggers will run simultaneously once again.
Users can also view the last timestamp when the trigger was run, the status of the run (good/bad) and a HTTP response code, in case the run failed. Last timestamp and last response code are saved in the database as attributes of the trigger.