Package Details: baikal 0.10.1-1

Git Clone URL: https://aur.archlinux.org/baikal.git (read-only, click to copy)
Package Base: baikal
Description: Lightweight CalDAV+CardDAV server
Upstream URL: http://sabre.io/baikal/
Licenses: GPL-3.0-only
Submitter: The-Compiler
Maintainer: Martchus
Last Packager: Martchus
Votes: 22
Popularity: 0.37
First Submitted: 2014-01-07 12:12 (UTC)
Last Updated: 2024-11-10 13:09 (UTC)

Dependencies (3)

Required by (0)

Sources (2)

Pinned Comments

Martchus commented on 2020-01-31 13:47 (UTC) (edited on 2024-02-05 14:39 (UTC) by Martchus)

When updating your PHP, have a look whether Baikal still works and checkout the comments here for possible issues. Any hints/patches from your side are welcome of course, too. PHP is known to break things and it broke Baikal in the past. At the bottom of this comment you also find NGINX configuration snippets to use an older PHP version. Using an older PHP version is likely the best for being on the safe side although support for older PHP versions is also dropped from time to time from Baikal's side.

All my packages are managed at GitHub where you can also contribute directly: https://github.com/Martchus/PKGBUILDs
There's also a binary repository, also including older PHP versions: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#ownstuff

head -n 20 /etc/nginx/nginx.conf 
[...]
http {
    include php-handler.conf;
    include phpXX-handler.conf;

cat /etc/nginx/php.conf 
location ~ ^(/baikal.+?\.php)(/.*)?$ {
  try_files $1 =404;
  include fastcgi.conf;
  fastcgi_pass phpXX-handler; # handler registered via phpXX-handler.conf included in nginx.conf
  fastcgi_index index.php;
  fastcgi_param SCRIPT_FILENAME $document_root$1;
  fastcgi_param PATH_INFO $2;
  fastcgi_param HTTPS on;
}
location ~ ^(.+?\.php)(/.*)?$ {
  try_files $1 =404;
  include fastcgi.conf;
  fastcgi_pass php-handler; # handler registered via php-handler.conf included in nginx.conf
  fastcgi_index index.php;
  fastcgi_param SCRIPT_FILENAME $document_root$1;
  fastcgi_param PATH_INFO $2;
  fastcgi_param HTTPS on;
}

cat /etc/nginx/phpXX-handler.conf 
upstream phpXX-handler {
  server unix:/run/phpXX-fpm/php-fpm.sock;
}
cat /etc/nginx/php-handler.conf 
upstream php-handler {
  server unix:/run/php-fpm/php-fpm.sock;
}

(XX is of course supposed to be replaced by the actual PHP version.)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

Iwmrby commented on 2016-01-10 08:57 (UTC) (edited on 2016-01-10 21:01 (UTC) by Iwmrby)

Baikal doesn't seem to sync anymore since the upgrade to PHP7. Does anybody else have this problem? Is there some config change I missed? Later edit: It might be an issue with my phone.

BunBum commented on 2014-09-05 07:27 (UTC)

Fixed. You also have to copy config.php and config.system.php to /var/lib/baikal Now everything works. Hopefully future updates will run much more smoother ;-)

BunBum commented on 2014-09-05 07:13 (UTC)

When I delete ENABLE_INSTALL I get Baïkal Install Tool is locked. To unlock it, create (or re-create if it exists already) an empty file named ENABLE_INSTALL (uppercase, no file extension) in the Specific/ folder of Baïkal. Could you tell me how I can enable Baikal without loosing all my contacts?

The-Compiler commented on 2014-09-05 07:11 (UTC)

Heh, weird - I got an email for both of your comments but only see one now. Looks like I need to take a closer look at the package again, having an ENABLE_INSTALL doesn't make much sense on upgrading, so I really should create that file in the .install... What happens when you delete the file entirely and proceed? Do you get the same baikal error?

BunBum commented on 2014-09-05 07:07 (UTC)

My comment here was deleted??? I found the issue. PHP Warning: file_exists(): open_basedir restriction in effect. File(/usr/share/webapps/baikal/Specific/ENABLE_INSTALL) is not within the allowed path After I added it to my open_basedir setting in my php.ini it works. But now I get the Baïkal initialization wizard in my browser :-(

The-Compiler commented on 2014-09-05 06:50 (UTC)

Did you wait more than an hour between installing the package and navigating to that path with your browser? Then that'd happen. Try doing a: touch /var/lib/baikal/ENABLE_INSTALL Could you tell me what happens then? I tried an upgrade and it worked fine for me, but maybe I missed something.

BunBum commented on 2014-09-05 06:47 (UTC)

After I made these steps: # mv /usr/share/webapps/baikal/Specific{,.bak} <upgrade the package> # mv /usr/share/webapps/baikal/Specific.bak/db/db.sqlite /var/lib/baikal/db # rm -r /usr/share/webapps/baikal/Specific.bak I get following error in my browser: Baïkal Install Tool is locked. To unlock it, create (or re-create if it exists already) an empty file named ENABLE_INSTALL (uppercase, no file extension) in the Specific/ folder of Baïkal. In /var/lib/baikal/ however the file ENABLE_INSTALL exist and is empty.

The-Compiler commented on 2014-09-02 09:17 (UTC)

I finally fixed this and I'm now installing everything to the proper locations. I disagree with the wiki page on the example configs though, and I'm placing them in /usr/share/doc/baikal. Manual intervention is required for upgrading: # mv /usr/share/webapps/baikal/Specific{,.bak} <upgrade the package> # mv /usr/share/webapps/baikal/Specific.bak/db/db.sqlite /var/lib/baikal/db # rm -r /usr/share/webapps/baikal/Specific.bak

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »