Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Link to ebook and blog post #3697

Merged
merged 1 commit into from
Apr 8, 2024
Merged

Link to ebook and blog post #3697

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 3 additions & 24 deletions docs/user/introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,29 +27,8 @@ NOTE: _Some blueprints may only be available on certain tiers_

## Creating Your First Flow

If you are already familiar with Node-RED, you can [skip this section](#creating-your-first-devops-pipeline).

1. **Access the Node-RED Editor**.

2. **Add Nodes**: Drag an "http in" node into the editor. This node will listen for incoming HTTP requests. Next, drag in the "change" and the "http response" nodes.

3. **Connect Nodes**: Connect the "http in" node to the "change" node, and then the "change" node to the "http response" node. Your flow should look like this:

![The three nodes](./images/getting-started/three-nodes.png)

4. **Configure 'http in' Node**: Double-click on the "http in" node to open its properties. Set the URL to "/hello" and the method to "GET".

5. **Configure 'change' Node**: Double-click the "change" node. Add "Hello World" to the field that says "to the value".

![Configure the change node](./images/getting-started/set-reply.png)

6. **Configure 'http response' Node**: Double-click to open its properties. Set the "Status Code" to be 200.

![Configure the http response node](./images/getting-started/response-code.png)

7. **Deploy**: Now that we have our flow set up, we can deploy it by clicking the "Deploy" button in the top right corner of the editor. Once the flow is deployed, you can test it by opening up a web browser, take the URL of your Instance and add "/hello" to the end, it should looks something like this `https://your-project.flowforge.cloud/hello`. You should see "Hello World!" displayed in the browser.

[Learn more about Flow creation](https://flowfuse.com/blog/2023/01/getting-started-with-node-red/#first-flow)
FlowFuse published an [eBook on Node-RED development](https://flowfuse.com/ebooks/beginner-guide-to-a-professional-nodered/), which is a great resources when you're new
to Node-RED. You can also read our [blog post on creating your first flow](https://flowfuse.com/blog/2023/01/getting-started-with-node-red/).

## Creating Your First DevOps Pipeline

Expand Down Expand Up @@ -97,4 +76,4 @@ FlowFuse supports reading and writing persistent files and persistent context.
- [Instance Settings](/docs/user/instance-settings.md) - Settings available for Node-RED instances.
- [Shared Team Library](/docs/user/shared-library.md) - Share flows easily between different Node-RED instances in your team.
- [Node-RED Tools Plugin](/docs/migration/node-red-tools.md) - A plugin for Node-RED that lets you work with your flows outside of FlowFuse.
- [High Availability mode](/docs/user/high-availability.md) - Run multiple copies of your instance for scaling and availability.
- [High Availability mode](/docs/user/high-availability.md) - Run multiple copies of your instance for scaling and availability.
Loading