Cavemanon/piratepoet
7
Fork 0
forked from MichaelYick/mailpoet
Code Pull Requests Actions Releases 12 Activity
piratepoet/.env.sample

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

35 lines
1.3 KiB
Plaintext
Raw Normal View History

adding comments to .env.sample
2018-10-10 11:49:06 +02:00
# Required
Merge WP_ROOT and WP_TEST_PATH environment vars [MAILPOET-1605]
2018-11-01 14:46:38 +01:00
WP_ROOT="/var/www/wordpress"
adding comments to .env.sample
2018-10-10 11:49:06 +02:00
WP_TEST_ENABLE_NETWORK_TESTS="false"
WP_TEST_MAILER_ENABLE_SENDING="false"
# Optional: for multisite acceptance tests
Merge WP_ROOT and WP_TEST_PATH environment vars [MAILPOET-1605]
2018-11-01 14:46:38 +01:00
WP_ROOT_MULTISITE="/var/www/wordpress"
Adds multisite test environment to CI Adds Robo command to run multisite tests locally and on CI
2017-11-13 17:04:55 -05:00
WP_TEST_MULTISITE_SLUG=""
Fix a syntax issue in .env.sample The .env.sample file contained a few comments using `//`. The problem is that `//` is not supported by vlucas/phpdotenv and this was resulting in the following fatal error when following the dev environment setup instructions and running `./do install`: ``` ERROR: Uncaught Dotenv\Exception\InvalidFileException: Failed to parse dotenv file due to unexpected whitespace. Failed at ["" // URL of your site (used for multisite env and equals to DOMAIN_CURRENT_SITE from wp-config.php)]. in /srv/www/mailpoet/public_html/wp-content/plugins/mailpoet/vendor/vlucas/phpdotenv/src/Parser.php:148 ``` To fix this problem, this commit replaces all instances of `//` in .env.sample with the `#` (see https://github.com/vlucas/phpdotenv#comments). Quick test show that `//` doesn't work and `#` does: ``` >>> Dotenv\Dotenv::parse("FOO=Bar // some comment") Dotenv\Exception\InvalidFileException with message 'Failed to parse dotenv file. Encountered unexpected whitespace at [Bar // some comment].' >>> Dotenv\Dotenv::parse("FOO=Bar # some comment") => [ "FOO" => "Bar", ] ```
2021-01-15 17:00:15 -03:00
HTTP_HOST="" # URL of your site (used for multisite env and equals to DOMAIN_CURRENT_SITE from wp-config.php)
adding comments to .env.sample
2018-10-10 11:49:06 +02:00
# Optional: for sending tests
# These are required if WP_TEST_MAILER_ENABLE_SENDING is "true"
- Updates MailChimp test and .env.sample
2016-02-05 09:35:32 -05:00
WP_TEST_IMPORT_MAILCHIMP_API=""
Fix a syntax issue in .env.sample The .env.sample file contained a few comments using `//`. The problem is that `//` is not supported by vlucas/phpdotenv and this was resulting in the following fatal error when following the dev environment setup instructions and running `./do install`: ``` ERROR: Uncaught Dotenv\Exception\InvalidFileException: Failed to parse dotenv file due to unexpected whitespace. Failed at ["" // URL of your site (used for multisite env and equals to DOMAIN_CURRENT_SITE from wp-config.php)]. in /srv/www/mailpoet/public_html/wp-content/plugins/mailpoet/vendor/vlucas/phpdotenv/src/Parser.php:148 ``` To fix this problem, this commit replaces all instances of `//` in .env.sample with the `#` (see https://github.com/vlucas/phpdotenv#comments). Quick test show that `//` doesn't work and `#` does: ``` >>> Dotenv\Dotenv::parse("FOO=Bar // some comment") Dotenv\Exception\InvalidFileException with message 'Failed to parse dotenv file. Encountered unexpected whitespace at [Bar // some comment].' >>> Dotenv\Dotenv::parse("FOO=Bar # some comment") => [ "FOO" => "Bar", ] ```
2021-01-15 17:00:15 -03:00
WP_TEST_IMPORT_MAILCHIMP_LISTS="" # (separated with comma)
- Updates .env.sample with available options for unit tests
2016-02-05 09:00:28 -05:00
WP_TEST_MAILER_AMAZON_ACCESS=""
WP_TEST_MAILER_AMAZON_SECRET=""
WP_TEST_MAILER_AMAZON_REGION=""
WP_TEST_MAILER_MAILPOET_API=""
WP_TEST_MAILER_SENDGRID_API=""
WP_TEST_MAILER_SMTP_HOST=""
WP_TEST_MAILER_SMTP_LOGIN=""
Add force mode to svn:publish command, add svn:checkout command
2016-12-15 16:20:12 +03:00
WP_TEST_MAILER_SMTP_PASSWORD=""
adding comments to .env.sample
2018-10-10 11:49:06 +02:00
# Optional: for plugin deployment
Add force mode to svn:publish command, add svn:checkout command
2016-12-15 16:20:12 +03:00
WP_SVN_USERNAME=""
WP_SVN_PASSWORD=""
Adds multisite test environment to CI Adds Robo command to run multisite tests locally and on CI
2017-11-13 17:04:55 -05:00
WP_TRANSIFEX_API_TOKEN=""
Fix a syntax issue in .env.sample The .env.sample file contained a few comments using `//`. The problem is that `//` is not supported by vlucas/phpdotenv and this was resulting in the following fatal error when following the dev environment setup instructions and running `./do install`: ``` ERROR: Uncaught Dotenv\Exception\InvalidFileException: Failed to parse dotenv file due to unexpected whitespace. Failed at ["" // URL of your site (used for multisite env and equals to DOMAIN_CURRENT_SITE from wp-config.php)]. in /srv/www/mailpoet/public_html/wp-content/plugins/mailpoet/vendor/vlucas/phpdotenv/src/Parser.php:148 ``` To fix this problem, this commit replaces all instances of `//` in .env.sample with the `#` (see https://github.com/vlucas/phpdotenv#comments). Quick test show that `//` doesn't work and `#` does: ``` >>> Dotenv\Dotenv::parse("FOO=Bar // some comment") Dotenv\Exception\InvalidFileException with message 'Failed to parse dotenv file. Encountered unexpected whitespace at [Bar // some comment].' >>> Dotenv\Dotenv::parse("FOO=Bar # some comment") => [ "FOO" => "Bar", ] ```
2021-01-15 17:00:15 -03:00
WP_JIRA_USER="" # JIRA username/email
WP_JIRA_TOKEN="" # JIRA token from https://id.atlassian.com/manage/api-tokens
WP_CIRCLECI_USERNAME="" # CircleCI organization or user
WP_CIRCLECI_TOKEN="" # CircleCI token from https://circleci.com/gh/{user|org}/{project}/edit#api
WP_GITHUB_USERNAME="" # GitHub username (not email)
WP_GITHUB_TOKEN="" # GitHub token from https://github.com/settings/tokens
WP_SLACK_WEBHOOK_URL="" # Webhook URL from https://mailpoet.slack.com/services/BHRB9AHSQ
Copy Permalink