>
>> 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.
Hello Mike sorry
Wrong word: "copy" it is a similar installation! in this case is a Laptop
not connected to internet! Both OpenBSD-7.5
>
> 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.
No changes in the Laptop, only at the Server.
>
> 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.
Yes, it is a fresh installation, thanks.
>
> But I think your question was meant to be more general, as in: How do I
> access the wiki on my laptop without Internet?
Correct, but English is my third Language!
>
>
>> 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?
The first server can be accessed by localhost, the second does not work
localhost/var/www/dokuwiki/install.php or localhost/install.php
# $OpenBSD: httpd.conf,v 1.22 2020/11/04 10:34:18 denis Exp $
server "agroena.ca" {
listen on * port 80
location "/.well-known/acme-challenge/*" {
root "/acme"
request strip 2
}
location * {
block return 302 "https://$HTTP_HOST$REQUEST_URI";
}
}
server "agroena.ca" {
listen on * tls port 443
root "/htdocs/libros"
tls {
certificate "/etc/ssl/agroena.ca.fullchain.pem"
key "/etc/ssl/private/agroena.ca.key"
}
location "/pub/*" {
directory auto index
}
location "/*" {
directory auto index
}
location "/.well-known/acme-challenge/*" {
root "/acme"
request strip 2
}
}
server "historia.agroena.ca" {
listen on * port 80
root "/dokuwiki"
location "/.well-known/acme-challenge/*" {
root "/acme"
request strip 2
}
location * {
block return 302 "https://$HTTP_HOST$REQUEST_URI";
}
}
server "historia.agroena.ca" {
listen on * tls port 443
root "/dokuwiki"
tls {
certificate "/etc/ssl/agroena.ca.fullchain.pem"
key "/etc/ssl/private/agroena.ca.key"
}
location "*.php" {
fastcgi socket "/run/php-fpm.sock"
}
location "/pub/*" {
directory auto index
}
location "/.well-known/acme-challenge/*" {
root "/acme"
request strip 2
}
}
The idea, is that this Laptop is going to go to a place where it be an
independent server. php is working, fmail is on list.
Thank you Mike.
>
> 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
>
Letsencryp pem/key generated at agroena.org with name historia.agroena.ca
