- The project is deployable on the Scalingo platform.
- Each service (pipeline, api, etc.) is deployed in its own application.
- It is made possible using the
PROJECT_DIR
env variable defined in each app. - Services are configured through the environment.
If you need to interact with Scaleway, once you have your access with the right IAM configuration:
- Install Scaleway CLI.
- Generate an SSH key (if you don't already have one).
- Upload it on Scaleway.
- Generate two API keys, one for the production bucket and one for the staging bucket.
- You can then create two profiles for the Scaleway CLI with the following command:
scw init -p staging \ access-key={youraccesskey} \ secret-key={yoursecretkey} \ organization-id={organization} \ project-id={projectid}
This is optional but allows you to interact with the datalake from the command line (staging and prod). It can be usefull for debug purposes.
See installation instructions here.
You can then create aliases for Scaleway S3 staging and production, as well as one for your local Minio server. For your local server, you need to first create your API key. After launching Docker Compose, go to the console, click on the Access Keys
tab, and create an access key.
You can add aliases with the following command:
mc alias set dev http://localhost:9000 {youraccesskey} {yoursecretkey}
Do the same for staging and production (replace the access key and the secret key with the API key you created in Scaleway):
mc alias set prod https://s3.fr-par.scw.cloud {youraccesskey} {yoursecretkey} --api S3v4
mc alias set staging https://s3.fr-par.scw.cloud {youraccesskey} {yoursecretkey} --api S3v4
You can test it out, and you should have results that look like this:
$ mc ls prod
[2024-04-22 13:33:54 CEST] 0B data-inclusion-datalake-prod-grand-titmouse/
$ mc ls staging
[2024-04-10 19:45:43 CEST] 0B data-inclusion-datalake-staging-sincere-buzzard/
$ mc ls dev
[2024-06-11 10:08:06 CEST] 0B data-inclusion-lake/
You can now easily interact with all the buckets.