-
-
Notifications
You must be signed in to change notification settings - Fork 66
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
a few improvements for developers.md
- Loading branch information
1 parent
42cdcba
commit 1259059
Showing
1 changed file
with
4 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,7 +2,7 @@ | |
|
||
## Getting Started | ||
|
||
Get started with Nitric development by forking the repository and cloning it to your local machine. | ||
Get started with Nitric development by [forking the repository](https://github.com/nitrictech/nitric/fork) and cloning it to your local machine. | ||
|
||
```bash | ||
git clone https://github.com/<your-github-username>/nitric.git | ||
|
@@ -74,8 +74,8 @@ export MIN_WORKERS=0; ./cloud/aws/bin/deploy-aws | |
|
||
There are two main ways to create a custom provider: | ||
|
||
1. Create a new provider: This is the most flexible option, but also the most complex. You can [create a new provider from scratch](https://nitric.io/docs/providers/custom/create). | ||
2. Extend an existing provider: This is a good option if you want to leverage the existing provider's deployment automation and only need to make specific changes, such as use your own Terraform modules or deploy Nitric resources to a different cloud service. You [can extend an existing provider](https://nitric.io/docs/providers/custom/extend) to add your own configuration options or change the deployment process. | ||
1. **Create a new provider:** This is the most flexible option, but also the most complex. You can [create a new provider from scratch](https://nitric.io/docs/providers/custom/create). | ||
2. **Extend an existing provider:** This is a good option if you want to leverage the existing provider's deployment automation and only need to make specific changes, such as use your own Terraform modules or deploy Nitric resources to a different cloud service. You [can extend an existing provider](https://nitric.io/docs/providers/custom/extend) to add your own configuration options or change the deployment process. | ||
|
||
## Documentation Contribution | ||
|
||
|
@@ -174,5 +174,5 @@ updated_at: 2024-12-21 | |
|
||
- Ask questions in [GitHub discussions](https://github.com/nitrictech/nitric/discussions) | ||
- Join us on [Discord](https://nitric.io/chat) | ||
- Find us on [Twitter](https://twitter.com/nitric_io) | ||
- Find us on [X](https://x.com/nitric_io) | ||
- Send us an [email](mailto:[email protected]) |