What file should I include the APP_DOMAIN variable? Is it container-compose.yml? I've edited the APP_DOMAIN variable with "localhost" which is the url of the project instead of "rails" but the error persists when I'm trying to sign in with default admin account. Can you help me?
Hi @ce7in
Yeah for the first attempt that worked i added all the environment variables of the .env file on the docker-compose.yml they should be on the environment section mainly on the rails service.
You can also use --env-file option of docker-compose to include the .env file that should be cleaner and simple to use.
Thank you @manuel
. I've one more question. I've visited your forem instance and it was fully published. What platform did you use to turn forem into production mode? Is it Heroku or DigitalOcean? When I'm trying to deploy forem on Heroku it throw an error like on the images I've added below. Do you have an idea about that?
Np! It's hosted on DigitalOcean. No I didn't get that error. The error for the images that i got where that i didnt have a Cloudinary Account, just created one change environment variables and solved the issue.
The other issue i had was regarding Fastly, i didnt have an account so but created an environment variable with: FASTLY_CDN_URL: hackerss.com and that solve the issue
For further actions, you may consider blocking this person and/or reporting abuse
What file should I include the APP_DOMAIN variable? Is it container-compose.yml? I've edited the APP_DOMAIN variable with "localhost" which is the url of the project instead of "rails" but the error persists when I'm trying to sign in with default admin account. Can you help me?
forem.dev/remoteimages/uploads/art...
Hi @ce7in Yeah for the first attempt that worked i added all the environment variables of the .env file on the docker-compose.yml they should be on the environment section mainly on the rails service.
You can also use --env-file option of docker-compose to include the .env file that should be cleaner and simple to use.
Thank you @manuel . I've one more question. I've visited your forem instance and it was fully published. What platform did you use to turn forem into production mode? Is it Heroku or DigitalOcean? When I'm trying to deploy forem on Heroku it throw an error like on the images I've added below. Do you have an idea about that?
forem.dev/remoteimages/uploads/art...
forem.dev/remoteimages/uploads/art...
Np! It's hosted on DigitalOcean. No I didn't get that error. The error for the images that i got where that i didnt have a Cloudinary Account, just created one change environment variables and solved the issue.
The other issue i had was regarding Fastly, i didnt have an account so but created an environment variable with: FASTLY_CDN_URL: hackerss.com and that solve the issue