config/packages/one_pilot_client.yaml
file with the following content.env
file the following parameters:ONE_PILOT_PRIVATE_KEY
can be any random alphanumeric string. If you are not sure what key to use, go to 1Pilot dashboard and open the page to add a new site: a random key will be generated for you, and you can copy / paste it in your file. Of course you are free to create a totally different key, just make sure you have the same key in your.env
and on the 1Pilot dashboard.ONE_PILOT_MAIL_FROM_ADDRESS
email address that you use for send mail from your application. It's used by the email verification tool for ensure emails are properly send by your application.
config/routes.yaml
the following configuration:config/packages/one_pilot_client.yaml
file with the following content.env
file the following parameters:ONE_PILOT_PRIVATE_KEY
can be any random alphanumeric string. If you are not sure what key to use, go to 1Pilot dashboard and open the page to add a new site: a random key will be generated for you, and you can copy / paste it in your file. Of course you are free to create a totally different key, just make sure you have the same key in your.env
and on the 1Pilot dashboard.ONE_PILOT_MAIL_FROM_ADDRESS
email address that you use for send mail from your application. It's used by the email verification tool for ensure emails are properly send by your application.
config/routes.yaml
the following configuration:config/packages/one_pilot_client.yaml
file with the following content.env
file the following parameters:ONE_PILOT_PRIVATE_KEY
can be any random alphanumeric string. If you are not sure what key to use, go to 1Pilot dashboard and open the page to add a new site: a random key will be generated for you, and you can copy / paste it in your file. Of course you are free to create a totally different key, just make sure you have the same key in your.env
and on the 1Pilot dashboard.ONE_PILOT_MAIL_FROM_ADDRESS
email address that you use for send mail from your application. It's used by the email verification tool for ensure emails are properly send by your application.
config/routes.yaml
the following configuration:app/config/config.yml
file the following configuration keys:app/config/parameters.yml.dist
file the following parameters:This defines the new required configuration parameters.
app/config/parameters.yml
file the following parameters:one_pilot_private_key
can be any random alphanumeric string. If you are not sure what key to use, go to 1Pilot dashboard and open the page to add a new site: a random key will be generated for you, and you can copy / paste it in your file. Of course you are free to create a totally different key, just make sure you have the same key in yourparameters.yml
and on the 1Pilot dashboard.one_pilot_mail_from_address
email address that you use for send mail from your application. It's used by the email verification tool for ensure emails are properly send by your application.
app/config/routing.yml
the following configuration:app/AppKernel.php
file, in the registerBundles
method, the following line:/onepilot/*
to the login form. /onepilot/
routes in the Symfony firewall and access_control
list.config/packages/security.yaml
and add following lines in the firewalls
section before the main
entry:access_control
sectionapp/config/config.yml
and add skip_timestamp_validation
like bellow.Please note that this option will decrease security and that you should as much as possible set your server at the correct time.