Installa Discourse su macOS per lo sviluppo

[Discourse]

Questa guida illustra le istruzioni di installazione per un ambiente di sviluppo macOS; per le guide di produzione, vedere: Install Discourse in production with the official supported instructions

Quindi vuoi configurare Discourse su macOS per lavorarci e svilupparci sopra?

Presumeremo che tu non abbia installato Ruby/Rails/Postgres/Redis sul tuo Mac. Iniziamo !

Installa le dipendenze di Discourse

Avrai bisogno dei seguenti pacchetti sul tuo sistema:

• Git
• rbenv o asdf
• ruby-build
• Ruby (ultima versione stabile)
• Rails
• PostgreSQL
• SQLite
• Redis
• Node.js
• pnpm
• MailHog**
• ImageMagick**

** opzionale

riavvia il tuo terminale

Ora che abbiamo installato le dipendenze di Discourse, passiamo all’installazione di Discourse stesso.

Riavvia il tuo Terminale

Esci dalla tua shell e riavviandola ti assicurerai che i percorsi ai pacchetti installati vengano acquisiti correttamente dal Terminale.

Clona Discourse

Clona il repository di Discourse nella cartella ~/discourse:

git clone https://github.com/discourse/discourse.git ~/discourse

~ indica la cartella home, quindi il codice sorgente di Discourse sarà disponibile nella tua cartella home.

Avvia Discourse

Passa alla tua cartella Discourse:

cd ~/discourse

Installa le gem richieste

bundle install

Installa le dipendenze JS

pnpm install

Successivamente, esegui questi comandi per configurare la tua istanza locale di Discourse:

bundle exec rake db:create
bundle exec rake db:migrate
RAILS_ENV=test bundle exec rake db:create db:migrate

Avvia i server rails + Ember, qui hai due opzioni.

Opzione 1: usando due schede/finestre separate del Terminale, esegui Rails ed Ember CLI separatamente tramite

bundle exec rails server

e

bin/ember-cli

Opzione 2: usando una sola scheda/finestra del Terminale:

bin/ember-cli -u # eseguirà il server Unicorn in background

Ora dovresti essere in grado di navigare su http://localhost:4200 per vedere la tua installazione locale di Discourse. (Nota che il primo caricamento potrebbe richiedere fino a un minuto mentre il server si riscalda.)

Puoi anche provare ad eseguire le specifiche:

bundle exec rake autospec

Tutti (o quasi tutti) i test dovrebbero essere superati.

Crea un nuovo Amministratore

Per creare un nuovo amministratore, esegui il seguente comando:

RAILS_ENV=development bundle exec rake admin:create

Segui le istruzioni per creare un account amministratore.

Configura la Posta

Esegui MailHog:

mailhog

---

Congratulazioni! Ora sei l’amministratore della tua installazione di Discourse!

Buon hacking! E per iniziare, consulta Guida per principianti alla creazione di plugin per Discourse.

---

Questo documento è controllato in versione - suggerisci modifiche su github.

[jamesmarkcook (James Cook)]

If anyone is getting failing specs with most of them being .count errors, then try the following:

RAILS_ENV=test bundle exec rake db:reset

I had a problem where development data somehow got into my test database and was causing lots of failures.

[henrikbg (Henrik Berg)]

Is it possible to reset a discourse completely?

[techAPJ (Arpit Jalan)]

@Henrik_B

Is it possible to reset a discourse completely?

Yes, do:

rake db:drop db:create db:migrate

Note that this will wipe everything and you will have to create your Admin user account again.

[Chaboi_3000]

Can someone assist me in how I can update my discourse?

/launcher rebuild app

returns an error.

[techAPJ (Arpit Jalan)]

./launcher rebuild app is for discourse_docker based production setup. To update local/development Discourse instance you need:

cd ~/discourse
git pull origin master

[Chaboi_3000]

@techAPJ

git pull origin master

I get this error @techAPJ,

error: Your local changes to the following files would be overwritten by merge:
	.gitignore
Please commit your changes or stash them before you merge.
Aborting

[techAPJ (Arpit Jalan)]

The error message is pretty clear:

Please commit your changes or stash them before you merge.

If you want to ignore your local changes, do:

git fetch origin
git reset --hard origin/master

[Decorbuz]

Using the guide from the Ruby on Rails forum, I’m currently stuck on step 7.

This is probably a very “newbie” question, but how do I “point” to the experimental branch that was linked in that topic? I tried a few things and was ultimately giving the Unknown command mini_racer, message every single time.

[blake (Blake Erickson)]

They’re fine asking here.

There are some specific m1 instructions we wrote that we reference on the rails forum in this guide.

@Decorbuz

This is probably a very “newbie” question, but how do I “point” to the experimental branch that was linked in that topic?

I’d have to look on my m1 air later, and maybe my fellow coworks who recently setup new macs might know better if this is even still needed, but there is an example of how to point to a branch in step 7:

gem 'mini_racer', github: 'rubyjs/mini_racer', branch: 'refs/pull/186/head'

So you would edit this line in your local version of discourse/Gemfile:

Gemfile

and then run bundle install.

[Decorbuz]

@pfaffman

If you didn’t follow these instructions (I don’t see a step 7) then this isn’t a very good place to ask your question.

It’s linked right at the top of the original post.

The topic from the Ruby on Rails forum has been dead for many months now. The OP hasn’t been active since Feburary and hasn’t replied to any comments there asking for help.

There are more people to help me here. Just saying.

@blake

there is an example of how to point to a branch in step 7:

gem 'mini_racer', github: 'rubyjs/mini_racer', branch: 'refs/pull/186/head'

I tried copying that into Terminal and received the same Unknown command mini_racer, error from before.

Admittedly, the guide from the Ruby on Rails forum isn’t as clear as I’d hope in that regard.

Apologies in advance…

[blake (Blake Erickson)]

@Decorbuz

I tried copying that into Terminal and received the same Unknown command mini_racer, error from before.

It’s not a command to run. You will need to EDIT the actual text file called “Gemfile” located inside the discourse directory.

[Decorbuz]

@blake

You will need to EDIT the actual text file called “Gemfile” located inside the discourse directory.

Doh!

Thanks! Let me try that right now.

In my opinion, somebody should edit the guide from the Ruby on Rails forum and provide further clarification regarding step 7. Just my two cents though.

I will be right back. Hold on a second…

[blake (Blake Erickson)]

Sorry I have to run, but I think that mini_racer fix for m1 macs has been merged in. I just checked my Gemfile on my m1 mac and mine isn’t edited. So I think you can skip step 7.

[Decorbuz]

I ran step 8 and received the Could not locate Gemfile error.

I (think) I was able to figure out step 7, but step 8 is still giving me trouble and is spitting out the error mentioned above.

[blake (Blake Erickson)]

@Decorbuz

I ran step 8 and received the Could not locate Gemfile error.

You need to be inside of the discourse directory when you run bundle install.

@techAPJ

Clone Discourse

Clone the Discourse repository in ~/discourse folder:

git clone https://github.com/discourse/discourse.git ~/discourse

~ indicates home folder, so Discourse source code will be available in your home folder.

Bootstrap Discourse

Switch to your Discourse folder:

cd ~/discourse

Install the needed gems

bundle install

[JQ331]

@merefield

Actually it’s a bit more than a couple of bucks (it’s a 4GB 8 core VPS - probably overkill) but allows me to develop from anywhere on any platform. Pretty performant but there will always be a few seconds delay if you restart the web server.

Hi @merefield: Can you describe your remote setup a little more?

While developing a theme allows me to add changes on a live site, for developing a plugin I don’t see any way around doing it on my local machine, having the whole discourse codebase there (with my plugin on top of it).

The result is that for any (non-css) change when coding a plugin, when I reload it 1) kicks off my computer’s fan and 2) takes a solid 30 seconds to reload. And if I need to restart the server, it takes several minutes.

Those delays really add up–with the result that it might take me an hour to code something up that with my normal coding flow (where there’s hot reload or at most 2-3 seconds per change) would take 15 minutes.

So, I’d appreciate any suggestions for speeding things up.

[merefield (Robert)]

This arguably would be better on the Ubuntu topic, as I’m just running that install on a cloud server, fronted by nginx and a full DNS (no docker), so I’m actually addressing the domain. Running everything from the terminal. I’ve even got Ember CLI working well in that set up now.

It’s not that quick either, but fast enough. It has the benefit of being able to run and test full https callback services.

The fastest plugin development environment by far that I’m aware of is local Docker Dev on WSL2 which screams. It’s also extremely simple to maintain. Unfortunately discourse_theme doesn’t work in that environment yet afaik so I’m back to my cloud server for that work.

It’s a little odd why Apple is lagging behind here? The Microsoft engineers have shown themselves to be very canny.

[Nacho_Caballero]

Nel caso in cui qualcuno riscontri errori durante l’installazione di ruby 2.7.3, apparentemente qualcosa è cambiato dopo Xcode 12 che interrompe il processo di installazione con rbenv:

installing older Ruby versions on OSX after XCode 12

Ho continuato a ricevere questo messaggio, anche se ho le ultime versioni di psych e libyaml installate:

Sembra che alla tua installazione di ruby manchi psych (per l'output YAML).
Per eliminare questo avviso, installa libyaml e reinstalla il tuo ruby.

Ho provato la soluzione alternativa che suggeriscono nella guida, ma ho continuato a ricevere lo stesso errore e alla fine ho dovuto usare rvm:

rvm install 2.7.3

[JQ331]

Per quanto riguarda la programmazione più veloce quando si sviluppa un plugin, ho recentemente cambiato il mio approccio. E sta funzionando alla grande. In sostanza, sposta tutte le cose di front-end in un componente del tema e codifica solo le cose di back-end nel plugin stesso. So che altri l’hanno già capito. Ma ora che lo sto facendo, la programmazione è molto più veloce e piacevole. Dettagli qui.