Turning installation to read-only access

[Philipp Conzett]

We'll soon be migrating our Dataverse installtion to cloud infrastructure. As part of this work, we need to turn our installation into read access only while we are migrating. Can this be achieved covering both interaction through the GUI and the API?

Thanks for your input!
Philipp

[Don Sizemore]

Philipp,

I've always accomplished this by simply stopping Glassfish/Payara and serving a maintenance page during the migration. I welcome a better solution.

Don

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/a1de7816-a7be-44e2-8431-832112f2ffacn%40googlegroups.com.

[Sebastian Karcher]

> I've always accomplished this by simply stopping Glassfish/Payara and serving a maintenance page during the migration. I welcome a better solution.

Same here.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CAPfMOaymFb%2BwZonzhXrJOG1nNQbAZDH-P%3D_5choYgy-6vDsv_A%40mail.gmail.com.

--

Sebastian Karcher, PhD
www.sebastiankarcher.com

[paul...@dans.knaw.nl]

We also use a maintenance page, however If you could disable login from the outside and disable most of the API endpoints you should close to 'read-only'. 

Op maandag 20 maart 2023 om 14:26:21 UTC+1 schreef sebastiank...@u.northwestern.edu:

[Don Sizemore]

Paul,

This is indeed "close to" but won't completely disable writes to the database - download/guestbookresponse entries, actionlogrecord, and possibly others may still get lost during the migration.

Thank you,

Don

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/f4c8531e-a2a6-40f1-b582-38b36c38967dn%40googlegroups.com.

[Philipp Conzett]

Thank you all for your replies!

Philipp