Skip to content

Commit 7ebc3f6

Browse files
arm4barm4b
committed
Fix GitHub naming
1 parent b3b9e14 commit 7ebc3f6

1 file changed

Lines changed: 13 additions & 13 deletions

File tree

‎2023/03/st2-github-action/index.html‎

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -31,15 +31,15 @@
3131
<meta name="google-site-verification" content="ovwnX0ej2kps4UuJ9NOzNjJcLOQD8JPDLNhe-hMYTMk">
3232
<meta name="robots" content="index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1">
3333

34-
<title>Github Action to deploy StackStorm to AWS</title>
34+
<title>GitHub Action to deploy StackStorm to AWS</title>
3535
<meta name="description"
36-
content="Announcing Github Action to deploy StackStorm to AWS on Github Marketplace and the power of Platform Engineering.">
36+
content="Announcing GitHub Action to deploy StackStorm to AWS on GitHub Marketplace and the power of Platform Engineering.">
3737
<link rel="canonical" href="/2023/03/st2-github-action/">
3838
<meta property="og:locale" content="en_US">
3939
<meta property="og:type" content="article">
40-
<meta property="og:title" content="Github Action to deploy StackStorm to AWS">
40+
<meta property="og:title" content="GitHub Action to deploy StackStorm to AWS">
4141
<meta property="og:description"
42-
content="Announcing Github Action to deploy StackStorm to AWS on Github Marketplace and the power of Platform Engineering.">
42+
content="Announcing GitHub Action to deploy StackStorm to AWS on GitHub Marketplace and the power of Platform Engineering.">
4343
<meta property="og:url" content="/2023/03/st2-github-action/">
4444
<meta property="og:site_name" content="StackStorm">
4545
<meta property="article:published_time" content="2022-12-02T00:00:00+00:00">
@@ -674,7 +674,7 @@
674674

675675
<div class="awr">
676676

677-
<h1 class="entry-title">Github Action to deploy StackStorm to AWS</h1>
677+
<h1 class="entry-title">GitHub Action to deploy StackStorm to AWS</h1>
678678

679679
<div class="awr-i">
680680
<p><strong>Mar 14, 2023</strong></p>
@@ -688,23 +688,23 @@ <h1 class="entry-title">Github Action to deploy StackStorm to AWS</h1>
688688
StackStorm installation and configuration pipeline fit your specific needs. Then you start benefiting from automation!
689689
</p>
690690
<p>
691-
At Bitovi we work a lot with CI/CD, Github Actions and we created an action that helps deploying StackStorm to AWS in
691+
At Bitovi we work a lot with CI/CD, GitHub Actions and we created an action that helps deploying StackStorm to AWS in
692692
under 15 minutes, including all the configuration. It’s a time-saving shortcut to get your deployment ready
693693
in the cloud.
694694
<span id="more-9809"></span>
695695
</p>
696696
<p>
697-
Today, we want to share it with the StackStorm community. Check the GHA on Github Marketplace:
697+
Today, we want to share it with the StackStorm community. Check the GHA on GitHub Marketplace:
698698
<a href="https://github.com/marketplace/actions/deploy-single-vm-stackstorm-to-aws-ec2" target="_blank">
699699
<img src="/wp/wp-content/uploads/2023/03//st2-gha-marketplace.png"
700-
alt="Github Action to deploy StackStorm ot AWS on Github Marketplace" />
700+
alt="GitHub Action to deploy StackStorm ot AWS on GitHub Marketplace" />
701701
</a>
702702
</p>
703703

704704
<hr class="wp-block-separator">
705705
<h3>Simple Configuration</h3>
706706
<p>
707-
To get started quickly, you will need to create a new Github repository, set your AWS credentials in the Github
707+
To get started quickly, you will need to create a new github repository, set your AWS credentials in the GitHub
708708
repository secrets, and configure <code>.github/workflows/st2.yaml</code>:
709709
</p>
710710
<p>
@@ -714,7 +714,7 @@ <h3>Simple Configuration</h3>
714714
Under the hood, it uses Terraform to provision the resources in AWS and Ansible to install and configure StackStorm.
715715
The following resources are created in AWS via Terraform: EC2 instance, Route53 records, a load balancer, security
716716
groups (ports 80, 443, 22), and optionally, a VPC with subnets. To make the Terraform configuration state persistent
717-
across the deployments, S3 bucket is created automatically. You can fine-tune the AWS configuration in Github Actions
717+
across the deployments, S3 bucket is created automatically. You can fine-tune the AWS configuration in GitHub Actions
718718
inputs, see
719719
<a href="https://github.com/marketplace/actions/deploy-single-vm-stackstorm-to-aws-ec2#customizing" target="_blank">AWS Configuration</a>.
720720
</p>
@@ -728,7 +728,7 @@ <h3>Advanced Configuration</h3>
728728
stackstorm configuration is needed, such as adjusting the st2.conf parameters, chatops, RBAC and LDAP, users,
729729
certificates, and more.
730730

731-
Here is an example Github workflow: <code>.github/workflows/st2.yaml</code>:
731+
Here is an example GitHub workflow: <code>.github/workflows/st2.yaml</code>:
732732
<script src="https://gist.github.com/armab/fc60416d7b3dd026ef84466e2d807133.js?file=github_workflows_st2_advanced.yaml"></script>
733733

734734
An example <code>st2_vars.yaml</code> you include in the repository with extra StackStorm configuration for <a
@@ -764,7 +764,7 @@ <h3>Live Webinar</h3>
764764
<center>
765765
<a href="https://my.demio.com/ref/jxCqbpBTjKhKLJdC" target="_blank">
766766
<img width="800" src="/wp/wp-content/uploads/2023/03/github-action-stackstorm-bitovi-webinar.gif"
767-
alt="Github Action to deploy StackStorm Webinar by Bitovi" />
767+
alt="GitHub Action to deploy StackStorm Webinar by Bitovi" />
768768
</a>
769769
</center>
770770
</p>
@@ -776,7 +776,7 @@ <h3>Live Webinar</h3>
776776
</p>
777777
<p>
778778
There’s more to show and tell. We’d like to invite everyone to join us live in a Webinar where we'll highlight the power
779-
of Platform Engineering, Github Actions, and StackStorm event-driven
779+
of Platform Engineering, GitHub Actions, and StackStorm event-driven
780780
automation. Join us on <i>April 4, 2023, 11am US Central / 9am US West / 6pm
781781
EU Central time</i>.
782782
</p>

0 commit comments

Comments
 (0)