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
DB projects - optionally use YAML for configuration (#552)
For the 9 single-instance database projects, switch from optionally
using the vagrant-env plugin for configuration to optionally using YAML.
The vagrant-env plugin is no longer maintained, and doesn't work
correctly with Vagrant 2.4.3+ without modifying the dotenv gem.
See #551.
The changes are the same for each project.
.env/config.yaml:
- rename .env to config.yaml and convert to YAML
- remove comment referring to the vagrant-env plugin
- update comment referring to .env/.env.local to refer to
config.yaml/config.local.yaml
.gitignore:
- remove .env.local* and add config.local*.yaml
README.md:
- remove references to the vagrant-env plugin
- replace references to .env/.env.local with references to
config.yaml/config.local.yaml
Vagrantfile:
- remove references to the vagrant-env plugin
- add "require 'yaml'"
- replace the code that loads environment variables from .env files
with code that loads environment variables from .yaml files
Tested with both VirtualBox and libvirt providers.
Signed-off-by: Paul Neumann <[email protected]>
Copy file name to clipboardExpand all lines: OracleDatabase/11.2.0.2/README.md
+6-11Lines changed: 6 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,7 @@ This Vagrant project provisions Oracle Database automatically, using Vagrant, an
4
4
5
5
## Prerequisites
6
6
7
-
1. Read the [prerequisites in the top level README](../../README.md#prerequisites) to set up Vagrant with either VirtualBox or KVM.
8
-
2. The [vagrant-env](https://github.com/gosuri/vagrant-env) plugin is optional but
9
-
makes configuration much easier
7
+
Read the [prerequisites in the top level README](../../README.md#prerequisites) to set up Vagrant with either VirtualBox or KVM.
10
8
11
9
## Getting started
12
10
@@ -53,14 +51,13 @@ There are three ways to set parameters:
53
51
54
52
1. Update the `Vagrantfile`. This is straightforward; the downside is that you will lose changes when you update this repository.
55
53
2. Use environment variables. It might be difficult to remember the parameters used when the VM was instantiated.
56
-
3. Use the `.env`/`.env.local` files (requires
57
-
[vagrant-env](https://github.com/gosuri/vagrant-env) plugin). You can configure your installation by editing the `.env` file, but `.env` will be overwritten on updates, so it's better to make a copy of `.env` called `.env.local`, then make changes in `.env.local`. The `.env.local` file won't be overwritten when you update this repository and it won't mark your Git tree as changed (you won't accidentally commit your local configuration!).
54
+
3. Use the `config.yaml`/`config.local.yaml` files. You can configure your installation by editing the `config.yaml` file, but `config.yaml` will be overwritten on updates, so it's better to make a copy of `config.yaml` called `config.local.yaml`, then make changes in `config.local.yaml`. The `config.local.yaml` file won't be overwritten when you update this repository and it won't mark your Git tree as changed (you won't accidentally commit your local configuration!).
58
55
59
56
Parameters are considered in the following order (first one wins):
60
57
61
58
1. Environment variables
62
-
2.`.env.local` (if it exists and the [vagrant-env](https://github.com/gosuri/vagrant-env) plugin is installed)
63
-
3.`.env` (if the [vagrant-env](https://github.com/gosuri/vagrant-env) plugin is installed)
59
+
2.`config.local.yaml` (if it exists)
60
+
3.`config.yaml`
64
61
4.`Vagrantfile` definitions
65
62
66
63
### VM parameters
@@ -78,12 +75,10 @@ Parameters are considered in the following order (first one wins):
Copy file name to clipboardExpand all lines: OracleDatabase/12.1.0.2/README.md
+6-11Lines changed: 6 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,7 @@ This Vagrant project provisions Oracle Database automatically, using Vagrant, an
4
4
5
5
## Prerequisites
6
6
7
-
1. Read the [prerequisites in the top level README](../../README.md#prerequisites) to set up Vagrant with either VirtualBox or KVM.
8
-
2. The [vagrant-env](https://github.com/gosuri/vagrant-env) plugin is optional but
9
-
makes configuration much easier
7
+
Read the [prerequisites in the top level README](../../README.md#prerequisites) to set up Vagrant with either VirtualBox or KVM.
10
8
11
9
## Getting started
12
10
@@ -57,14 +55,13 @@ There are three ways to set parameters:
57
55
58
56
1. Update the `Vagrantfile`. This is straightforward; the downside is that you will lose changes when you update this repository.
59
57
2. Use environment variables. It might be difficult to remember the parameters used when the VM was instantiated.
60
-
3. Use the `.env`/`.env.local` files (requires
61
-
[vagrant-env](https://github.com/gosuri/vagrant-env) plugin). You can configure your installation by editing the `.env` file, but `.env` will be overwritten on updates, so it's better to make a copy of `.env` called `.env.local`, then make changes in `.env.local`. The `.env.local` file won't be overwritten when you update this repository and it won't mark your Git tree as changed (you won't accidentally commit your local configuration!).
58
+
3. Use the `config.yaml`/`config.local.yaml` files. You can configure your installation by editing the `config.yaml` file, but `config.yaml` will be overwritten on updates, so it's better to make a copy of `config.yaml` called `config.local.yaml`, then make changes in `config.local.yaml`. The `config.local.yaml` file won't be overwritten when you update this repository and it won't mark your Git tree as changed (you won't accidentally commit your local configuration!).
62
59
63
60
Parameters are considered in the following order (first one wins):
64
61
65
62
1. Environment variables
66
-
2.`.env.local` (if it exists and the [vagrant-env](https://github.com/gosuri/vagrant-env) plugin is installed)
67
-
3.`.env` (if the [vagrant-env](https://github.com/gosuri/vagrant-env) plugin is installed)
63
+
2.`config.local.yaml` (if it exists)
64
+
3.`config.yaml`
68
65
4.`Vagrantfile` definitions
69
66
70
67
### VM parameters
@@ -89,12 +86,10 @@ Parameters are considered in the following order (first one wins):
89
86
*`VM_EM_EXPRESS_PORT` (default: `5500`): EM Express port.
90
87
*`VM_ORACLE_PWD` (default: automatically generated): Oracle Database password for the SYS, SYSTEM and PDBADMIN accounts.
91
88
92
-
## Optional plugins
89
+
## Optional plugin
93
90
94
-
When installed, this Vagrant project will make use of the following third party Vagrant plugins:
91
+
When installed, this Vagrant project will make use of the following third party Vagrant plugin:
Copy file name to clipboardExpand all lines: OracleDatabase/12.2.0.1/README.md
+6-11Lines changed: 6 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,7 @@ This Vagrant project provisions Oracle Database automatically, using Vagrant, an
4
4
5
5
## Prerequisites
6
6
7
-
1. Read the [prerequisites in the top level README](../../README.md#prerequisites) to set up Vagrant with either VirtualBox or KVM.
8
-
2. The [vagrant-env](https://github.com/gosuri/vagrant-env) plugin is optional but
9
-
makes configuration much easier
7
+
Read the [prerequisites in the top level README](../../README.md#prerequisites) to set up Vagrant with either VirtualBox or KVM.
10
8
11
9
## Getting started
12
10
@@ -55,14 +53,13 @@ There are three ways to set parameters:
55
53
56
54
1. Update the `Vagrantfile`. This is straightforward; the downside is that you will lose changes when you update this repository.
57
55
2. Use environment variables. It might be difficult to remember the parameters used when the VM was instantiated.
58
-
3. Use the `.env`/`.env.local` files (requires
59
-
[vagrant-env](https://github.com/gosuri/vagrant-env) plugin). You can configure your installation by editing the `.env` file, but `.env` will be overwritten on updates, so it's better to make a copy of `.env` called `.env.local`, then make changes in `.env.local`. The `.env.local` file won't be overwritten when you update this repository and it won't mark your Git tree as changed (you won't accidentally commit your local configuration!).
56
+
3. Use the `config.yaml`/`config.local.yaml` files. You can configure your installation by editing the `config.yaml` file, but `config.yaml` will be overwritten on updates, so it's better to make a copy of `config.yaml` called `config.local.yaml`, then make changes in `config.local.yaml`. The `config.local.yaml` file won't be overwritten when you update this repository and it won't mark your Git tree as changed (you won't accidentally commit your local configuration!).
60
57
61
58
Parameters are considered in the following order (first one wins):
62
59
63
60
1. Environment variables
64
-
2.`.env.local` (if it exists and the [vagrant-env](https://github.com/gosuri/vagrant-env) plugin is installed)
65
-
3.`.env` (if the [vagrant-env](https://github.com/gosuri/vagrant-env) plugin is installed)
61
+
2.`config.local.yaml` (if it exists)
62
+
3.`config.yaml`
66
63
4.`Vagrantfile` definitions
67
64
68
65
### VM parameters
@@ -87,12 +84,10 @@ Parameters are considered in the following order (first one wins):
87
84
*`VM_EM_EXPRESS_PORT` (default: `5500`): EM Express port.
88
85
*`VM_ORACLE_PWD` (default: automatically generated): Oracle Database password for the SYS, SYSTEM and PDBADMIN accounts.
89
86
90
-
## Optional plugins
87
+
## Optional plugin
91
88
92
-
When installed, this Vagrant project will make use of the following third party Vagrant plugins:
89
+
When installed, this Vagrant project will make use of the following third party Vagrant plugin:
0 commit comments