We use the official Docker hosting setup on AWS based on GitHub - aws-samples/aws-cdk-for-discourse: AWS CDK for Discourse .
The general CDN setup works fine, e.g. images are delivered fine via CDN URL.
However the initial “32x32” request seems to go to the S3 bucket URL which yields a 403.
Did I miss a configuration bit or is it a bug?
2 Mi Piace
Falco
26 Aprile 2023, 5:01pm
2
That’s not official, as it’s an AWS project using a bitnami image for Discourse which we explicitly do not recognize as an official standard install of Discourse, making this outside of the scope of installs that we support here.
Not a bug as it’s not running the app the way we intend it to be ran, but it may be fixed with a config change. Maybe open an issue about this on the sample repository ?
1 Mi Piace
The referenced project uses the official Docker image.
userData.addCommands(
"sudo -s",
"yum -y update",
"yum -y install docker",
"yum -y install git",
"yum -y install jq",
"amazon-linux-extras install -y postgresql13",
"systemctl enable docker.service",
"systemctl start docker.service",
"systemctl status docker.service",
"git clone https://github.com/discourse/discourse_docker.git /var/discourse",
"cd /var/discourse",
"chmod 700 containers",
"aws s3 cp s3://" + props.backupBucket.bucketName + "/app.yml.template ./containers/app.yml.template",
"aws s3 cp s3://" + props.backupBucket.bucketName + "/smtp_credentials_generate.py ./smtp_credentials_generate.py",
"echo -e 'export DISCOURSE_DB_USERNAME=$(aws secretsmanager get-secret-value --region " + this.region + " --secret-id " + props.auroraServerlessV2SecretArn + " --query SecretString --output text | jq -r .username)' > discourse-env",
"echo -e 'export DISCOURSE_DB_PASSWORD=$(aws secretsmanager get-secret-value --region " + this.region + " --secret-id " + props.auroraServerlessV2SecretArn + " --query SecretString --output text | jq -r .password)' >> discourse-env",
"echo -e 'export DISCOURSE_DB_HOST=$(aws secretsmanager get-secret-value --region " + this.region + " --secret-id " + props.auroraServerlessV2SecretArn + " --query SecretString --output text | jq -r .host)' >> discourse-env",
"echo -e 'export DISCOURSE_DB_NAME=$(aws secretsmanager get-secret-value --region " + this.region + " --secret-id " + props.auroraServerlessV2SecretArn + " --query SecretString --output text | jq -r .dbname)' >> discourse-env",
"echo -e 'export DISCOURSE_DB_PORT=$(aws secretsmanager get-secret-value --region " + this.region + " --secret-id " + props.auroraServerlessV2SecretArn + " --query SecretString --output text | jq -r .port)' >> discourse-env",
"echo -e 'export PGPASSWORD=$(aws secretsmanager get-secret-value --region " + this.region + " --secret-id " + props.auroraServerlessV2SecretArn + " --query SecretString --output text | jq -r .password)' >> discourse-env",
No Bitnami - I would not have used that in the first place either
I am going to dig into it and report an issue either there, or here.
1 Mi Piace
Falco
26 Aprile 2023, 8:03pm
4
Oh, sorry I went by what is written in the project README.md
Good luck. Please update here if you find any clues.
Pull request for README incoming
I found the issue. I restored a backup from another system.
2 Mi Piace
Somehow it used the s3 URL for the default Discourse system user avatar image. I did not spend time fixing it because I am still in progress of regularly recreating the environments due to some testing activities.
2 Mi Piace
system
27 Maggio 2023, 2:12pm
9
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
