Project

General

Profile

feature #13

Redmine 4.x support

Added by lupa18 6 months ago. Updated 10 days ago.

Status:
closed
Priority:
urgent
Assignee:

Description

Are you planning make the plugin works with redmine 4.x ?
I'm getting errors at least with method 'to_prepare'

Dockerfile (391 Bytes) Dockerfile lupa18, 2019-07-05 23:23

Token votes

History

#1 Updated by cryptogopher 6 months ago

Thank you for interest! Currently I don't have Redmine 4 installed, so it will take some time to run the tests + fix errors.

#2 Updated by lupa18 22 days ago

Hello ! Are you considering test with redmine 4 ? I think branch 3.x is arriving to end...

You can easy deploy 4.x redmine with docker :D

#3 Updated by cryptogopher 22 days ago

lupa18 wrote:

Hello ! Are you considering test with redmine 4 ? I think branch 3.x is arriving to end...

You can easy deploy 4.x redmine with docker :D

Yes, I already have Docker set up for development/testing. But I still didn't install Redmine 4 though... Anyway I will try to install it on weekend. I will probably go with 4.0.4 as it's the newest. Which version are you currently running?

#4 Updated by lupa18 20 days ago

I still running 3.x branch, exactly 3.4.11 and I'm using official redmine image, so if I change to 4.x branch I will be in 4.0.4

thanks!

#5 Updated by cryptogopher 15 days ago

  • Status changed from new to closed

lupa18 wrote:

I still running 3.x branch, exactly 3.4.11 and I'm using official redmine image, so if I change to 4.x branch I will be in 4.0.4

Plugin updated and tested with Redmine 4.0.4/ruby 2.4.6/Rails 5.2.3. You can checkout 1.2 tag/release from Github.

Closing issue for now. Please comment here if you'll find any errors.

#6 Updated by lupa18 13 days ago

Hello cryptogopher

I'm having this error:

app_1  | W, [2019-07-05T20:56:03.396637 #7]  WARN -- : Creating scope :system. Overwriting existing method Enumeration.system.
app_1  | rake aborted!
app_1  | ArgumentError: Missing `secret_key_base` for 'production' environment, set this string with `rails credentials:edit`

do u need more logs?

#7 Updated by cryptogopher 13 days ago

lupa18 wrote:

Hello cryptogopher

I'm having this error:
[...]

This doesn't look like plugin error. Did you run:

bundle exec rake generate_secret_token

as described in Redmine install guide https://www.redmine.org/projects/redmine/wiki/RedmineInstall#Step-5-Session-store-secret-generation ?

#8 Updated by lupa18 13 days ago

I'm using this Dockerfile (see attachment)

When uncomment issue_recurrent lines, I got the error.

If let it commented, then works well.

#9 Updated by cryptogopher 13 days ago

lupa18 wrote:

I'm using this Dockerfile (see attachment)

When uncomment issue_recurrent lines, I got the error.

If let it commented, then works well.

I still think that your Docker Redmine installation is not configured properly. Try to start docker container without plugin installation steps. Then log into the container. Make sure, that all steps described in https://www.redmine.org/projects/redmine/wiki/RedmineInstall are executed (especially the secret generation step). Then install plugin and see if there are any errors.

Eventually try different Dockerfile, e.g. https://hub.docker.com/_/redmine (I didn't test it).

I'm running plugin in Redmine installation prepared according to Redmine guide (link above) and did not encounter such error.

#10 Updated by lupa18 10 days ago

It's weird, I fixed changing default run user to redmine.

thanks!

#11 Updated by cryptogopher 10 days ago

lupa18 wrote:

It's weird, I fixed changing default run user to redmine.

thanks!

Happy to hear it's working for you!

#12 Updated by lupa18 10 days ago

But when I put in a Dockerfile, then got it broke again.

So last sentence of this text is not working (from official docker image):

REDMINE_SECRET_KEY_BASE
This variable is used to create an initial config/secrets.yml and set the secret_key_base value, which is "used by Rails to encode cookies storing session data thus preventing their tampering. Generating a new secret token invalidates all existing sessions after restart" (session store). If you do not set this variable or provide a secrets.yml one will be generated using rake generate_secret_token.

So I set an explicit key using that env variable and now it works !

Also available in: Atom PDF