Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/puppetlabs/iac
Infrastructure Automation Content Team Content
https://github.com/puppetlabs/iac
blog infrastructure-as-code puppet
Last synced: 14 days ago
JSON representation
Infrastructure Automation Content Team Content
- Host: GitHub
- URL: https://github.com/puppetlabs/iac
- Owner: puppetlabs
- License: apache-2.0
- Archived: true
- Created: 2019-12-02T10:32:40.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2023-07-31T14:37:27.000Z (over 1 year ago)
- Last Synced: 2024-09-28T02:43:21.102Z (4 months ago)
- Topics: blog, infrastructure-as-code, puppet
- Language: Ruby
- Homepage: https://puppetlabs.github.io/iac/?utm_source=github.com&utm_medium=repo_link
- Size: 27.1 MB
- Stars: 4
- Watchers: 9
- Forks: 24
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: CODEOWNERS
Awesome Lists containing this project
README
> 🏠 We've moved! Keep up with the latest developments on our new [micro-site](http://pup.pt/cat)!
# the public Infrastructure Automation Content Team page
This repo hosts the source for the [Infrastructure Automation Content Team's page](https://puppetlabs.github.io/iac/).
## Writing a blog post
Contributions from everyone are welcome!
See the [jekyll docs](https://jekyllrb.com/docs/posts/) for a quick intro on the mechanics.Please choose two categories for your post.
The first category should be a thing (like a tool, a module, or a technology),
the second category should be an activity (like development, testing, etc).
Tags can be anything that comes to mind, but please do look at other related posts to link with existing tags if possible.
Prefer singular over plural tags.When writing long-form text, please use [semantic line breaks](https://sembr.org/) to make reviewing and editing easier.
Use your puppetcommunity slack handle for the `author` field.
## Reviewing output
To review a blog post,
pull down the PR and run `bundle install && bundle exec jekyll serve --future`
to get a locally hosted webserver that allows access to the rendered pages.
This will allow you to check formatting, links, etc, as it will be presented on the site.## Ops-y things
On every push to main, the [deploy](./.github/workflows/deploy.yml) github action builds and deploys the current state to https://puppetlabs.github.io/iac/
Look at the [Jekyll Deploy action](https://github.com/puppetlabs/iac/actions?query=workflow%3A%22Jekyll+Deploy%22)
and the ["GitHub Pages" settings](https://github.com/puppetlabs/iac/settings)
to see if the build was successful.
Note that the github pages deployment is not very helpful with error messages.
The site is also rendered fresh every day at 02:00 UTC to publish new pages, if we already have scheduled pages for the future.