You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Click **Environmental Footprint** in the Organization drop-down menu to go to the **Environmental Footprint Overview** page. The **Environmental Footprint** dashboard appears, displaying the list of your current and past monthly reports.
Copy file name to clipboardExpand all lines: pages/transactional-email/reference-content/smtp-configuration.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ content:
7
7
paragraph: This page goes into detail about the different elements in a standard SMTP configuration, and how to fill out each entry to ensure an optimal configuration of Transactional Email services.
We will also add `-f` option to specify a filename in which to output our new user's private RSA key. We will need this to authenticate using the `knife` management command later. In the end, the command translates to:
140
+
We will also add `-f` option to specify a `FILENAME` in which to output our new user's private RSA key. We will need this to authenticate using the `knife` management command later. In the end, the command translates to:
141
141
142
142
```
143
143
chef-server-ctl user-create testuser test user [email protected] pwdexample -f testuser.pem
144
144
```
145
145
2. Launch the `chef-server-ctl` with the `org-create` subcommand:
For our example, we will create an organization with the following information:
151
-
-**Short Name** (refers to the organization within Chef): scaleway
152
-
-**Long Name** (name of the organization): Scaleway, Inc.
153
-
-**Association User** (username that has access to administer the organization): testuser
154
-
-**Filename:** scaleway-file.pem
151
+
152
+
-`SHORT_NAME` - Refers to the organization within Chef. In this example we use `scaleway`
153
+
-`LONG_NAME` - The name of the organization. In this example, `Scaleway, Inc`
154
+
-`ADMIN_USERNAME` - The username of a user with administration rights on the organization. In this example, `testuser`
155
+
-`FILENAME` - `scaleway-file.pem`
155
156
156
157
Again, we will add the `-f` flag to specify the private key file location. The key that will be created is used to validate new clients as part of the organization until they can get their own unique client key. In the end, the command translates to:
157
158
@@ -218,18 +219,18 @@ The method that you use to connect to the Chef server will determine how to down
218
219
219
220
#### Option 1: (Recommended) Downloading keys when connecting to a Chef server using SSH keys
220
221
221
-
1. Leave your workstation
222
+
1. Leave your workstation.
222
223
```
223
224
exit
224
225
```
225
226
226
-
The next steps should be carried out from the machine that holds the private SSH key needed to connect to your Chef server.
227
+
The next steps should be carried out from the machine that holds the private SSH key needed to connect to your Chef server.
227
228
2. Add the SSH key you use to connect to the Chef server to an SSH agent:
228
229
```
229
230
eval $(ssh-agent)
230
231
```
231
232
232
-
which should start the agent and return something similar to
233
+
Which should start the agent and return something similar to:
233
234
234
235
```
235
236
Agent pid 2893
@@ -306,18 +307,18 @@ This is done through a `knife.rb` file that we will place in the `~/chef_repo/.c
-**node_name:** Specifies the name that knife will use to connect to your Chef server. This should match your username.
317
-
-**client_key:** Name and path to the user key that you copied over from the Chef server. We can use the `#{current_dir}` snippet to fill in the path if the key is in the same directory as the `knife.rb` file.
318
-
-**validation_client_name:** Name of the validation client that knife will use to bootstrap new nodes. This will take the form of your organization short name, followed by `-validator`.
319
-
-**validation_key:** Like the `client_key`, this includes the name and path to the validation key you copied from the Chef server. Again, you can use the `#{current_dir}`.
320
-
-**chef_server_url:** This is the URL where the Chef server can be reached. It should begin with `https://`, followed by your Chef server's domain name or **Public IP address**. Afterward, the path to your organization should be specified by appending /organizations/your_organization_name.
317
+
-`node_name` - Specifies the name that knife will use to connect to your Chef server. This should match your username.
318
+
-`client_key` - Name and path to the user key that you copied over from the Chef server. We can use the `#{current_dir}` snippet to fill in the path if the key is in the same directory as the `knife.rb` file.
319
+
-`validation_client_name` - Name of the validation client that knife will use to bootstrap new nodes. This will take the form of your organization short name, followed by `-validator`.
320
+
-`validation_key` - Like the `client_key`, this includes the name and path to the validation key you copied from the Chef server. Again, you can use the `#{current_dir}`.
321
+
-`chef_server_url` - This is the URL where the Chef server can be reached. It should begin with `https://`, followed by your Chef server's domain name or **Public IP address**. Afterward, the path to your organization should be specified by appending /organizations/your_organization_name.
Copy file name to clipboardExpand all lines: tutorials/configure-netbox-managed-postgresql-database/index.mdx
+35-41Lines changed: 35 additions & 41 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ categories:
10
10
- postgresql-and-mysql
11
11
hero: assets/scaleway_netbox.webp
12
12
dates:
13
-
validation: 2024-10-29
13
+
validation: 2025-05-14
14
14
posted: 2019-11-14
15
15
---
16
16
@@ -24,30 +24,20 @@ In this tutorial, you learn how to install and configure NetBox on an Instance r
24
24
-[Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
25
25
- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
26
26
- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu Focal Fossa (20.04 LTS) or later
27
-
- A [Database for PostgreSQL](/managed-databases-for-postgresql-and-mysql/quickstart/)
27
+
- A [Managed Database for PostgreSQL](/managed-databases-for-postgresql-and-mysql/quickstart/)
28
28
29
29
## Configuring the database
30
30
31
31
NetBox requires a PostgreSQL database. Configure your [Database for PostgreSQL](https://www.scaleway.com/en/database/) with a few steps from your [Scaleway console](https://console.scaleway.com/rdb/instances)
32
32
33
33
1. Enter the Databases section of your [Scaleway console](https://console.scaleway.com/rdb/instances) by clicking on **Managed Databases** in the side menu.
34
-
2. Click the name of the Database you want to use to view the Instance's details:
2.[Create a Database Instance.](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/)
35
+
3.[Create a database](/managed-databases-for-postgresql-and-mysql/how-to/add-a-database/) called `netbox`.
36
+
4.[Create a new user](/managed-databases-for-postgresql-and-mysql/how-to/add-users/) also called `netbox` and grant it ALL permissions to the `netbox` database.
47
37
48
38
## Installing NetBox
49
39
50
-
1.Log into your Instance using [SSH](/instances/how-to/connect-to-instance/).
40
+
1.Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/).
51
41
2. Update the `apt` package cache and upgrade the software already installed on the Instance to the latest version available in Ubuntu's repositories:
52
42
```
53
43
apt update && apt upgrade -y
@@ -56,13 +46,13 @@ NetBox requires a PostgreSQL database. Configure your [Database for PostgreSQL](
4. Download the [latest release](https://github.com/netbox-community/netbox/releases/latest) of NetBox. At the time of writing this tutorial, it is version 3.7.5. Unpack it into the `/opt` directory:
49
+
4. Download the [latest release](https://github.com/netbox-community/netbox/releases/latest) of NetBox. At the time of writing this tutorial, it is version 4.3.1. Unpack it into the `/opt` directory:
60
50
```
61
-
wget https://github.com/netbox-community/netbox/archive/refs/tags/v3.7.5.tar.gz && tar -xzf v3.7.5.tar.gz -C /opt
51
+
wget https://github.com/netbox-community/netbox/archive/refs/tags/v4.3.1.tar.gz && tar -xzf v4.3.1.tar.gz -C /opt
62
52
```
63
53
5. Create a symlink from the actual NetBox directory to `/opt/netbox`:
64
54
```
65
-
ln -s /opt/netbox-3.6.3/ /opt/netbox
55
+
ln -s /opt/netbox-4.3.1/ /opt/netbox
66
56
```
67
57
6. Create a new system user for the NetBox application:
68
58
```
@@ -103,29 +93,33 @@ NetBox requires a PostgreSQL database. Configure your [Database for PostgreSQL](
103
93
-`REDIS` specifies the configuration parameters of Redis, an in-memory key-value store required as part of the NetBox installation. For most installations, the default configuration is good enough, and you can leave it as it is. For more information about advanced Redis configuration, refer to the [official documentation](https://docs.netbox.dev/en/stable/configuration/required-parameters/#redis).
104
94
-`SECRET_KEY` specifies a secret cryptographic key that is used to improve the security of cookies and password resets. It should be at least 50 characters long and should not be shared outside the configuration file. You may change the value of the key at any time, resulting in a termination of all active sessions.
105
95
106
-
Enter the key in the configuration file as follows, then save the file and exit your text editor:
The `SECRET_KEY` is not used for hashing user passwords or for the encrypted storage of secret data in NetBox.
105
+
NetBox comes with a script, that you may use to generate a random key:
110
106
111
-
<Messagetype="important">
112
-
The `SECRET_KEY` is not used for hashing user passwords or for the encrypted storage of secret data in NetBox.
113
-
NetBox comes with a script, that you may use to generate a random key:
114
-
```
115
-
python3 /opt/netbox/netbox/generate_secret_key.py
116
-
```
117
-
</Message>
118
-
12. Once NetBox has been configured, proceed with the actual installation by running the packaged upgrade script (`upgrade.sh`):
107
+
```
108
+
python3 /opt/netbox/netbox/generate_secret_key.py
109
+
```
110
+
</Message>
111
+
112
+
12. Once NetBox is configured, proceed with the actual installation by running the packaged upgrade script (`upgrade.sh`):
119
113
```
120
114
/opt/netbox/upgrade.sh
121
115
```
122
116
123
117
This script performs the following actions on your instance:
124
118
125
-
- Creating a Python virtual environment
126
-
- Installing all required Python packages
127
-
- Running database schema migrations
128
-
- Aggregating static resource files on disk
119
+
- Creating a Python virtual environment
120
+
- Installing all required Python packages
121
+
- Running database schema migrations
122
+
- Aggregating static resource files on disk
129
123
130
124
<Messagetype="note">
131
125
The upgrade script may warn you, that no existing virtual environment was detected. As this is a new installation, you can safely ignore this warning.
@@ -150,7 +144,7 @@ NetBox does not come with any default user accounts. Create a first user by comp
150
144
python3 manage.py createsuperuser
151
145
```
152
146
153
-
Enter the `username`, `email`, `password`, and `password confirmation` for the user and confirm by pressing Enter. The following message displays once the user is created: `Superuser created successfully.`
147
+
4.Enter the `username`, `email`, `password`, and `password confirmation` for the user and confirm by pressing Enter. The following message displays once the user is created: `Superuser created successfully.`
154
148
155
149
## Testing the application
156
150
@@ -165,10 +159,10 @@ Enter the `username`, `email`, `password`, and `password confirmation` for the u
165
159
166
160
[gunicorn](https://gunicorn.org/) is a Python [WSGI](https://wsgi.readthedocs.io/en/latest/what.html) HTTP Server for UNIX which will be used to serve the NetBox application to Nginx.
167
161
168
-
1.Copy the gunicorn configuration file from the `contrib` directory to its final destination:
The configuration file shipped with the NetBox application works for most setups, however, if you need some specific settings, refer to the [gunicorn documentation](https://docs.gunicorn.org/en/stable/configure.html).
174
168
@@ -221,7 +215,7 @@ To provide an additional layer of security, NetBox will be running behind a [NGI
221
215
}
222
216
```
223
217
224
-
Save the file and exit the text editor.
218
+
Save the file and exit the text editor.
225
219
3. Create a symlink to enable the new configuration with NGINX:
0 commit comments