Publishflow Block: Deploy view: Difference between revisions
From MoodleDocs
| Line 27: | Line 27: | ||
===Deploy in a default preset category=== | ===Deploy in a default preset category=== | ||
[ | [[Image:deploy_in_default_cat.jpg]] | ||
===Deploy with a key=== | ===Deploy with a key=== | ||
[image:deploy_w_key.jpg] | [image:deploy_w_key.jpg] | ||
Revision as of 21:20, 28 December 2010
This view is available on in a Course Factory mode. It will propose the possibility to publish the course to any of the proposed remote category.
Deploying is possible :
- Only from a Catalog or a combined Factory+Catalog.
- If MNET is enabled (obvious).
- If publishing services are setup between the Catalog and a Training node.
- If the user has a peer User record in the remote Training node (i.e. he must be a known user matching his current identity regarding the MNET operations).
- If the user has the 'block/publishflow:deploy' capability in his current profile resolution and comes from this node (considering his mnethostid).
- Or if the user has the 'block/publishflow:deployeverywhere' capability.
- If the course to publish has at least one backup in 'backupdata'. (Usually, the course backup that was published has been relocated in 'backupdata', so there is no special operation to get one available).
To deploy a course
Deploy in targetted remote category
- choose one of the targets for deployement
- choose a remote category to deploy the course
- Just click the "deploy" link
After the deployement you may be invited to browse back to the original course template, or jump to the deployed instance.
Deploy in a default preset category
Deploy with a key
[image:deploy_w_key.jpg]
