Webpack::Rails::Manifest::ManifestLoadError in Auth::Registrations#new

[rzcastilho]

Hi everyone,

After checkout latest Portus version, I followed the basic steps to configure with command bellow.

./compose-setup.sh -e <my_domain>

Everything works fine, but, when I access the url http://<my_domain>:3000, I get the error bellow.

Webpack::Rails::Manifest::ManifestLoadError in Auth::Registrations#new
Showing /portus/app/views/layouts/authentication.html.slim where line #6 raised:

Could not load compiled manifest from /portus/public/assets/webpack/manifest.json - have you run `rake webpack:compile`? (original error No such file or directory @ rb_sysopen - /portus/public/assets/webpack/manifest.json)

[vitoravelino]

@rodrigozc

I'm assuming you are trying to run everything on development environment, right?

You need to run yarn install and then webpack --watch --config config/webpack.js. Not sure if restarting the web container is necessary.

Webpack must also be installed globally. I guess yarn add global webpack should do the job, if not try npm install webpack -g.

These steps are still missing on docs. Sorry for that.

/cc @mssola

[mssola]

That is correct. I need to update the docker-compose setup for this.

[rzcastilho]

Thanks @vitoravelino and @mssola

[lukeshaughnessy]

Could you please clarify where/how to install webpack.js? I tried execing into the web container and running the npm command, and it failed to resolve the problem.

[vitoravelino]

@lukeshaughnessy try executing from outside the web container.

[mssola]

As @vitoravelino points out, running this outside of the container should work because the source code is shared in a volume. That being said, I'll add documentation and all that asap.

[lukeshaughnessy]

docker exec -it portus_web_1 /usr/bin/npm install webpack -g
docker restart portus_web_1

Issue persists. Perhaps I am misunderstanding?

[vitoravelino]

There's no difference between docker exec and entering the container and running the command. When we meant outside we mean not related to docker.

[lukeshaughnessy]

I assume then that you mean running npm install webpack -g on the host operating system? This also does not work. I am quite confused. How does running this outside the container provide whatever files are needed in the volume? Could you please provide more specific details for this workaround?

[post707]

@rodrigozc Hi, solved yet?

[Diokuz]

I think having local webpack is better #1256
especially when you already have it in node_modules

[ajeetraina]

I tried the below steps on Alpine Host OS and Fixed the issue:

(Please note that you need to run the below commands on the host machine and NOT on the docker container)

1. echo -e 'http://dl-cdn.alpinelinux.org/alpine/edge/main\nhttp://dl-cdn.alpinelinux.org/alpine /edge/community\nhttp://dl-cdn.alpinelinux.org/alpine/edge/testing' > /etc/apk/repositories
2. apk add --no-cache nodejs-current yarn
3. yarn install
4. yarn add global webpack
5. yarn install
6. apk add --update nodejs nodejs-npm && npm install npm@latest -g
7. npm install webpack -g
8. webpack --watch --config config/webpack.js

Done. Portus is up and running.