After several trials in various operating systems with a different way of installation procedures, finally, I was able to install Forem in my local machine.
Linux + Docker combination is a hassle-free installation.
Windows with WSL with the documentation is also pretty good.
Mac + Docker is easy peasy.
Now I have a local instance, but pushing it to Heroku is not an easy task; I was encountering a lot of errors.
So I decided to look over the complete documentation of Forem before pushing it to Heroku. During this process, I learned a lot about rails and foreman and found some interesting points which might have a reason for the failure of production Forem instance.
- Almost all env variables are essential.
- Addons like Redis, ElasticSearch, Postgres are crucial.
Noting these developments, I restarted my trials to push my development local instance to Heroku for a production instance but failed π.
I am not a developer and not sure what I am missing here, and if anyone can suggest to me how to proceed to the next phase, please guide me through it.
Top comments (9)
We're definitely lacking the docs to give good guidance here.
The moment I saw this reply from you, Ben, I was attached to my chair and keyboard -I was typing some reply, then erasing back to first and rethinking how to reply to this.
I realized that I don't have any words; I would be waiting for that documentation π.
I searched in Docs but failed to find any. Can I have an update on this?
I managed to run it locally on a Mac running Postrgres and ElasticSearch with Docker and it wasn't too much hassle, but gave me the impression that on Heroku it wouldn't be as easy.
As self-hosting was openly discouraged by the devs I'm looking around to figure out how to proceed.
For the official rollout, with proper documentation; we should wait till the first quarter of 2021.
Also, I'm not sure about, "how it would be" and "when it would be", but it will be much easier for an individual to configure and host Forem in their own VPS (Which is more cost-efficient, for smaller communities)
Do you want to drop some of the errors / issues you are facing in this thread and Iβll see what I can help with?
@lee Wynne
I'm back again to check the updates if the
ready to dev
is available or not, but realised that it might take some more time.Also, I've gone through the entire procedure to have a production forem; failed again! The build was successful, but the release phase in Heroku failed me.
Here I'm attaching the release phase error.
Hey! I just got around this error.
Elasticsearch::Transport::Transport::Errors::Forbidden 403
is due to theupdate_settings
call incluster.rb
. With the managed Elasticsearch providers on Heroku you're not allowed to edit the settings of the cluster.I added a rescue block in that code so it looks like
def update_settings
Search::Client.cluster.put_settings(body: default_settings)
rescue StandardError
handle_exception
end
It's been a while since I've seen this error and got around it. If I remember right I think it might be that Elastic Search may not be setup properly. If you don't have an account we use elastic.co/ and are using the Standard tier.
I hope this helps. π