Skip to content

Commit 58e8811

Browse files
HeyItsGilbertclaude
HeyItsGilbert
and
claude
committed
fix(content): restore content dropped as raw HTML under Goldmark unsafe:false
Two pages lost real content because `markup.goldmark.renderer.unsafe` is false (kept for security) and Goldmark silently drops anything that looks like raw HTML: - Podcast 238 IRC log: leading `<nick>` lines parsed as HTML tags and stripped. Escaped the angle brackets (`\<nick\>`) so the names render while the `<http://...>` autolinks stay clickable. - MobileShell RBAC article: a botched WordPress conversion left the setup script as an inline code span exploded across blank lines, pushing the `<?xml?>` block and `<!-- -->` comment outside any code context. Rebuilt it as a fenced `powershell` block so it renders verbatim. `hugo --gc --minify` now emits no raw-html warnings and both pages render their full content with unsafe:false retained. Closes #23 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent c5d866f commit 58e8811

2 files changed

Lines changed: 48 additions & 221 deletions

‎content/articles/2011-05-18-configuring-rbac-for-mobileshell-in-powergui-pro-3-0.md‎

Lines changed: 14 additions & 187 deletions
Original file line numberDiff line numberDiff line change
@@ -24,203 +24,30 @@ Any user who will access MobileShell needs to be a member of the PowerGUI Mobile
2424

2525
With your MobileShell users configured, you can now associate PowerPacks with different AD users and groups.  When a user logs on to MobileShell, they are presented with any PowerPacks that are associated with their user account or with any groups in which their user account is a member. MobileShell PowerPack configuration is done via a simple xml file.  The file does not exist by default, so you need to create it.  Invoke the following PowerShell script on your MobileShell server to create and open the configuration xml file:
2626

27+
```powershell
28+
$programDataPath = [Environment]::GetFolderPath('CommonApplicationData')
29+
$powerGUIDataPath = 'Quest Software\PowerGUI Pro'
30+
$folder = Join-Path -Path $programDataPath -ChildPath $powerGUIDataPath
2731
28-
`$programDataPath
29-
30-
=
31-
32-
[
33-
34-
Environment
35-
36-
]::
37-
38-
GetFolderPath
39-
40-
(
41-
42-
'
43-
44-
CommonApplicationData
45-
46-
'
47-
48-
)
49-
50-
51-
$powerGUIDataPath
52-
53-
=
54-
55-
'
56-
57-
Quest Software\PowerGUI Pro
58-
59-
'
60-
61-
62-
$folder
63-
64-
=
65-
66-
Join-Path
67-
68-
-Path
69-
70-
$programDataPath
71-
72-
-ChildPath
73-
74-
$powerGUIDataPath
75-
76-
77-
if
78-
79-
(
80-
81-
-not
82-
83-
(
84-
85-
Test-Path
86-
87-
-LiteralPath
88-
89-
$folder
90-
91-
)) {
92-
93-
94-
    New-Item
95-
96-
-ItemType
97-
98-
Directory
99-
100-
-Path
101-
102-
$folder
103-
104-
|
105-
106-
Out-Null
107-
108-
32+
if (-not (Test-Path -LiteralPath $folder)) {
33+
New-Item -ItemType Directory -Path $folder | Out-Null
10934
}
11035
36+
$configPath = Join-Path -Path $folder -ChildPath 'MobileShellConfig.xml'
11137
112-
$configPath
113-
114-
=
115-
116-
Join-Path
117-
118-
-Path
119-
120-
$folder
121-
122-
-ChildPath
123-
124-
'
125-
126-
MobileShellConfig.xml
127-
128-
'
129-
130-
131-
$configuration
132-
133-
=
134-
135-
@"
136-
137-
38+
$configuration = @"
13839
<?xml version="1.0" encoding="utf-8"?>
13940
140-
141-
 
142-
143-
144-
   
145-
146-
147-
     
148-
149-
150-
       
151-
152-
153-
       
154-
155-
156-
       
157-
158-
159-
       
160-
161-
162-
       
163-
164-
165-
       
166-
167-
168-
     
169-
170-
171-
   
172-
173-
174-
 
175-
176-
177-
  <!--
178-
179-
180-
   
181-
182-
183-
     
184-
185-
186-
       
187-
188-
189-
       
190-
191-
192-
     
193-
194-
195-
   
196-
197-
198-
  -->
199-
200-
41+
<!--
42+
-->
20143
"@
20244
45+
$configuration | Out-File -FilePath $configPath -Encoding UTF8
20346
204-
$configuration
205-
206-
|
207-
208-
Out-File
209-
210-
-FilePath
211-
212-
$configPath
213-
214-
-Encoding
215-
216-
UTF8
217-
218-
219-
notepad
220-
221-
$configPath
47+
notepad $configPath
48+
```
22249

223-
`Once you have the configuration file open, you will see the layout that is used to associate AD user or group SIDs with PowerPacks.  Copy all of the core PowerPacks that you have in the PowerPacks subfolder of your PowerGUI Pro installation folder that you want to use via the MobileShell UI into the same path where this file was created (the value of the $folder variable in the script above contains this path).  Then modify this file to contain only the PowerPacks you copied over, update the first User SID for your user account, and this will finish off the initial configuration of PowerPacks for MobileShell.  If you want to add additional users, you can copy and paste the User node in the XML document and then modify the SID for the users you add.  Retrieving a SID should be an easy task of course: simply use Get-QADUser from the Quest AD cmdlets!![Smile](http://kirkmunro.files.wordpress.com/2011/05/wlemoticon-smile.png?w=595)
50+
Once you have the configuration file open, you will see the layout that is used to associate AD user or group SIDs with PowerPacks.  Copy all of the core PowerPacks that you have in the PowerPacks subfolder of your PowerGUI Pro installation folder that you want to use via the MobileShell UI into the same path where this file was created (the value of the $folder variable in the script above contains this path).  Then modify this file to contain only the PowerPacks you copied over, update the first User SID for your user account, and this will finish off the initial configuration of PowerPacks for MobileShell.  If you want to add additional users, you can copy and paste the User node in the XML document and then modify the SID for the users you add.  Retrieving a SID should be an easy task of course: simply use Get-QADUser from the Quest AD cmdlets!![Smile](http://kirkmunro.files.wordpress.com/2011/05/wlemoticon-smile.png?w=595)
22451

22552
Note: With this beta release there is a bug in the Groups support in this configuration document, so simply associate PowerPacks to users for now.  Thanks!
22653

‎content/podcast/2013-08-14-episode-238-powerscripting-podcast-glenn-block-jim-christopher-on-scriptcs.md‎

Lines changed: 34 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -100,9 +100,9 @@ aliases:
100100

101101
#### Chatroom Buzz
102102

103-
<BellyTimber> <http://poshcode.org/4325>
103+
\<BellyTimber\> <http://poshcode.org/4325>
104104
 <http://webbrain.com/brainpage/brain/4685C1B4-FE68-2D62-3AFA-CE674E67F742#-638>
105-
<MikeFRobbins> irm -Uri http://feeds.feedburner.com/PowerScripting | where title -like \*jim\*christopher* | select title
105+
\<MikeFRobbins\> irm -Uri http://feeds.feedburner.com/PowerScripting | where title -like \*jim\*christopher* | select title
106106

107107
 <http://scriptcs.net/>
108108
 <http://www.nuget.org/>
@@ -113,7 +113,7 @@ aliases:
113113

114114
 <https://github.com/scriptcs/scriptcs-samples/tree/master/wpf>
115115
scriptcs sublime plugin - <https://github.com/scriptcs/scriptcs-sublime>
116-
<beefarino> ouch: <http://visualstudiomagazine.com/articles/2013/08/07/devs-angry-over-msdn-redesign.aspx>
116+
\<beefarino\> ouch: <http://visualstudiomagazine.com/articles/2013/08/07/devs-angry-over-msdn-redesign.aspx>
117117
scriptcs webapi script pack + example <https://github.com/scriptcs/scriptcs-webapi>
118118
 <http://www.youtube.com/watch?v=cKqKrH0O9yg>
119119
 <http://msdn.microsoft.com/en-us/library/dd460648.aspx>
@@ -122,39 +122,39 @@ aliases:
122122
Re Roslyn check out this session from PDC \*\*08\*\* at about time index 1:04:00 <http://channel9.msdn.com/Blogs/pdc2008/TL16>
123123
 [http://en.wikipedia.org/wiki/Virtual_Audio_Cable][2]
124124
Jaykul: It's pretty interesting. He mentions that there is a little Roslyn in VS2013. The Roslyn portion starts around 34minutes in. <http://channel9.msdn.com/Events/Build/2013/9-006>
125-
<BellyTimber> <http://theoatmeal.com/blog/fix_computer>
126-
<sepeck> BellyTimber: <http://channel9.msdn.com/> <-- has lots and lots of coding stuff on it as well
127-
<ScriptingWife> <http://csharpening.net/>
128-
<beefarino> BTW, here's the ScriptCS powershell module: <https://github.com/beefarino/ScriptCS-PowerShell-Module>
129-
<MikeFRobbins> Here's my library: [http://mikefrobbins.files.wordpress.com/2013/08/library.jpg](http://mikefrobbins.files.wordpress.com/2013/08/library.jpg)
130-
<sepeck> halr9000: <http://calibre-ebook.com/> makes it go away
131-
<BellyTimber> <http://www.codinghorror.com/blog/2010/09/go-that-way-really-fast.html>
125+
\<BellyTimber\> <http://theoatmeal.com/blog/fix_computer>
126+
\<sepeck\> BellyTimber: <http://channel9.msdn.com/> <-- has lots and lots of coding stuff on it as well
127+
\<ScriptingWife\> <http://csharpening.net/>
128+
\<beefarino\> BTW, here's the ScriptCS powershell module: <https://github.com/beefarino/ScriptCS-PowerShell-Module>
129+
\<MikeFRobbins\> Here's my library: [http://mikefrobbins.files.wordpress.com/2013/08/library.jpg](http://mikefrobbins.files.wordpress.com/2013/08/library.jpg)
130+
\<sepeck\> halr9000: <http://calibre-ebook.com/> makes it go away
131+
\<BellyTimber\> <http://www.codinghorror.com/blog/2010/09/go-that-way-really-fast.html>
132132
http://www.hanselminutes.com/161/bbss-and-wildcat-from-mustang-software
133133
we have an org, <https://github.com/scriptcs>
134-
<11beefarino> #### this one is for beefarino: how does one maintain such a ruggedly handsome demeanor?
135-
<11BellyTimber> ##What's the difference?
136-
<1BrendanLiamT> ### will this be recorded?
137-
<0halr9000> ## asdfasdfasdf
138-
<2gblock> ##### hashmark people ####
139-
<11BellyTimber> ## Will the beef guy have anymore brain teasers?
140-
<11sepeck> ## link to scriptcs? site
141-
<11BellyTimber> ## All the code gets compiled and outputs an exe?
142-
<12DougFinke> ## LinqPad just announced a command line. Any thoughts? Have they approached you about using Scriptcs?
143-
<5MarcoShaw> ## How "official" is ScriptCS? Will Server 2014 be written in ScriptCS? PowerShell first, then ScriptCS...
144-
<0halr9000> ## like this: what's MEF
145-
<6jrusbatch> ## Is scriptcs extensible at all?
146-
<12DougFinke> ## Some folks are concerned that Scriptcs is built on Roslyn, a CTP and the ecosystem is not there. What do you think?
147-
<0Jaykul> ## Is Roslyn EVER going to actually ship?
148-
<0Jaykul> ## Why is ScriptCS built on Roslyn instead of Mono's (already shipped) REPL?
149-
<0halr9000> that's what the ## are for
150-
<0halr9000> json2: ### HASHMARK PEOPLE ####
151-
<0halr9000> ## OCTOTHORPE PEOPLE ##
152-
<0halr9000> ## json2: What's the "killer app" use case for ScriptCS? Give me a concrete example of something that I can use it for to solve a problem today.
153-
<11sepeck> ## are you goign to do a singing quartet afterwards?
154-
<3HalsWife> ##Blister in the Sun first pleasethankyou
155-
<4Keith_> ## Do you thinking using Roslyn would allow you to build an effective in-app scripting solution complete with Intellisense and debugging similar to VBA?
156-
<12json2> ## Doesnt Roslyn already permit loading/running .cs at runtime? What does ScriptCS add to the "WoW/LUA-like" scripting story?
157-
<14ScriptingWife> ## Up Next Rob Willis and PowerShell Deployment Toolkit
134+
\<11beefarino\> #### this one is for beefarino: how does one maintain such a ruggedly handsome demeanor?
135+
\<11BellyTimber\> ##What's the difference?
136+
\<1BrendanLiamT\> ### will this be recorded?
137+
\<0halr9000\> ## asdfasdfasdf
138+
\<2gblock\> ##### hashmark people ####
139+
\<11BellyTimber\> ## Will the beef guy have anymore brain teasers?
140+
\<11sepeck\> ## link to scriptcs? site
141+
\<11BellyTimber\> ## All the code gets compiled and outputs an exe?
142+
\<12DougFinke\> ## LinqPad just announced a command line. Any thoughts? Have they approached you about using Scriptcs?
143+
\<5MarcoShaw\> ## How "official" is ScriptCS? Will Server 2014 be written in ScriptCS? PowerShell first, then ScriptCS...
144+
\<0halr9000\> ## like this: what's MEF
145+
\<6jrusbatch\> ## Is scriptcs extensible at all?
146+
\<12DougFinke\> ## Some folks are concerned that Scriptcs is built on Roslyn, a CTP and the ecosystem is not there. What do you think?
147+
\<0Jaykul\> ## Is Roslyn EVER going to actually ship?
148+
\<0Jaykul\> ## Why is ScriptCS built on Roslyn instead of Mono's (already shipped) REPL?
149+
\<0halr9000\> that's what the ## are for
150+
\<0halr9000\> json2: ### HASHMARK PEOPLE ####
151+
\<0halr9000\> ## OCTOTHORPE PEOPLE ##
152+
\<0halr9000\> ## json2: What's the "killer app" use case for ScriptCS? Give me a concrete example of something that I can use it for to solve a problem today.
153+
\<11sepeck\> ## are you goign to do a singing quartet afterwards?
154+
\<3HalsWife\> ##Blister in the Sun first pleasethankyou
155+
\<4Keith_\> ## Do you thinking using Roslyn would allow you to build an effective in-app scripting solution complete with Intellisense and debugging similar to VBA?
156+
\<12json2\> ## Doesnt Roslyn already permit loading/running .cs at runtime? What does ScriptCS add to the "WoW/LUA-like" scripting story?
157+
\<14ScriptingWife\> ## Up Next Rob Willis and PowerShell Deployment Toolkit
158158

159159
#### The Question -
160160

0 commit comments

Comments
 (0)