share powershell scripts on-site

apiVersion: soultec.ch/v1kind: Postmetadata: name: my-solution-to-share-powershell-scripts locale: en labels: author: dario-doerflinger capability/automation: 1.81 capability/devops: 3.16 vendor/vmware: 0.98 annotations: source: blog-content/posts/en/my-solution-to-share-powershell-scripts.md route: /en/insights/my-solution-to-share-powershell-scripts/ schema: /nerd/schema/posts.json markdown: /en/insights/my-solution-to-share-powershell-scripts.mdspec: title: share powershell scripts on-site date: 2017-07-18 author: dario-doerflinger locale: en summary: >- If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over. capabilities: [automation, devops] vendors: [vmware] hero: /blog-assets/my-solution-to-share-powershell-scripts/hero.webp legacySlug: my-solution-to-share-powershell-scripts migrated: 2026-08-24 draft: false sections: - body: | If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over. So over the years I have written many PowerCLI scripts to automate one thing or another and saved it somewhere on my disk. When a co-worker asked me about some things he wanted to automate I always had done something similar in the past and wanted to share it with him. Exchange filters prohibit sending .ps1 file so we had to copy past in txt form and send over e-mail. This is a very outdated approach. A couple of months ago I got sick of this an was looking for a platform to share such things. I could not do that publicly (because scripts I write on company time are company property) so I was looking for a solution to have on-premise. Enter GitLab Community Edition (https://about.gitlab.com/ ). It was very easy to install and configure. (I'm not going to write about the details of the installation, because it depends which underlaying OS you want to use, and the site itself has good instructions). We now have a semi-public (user access management) GitLab which all of our engineers can access on the road and download the repositories to their laptops. This way they can update older scripts, add new scripts and in general benefit from the work our team does everyday without having the reinvent the wheel every time a new requirement comes up. I urge you to set up a GitLab for yourself, even if it is just you that works on it. The versioning and availability is just awesome when it comes to saving your hard work somewhere besides the hard disk (and some backups, of course).status: corpus: 315 alsoLike: - {ref: services/orchestration-automation, score: 0.80} - {ref: posts/breaking-and-fixing-gitlab, score: 0.75} - {ref: solutions/vmware/vmware-cloud-foundation/vcf-automation, score: 0.72} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "my-solution-to-share-powershell-scripts", "locale": "en", "labels": { "author": "dario-doerflinger", "capability/automation": 1.81, "capability/devops": 3.16, "vendor/vmware": 0.98 }, "annotations": { "source": "blog-content/posts/en/my-solution-to-share-powershell-scripts.md", "route": "/en/insights/my-solution-to-share-powershell-scripts/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/my-solution-to-share-powershell-scripts.md" } }, "spec": { "title": "share powershell scripts on-site", "date": "2017-07-18", "author": "dario-doerflinger", "locale": "en", "summary": "If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.", "capabilities": [ "automation", "devops" ], "vendors": [ "vmware" ], "hero": "/blog-assets/my-solution-to-share-powershell-scripts/hero.webp", "legacySlug": "my-solution-to-share-powershell-scripts", "migrated": "2026-08-24", "draft": false, "sections": [ { "body": "If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.\n\nSo over the years I have written many PowerCLI scripts to automate one thing or another and saved it somewhere on my disk. When a co-worker asked me about some things he wanted to automate I always had done something similar in the past and wanted to share it with him. Exchange filters prohibit sending .ps1 file so we had to copy past in txt form and send over e-mail. This is a very outdated approach.\n\nA couple of months ago I got sick of this an was looking for a platform to share such things. I could not do that publicly (because scripts I write on company time are company property) so I was looking for a solution to have on-premise.\n\nEnter GitLab Community Edition (https://about.gitlab.com/ ). It was very easy to install and configure. (I'm not going to write about the details of the installation, because it depends which underlaying OS you want to use, and the site itself has good instructions).\n\nWe now have a semi-public (user access management) GitLab which all of our engineers can access on the road and download the repositories to their laptops.\n\nThis way they can update older scripts, add new scripts and in general benefit from the work our team does everyday without having the reinvent the wheel every time a new requirement comes up.\n\nI urge you to set up a GitLab for yourself, even if it is just you that works on it. The versioning and availability is just awesome when it comes to saving your hard work somewhere besides the hard disk (and some backups, of course)." } ] }, "status": { "corpus": 315, "alsoLike": [ { "ref": "services/orchestration-automation", "score": "0.80" }, { "ref": "posts/breaking-and-fixing-gitlab", "score": "0.75" }, { "ref": "solutions/vmware/vmware-cloud-foundation/vcf-automation", "score": "0.72" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Post"[metadata]name = "my-solution-to-share-powershell-scripts"locale = "en"[metadata.labels]author = "dario-doerflinger""capability/automation" = 1.81"capability/devops" = 3.16"vendor/vmware" = 0.98[metadata.annotations]source = "blog-content/posts/en/my-solution-to-share-powershell-scripts.md"route = "/en/insights/my-solution-to-share-powershell-scripts/"schema = "/nerd/schema/posts.json"markdown = "/en/insights/my-solution-to-share-powershell-scripts.md"[spec]title = "share powershell scripts on-site"date = 2017-07-18author = "dario-doerflinger"locale = "en"summary = "If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over."capabilities = ["automation", "devops"]vendors = ["vmware"]hero = "/blog-assets/my-solution-to-share-powershell-scripts/hero.webp"legacySlug = "my-solution-to-share-powershell-scripts"migrated = 2026-08-24draft = false[[spec.sections]]body = '''If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.So over the years I have written many PowerCLI scripts to automate one thing or another and saved it somewhere on my disk. When a co-worker asked me about some things he wanted to automate I always had done something similar in the past and wanted to share it with him. Exchange filters prohibit sending .ps1 file so we had to copy past in txt form and send over e-mail. This is a very outdated approach.A couple of months ago I got sick of this an was looking for a platform to share such things. I could not do that publicly (because scripts I write on company time are company property) so I was looking for a solution to have on-premise.Enter GitLab Community Edition (https://about.gitlab.com/ ). It was very easy to install and configure. (I'm not going to write about the details of the installation, because it depends which underlaying OS you want to use, and the site itself has good instructions).We now have a semi-public (user access management) GitLab which all of our engineers can access on the road and download the repositories to their laptops.This way they can update older scripts, add new scripts and in general benefit from the work our team does everyday without having the reinvent the wheel every time a new requirement comes up.I urge you to set up a GitLab for yourself, even if it is just you that works on it. The versioning and availability is just awesome when it comes to saving your hard work somewhere besides the hard disk (and some backups, of course).'''[status]corpus = 315search = "/en/search.json"[[status.alsoLike]]ref = "services/orchestration-automation"score = "0.80"[[status.alsoLike]]ref = "posts/breaking-and-fixing-gitlab"score = "0.75"[[status.alsoLike]]ref = "solutions/vmware/vmware-cloud-foundation/vcf-automation"score = "0.72"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Post"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>my-solution-to-share-powershell-scripts</name> <locale>en</locale> <labels> <author>dario-doerflinger</author> <entry key="capability/automation">1.81</entry> <entry key="capability/devops">3.16</entry> <entry key="vendor/vmware">0.98</entry> </labels> <annotations> <source>blog-content/posts/en/my-solution-to-share-powershell-scripts.md</source> <route>/en/insights/my-solution-to-share-powershell-scripts/</route> <schema>/nerd/schema/posts.json</schema> <markdown>/en/insights/my-solution-to-share-powershell-scripts.md</markdown> </annotations> </metadata> <spec> <title>share powershell scripts on-site</title> <date>2017-07-18</date> <author>dario-doerflinger</author> <locale>en</locale> <summary>If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.</summary> <capabilities> <item>automation</item> <item>devops</item> </capabilities> <vendors> <item>vmware</item> </vendors> <hero>/blog-assets/my-solution-to-share-powershell-scripts/hero.webp</hero> <legacySlug>my-solution-to-share-powershell-scripts</legacySlug> <migrated>2026-08-24</migrated> <draft>false</draft> <sections> <section> <body>If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.So over the years I have written many PowerCLI scripts to automate one thing or another and saved it somewhere on my disk. When a co-worker asked me about some things he wanted to automate I always had done something similar in the past and wanted to share it with him. Exchange filters prohibit sending .ps1 file so we had to copy past in txt form and send over e-mail. This is a very outdated approach.A couple of months ago I got sick of this an was looking for a platform to share such things. I could not do that publicly (because scripts I write on company time are company property) so I was looking for a solution to have on-premise.Enter GitLab Community Edition (https://about.gitlab.com/ ). It was very easy to install and configure. (I'm not going to write about the details of the installation, because it depends which underlaying OS you want to use, and the site itself has good instructions).We now have a semi-public (user access management) GitLab which all of our engineers can access on the road and download the repositories to their laptops.This way they can update older scripts, add new scripts and in general benefit from the work our team does everyday without having the reinvent the wheel every time a new requirement comes up.I urge you to set up a GitLab for yourself, even if it is just you that works on it. The versioning and availability is just awesome when it comes to saving your hard work somewhere besides the hard disk (and some backups, of course). </body> </section> </sections> </spec> <status> <corpus>315</corpus> <alsoLike> <item> <ref>services/orchestration-automation</ref> <score>0.80</score> </item> <item> <ref>posts/breaking-and-fixing-gitlab</ref> <score>0.75</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/vcf-automation</ref> <score>0.72</score> </item> </alsoLike> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "my-solution-to-share-powershell-scripts", "locale": "en", "labels": { "author": "dario-doerflinger", "capability/automation": 1.81, "capability/devops": 3.16, "vendor/vmware": 0.98, }, "annotations": { "source": "blog-content/posts/en/my-solution-to-share-powershell-scripts.md", "route": "/en/insights/my-solution-to-share-powershell-scripts/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/my-solution-to-share-powershell-scripts.md", }, }, "spec": { "title": "share powershell scripts on-site", "date": "2017-07-18", "author": "dario-doerflinger", "locale": "en", "summary": "If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.", "capabilities": ["automation", "devops"], "vendors": ["vmware"], "hero": "/blog-assets/my-solution-to-share-powershell-scripts/hero.webp", "legacySlug": "my-solution-to-share-powershell-scripts", "migrated": "2026-08-24", "draft": False, "sections": [ { "body": ( "If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.\n" "\n" "So over the years I have written many PowerCLI scripts to automate one thing or another and saved it somewhere on my disk. When a co-worker asked me about some things he wanted to automate I always had done something similar in the past and wanted to share it with him. Exchange filters prohibit sending .ps1 file so we had to copy past in txt form and send over e-mail. This is a very outdated approach.\n" "\n" "A couple of months ago I got sick of this an was looking for a platform to share such things. I could not do that publicly (because scripts I write on company time are company property) so I was looking for a solution to have on-premise.\n" "\n" "Enter GitLab Community Edition (https://about.gitlab.com/ ). It was very easy to install and configure. (I'm not going to write about the details of the installation, because it depends which underlaying OS you want to use, and the site itself has good instructions).\n" "\n" "We now have a semi-public (user access management) GitLab which all of our engineers can access on the road and download the repositories to their laptops.\n" "\n" "This way they can update older scripts, add new scripts and in general benefit from the work our team does everyday without having the reinvent the wheel every time a new requirement comes up.\n" "\n" "I urge you to set up a GitLab for yourself, even if it is just you that works on it. The versioning and availability is just awesome when it comes to saving your hard work somewhere besides the hard disk (and some backups, of course)." ), }, ], }, "status": { "corpus": 315, "alsoLike": [ { "ref": "services/orchestration-automation", "score": "0.80", }, { "ref": "posts/breaking-and-fixing-gitlab", "score": "0.75", }, { "ref": "solutions/vmware/vmware-cloud-foundation/vcf-automation", "score": "0.72", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Post' metadata = [ordered]@{ name = 'my-solution-to-share-powershell-scripts' locale = 'en' labels = [ordered]@{ author = 'dario-doerflinger' 'capability/automation' = 1.81 'capability/devops' = 3.16 'vendor/vmware' = 0.98 } annotations = [ordered]@{ source = 'blog-content/posts/en/my-solution-to-share-powershell-scripts.md' route = '/en/insights/my-solution-to-share-powershell-scripts/' schema = '/nerd/schema/posts.json' markdown = '/en/insights/my-solution-to-share-powershell-scripts.md' } } spec = [ordered]@{ title = 'share powershell scripts on-site' date = '2017-07-18' author = 'dario-doerflinger' locale = 'en' summary = 'If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.' capabilities = @('automation', 'devops') vendors = @('vmware') hero = '/blog-assets/my-solution-to-share-powershell-scripts/hero.webp' legacySlug = 'my-solution-to-share-powershell-scripts' migrated = '2026-08-24' draft = $false sections = @( [ordered]@{ body = @'If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.So over the years I have written many PowerCLI scripts to automate one thing or another and saved it somewhere on my disk. When a co-worker asked me about some things he wanted to automate I always had done something similar in the past and wanted to share it with him. Exchange filters prohibit sending .ps1 file so we had to copy past in txt form and send over e-mail. This is a very outdated approach.A couple of months ago I got sick of this an was looking for a platform to share such things. I could not do that publicly (because scripts I write on company time are company property) so I was looking for a solution to have on-premise.Enter GitLab Community Edition (https://about.gitlab.com/ ). It was very easy to install and configure. (I'm not going to write about the details of the installation, because it depends which underlaying OS you want to use, and the site itself has good instructions).We now have a semi-public (user access management) GitLab which all of our engineers can access on the road and download the repositories to their laptops.This way they can update older scripts, add new scripts and in general benefit from the work our team does everyday without having the reinvent the wheel every time a new requirement comes up.I urge you to set up a GitLab for yourself, even if it is just you that works on it. The versioning and availability is just awesome when it comes to saving your hard work somewhere besides the hard disk (and some backups, of course).'@ } ) } status = [ordered]@{ corpus = 315 alsoLike = @( [ordered]@{ ref = 'services/orchestration-automation' score = '0.80' } [ordered]@{ ref = 'posts/breaking-and-fixing-gitlab' score = '0.75' } [ordered]@{ ref = 'solutions/vmware/vmware-cloud-foundation/vcf-automation' score = '0.72' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": map[string]any{ "name": "my-solution-to-share-powershell-scripts", "locale": "en", "labels": map[string]any{ "author": "dario-doerflinger", "capability/automation": 1.81, "capability/devops": 3.16, "vendor/vmware": 0.98, }, "annotations": map[string]any{ "source": "blog-content/posts/en/my-solution-to-share-powershell-scripts.md", "route": "/en/insights/my-solution-to-share-powershell-scripts/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/my-solution-to-share-powershell-scripts.md", }, }, "spec": map[string]any{ "title": "share powershell scripts on-site", "date": "2017-07-18", "author": "dario-doerflinger", "locale": "en", "summary": "If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.", "capabilities": []any{"automation", "devops"}, "vendors": []any{"vmware"}, "hero": "/blog-assets/my-solution-to-share-powershell-scripts/hero.webp", "legacySlug": "my-solution-to-share-powershell-scripts", "migrated": "2026-08-24", "draft": false, "sections": []any{ map[string]any{ "body": "If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.\n" + "\n" + "So over the years I have written many PowerCLI scripts to automate one thing or another and saved it somewhere on my disk. When a co-worker asked me about some things he wanted to automate I always had done something similar in the past and wanted to share it with him. Exchange filters prohibit sending .ps1 file so we had to copy past in txt form and send over e-mail. This is a very outdated approach.\n" + "\n" + "A couple of months ago I got sick of this an was looking for a platform to share such things. I could not do that publicly (because scripts I write on company time are company property) so I was looking for a solution to have on-premise.\n" + "\n" + "Enter GitLab Community Edition (https://about.gitlab.com/ ). It was very easy to install and configure. (I'm not going to write about the details of the installation, because it depends which underlaying OS you want to use, and the site itself has good instructions).\n" + "\n" + "We now have a semi-public (user access management) GitLab which all of our engineers can access on the road and download the repositories to their laptops.\n" + "\n" + "This way they can update older scripts, add new scripts and in general benefit from the work our team does everyday without having the reinvent the wheel every time a new requirement comes up.\n" + "\n" + "I urge you to set up a GitLab for yourself, even if it is just you that works on it. The versioning and availability is just awesome when it comes to saving your hard work somewhere besides the hard disk (and some backups, of course).", }, }, }, "status": map[string]any{ "corpus": 315, "alsoLike": []any{ map[string]any{ "ref": "services/orchestration-automation", "score": "0.80", }, map[string]any{ "ref": "posts/breaking-and-fixing-gitlab", "score": "0.75", }, map[string]any{ "ref": "solutions/vmware/vmware-cloud-foundation/vcf-automation", "score": "0.72", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Post", metadata: { name: "my-solution-to-share-powershell-scripts", locale: "en", labels: { author: "dario-doerflinger", "capability/automation": 1.81, "capability/devops": 3.16, "vendor/vmware": 0.98, }, annotations: { source: "blog-content/posts/en/my-solution-to-share-powershell-scripts.md", route: "/en/insights/my-solution-to-share-powershell-scripts/", schema: "/nerd/schema/posts.json", markdown: "/en/insights/my-solution-to-share-powershell-scripts.md", }, }, spec: { title: "share powershell scripts on-site", date: "2017-07-18", author: "dario-doerflinger", locale: "en", summary: "If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.", capabilities: ["automation", "devops"], vendors: ["vmware"], hero: "/blog-assets/my-solution-to-share-powershell-scripts/hero.webp", legacySlug: "my-solution-to-share-powershell-scripts", migrated: "2026-08-24", draft: false, sections: [ { body: "If you work in the field of VMware you tend to automate things as soon as the opportunity presents itself. Either to save time or to rid yourself of tedious work that repeats itself over and over.\n" + "\n" + "So over the years I have written many PowerCLI scripts to automate one thing or another and saved it somewhere on my disk. When a co-worker asked me about some things he wanted to automate I always had done something similar in the past and wanted to share it with him. Exchange filters prohibit sending .ps1 file so we had to copy past in txt form and send over e-mail. This is a very outdated approach.\n" + "\n" + "A couple of months ago I got sick of this an was looking for a platform to share such things. I could not do that publicly (because scripts I write on company time are company property) so I was looking for a solution to have on-premise.\n" + "\n" + "Enter GitLab Community Edition (https://about.gitlab.com/ ). It was very easy to install and configure. (I'm not going to write about the details of the installation, because it depends which underlaying OS you want to use, and the site itself has good instructions).\n" + "\n" + "We now have a semi-public (user access management) GitLab which all of our engineers can access on the road and download the repositories to their laptops.\n" + "\n" + "This way they can update older scripts, add new scripts and in general benefit from the work our team does everyday without having the reinvent the wheel every time a new requirement comes up.\n" + "\n" + "I urge you to set up a GitLab for yourself, even if it is just you that works on it. The versioning and availability is just awesome when it comes to saving your hard work somewhere besides the hard disk (and some backups, of course).", }, ], }, status: { corpus: 315, alsoLike: [ { ref: "services/orchestration-automation", score: "0.80", }, { ref: "posts/breaking-and-fixing-gitlab", score: "0.75", }, { ref: "solutions/vmware/vmware-cloud-foundation/vcf-automation", score: "0.72", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

share powershell scripts on-site

You might also like

Orchestration

Breaking and Fixing

VCF Automation