I have a backup that I need to restore on a fresh discourse instance but for some reason it’s a discourse 1.6.0 (postgresql 9.3) backup (actually I’m not sure what the version was, the version tag is 20160405172827
). And the original instance doesn’t exist anymore), so I am trying to restore it on a fresh one.
- If I go for the
tests-passed
branch (currently 1.7.0 beta), the restore fails: some tables are missing. This is unsurprising (but maybe there is some workaround here that I’m missing). - If I go for the
stable
branch (or actually any older revision) … the bootstrap fails trying to install mini_racer 0.1.3 (missingv8.h
).
Developing a bit on the last failure, here is the full output of launcher bootstrap app
:
And here is my app.yml
:
##
## After making changes to this file, you MUST rebuild for any changes
## to take effect in your live Discourse instance:
##
## /var/discourse/launcher rebuild app
##
## Make sure to obey YAML syntax! You can use this site to help check:
## http://www.yamllint.com/
## this is the all-in-one, standalone Discourse Docker container template
# You may add rate limiting by uncommenting the web.ratelimited template.
# Out of the box it allows 12 reqs a second per ip, and 100 per minute per ip
# This is configurable by amending the params in this file
templates:
- "templates/postgres.template.yml"
- "templates/redis.template.yml"
- "templates/web.template.yml"
- "templates/web.ratelimited.template.yml"
## which TCP/IP ports should this container expose?
expose:
- "8002:80" # fwd host port 80 to container port 80 (http)
params:
db_default_text_search_config: "pg_catalog.french"
## Set db_shared_buffers to a max of 25% of the total memory.
##
## On 1GB installs set to 128MB (to leave room for other processes)
## on a 4GB instance you may raise to 1GB
db_shared_buffers: "256MB"
#
## Set higher on large instances it defaults to 10MB, for a 3GB install 40MB is a good default
## this improves sorting performance, but adds memory usage per-connection
db_work_mem: "40MB"
#
## Which Git revision should this container use? (default: tests-passed)
version: stable
env:
LANG: en_US.UTF-8
DISCOURSE_DEFAULT_LOCALE: fr
## TODO: How many concurrent web requests are supported?
## With 2GB we recommend 3-4 workers, with 1GB only 2
UNICORN_WORKERS: 4
## TODO: List of comma delimited emails that will be made admin and developer
## on initial signup example 'user1@example.com,user2@example.com'
DISCOURSE_DEVELOPER_EMAILS: 'redacted'
## TODO: The domain name this Discourse instance will respond to
DISCOURSE_HOSTNAME: 'redacted'
## TODO: The mailserver this Discourse instance will use
DISCOURSE_SMTP_ADDRESS: redacted
DISCOURSE_SMTP_PORT: 587
DISCOURSE_SMTP_USER_NAME: redacted
DISCOURSE_SMTP_PASSWORD: redacted
DISCOURSE_SMTP_ENABLE_START_TLS: true
## The CDN address for this Discourse instance (configured to pull)
#DISCOURSE_CDN_URL: //discourse-cdn.example.com
## These containers are stateless, all data is stored in /shared
volumes:
- volume:
host: /var/discourse/shared/app
guest: /shared
- volume:
host: /var/discourse/shared/app/log/var-log
guest: /var/log
## The docker manager plugin allows you to one-click upgrade Discourse
## http://discourse.example.com/admin/docker
hooks:
after_code:
- exec:
cd: $home/plugins
cmd:
- mkdir -p plugins
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/cpradio/discourse-plugin-checklist.git
- git clone https://github.com/discourse/discourse-tagging.git
#- git clone https://github.com/scossar/discourse-header-links.git
## Remember, this is YAML syntax - you can only have one block with a name
run:
- exec: echo "Beginning of custom commands"
## If you want to set the 'From' email address for your first registration, uncomment and change:
#- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'"
## After getting the first signup email, re-comment the line. It only needs to run once.
## If you want to configure password login for root, uncomment and change:
## Use only one of the following lines:
#- exec: /usr/sbin/usermod -p 'PASSWORD_HASH' root
#- exec: /usr/sbin/usermod -p "$(mkpasswd -m sha-256 'RAW_PASSWORD')" root
## If you want to authorized additional users, uncomment and change:
#- exec: ssh-import-id username
#- exec: ssh-import-id anotherusername
- exec: echo "End of custom commands"
I read through some other topics with some related problems (postresql 9.3 template, …) but I couldn’t get anything to work. Any hint?