# Installare Discourse su Ubuntu o Debian per lo sviluppo
**URL:** https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727
**Category:** Developer Guides
**Tags:** dev-install, how-to
**Created:** [12 Aprile 2014, 10:22pm UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727 "2014-04-12T22:22:07Z")
**Posts on this page:** 20
**Page:** 3
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [28 Ottobre 2024, 9:20am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/707 "2024-10-28T09:20:28Z")
@merefield Dovrei preoccuparmi di questi?
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [28 Ottobre 2024, 10:00am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/708 "2024-10-28T10:00:41Z")
Sì, dovresti esserlo.
Cosa restituisce `redis-cli ping`?
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [28 Ottobre 2024, 10:03am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/709 "2024-10-28T10:03:30Z")
Ti darò una risposta domani (sono un po’ impegnato oggi)
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [29 Ottobre 2024, 5:19am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/710 "2024-10-29T05:19:59Z")
Restituisce `PONG`.
@merefield Presumo che questo significhi che va bene? Qualche idea sul perché dovrebbe andare in timeout allora?
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [30 Ottobre 2024, 12:25pm UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/712 "2024-10-30T12:25:03Z")
Stai suggerendo che faccia il downgrade di Docker a quello menzionato?
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [31 Ottobre 2024, 2:48am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/714 "2024-10-31T02:48:48Z")
Hmm… okay. C’è solo 1 problema: non sto usando Docker. Suppongo che dovrò solo seguire [questa guida](https://meta.discourse.org/t/-/102009?silent=true) allora…
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [31 Ottobre 2024, 6:58am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/715 "2024-10-31T06:58:16Z")
Sì, certo che non lo sei! :facepalm: Quel consiglio era errato, cancellato.
Dalla tua risposta sembra che Redis stia rispondendo e sia in esecuzione.
È in esecuzione sulla porta classica che Discourse si aspetta?
prova `lsof -wni | grep redis`
Dovrebbe essere sulla porta 6379, credo.
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [1 Novembre 2024, 8:45am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/716 "2024-11-01T08:45:05Z")
Quando lo eseguo, non succede nulla.
```plaintext
natedhaliwal@raspberrypi:~ $ lsof -wni | grep redis
natedhaliwal@raspberrypi:~ $ cd discourse-f
natedhaliwal@raspberrypi:~/discourse-f $ lsof -wni | grep redis
natedhaliwal@raspberrypi:~/discourse-f $
```
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [1 Novembre 2024, 9:39am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/717 "2024-11-01T09:39:20Z")
È indipendente dalla directory.
Prova:
`sudo lsof -wni | grep redis`
Questo _dovrebbe_ riportare il servizio redis. In caso contrario, il tuo servizio per qualche motivo non è in esecuzione e dovrai indagare sul perché.
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [4 Novembre 2024, 6:18am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/718 "2024-11-04T06:18:48Z")
Dopo aver eseguito questo, ricevo ancora l’errore di timeout. Molto strano. Potrebbe essere il mio ISP che lo blocca?
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [4 Novembre 2024, 7:41am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/719 "2024-11-04T07:41:23Z")
Non è una soluzione, è una diagnosi. Qual è stato il risultato di quel comando?
Dovrebbe assomigliare a questo:
```plaintext
robert@raspberrypi:~/discourse $ sudo lsof -wni | grep redis
redis-ser 890 redis 6u IPv4 4052 0t0 TCP 127.0.0.1:redis (LISTEN)
```
prova anche questo:
```plaintext
robert@raspberrypi:~/discourse $ ps -A | grep redis
890 ? 00:00:05 redis-server
```
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [5 Novembre 2024, 6:10am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/720 "2024-11-05T06:10:39Z")
@merefield Ho ottenuto questo:
```plaintext
natedhaliwal@raspberrypi:~/discourse-f $ sudo lsof -wni | grep redis
redis-ser 750 redis 8u IPv4 16886 0t0 TCP 127.0.0.1:redis (LISTEN)
natedhaliwal@raspberrypi:~/discourse-f $ ps -A | grep redis
750 ? 00:00:01 redis-server
9449 ? 00:00:00 redis-server
```
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [5 Novembre 2024, 6:27am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/721 "2024-11-05T06:27:11Z")
Non sembra corretto: hai due processi redis in esecuzione?
Eliminerei il secondo processo.
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [5 Novembre 2024, 6:29am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/722 "2024-11-05T06:29:55Z")
Presumo di usare il comando `shutdown` in `redis-cli`, quindi ricreare e migrare nuovamente il db?
O `client kill`?
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [5 Novembre 2024, 6:30am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/723 "2024-11-05T06:30:34Z")
no, just kill the second process
`kill -9 `
In questo caso, l’ID del processo è 9449, credo.
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [5 Novembre 2024, 6:41am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/724 "2024-11-05T06:41:31Z")
Hmm…
```plaintext
-bash: kill: (9449) - Operazione non permessa
```
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [5 Novembre 2024, 6:42am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/725 "2024-11-05T06:42:11Z")
Usa sudo …
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [5 Novembre 2024, 6:47am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/726 "2024-11-05T06:47:46Z")
Sarebbe questo un errore?
```plaintext
natedhaliwal@raspberrypi:~/discourse-f $ RAILS_ENV=test bin/rails db:create db:migrate
Database 'discourse_test' already exists
Database 'discourse_test_multisite' already exists
/home/natedhaliwal/discourse-f/app/models/post_action_type.rb:16:in `expire_cache'
/home/natedhaliwal/discourse-f/app/models/post_action_type.rb:42:in `reload_types'
/home/natedhaliwal/discourse-f/app/models/flag.rb:37:in `reset_flag_settings!'
(eval):78:in `block (2 levels) in run_file'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/discourse-seed-fu-2.3.12/lib/seed-fu/runner.rb:46:in `eval'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/discourse-seed-fu-2.3.12/lib/seed-fu/runner.rb:46:in `block (2 levels) in run_file'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/discourse-seed-fu-2.3.12/lib/seed-fu/runner.rb:58:in `block in open'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/discourse-seed-fu-2.3.12/lib/seed-fu/runner.rb:57:in `open'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/discourse-seed-fu-2.3.12/lib/seed-fu/runner.rb:57:in `open'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/discourse-seed-fu-2.3.12/lib/seed-fu/runner.rb:36:in `block in run_file'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/activerecord-7.1.4.1/lib/active_record/connection_adapters/abstract/transaction.rb:535:in `block in within_new_transaction'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/activesupport-7.1.4.1/lib/active_support/concurrency/null_lock.rb:9:in `synchronize'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/activerecord-7.1.4.1/lib/active_record/connection_adapters/abstract/transaction.rb:532:in `within_new_transaction'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/activerecord-7.1.4.1/lib/active_record/connection_adapters/abstract/database_statements.rb:344:in `transaction'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/activerecord-7.1.4.1/lib/active_record/transactions.rb:212:in `transaction'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/discourse-seed-fu-2.3.12/lib/seed-fu/runner.rb:35:in `run_file'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/discourse-seed-fu-2.3.12/lib/seed-fu/runner.rb:26:in `block in run'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/discourse-seed-fu-2.3.12/lib/seed-fu/runner.rb:25:in `each'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/discourse-seed-fu-2.3.12/lib/seed-fu/runner.rb:25:in `run'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/discourse-seed-fu-2.3.12/lib/discourse-seed-fu.rb:29:in `seed'
/home/natedhaliwal/discourse-f/lib/tasks/db.rake:264:in `block (2 levels) in '
/home/natedhaliwal/discourse-f/lib/distributed_mutex.rb:53:in `block in synchronize'
/home/natedhaliwal/discourse-f/lib/distributed_mutex.rb:49:in `synchronize'
/home/natedhaliwal/discourse-f/lib/distributed_mutex.rb:49:in `synchronize'
/home/natedhaliwal/discourse-f/lib/distributed_mutex.rb:34:in `synchronize'
/home/natedhaliwal/discourse-f/lib/tasks/db.rake:234:in `block in '
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/task.rb:281:in `block in execute'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/task.rb:281:in `each'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/task.rb:281:in `execute'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/task.rb:199:in `synchronize'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/task.rb:199:in `invoke_with_call_chain'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/task.rb:188:in `invoke'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/application.rb:188:in `invoke_task'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/application.rb:138:in `block (2 levels) in top_level'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/application.rb:138:in `each'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/application.rb:138:in `block in top_level'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/application.rb:147:in `run_with_threads'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/application.rb:132:in `top_level'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/railties-7.1.4.1/lib/rails/commands/rake/rake_command.rb:27:in `block (2 levels) in perform'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/application.rb:214:in `standard_exception_handling'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/railties-7.1.4.1/lib/rails/commands/rake/rake_command.rb:27:in `block in perform'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/railties-7.1.4.1/lib/rails/commands/rake/rake_command.rb:44:in `block in with_rake'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rake-13.2.1/lib/rake/rake_module.rb:59:in `with_application'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/railties-7.1.4.1/lib/rails/commands/rake/rake_command.rb:41:in `with_rake'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/railties-7.1.4.1/lib/rails/commands/rake/rake_command.rb:20:in `perform'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/railties-7.1.4.1/lib/rails/command.rb:156:in `invoke_rake'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/railties-7.1.4.1/lib/rails/command.rb:73:in `block in invoke'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/railties-7.1.4.1/lib/rails/command.rb:149:in `with_argv'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/railties-7.1.4.1/lib/rails/command.rb:69:in `invoke'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/railties-7.1.4.1/lib/rails/commands.rb:18:in `:37:in `require'
:37:in `require'
/home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
bin/rails:18:in `
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [5 Novembre 2024, 6:50am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/727 "2024-11-05T06:50:09Z")
Perché la tua directory discourse si chiama `discourse-f`?
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [5 Novembre 2024, 6:57am UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/728 "2024-11-05T06:57:13Z")
Poiché esiste già una cartella chiamata `discourse`, che contiene una cartella `postgres` che ha dichiarato di non poter essere clonata poiché era già piena. Pertanto, l’ho clonata in una nuova cartella.
Sono appena riuscito a `sudo rm -rf` quella cartella (ho provato `rm -rf` ma ha detto “permission denied”, quindi ho applicato la stessa tattica [qui](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/725?u=natedhaliwal) e ho usato `sudo`)
Ciò influisce sull’installazione?
[Pagina precedente](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727.md?page=2)
[Pagina seguente](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727.md?page=4)