EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #10265

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Fwd: Docker related.

CAUTION: This e-mail originated outside the University of Southampton.

I messaged Ed on LinkedIn recently, three docker-related things I too
haven't had much time to look at, and may prove useful to adapting
into EPrint-y things:

COPY'N'PASTE:

======

I have seen three docker related Perl things since I left:

1) A github with a variety of apache mod_perls and Perl Versions
already setup ready to go:
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmotemen%2Fdocker-mod_perl&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129549888901%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=YWnlS8VdauhjdUmVV8UkkFfFkS4JaEZCkN3XREhEhL4%3D&reserved=0
 I learned about it from this blog post:
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawley.xyz%2Fposts%2Fdocker-mod-perl.html&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129549918812%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=yNP97k%2B15WUSWTfWXBLIBhbyrIZ9N5cIrdpaqRIFi2I%3D&reserved=0

2) Struan from NewsNow has put together a docker that contains his dev
environment - so support for Perl and Python, and an environment for
coding, AI, command prompt, code reviews, etc: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdockside.io%2F&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129549935056%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ztxjZ7uE3o%2BXH7BCuDyLjznHUT64RsuH8lmH1kCMpCU%3D&reserved=0

3) CPI Books let go of some Perl staff. I contacted one of them to see
what was up, and saw his github had a docker thing:
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPaulGWebster%2Fperlbase&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129549950583%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=xyb8r%2BJ5tR8nVe4e3mBLn7APoxhP3j0Ct71KHnGTEQA%3D&reserved=0

When at EPrints, I struggled to use a local Perl instead of system
Perl, because your apache mod_perl wanted Apache perl modules compiled
against the specific system os, and without those modules in the local
Perl, EPrints would fail to work, which is why I begun to advocate for
an EPrints divorced from Apache. I recently came across a very old
thread where someone says - you shouldn't really do this - but if you
have to [have those Apache modules in local Perl (if I'm understanding
correctly at least - I could be misunderstanding)], here's how you do
it:
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F3794922%2Fhow-do-i-use-perlbrew-to-manage-perl-installations-aimed-at-web-applications%23answer-16861137&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129549968224%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=bod2HvuzeZufpYJKv%2B%2BjgvK%2Bbu2kcHzrh0i%2FTZ8Slrk%3D&reserved=0

Of course, I should probably ditch Perlbrew and start using Plenv and
Carton like my old workplace before EPrints used (Upland Software -
Adestra business unit).

Yours,
Andrew.

======

Quoting David R Newman <drn@ecs.soton.ac.uk>:


Hi,

We did have a rather hacked together Docker image [1] but this was
really just intended as a preview demo, so people could have a play
with EPrints beyond what you can do on
tryme.demo.eprints-hosting.org.  .  If someone want to build a
Docker image, then feel free.  Unfortunately, that have not even
made it onto my (never get round) to-do list.

I think I have said so many times, "Don't try to upgrade your live
production EPrints repository without some prior testing" either on
pre-production or a server you span up purposely to test your
upgrade, that it feels like a cliche to say this again.  However,
just for the record: It is a very bad idea trying to upgrade your
live production EPrints repository without testing this on a copy
(e.g. pre-production) of this repository.  This is especially the
case if you are upgrading between 3.3.x and 3.4.y or similar jumps.

Regards

David Newman
[1] https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FInstalling_EPrints_using_Docker&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129549983800%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=vri2spewO4YqZtILHOgzuPqUJ7P7bK440Mpluqf87UU%3D&reserved=0 (I
thought there was a not on this page saying for demo/experimental
purposes only. I will look into adding this)

On 23/09/2025 8:30 am, Yuri wrote:

*CAUTION:* This e-mail originated outside the University of Southampton.
*CAUTION:* This e-mail originated outside the University of Southampton.

Is there a docker image of Eprints? With a good compose file (i.e.
repo cfg conf in a local dir, database config) and a good .env
(hostname, passwords, other general configs that don't belongs to
the cfg directories) it could help a lot on migrations. What do you
think? I'm also thinking to OS updates and other tasks.

About the topic, the important part is the configuration updates,
check if plugins will work, base code customisations (it happens!),
then you can also export data and import it in a new installation,
no need of an in place migration, even if you can clone your vm and
repeat the migration process until you're satisfied of it.

Il 23/09/25 09:08, David R Newman ha scritto:

Hi,

3.3.16 is not hugely different to 3.3.12.  I would follow the
instructions at:

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FUpgrading_3.3.12%252B_to_3.4&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129549998411%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=XjJFvQyyv1U1Y3Rqsbw8ZOCST4Ct2JL7ofv8yVfT7Tc%3D&reserved=0

However, there are a few oddities here:

1. You are probably not running the indexer through the epindexer
init script.  So for the "eprints3/bin/epindexer stop" maybe
unnecessary, if you have already stopped Apache.  As if you
originally started the indexer through the EPrints web admin
interface, stop Apache will stop the indexer as it will have been
a child process of Apache.  The important thing is that the
indexer is not running.  So run "ps aux | grep indexer | grep -v
indexer" to check.  If there are any indexer processes running
then you can try the epindexer command, else otherwise use Unix's
kill command to kill any running indexer processes.

2.  Rather than using the tarball, I would clone EPrints 3.4 from
GitHub (after moving EPrints 3.3 out of the way):

mkdir /opt/eprints3/
chown eprints:eprints /opt/eprints3
chmod 2775 /opt/eprints3
cd  /opt/eprints3
git clone https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feprints%2Feprints3.4.git&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129550013004%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=oZqXH%2BvoftI9TdOCQ596MHLAAw3kLSNkG%2B%2Bj%2BNmfog0%3D&reserved=0 .
git checkout tags/v3.4.7

The first three commands (mkdir, chown and chmod) need to be run
by root but the last three should be as the eprints user.  If you
do the above it saves needing to run the wget, tar, configure and
make commands.  (I am not really sure why the configure and make
commands are there in the first place, as they don't look to make
any functional changes to how EPrints will run).  Using git should
also make it easy to upgrade in future, (just a git fetch and
checkout* rather than needing to run all the command listed to
deploy the new set of tarballs for the latest release).  I will
also you to see if you have modified any core files before you try
to upgrade.

If I get a chance, I will looking into updating these instructions
to reflect the suggestion to use git rather than downloading
tarballs to install EPrints 3.4.

Regards

David Newman
*It is a little bit more complicated than just a git fetch and
checkout but for upgrades within the 3.4.x series, probably just
an "epadmin update <ARCHIVEID>" is all that is needed.  It is also
worth ensuring all server-side caches are cleared, by running the
refresh_abstracts and refresh_views options for epadmin and the
stand-alone generate_static command.


On 23/09/2025 5:12 am, jokoe soesilo wrote:

*CAUTION:* This e-mail originated outside the University of Southampton.
*CAUTION:* This e-mail originated outside the University of Southampton.
Hi,
i would like to ask wheter there is a recommended best practice
for upgrading EPrints from version 3.3.16 to 3.4 could you please
provide guidance or documentation on the safest and most
efficient upgrade procedure?

Thank you in advance for your assistance

best Regards,
jaka

*** Options:https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FEprints-tech_Mailing_List&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129550030164%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=sXRNI3i9ZAtAcruieCpt5xT6v7rKkSOKh9x42cA%2FQDE%3D&reserved=0
*** Archive:https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129550051948%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=XfsTT%2B9Z%2BifngO5niSa6eaauFoBSQ%2FH%2Bn5Byn1R%2Fv%2FY%3D&reserved=0
*** EPrints community wiki:https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2F&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129550073248%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=fxydKb9NQyo79EbUXpU9hruriJ97O%2B3xU5eAAxB0PvM%3D&reserved=0




*** Options:https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FEprints-tech_Mailing_List&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129550093326%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=abqgLgDoYzEleUn67Phj3vConilWCWQPidnW8MKUhJI%3D&reserved=0
*** Archive:https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129550113937%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=do65N679uykPCjomp2CVCjbQ6KF26iE9ENFmvfTatN8%3D&reserved=0
*** EPrints community wiki:https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2F&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129550134227%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=yH%2FVTiPvOdcgeYCq%2BpYLhmT0bGb8FvJvzDdAd6weLg0%3D&reserved=0



*** Options:https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FEprints-tech_Mailing_List&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129550154664%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=tyRWefdnqeZFjfcxvy0T4oYlWW%2FN8Wu74hZGAbvDLUQ%3D&reserved=0
*** Archive:https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129550174936%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ptWpKFflHiwWkjlV%2BKXV5FPN9lhhd6JEW%2FwirAvNws8%3D&reserved=0
*** EPrints community wiki:https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2F&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7C44a4b996ff9342839c2208ddfb641a15%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638943129550203304%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=BGY2hJdQlTiR726dQ08hzcYElZ%2Fv%2B2TUDcIbN2uXNvs%3D&reserved=0



----- End forwarded message -----