mirror of
https://github.com/gogrlx/docs.grlx.dev.git
synced 2026-04-02 03:08:53 -07:00
initial content for file
This commit is contained in:
39
content/docs/Overview/_index.md
Normal file
39
content/docs/Overview/_index.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: Overview
|
||||
description: Here's where your user finds out if your project is for them.
|
||||
weight: 1
|
||||
---
|
||||
|
||||
{{% pageinfo %}}
|
||||
This is a placeholder page that shows you how to use this template site.
|
||||
{{% /pageinfo %}}
|
||||
|
||||
|
||||
The Overview is where your users find out about your project. Depending on the size of your docset, you can have a separate overview page (like this one) or put your overview contents in the Documentation landing page (like in the Docsy User Guide).
|
||||
|
||||
Try answering these questions for your user in this page:
|
||||
|
||||
## What is `grlx`?
|
||||
`grlx` is a tool for fleet-level configuration management written in Go.
|
||||
|
||||
## What is it?
|
||||
|
||||
Introduce your project, including what it does or lets you do, why you would use it, and its primary goal (and how it achieves it). This should be similar to your README description, though you can go into a little more detail here if you want.
|
||||
|
||||
## Why do I want it?
|
||||
|
||||
Help your user know if your project will help them. Useful information can include:
|
||||
|
||||
* **What is it good for?**: What types of problems does your project solve? What are the benefits of using it?
|
||||
|
||||
* **What is it not good for?**: For example, point out situations that might intuitively seem suited for your project, but aren't for some reason. Also mention known limitations, scaling issues, or anything else that might let your users know if the project is not for them.
|
||||
|
||||
* **What is it *not yet* good for?**: Highlight any useful features that are coming soon.
|
||||
|
||||
## Where should I go next?
|
||||
|
||||
Give your users next steps from the Overview. For example:
|
||||
|
||||
* [Getting Started](/docs/getting-started/): Get started with $project
|
||||
* [Examples](/docs/examples/): Check out some example code!
|
||||
|
||||
8
content/docs/Recipe Ingredients/_index.md
Normal file
8
content/docs/Recipe Ingredients/_index.md
Normal file
@@ -0,0 +1,8 @@
|
||||
---
|
||||
title: Recipe Ingredients
|
||||
description: The foundation of grlx
|
||||
weight: 1
|
||||
---
|
||||
Recipe ingredients are how we build configurations with `grlx`. They can be thought of as the building blocks for completing various file, service, or management operations.
|
||||
|
||||
## Components
|
||||
50
content/docs/Recipe Ingredients/file.md
Normal file
50
content/docs/Recipe Ingredients/file.md
Normal file
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: grlx.ingredients.file
|
||||
---
|
||||
## file.absent
|
||||
Deletes a file or directory
|
||||
### Parameters
|
||||
* _name_ (string,required): the name/path of the file to delete
|
||||
### Example
|
||||
```yaml
|
||||
file.absent:
|
||||
name: ~/.config/sytemd/user/backup.service
|
||||
```
|
||||
|
||||
## file.append
|
||||
Appends content to a file. Only appends the content if it doesn't exist.
|
||||
### Parameters
|
||||
* _name_ (string,required): the name/path of the file to delete
|
||||
* _text_ (string,required): the text to append to a file
|
||||
### Example
|
||||
```yaml
|
||||
file.append:
|
||||
- name: /etc/profile
|
||||
- text: |
|
||||
export PATH=$PATH:/usr/local/go/bin
|
||||
```
|
||||
|
||||
## file.contains
|
||||
Checks if a file contains a given selection. If multiple sources are provided, all must be satisfied.
|
||||
### Parameters
|
||||
* _name_ (string,required): the name/path of the file to check
|
||||
* _text_ (string): the item to search for
|
||||
* _source_ (string): a file source (such as HTTP, file, etc.) to reference
|
||||
* _source_hash_ (string): a hash for a given source
|
||||
* _sources_ (list): a list of sources to check against
|
||||
* _source_hashes_ (list): a list of source hashes
|
||||
* _skip_verify_ (boolean): whether to skip hash validation, false by default
|
||||
|
||||
|
||||
## file.directory
|
||||
Handles many directory operations. Ensures that a directory exists with the given permissions.
|
||||
### Parameters
|
||||
* _name_ (string,required): the name/path of the directory
|
||||
* _makedirs_ (bool): option to make directory if it doesn't exist, defaults to true
|
||||
* _user_ (string): the user who will own the directory
|
||||
* _group_ (string): the group who will own the directory
|
||||
* _dir_mode_ (string): the directory mode
|
||||
* _file_mode_ (string): the file mode to set
|
||||
* _recurse_ (bool): whether to recurse the directories and apply permissions
|
||||
### Example
|
||||
|
||||
29
content/docs/_index.md
Normal file
29
content/docs/_index.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: Documentation
|
||||
linkTitle: Docs
|
||||
menu: {main: {weight: 20}}
|
||||
weight: 20
|
||||
---
|
||||
|
||||
{{% pageinfo %}}
|
||||
This is a placeholder page that shows you how to use this template site.
|
||||
{{% /pageinfo %}}
|
||||
|
||||
This section is where the user documentation for your project lives - all the
|
||||
information your users need to understand and successfully use your project.
|
||||
|
||||
For large documentation sets we recommend adding content under the headings in
|
||||
this section, though if some or all of them don’t apply to your project feel
|
||||
free to remove them or add your own. You can see an example of a smaller Docsy
|
||||
documentation site in the [Docsy User Guide](https://docsy.dev/docs/), which
|
||||
lives in the [Docsy theme
|
||||
repo](https://github.com/google/docsy/tree/master/userguide) if you'd like to
|
||||
copy its docs section.
|
||||
|
||||
Other content such as marketing material, case studies, and community updates
|
||||
should live in the [About](/about/) and [Community](/community/) pages.
|
||||
|
||||
Find out how to use the Docsy theme in the [Docsy User
|
||||
Guide](https://docsy.dev/docs/). You can learn more about how to organize your
|
||||
documentation (and how we organized this site) in [Organizing Your
|
||||
Content](https://docsy.dev/docs/best-practices/organizing-content/).
|
||||
Reference in New Issue
Block a user