Hi,

Could anyone provide some inputs on this if possible?

Regards,

Amrutha

Hi Amrutha,

you can theoretically set the OPENPROJECT_RAILS__RELATIVE__URL__ROOT variable which controls the internal server to run in a subdirectory. However whenever doing that, assets will need to be recompiled which is going to be difficult in the docker container. You could base a custom container on ours, set the environment and run bundle exec rails assets:precompile

Best,

Oliver

So as per the above suggestion, we need to create another container taking your official image as a build a new container out of it keeping OPENPROJECT_RAILS__RELATIVE__URL__ROOT?

Please correct me if my understanding is wrong?

Hi,

I just ran the below docker command to bring up the container and then i went inside the container and tried to compile with the above mentioned command and was getting the below error

Linking frontend plugins

hook registered

Cleaning linked target directory /app/frontend/src/app/modules/plugins/linked

Linking frontend of OpenProject plugin openproject-avatars to /app/frontend/src/app/modules/plugins/linked/openproject-avatars.

Linking frontend of OpenProject plugin openproject-costs to /app/frontend/src/app/modules/plugins/linked/openproject-costs.

Linking frontend of OpenProject plugin openproject-documents to /app/frontend/src/app/modules/plugins/linked/openproject-documents.

Regenerating frontend plugin registry /app/frontend/src/app/modules/plugins/linked-plugins.module.ts.

Building angular frontend

npm run build

> openproject-frontend@0.1.0 prebuild /app/frontend

> ./scripts/link_plugin_placeholder.js

> openproject-frontend@0.1.0 build /app/frontend

> ng build --prod

sh: 1: ng: not found

npm ERR! file sh

npm ERR! code ELIFECYCLE

npm ERR! errno ENOENT

npm ERR! syscall spawn

npm ERR! openproject-frontend@0.1.0 build: `ng build --prod`

npm ERR! spawn ENOENT

npm ERR!

npm ERR! Failed at the openproject-frontend@0.1.0 build script.

npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in:

npm ERR!     /root/.npm/_logs/2019-09-26T05_31_36_110Z-debug.log

rails aborted!

Failed to compile angular frontend: 1

/app/lib/tasks/assets.rake:66:in `block (4 levels) in <top (required)>'

/app/lib/tasks/assets.rake:65:in `block (3 levels) in <top (required)>'

/app/lib/tasks/assets.rake:64:in `chdir'

/app/lib/tasks/assets.rake:64:in `block (2 levels) in <top (required)>'

/app/vendor/bundle/ruby/2.6.0/gems/railties-5.2.2.1/lib/rails/commands/rake/rake_command.rb:23:in `block in perform'

/app/vendor/bundle/ruby/2.6.0/gems/railties-5.2.2.1/lib/rails/commands/rake/rake_command.rb:20:in `perform'

/app/vendor/bundle/ruby/2.6.0/gems/railties-5.2.2.1/lib/rails/command.rb:48:in `invoke'

/app/vendor/bundle/ruby/2.6.0/gems/railties-5.2.2.1/lib/rails/commands.rb:18:in `<top (required)>'

bin/rails:9:in `require'

bin/rails:9:in `<main>'

Tasks: TOP => assets:precompile => assets:compile_environment => assets:prepare_op => assets:angular

(See full trace by running task with --trace)

Hi,

Could someone please help on this issue as we are stuck with this from past 2 weeks.

Hi Oliver Günther,

could someone please help us out with this issue?

Hi Team,

Could you please help out with this issue as I am stuck from past 2 weeks on this.

Regards,
Amrutha

I would recommend to use the regular packaged installation which allows you to set a relative URL root in the configuration process. It will be easier to maintain than with the docker setup

Best,

Oliver

Hi,

Our requirement is to use a docker image since we are running open project in a kubernertes cluster.

Regards,
Amrutha

Hi Team,

Any update on this issue?

Regards,
Amrutha