Double check that all required services are running and accessible before trying this step.
Database
The database must exist before trying to configure TeSLA CE. If root credentials are provided, this process will create the not privileged user, otherwise, the not privileged should have owner permissions in the TeSLA database.
Storage Buckets
If you are using MinIO, the configuration process will create and initialize the buckets if they do not exist. If using another storage like Amazon S3 or the provided credentials cannot create buckets, they may exist before trying to run the configuration script.
If the buckets are created by the configuration script, at the end of the configuration process you need to set the correct policy to the public bucket. This can be done with the MinIO client following those steps:
- Get the configuration parameters STORAGE_URL, BUCKET_NAME, STORAGE_KEY and STORAGE_SECRET from the configuration
file
tesla-ce.cfg
generated previously (see Configuration ).
# Storage configuration (S3 or Minio)
[storage]
# Storage url
# (str) default: http://localhost:9000
url=STORAGE_URL
# Storage default public bucket
# (str) default: tesla-public
public_bucket_name=BUCKET_NAME
...
# Storage access key id
# (str)
access_key=STORAGE_KEY
# Storage secret access key
# (str)
secret_key=STORAGE_SECRET
Run a MinIO client
docker run -it --entrypoint=/bin/bash minio/mc
Setup the MinIO connection. If you are not using a real domain, use
--insecure
option to avoid certificate errors.mc alias set minio STORAGE_URL STORAGE_KEY STORAGE_SECRET [--insecure]
Change the policy for the public bucket. If you are not using a real domain, use
--insecure
option to avoid certificate errors.mc policy set download minio/BUCKET_NAME [--insecure]
Initialize TeSLA CE
Once the configuration options are set on the configuration file, in this step we will prepare all the services to be used. First check that configuration is valid:
tesla_ce reconfigure --check
And finally apply the configuration:
tesla_ce reconfigure
This command will initialize all the services to be ready for TeSLA CE deployment.
Depending on the services and connection performance, some actions can take longer than default HTTP timeout. If this happens, the command will fail. Just run this command again to finish the configuration process.