Setting up Forem using Docker is one of the easiest ways to have Development Instance 😇. If you already have Docker and Docker-Compose, you can ins...
For further actions, you may consider blocking this person and/or reporting abuse
In Digital Ocean we usually do not deploy like the case in Heroku.
In a vague sense, in Digital Ocean
But the main difference from your PC installation is that you will also change the app's environment variable to
Productionin the Digital Ocean.In your personal PC, it is most; likely a development instance and by default uses production variables until you configure them to production.
Usually in Heroku, by default it is nodejs and many other variables are in a Production environment. Also, this is one of the main reason that you are supposed to configure all the environment variables in Heroku for a successful build and release.
The command
bin/container-setupis supposed to execute two steps; so try those two commands manually and let me know the status.The script
bin/container-setupexecutes these two steps in order.docker-compose builddocker-compose upOk, I found one of my old text files which have a list of commands to Install Forem in Linux manually. So with less commentary, I am posting another article out of those.
Check out the next article in line or click here
By looking at the screenshot, I realised that you are using WSL. So I would like to suggest you to check your WSL version and if it is not WSL2, do change it to WSL2.
Secondly, while using docker it takes time for the initial setup, even if it is 8GB ram VM or HYPER-V, it may take up to 30-40 minutes. "Optimisation Issues:"
Can I use this method to run a production instance or would you suggest another way?
It is always better to have 2 different instances one in local (development) and the other to the public through the production (in Heroku or VPS)
Also, remember, unlike the development forem instance to have a working production instance you have to configure all most all the environment variable in the
.envfile.I would like to deploy it in production and I understand that I need to copy
.env_sampleas.envand add values but what aboutdocker-compose.yml? It hasRAILS_ENV,DATABASE_URL, and many things set as development. Do I have to modify it as well?Please advise. Thank you.
No need to modify system-oriented variables, by default in a system like Heroku the environmental variables of rails are configured as production. All you have to do is configure
.envfile.Also just having a
.envis not sufficient, you need to configure everything in it. Take for example the Cloudinary, Honey badger, Fastly, Pusher, Honeycomb, AWS.. All of them have to be configured.Yes, thank you. I will install and get back to you if there is anymore questions.
By the way, I used
apt install docker-composeto install Docker Compose.Usually installing in such a way is not a problem, but downloading source code and installing it manually never, usually, results in an error.
Also, I would like to know if you have a successful forem production instance. If possible just ping me here, if you have one.
Can you guide the installation for production?
I'm working on a individual SaaS for this purpose, ping me forem.dev
You can follow this guide, and it is working; I confirmed it in my Droplet.
There are some aftermath modifications for full functionality, in a day I might add those.
Hi, it doesn't seem to work in my droplet
Can you elaborate on the error?
It says connection refused. I detailed this issue on forem.dev
Thanks for sharing 👏
Deploying in Heroku is a bit different and even Forem itself is shifting from it, I think so.
Article 03, which I uploaded just now, can be used in Digital Ocean too.
Heeelp please :)
dev.to/miawmiaw/forem-erros-during...