Task #2306 (new)
Opened 14 years ago
Last modified 14 years ago
Script-writing workflows — at Version 1
| Reported by: | wmoore | Owned by: | wmoore |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-Beta4.2 |
| Component: | General | Version: | n.a. |
| Keywords: | n.a. | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | 2010-04-30 (8) |
Description (last modified by wmoore)
Document typical script-writing workflows for admins and users. Both for our use in developing and testing the workflow, and for web-site documentation.
Intro
If you are planning to spend a significant amount of time developing scripts to run on an OMERO server, you may find it worthwhile to install an instance of the server on your own machine. This will give you admin privileges, and allow you direct access to the various files generated on the server by the scripting service.
Admins
It is assumed that scripts written by a server admin are "trusted" to run on the server without causing any disruption or security risks.
- Write script
- Upload script
Change History (1)
comment:1 Changed 14 years ago by wmoore
- Description modified (diff)
- Owner set to wmoore
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
