> Am 14.08.2024 um 02:06 schrieb lati...@vcn.bc.ca: > > Hello misc > > I have a private Dokuwiki at historia.agroena.org working correctly, but i > would like to have a copy in my Laptop without internet.
Copying DokuWiki to another machine is easy. I do that all the time to make functioning backup copies of DokuWiki sites. However if you plan to make changes in both versions you may end having to sync both ways, which is non-trivial. But for a read-only copy, just use your favorite tool to copy the files. Personally I prefer rsync over SSH for this. Whenever your laptop is connected to the Internet, re-sync from the original to get the changes made there. Another issue might be file system permissions. Unless you are using the the same web server software and OS on both machines, you may need to adjust the permissions after copying the files. In my cases I mark the copies in their page header by adjusting the $conf['tagline‘] setting in …/dokuwiki/conf/local.php on the destination to clearly signal that this is a copy not meant for editing. (The chosen template needs to support this setting of course.) I have scripts to handle this when copying from OpenBSD to OpenBSD even if the destination path may be sightly altered, e.g. from /var/www/admin-wiki to /var/www/admin-wiki-backup. > How should i access install.php please? If you are copying the wiki then you don’t need to access install.php at all. That file is only needed for fresh installations. But I think your question was meant to be more general, as in: How do I access the wiki on my laptop without Internet? > I have tried localhost/var/www/dokuwiki/install.php and ip/install.php, > but it does not work! Did you configure a web server? If so which one and what does your config look like? Without a web server DokuWiki will not function. And DokuWiki also requires PHP, either integrated into the web server or in the form of a separate PHP-FPM process. See https://www.dokuwiki.org/requirements for details. You should be able to configure a web server on localhost on most OSes. So your URLs in the browser will use localhost instead of historia.agroena.org. One issue you may have is HTTPS support. You might need to generate a self-signed certificate and get your clients (web browsers) to trust that certificate. Even when server and client are on the same machine, I’d recommend using HTTPS, if only because the authentication mechanism may need it. Mike
