[i-Diário] Erro na execução do i-Diário 1.6 em servidor web

Dúvidas
1

Estou seguindo o tutorial de instalação em servidor web do i-Diário 1.6, a parte de instalação ocorreu tudo como esperado. Porém na parte de execução ao tentar executar o primeiro comando em uma aba separada do terminal no servidor, apresenta o seguinte erro.

root@ti:~/i-diario# bundle exec rails server -b 0.0.0.0 -p 80
Tilt::LessTemplate is deprecated, consider switching from LESS to SCSS
warning: parser/current is loading parser/ruby26, which recognizes 2.6.10-compliant syntax, but you are running 2.6.6.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
=> Booting Puma
=> Rails 5.0.7.2 application starting in development on http://0.0.0.0:80
=> Run `rails server -h` for more startup options
Exiting
Traceback (most recent call last):
	79: from bin/rails:3:in `<main>'
	78: from bin/rails:3:in `load'
	77: from /root/i-diario/bin/spring:15:in `<top (required)>'
	76: from /root/i-diario/bin/spring:15:in `require'
	75: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/spring-2.1.1/lib/spring/binstub.rb:11:in `<top (required)>'
	74: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/spring-2.1.1/lib/spring/binstub.rb:11:in `load'
	73: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/spring-2.1.1/bin/spring:49:in `<top (required)>'
	72: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/spring-2.1.1/lib/spring/client.rb:30:in `run'
	71: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/spring-2.1.1/lib/spring/client/command.rb:7:in `call'
	70: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/spring-2.1.1/lib/spring/client/rails.rb:28:in `call'
	69: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/spring-2.1.1/lib/spring/client/rails.rb:28:in `load'
	68: from /root/i-diario/bin/rails:9:in `<top (required)>'
	67: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bootsnap-1.18.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
	66: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/bootsnap-1.18.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
	65: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/commands.rb:18:in `<main>'
	64: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/commands/commands_tasks.rb:49:in `run_command!'
	63: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/commands/commands_tasks.rb:85:in `server'
	62: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/commands/commands_tasks.rb:85:in `tap'
	61: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/commands/commands_tasks.rb:90:in `block in server'
	60: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/commands/server.rb:102:in `start'
	59: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/commands/server.rb:148:in `log_to_stdout'
	58: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/rack-2.2.17/lib/rack/server.rb:422:in `wrapped_app'
	57: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/commands/server.rb:84:in `app'
	56: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/rack-2.2.17/lib/rack/server.rb:249:in `app'
	55: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/rack-2.2.17/lib/rack/server.rb:349:in `build_app_and_options_from_config'
	54: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/rack-2.2.17/lib/rack/builder.rb:66:in `parse_file'
	53: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/rack-2.2.17/lib/rack/builder.rb:105:in `load_file'
	52: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/rack-2.2.17/lib/rack/builder.rb:116:in `new_from_string'
	51: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/rack-2.2.17/lib/rack/builder.rb:116:in `eval'
	50: from /root/i-diario/config.ru:3:in `block in <main>'
	49: from /root/i-diario/config.ru:3:in `require_relative'
	48: from /root/i-diario/config/environment.rb:5:in `<main>'
	47: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/application.rb:352:in `initialize!'
	46: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/initializable.rb:54:in `run_initializers'
	45: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:205:in `tsort_each'
	44: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:226:in `tsort_each'
	43: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:347:in `each_strongly_connected_component'
	42: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:347:in `call'
	41: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:347:in `each'
	40: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:349:in `block in each_strongly_connected_component'
	39: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:415:in `each_strongly_connected_component_from'
	38: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:415:in `call'
	37: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/initializable.rb:44:in `tsort_each_child'
	36: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/initializable.rb:44:in `each'
	35: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:421:in `block in each_strongly_connected_component_from'
	34: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:415:in `each_strongly_connected_component_from'
	33: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:415:in `call'
	32: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/initializable.rb:44:in `tsort_each_child'
	31: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/initializable.rb:44:in `each'
	30: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:421:in `block in each_strongly_connected_component_from'
	29: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:415:in `each_strongly_connected_component_from'
	28: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:415:in `call'
	27: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/initializable.rb:44:in `tsort_each_child'
	26: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/initializable.rb:44:in `each'
	25: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:421:in `block in each_strongly_connected_component_from'
	24: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:431:in `each_strongly_connected_component_from'
	23: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:422:in `block (2 levels) in each_strongly_connected_component_from'
	22: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:422:in `block (2 levels) in each_strongly_connected_component_from'
	21: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:422:in `block (2 levels) in each_strongly_connected_component_from'
	20: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
	19: from /root/.rbenv/versions/2.6.6/lib/ruby/2.6.0/tsort.rb:228:in `block in tsort_each'
	18: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/initializable.rb:55:in `block in run_initializers'
	17: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/initializable.rb:30:in `run'
	16: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/initializable.rb:30:in `instance_exec'
	15: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/engine.rb:611:in `block in <class:Engine>'
	14: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/engine.rb:611:in `each'
	13: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/engine.rb:612:in `block (2 levels) in <class:Engine>'
	12: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/engine.rb:647:in `load_config_initializer'
	11: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/activesupport-5.0.7.2/lib/active_support/notifications.rb:166:in `instrument'
	10: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/railties-5.0.7.2/lib/rails/engine.rb:648:in `block in load_config_initializer'
	 9: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/activesupport-5.0.7.2/lib/active_support/dependencies.rb:287:in `load'
	 8: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/activesupport-5.0.7.2/lib/active_support/dependencies.rb:259:in `load_dependency'
	 7: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/activesupport-5.0.7.2/lib/active_support/dependencies.rb:287:in `block in load'
	 6: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/activesupport-5.0.7.2/lib/active_support/dependencies.rb:287:in `load'
	 5: from /root/i-diario/config/initializers/redis.rb:17:in `<main>'
	 4: from /root/i-diario/config/initializers/redis.rb:17:in `new'
	 3: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/redis-4.8.1/lib/redis.rb:87:in `initialize'
	 2: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/redis-4.8.1/lib/redis.rb:87:in `new'
	 1: from /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/redis-4.8.1/lib/redis/client.rb:92:in `initialize'
/root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/redis-4.8.1/lib/redis/client.rb:465:in `_parse_options': invalid uri scheme '' (ArgumentError)
root@ti:~/i-diario#

O servidor do i-Educar está instalado em outra máquina executando normalmente, é necessário alguma configuração no i-Diário antes da execução? Se sim seria bom incluir isso no Guia de Instalação.

2

Você instalou o redis?
A aplicação consegue acessa-lo?

3

Sim o redis está instalado:

root@ti:~/i-diario# redis-server --version
Redis server v=6.0.16 sha=00000000:0 malloc=jemalloc-5.2.1 bits=64 build=a3fdef44459b3ad6
root@ti:~/i-diario#

Como faço para verificar se a aplicação consegue acessar?

O redis está rodando.

Segue o arquivo de configuração do redis.rb

 root@ti:~/i-diario# cat /root/i-diario/config/initializers/redis.rb
if Rails.env.test?
  require 'mock_redis'
  $REDIS_DB = MockRedis.new
else
  if (Rails.application.secrets[:REDIS_MODE] == 'sentinel')
    config_redis = {
      url: "#{Rails.application.secrets[:REDIS_URL]}#{Rails.application.secrets[:REDIS_DB_SIDEKIQ]}",
      role: "master",
      sentinels: Rails.application.secrets[:REDIS_SENTINELS].split(";").map { |host| { host: host,  port: 26379 }}
    }
  else
    config_redis = {
      url: "#{Rails.application.secrets[:REDIS_URL]}#{Rails.application.secrets[:REDIS_DB_SIDEKIQ]}"
    }
  end

  $REDIS_DB = Redis.new(config_redis)

  Sidekiq.configure_server do |config|
    config.redis = config_redis
  end

  Sidekiq.configure_client do |config|
    config.redis = config_redis
  end
end
root@ti:~/i-diario#

No arquivo /i-diario/config/secrets.yml está preenchido com apenas development: secret_key_base:

4

Você precisa acrescentar REDIS_URL: redis://localhost no secrets.yml

1 curtida
5

Acrescentei REDIS_URL: redis://localhost no secrets.yml e deu certo a execução dos 3 comandos em abas distintas no servidor, porém não consigo acessar localhost.

image
image855×480 35.1 KB

O firewall já está desabilitado. Tentei acessar pelo IP 10.35.209.248 do servidor e dá erro 404

Segue saída do comando bundle exec rails server -b 0.0.0.0 -p 80:

root@ti:~/i-diario# bundle exec rails server -b 0.0.0.0 -p 80
Tilt::LessTemplate is deprecated, consider switching from LESS to SCSS
warning: parser/current is loading parser/ruby26, which recognizes 2.6.10-compliant syntax, but you are running 2.6.6.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
=> Booting Puma
=> Rails 5.0.7.2 application starting in development on http://0.0.0.0:80
=> Run `rails server -h` for more startup options
WARNING: Sidekiq::Web.session_secret= is no longer relevant and will be removed in Sidekiq 7.0. /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/sidekiq-6.5.12/lib/sidekiq/web.rb:79:in `set'
/root/i-diario/config/initializers/sidekiq_web.rb:9: warning: Sidekiq's Delayed Extensions will be removed in Sidekiq 7.0
Puma starting in single mode...
* Puma version: 6.6.0 ("Return to Forever")
* Ruby version: ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-linux]
*  Min threads: 0
*  Max threads: 5
*  Environment: development
*          PID: 3613
* Listening on http://0.0.0.0:80
Use Ctrl-C to stop
Started GET "/" for 10.35.209.248 at 2025-08-04 15:55:30 -0300
  ActiveRecord::SchemaMigration Load (6.3ms)  SELECT "schema_migrations".* FROM "schema_migrations"
Processing by DashboardController#index as HTML
  Parameters: {"locale"=>"en"}
  Entity Load (2.1ms)  SELECT  "entities".* FROM "entities" WHERE "entities"."domain" = $1 LIMIT $2  [["domain", "10.35.209.248"], ["LIMIT", 1]]
Redirected to http://10.35.209.248/404
Completed 302 Found in 21ms (ActiveRecord: 9.7ms)

Saída do comando bundle exec sidekiq -q synchronizer_enqueue_next_job -c 1 --logfile log/sidekiq.log

root@ti:~/i-diario# bundle exec sidekiq -q synchronizer_enqueue_next_job -c 1 --logfile log/sidekiq.log
ERROR: Logfile redirection was removed in Sidekiq 6.0, Sidekiq will only log to STDOUT
Tilt::LessTemplate is deprecated, consider switching from LESS to SCSS
warning: parser/current is loading parser/ruby26, which recognizes 2.6.10-compliant syntax, but you are running 2.6.6.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
2025-08-04T18:54:29.637Z pid=3725 tid=illc4xagd INFO: Booting Sidekiq 6.5.12 with Sidekiq::RedisConnection::RedisAdapter options {:url=>"redis://localhost/"}
WARNING: Sidekiq::Web.session_secret= is no longer relevant and will be removed in Sidekiq 7.0. /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/sidekiq-6.5.12/lib/sidekiq/web.rb:79:in `set'
/root/i-diario/config/initializers/sidekiq_web.rb:9: warning: Sidekiq's Delayed Extensions will be removed in Sidekiq 7.0


               m,
               `$b
          .ss,  $$:         .,d$
          `$$P,d$P'    .,md$P"'
           ,$$$$$b/md$$$P^'
         .d$$$$$$/$$$P'
         $$^' `"/$$$'       ____  _     _      _    _
         $:     ,$$:       / ___|(_) __| | ___| | _(_) __ _
         `b     :$$        \___ \| |/ _` |/ _ \ |/ / |/ _` |
                $$:         ___) | | (_| |  __/   <| | (_| |
                $$         |____/|_|\__,_|\___|_|\_\_|\__, |
              .d$$                                       |_|
      

2025-08-04T18:54:31.261Z pid=3725 tid=illc4xagd INFO: Booted Rails 5.0.7.2 application in development environment
2025-08-04T18:54:31.261Z pid=3725 tid=illc4xagd INFO: Running in ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-linux]
2025-08-04T18:54:31.261Z pid=3725 tid=illc4xagd INFO: See LICENSE and the LGPL-3.0 for licensing details.
2025-08-04T18:54:31.261Z pid=3725 tid=illc4xagd INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org
2025-08-04T18:54:31.265Z pid=3725 tid=illc4xagd INFO: Starting processing, hit Ctrl-C to stop

Saída do comando bundle exec sidekiq -c 10 --logfile log/sidekiq.log:

root@ti:~/i-diario# bundle exec sidekiq -c 10 --logfile log/sidekiq.log
ERROR: Logfile redirection was removed in Sidekiq 6.0, Sidekiq will only log to STDOUT
Tilt::LessTemplate is deprecated, consider switching from LESS to SCSS
warning: parser/current is loading parser/ruby26, which recognizes 2.6.10-compliant syntax, but you are running 2.6.6.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
2025-08-04T18:55:03.208Z pid=3835 tid=javjyr6g3 INFO: Booting Sidekiq 6.5.12 with Sidekiq::RedisConnection::RedisAdapter options {:url=>"redis://localhost/"}
WARNING: Sidekiq::Web.session_secret= is no longer relevant and will be removed in Sidekiq 7.0. /root/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/sidekiq-6.5.12/lib/sidekiq/web.rb:79:in `set'
/root/i-diario/config/initializers/sidekiq_web.rb:9: warning: Sidekiq's Delayed Extensions will be removed in Sidekiq 7.0


               m,
               `$b
          .ss,  $$:         .,d$
          `$$P,d$P'    .,md$P"'
           ,$$$$$b/md$$$P^'
         .d$$$$$$/$$$P'
         $$^' `"/$$$'       ____  _     _      _    _
         $:     ,$$:       / ___|(_) __| | ___| | _(_) __ _
         `b     :$$        \___ \| |/ _` |/ _ \ |/ / |/ _` |
                $$:         ___) | | (_| |  __/   <| | (_| |
                $$         |____/|_|\__,_|\___|_|\_\_|\__, |
              .d$$                                       |_|
      

2025-08-04T18:55:04.982Z pid=3835 tid=javjyr6g3 INFO: Booted Rails 5.0.7.2 application in development environment
2025-08-04T18:55:04.983Z pid=3835 tid=javjyr6g3 INFO: Running in ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-linux]
2025-08-04T18:55:04.983Z pid=3835 tid=javjyr6g3 INFO: See LICENSE and the LGPL-3.0 for licensing details.
2025-08-04T18:55:04.984Z pid=3835 tid=javjyr6g3 INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org
2025-08-04T18:55:04.986Z pid=3835 tid=javjyr6g3 INFO: Starting processing, hit Ctrl-C to stop
6

Veja que estás pedindo para o rails server responder na porta 80, mas na web você está requisitando a porta 3000. Tem que ser a mesma porta.

7

Executei o comando com a porta 3000 e agora dá erro 404 de página não encontrada.

image
image829×425 24.4 KB

Tentei executar com a porta 80 e acessando na web com 80 também dá o mesmo erro.

No tutorial de instalação em servidor web primeiro instrui a executar na porta 80 e depois acessar o localhost na porta 3000.

8

Tens que ver a sua configuração da entidade. Esta na tabela entities, acho que coluna domain.

1 curtida
9

Bem estou com o mesmo problema. Alguma solução encontrada?

10

Tinha apenas os bancos de dados idiario_development e idiario_test, então executei novamente os comandos do tutoral de instalação em servidor web da etapa “Finalize a instalação”:

bundle exec rails db:create
bundle exec rails db:migrate

echo "bundle exec rails entity:setup NAME=idiario DOMAIN=$(hostname -I | awk '{print $1}') DATABASE=idiario" | bash
bundle exec rails entity:admin:create NAME=idiario ADMIN_PASSWORD=A123456789$

para criar o banco de dados idiario.

Conferi no histórico do terminal e eu tinha executado os comandos corretamente, mas parece que por algum motivo não foi feito nenhuma modificação desde a etapa “Configure e copie os arquivos necessários:”

Após executar novamente a etapa “Finalize a instalação” e executar os comandos de execução em abas distintas, deu certo acessar o i-Diário pelo endereço IP, mas não deu certo acessar pelo localhost. Tem haver com a tabela entities? Como devo preencher? Atualmente está vazia:

postgres=# \c idiario
You are now connected to database "idiario" as user "postgres".
idiario=# SELECT * FROM entities;
 id | name | domain | config | created_at | updated_at | disabled | disabled_sync 
----+------+--------+--------+------------+------------+----------+---------------
(0 rows)

Estou com dúvida sobre como configurar API de Integração para fazer a conexão com o i-Educar, no tutorial não dá muitos detalhes do que fazer, mas acho que vou abrir outra Dúvida para separar os assuntos.

1 curtida
11

Qual a saída desse comando?

12

Não vou ter mais o histórico da saída desses comandos. O banco de dados idiario agora existe assim como o usuario admin. Porém a tabela entities do banco de dados continua vazia.

postgres=# \c idiario
You are now connected to database "idiario" as user "postgres".
idiario=# SELECT * FROM entities;
 id | name | domain | config | created_at | updated_at | disabled | disabled_sync 
----+------+--------+--------+------------+------------+----------+---------------
(0 rows)