Default Squidex Installation Environment Variables

spacecat · January 26, 2021, 3:23pm

Hi Sebastian,

I saw the last commit in the Docker repo was for the docker-compose.yml file.

Squidex/squidex-docker/blob/master/standalone/docker-compose.yml

version: '2.3'
services:
  squidex_mongo:
    image: mongo:4.4.1
    volumes:
      - /etc/squidex/mongo/db:/data/db
    networks:
      - internal
    restart: unless-stopped

  squidex_squidex:
    image: "squidex/squidex:5"
    environment:
      - URLS__BASEURL=https://${SQUIDEX_DOMAIN}/
      - EVENTSTORE__TYPE=MongoDB
      - EVENTSTORE__MONGODB__CONFIGURATION=mongodb://squidex_mongo
      - STORE__MONGODB__CONFIGURATION=mongodb://squidex_mongo
      - IDENTITY__ADMINEMAIL=${SQUIDEX_ADMINEMAIL}
      - IDENTITY__ADMINPASSWORD=${SQUIDEX_ADMINPASSWORD}
      - IDENTITY__GOOGLECLIENT=${SQUIDEX_GOOGLECLIENT}

This file has been truncated. show original

You bumped up the version to 5.

So I assume this file is the most recent and the one that dictates how a default Squidex installation should look like.

I’m about to upgrade from an image that is about 3 months old to version 5.5 released a couple of days ago and I was wondering:

1. Are these env vars the minimum in order for getting Squidex up and running successfully?

2. In my current config/env var list I have URLS__ENFORCEHTTPS… I assume I can remove this env var now without breaking anything, correct?

3. Also, I don’t see ASSETSTORE__TYPE. The default I believe is Folder, yes? I use MongoDB to store my images so I still would need to override the default setting and set it to MongoDb?

4. And can I remove the following env vars from my env list in my Kubernetes yaml? I will most likely never use these.

  - IDENTITY__GOOGLECLIENT=${SQUIDEX_GOOGLECLIENT}
  - IDENTITY__GOOGLESECRET=${SQUIDEX_GOOGLESECRET}
  - IDENTITY__GITHUBCLIENT=${SQUIDEX_GITHUBCLIENT}
  - IDENTITY__GITHUBSECRET=${SQUIDEX_GITHUBSECRET}
  - IDENTITY__MICROSOFTCLIENT=${SQUIDEX_MICROSOFTCLIENT}
  - IDENTITY__MICROSOFTSECRET=${SQUIDEX_MICROSOFTSECRET}

5. Is the following line for DEV environment? Can I remove it for my PROD environment? What’s it used for exactly?

- ASPNETCORE_URLS=http://+:5000

6. And if needed I can add additional env vars from whatever is in this .json file, yes?

github.com

Squidex/squidex/blob/master/backend/src/Squidex/appsettings.json

{
  "mode": {
    /*
     * Use this flag to set Squidex to readonly, e.g. when you deploy a second instance for migration.
     */
    "isReadonly": false
  },

  "urls": {
    /*
     * Set the base url of your application, to generate correct urls in background process.
     */
    "baseUrl": "https://localhost:5001",

    /*
     * Set it to true to redirect the user from http to https permanently.
     */
    "enforceHttps": false,

    /*

This file has been truncated. show original

Sebastian · January 26, 2021, 3:39pm

No, the Minimum is only these 3. The current version has a small installation wizard with some tipps and a form to create the admin user.

URLS__BASEURL=https://${SQUIDEX_DOMAIN}/
EVENTSTORE__MONGODB__CONFIGURATION=mongodb://squidex_mongo
STORE__MONGODB__CONFIGURATION=mongodb://squidex_mongo

URLS__ENFORCEHTTPS can be removed, it is typically handled by the reverse proxy (in this case caddy) anyway.
Yes, thats correct, but if you have kubernetes in a cloud I would just use this cloud provider for assets anyway, like S3 or AzureBlob
Yes, you can remove them
It sets the port where Squidex listens to. It cannot listen to port 80 because of caddy, but you can ignore it for kubernetes