random-mirrors
/
gab-social
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
gab-social/config/database.yml

53 lines
1.5 KiB
YAML
Raw Normal View History

Gab Social. All are welcome.
2019-07-02 08:10:25 +01:00
default: &default
adapter: postgresql
pool: <%= ENV["DB_POOL"] || ENV['MAX_THREADS'] || 5 %>
timeout: 5000
encoding: unicode
sslmode: <%= ENV['DB_SSLMODE'] || "prefer" %>
Simplify database.yml by merging in default options Anything in the &default section can be merged in using <<: *default In this case, the default already specifies that the adapter is postgresql, the timeout is 5000, the encoding is unicode. It also already specified the db pool, but the default actually checked 2 different ENVs and provided a fallback if it's not provided. Lastly, I was able to move the prepared_statements section to the defaults, because the .env.vagrant file doesn't specify ENV['PREPARED_STATEMENTS'], development still just sets it to 'false'.
2021-02-14 04:51:23 +00:00
prepared_statements: <%= ENV['PREPARED_STATEMENTS'] || 'false' %>
Gab Social. All are welcome.
2019-07-02 08:10:25 +01:00
development:
Avoid redundant OAuth queries when not signed in If you aren't signed in, you don't have an auth token. When you don't have an auth token, React was sending the headers "Authorization: Bearer null" This caused 5 Doorkeeper token lookups using WHERE "oauth_access_tokens"."token" = 'null' on the Explore page (the root of the app when not signed in).
2021-02-15 23:26:00 +00:00
primary:
Simplify database.yml by merging in default options Anything in the &default section can be merged in using <<: *default In this case, the default already specifies that the adapter is postgresql, the timeout is 5000, the encoding is unicode. It also already specified the db pool, but the default actually checked 2 different ENVs and provided a fallback if it's not provided. Lastly, I was able to move the prepared_statements section to the defaults, because the .env.vagrant file doesn't specify ENV['PREPARED_STATEMENTS'], development still just sets it to 'false'.
2021-02-14 04:51:23 +00:00
<<: *default
Replace Makara with an initial Rails 6 role based splitting method.
2021-02-09 19:38:10 +00:00
url: <%= ENV['DB_MASTER_URL'] %>
slave1:
Simplify database.yml by merging in default options Anything in the &default section can be merged in using <<: *default In this case, the default already specifies that the adapter is postgresql, the timeout is 5000, the encoding is unicode. It also already specified the db pool, but the default actually checked 2 different ENVs and provided a fallback if it's not provided. Lastly, I was able to move the prepared_statements section to the defaults, because the .env.vagrant file doesn't specify ENV['PREPARED_STATEMENTS'], development still just sets it to 'false'.
2021-02-14 04:51:23 +00:00
<<: *default
Replace Makara with an initial Rails 6 role based splitting method.
2021-02-09 19:38:10 +00:00
url: <%= ENV['DB_SLAVE1_URL'] %>
Mark the replicas as replicas Rails won't even attempt to write to a replica. Without this option, a write attempt would actually run against Postgres, and it would be up to Postgres to throw a readonly error. Additionally, marking it as a replica teaches ActiveRecord that it should not attempt to run migrations against this connection. https://api.rubyonrails.org/classes/ActiveRecord/DatabaseConfigurations.html#method-i-configs_for I'm actually pretty sure that the lack of `replica: true` is why there's currently a db/slave1_schema.rb and db/slave2_schema.rb
2021-02-14 04:59:02 +00:00
replica: true
Replace Makara with an initial Rails 6 role based splitting method.
2021-02-09 19:38:10 +00:00
slave2:
Simplify database.yml by merging in default options Anything in the &default section can be merged in using <<: *default In this case, the default already specifies that the adapter is postgresql, the timeout is 5000, the encoding is unicode. It also already specified the db pool, but the default actually checked 2 different ENVs and provided a fallback if it's not provided. Lastly, I was able to move the prepared_statements section to the defaults, because the .env.vagrant file doesn't specify ENV['PREPARED_STATEMENTS'], development still just sets it to 'false'.
2021-02-14 04:51:23 +00:00
<<: *default
Bundle of corrections and one doorkeeper writing role change
2021-02-10 03:32:24 +00:00
url: <%= ENV['DB_SLAVE2_URL'] %>
Mark the replicas as replicas Rails won't even attempt to write to a replica. Without this option, a write attempt would actually run against Postgres, and it would be up to Postgres to throw a readonly error. Additionally, marking it as a replica teaches ActiveRecord that it should not attempt to run migrations against this connection. https://api.rubyonrails.org/classes/ActiveRecord/DatabaseConfigurations.html#method-i-configs_for I'm actually pretty sure that the lack of `replica: true` is why there's currently a db/slave1_schema.rb and db/slave2_schema.rb
2021-02-14 04:59:02 +00:00
replica: true
Gab Social. All are welcome.
2019-07-02 08:10:25 +01:00
# Warning: The database defined as "test" will be erased and
# re-generated from your development database when you run "rake".
# Do not set this db to the same as development or production.
test:
<<: *default
database: <%= ENV['DB_NAME'] || 'gabsocial' %>_test<%= ENV['TEST_ENV_NUMBER'] %>
username: <%= ENV['DB_USER'] %>
password: <%= ENV['DB_PASS'] %>
host: <%= ENV['DB_HOST'] %>
port: <%= ENV['DB_PORT'] %>
Replace Makara with an initial Rails 6 role based splitting method.
2021-02-09 19:38:10 +00:00
#production:
# <<: *default
# database: <%= ENV['DB_NAME'] || 'gabsocial_production' %>
# username: <%= ENV['DB_USER'] || 'gabsocial' %>
# password: <%= ENV['DB_PASS'] || '' %>
# host: <%= ENV['DB_HOST'] || 'localhost' %>
# port: <%= ENV['DB_PORT'] || 5432 %>
# prepared_statements: <%= ENV['PREPARED_STATEMENTS'] || 'true' %>
Gab Social. All are welcome.
2019-07-02 08:10:25 +01:00
production:
Avoid redundant OAuth queries when not signed in If you aren't signed in, you don't have an auth token. When you don't have an auth token, React was sending the headers "Authorization: Bearer null" This caused 5 Doorkeeper token lookups using WHERE "oauth_access_tokens"."token" = 'null' on the Explore page (the root of the app when not signed in).
2021-02-15 23:26:00 +00:00
primary:
Simplify database.yml by merging in default options Anything in the &default section can be merged in using <<: *default In this case, the default already specifies that the adapter is postgresql, the timeout is 5000, the encoding is unicode. It also already specified the db pool, but the default actually checked 2 different ENVs and provided a fallback if it's not provided. Lastly, I was able to move the prepared_statements section to the defaults, because the .env.vagrant file doesn't specify ENV['PREPARED_STATEMENTS'], development still just sets it to 'false'.
2021-02-14 04:51:23 +00:00
<<: *default
Replace Makara with an initial Rails 6 role based splitting method.
2021-02-09 19:38:10 +00:00
url: <%= ENV['DB_MASTER_URL'] %>
slave1:
Simplify database.yml by merging in default options Anything in the &default section can be merged in using <<: *default In this case, the default already specifies that the adapter is postgresql, the timeout is 5000, the encoding is unicode. It also already specified the db pool, but the default actually checked 2 different ENVs and provided a fallback if it's not provided. Lastly, I was able to move the prepared_statements section to the defaults, because the .env.vagrant file doesn't specify ENV['PREPARED_STATEMENTS'], development still just sets it to 'false'.
2021-02-14 04:51:23 +00:00
<<: *default
Replace Makara with an initial Rails 6 role based splitting method.
2021-02-09 19:38:10 +00:00
url: <%= ENV['DB_SLAVE1_URL'] %>
Mark the replicas as replicas Rails won't even attempt to write to a replica. Without this option, a write attempt would actually run against Postgres, and it would be up to Postgres to throw a readonly error. Additionally, marking it as a replica teaches ActiveRecord that it should not attempt to run migrations against this connection. https://api.rubyonrails.org/classes/ActiveRecord/DatabaseConfigurations.html#method-i-configs_for I'm actually pretty sure that the lack of `replica: true` is why there's currently a db/slave1_schema.rb and db/slave2_schema.rb
2021-02-14 04:59:02 +00:00
replica: true
Replace Makara with an initial Rails 6 role based splitting method.
2021-02-09 19:38:10 +00:00
slave2:
Simplify database.yml by merging in default options Anything in the &default section can be merged in using <<: *default In this case, the default already specifies that the adapter is postgresql, the timeout is 5000, the encoding is unicode. It also already specified the db pool, but the default actually checked 2 different ENVs and provided a fallback if it's not provided. Lastly, I was able to move the prepared_statements section to the defaults, because the .env.vagrant file doesn't specify ENV['PREPARED_STATEMENTS'], development still just sets it to 'false'.
2021-02-14 04:51:23 +00:00
<<: *default
Replace Makara with an initial Rails 6 role based splitting method.
2021-02-09 19:38:10 +00:00
url: <%= ENV['DB_SLAVE1_URL'] %>
Mark the replicas as replicas Rails won't even attempt to write to a replica. Without this option, a write attempt would actually run against Postgres, and it would be up to Postgres to throw a readonly error. Additionally, marking it as a replica teaches ActiveRecord that it should not attempt to run migrations against this connection. https://api.rubyonrails.org/classes/ActiveRecord/DatabaseConfigurations.html#method-i-configs_for I'm actually pretty sure that the lack of `replica: true` is why there's currently a db/slave1_schema.rb and db/slave2_schema.rb
2021-02-14 04:59:02 +00:00
replica: true