-
-
MacVoices Podcast With Chuck Joiner About The New Take Control Of OS X Server Book!
Yay, podcasts! Chuck Joiner was kind enough to have me on MacVoices. We did a show, now available at http://www.macvoices.com/macvoices-14223-charles-edge-helps-take-control-os-x-server Or if you’d like to watch on YouTube or inline: http://youtu.be/AeccoRqIrgc
-
Deleting a Podcast in Podcast Producer
In an earlier post I looked at querying feeds and removing objects from Podcast Producer in a somewhat broad manner. To delete a single podcast (not a feed), you need to first find the ID for the podcast, then delete the corresponding podcast bundle (pdb). Removing assets is one of the only processes with regards to Podcast Producer that isn’t intuitive, and it’s just waiting for someone to wrap these steps into a nice pretty GUI… To find the ID of the podcast, first let’s query the sql database for the title: sqlite3 /Volumes/pcp/PodcastProducer/Server/db.sqlite3 'SELECT * FROM episodes' | grep "TITLE" Note the date and the ID (the big long…
-
Scrubbing Assets from Podcast Producer
At some point, you may find that you would like to remove all episodes from Podcast Producer that were brought in using a specific workflow, or based on a specific keyword, a string in the title, a date, or the user that created the episodes. All of these attributes are trapped in the db.sqlite3 database for Podcast Producer. This database is stored in the Server directory of your shared library. Within this database there is a table called episodes. Using that table you can locate all episodes that match the given pattern. To query, you will use the sqlite3 command and identify the database path. A very basic incantation of…
-
Podcast Producer Workflow ACLs
When using Podcast Producer, the Podcast Capture client application will ask each user for a username and password. Armed with the authentication credentials. Once a podcast has been captured then the user will be provided with a list of workflows that they have access to. But where are these configured? They can be added and removed from Server Admin. And each can have a user, users, a group or groups that have access to use them. By limiting access to each workflow, based on the Workflow ACL, you can then limit who can access to different blogs, who can use various automations and even who can publish to an iTunes…