We've noticed that your podcasts (unelma.dev/pod) are using image that are generally used in our test and development environment. Did you happen to choose those images on purpose or perhaps your rail environment wasn't configured to production ?
Yes, I know through .env file but the problem is whenever I switch that it throws me following error message:
13:45:19 webpacker.1 | webpack dev_server configuration not found in /home/udev/forem/config/webpacker.yml[production].
13:45:19 webpacker.1 | Please run bundle exec rails webpacker:install to install Webpacker
13:45:20 webpacker.1 | exited with code 1
then I tried running bundle exec rails webpacker:install but does not seem to resolve the issue
I am an Engineering Physics graduate from IIT Guwahati, but merely not restricted to Physics itself. In the past few years, I involved in many Cybersecurity blogging and now on Open-source.
Hello @tespok !
We've noticed that your podcasts (unelma.dev/pod) are using image that are generally used in our test and development environment. Did you happen to choose those images on purpose or perhaps your rail environment wasn't configured to
production
?Yes, it is still in development. How to change to production mode?
@tespok can you tell me which instruction did you follow to get your own selfhost set up? and who is your cloud provider?
but as a sidenote, you can generally change this via environment variable.
Yes, I know through .env file but the problem is whenever I switch that it throws me following error message:
then I tried running
bundle exec rails webpacker:install
but does not seem to resolve the issuebin/webpack-dev-server
is a development-only tool. When app runs on production you don't need to run it.Okay, but it throws error like before when changing the .env variable from development to production
Can you please elaborate on which cloud provider you chose? did you go down the selfhost documentation? or did you tried hosting via your own methods?
It is a
development
version; you can confirm it by visiting this: unelma.dev/adminIn case, if the hosted Forem is a
production
version it should retrive a 404 error, similar to this: app.leewardslope.com/adminEven though this comparison is vauge, I found this as a quicker way to identify the deployment method.
Yes, you are right..