Configure postgresql tcp11/23/2023 Pups::ExecError: cd /var/www/discourse & su discourse -c 'bundle exec rake db:migrate' failed with return # If I use the public IP address of the postgres instance in the app.yml config, when I rebuild the app, I get the following: FAILED The default port for PostgreSQL on Google Cloud is 5432 so I left out those lines. I then created a PostgreSQL 15.2 instance on Google Cloud and did the database setup procedure that’s outlined in the first post and configured the app.yml file as well. I can see the test uploads in the bucket and when I look at upload URLs, all uploads are showing the proper URL from the CDN so they seem like they are pulling correctly from the bucket. I currently have file uploads and discourse backups to buckets on Google Cloud enabled and those functions are working properly after following the instructions on the Configure an S3 compatible object storage provider for uploads thread. So I have a newly installed Discourse instance running via docker in a VM on Google Cloud. discourse-doctor may help diagnose the problem. ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. Rm: cannot remove 'cids/app_bootstrap.cid': No such file or directory "docker rm" requires at least 1 argument. launcher rebuild appĬd /pups & git pull & git checkout v1.0.3 & /pups/bin/pups -stdinĭocker: Error response from daemon: could not get container for .: No such container: .Ĭat: cids/app_bootstrap.cid: No such file or directory And it worked fine.īut with external RDS launcher failed. Initially I created discourse using launcher for all - app/redis/postgres. Unfortunately I got an error while reproducing it. Is there a simpler way to do it, just with environment variables? visit and log in with credentials you set up earlier on that database.bin/rails db:migrate RAILS_ENV=development" you may need to run migrations: docker exec -it discourse_dev /bin/bash -c "cd /src.vim bin/docker/boot_dev, find the line starting with docker run, and add a network definition matching the docker network to which your postgres container is attached to: docker run -network my-docker_network-name -d -p 4305.# - rebake all to posts using: `RAILS_ENV=production bundle exec rake posts:rebake` # - restart sidekiq if you change this setting # If you change this setting you will need to Change the "port" site setting instead, at /admin/site_settings. vim config/database.yml, on the top of the file, make it into:.To do so, I had to modify the installation steps as follows: I needed to run development discourse (set up following Beginners Guide to Install Discourse for Development using Docker ) using database from another container.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |