Package Details: organizr-git r3852.4f2e6c5f-2

Git Clone URL: https://aur.archlinux.org/organizr-git.git (read-only, click to copy)
Package Base: organizr-git
Description: HTPC/HomeLab services organizer (git version).
Upstream URL: https://github.com/causefx/Organizr
Licenses: GPL3
Conflicts: organizr
Provides: organizr
Submitter: eta-carinae
Maintainer: eta-carinae
Last Packager: eta-carinae
Votes: 4
Popularity: 0.000006
First Submitted: 2019-01-11 17:27 (UTC)
Last Updated: 2022-06-07 00:47 (UTC)

Required by (0)

Sources (2)

Latest Comments

eta-carinae commented on 2022-06-07 00:49 (UTC)

Shasta,

Another update. After thinking about it, I replaced the data symlink with a data directory containing symlinks to the individual subdirectories, excluding config since that could potentially expose private information. I guess that was probably your point. Anyway, should be good to go now.

eta-carinae commented on 2022-06-07 00:18 (UTC)

Shasta,

Thanks for the heads-up. I modified the PKGBUILD to add a symlink to the entire data directory since the web server needs access to many of the subdirectories. I haven't seen any problems with data/config.

Cache, user-installed themes, etc now work correctly again.

Shasta commented on 2022-06-05 07:41 (UTC) (edited on 2022-06-05 07:43 (UTC) by Shasta)

As of these commits (and the associated PR): c7858cc2 cac6c04b

Organizr is now using a new /var/lib/organizr/data/ folder with some subfolders that potentially need to be symlinked over to /usr/share/webapps/organizr.

I'm not sure on the full set, and data/config definitely shouldn't be symlinked.

data/cache does need to be linked over. I'm guessing data/favicon, data/pages, and data/userTabs may need symlinks as well, but I don't use any of those features.

eta-carinae commented on 2021-12-27 13:20 (UTC)

nhrjr,

I updated the PKGBUILD to move css into /var/lib/organizr as suggested. This follows the arch packaging guidelines, so it should be ok. Thanks for the comment. I had never used themes before. They're working for me now.

nhrjr commented on 2021-12-27 09:47 (UTC)

The in-app themes install their css files into the css directory, which is located in /usr/share/webapps/organizr and owned by root, so theming support using the marketplace is broken - unless the css directory is also moved to /var/lib/organizr and symlinked back into the webapps dir. Maybe you could modify the PKGBUILD?

Don't know if this is a security risk.

eta-carinae commented on 2020-01-02 17:33 (UTC)

I have moved the install location once again, this time to conform to the Arch guidelines for packaging web applications. The read-only portions of organizr are now in /usr/share/webapps/organizr, while the directories needing write access (api and plugins) are now in /var/lib/organizr. Apologies to everyone who already moved their install to /opt.

eta-carinae commented on 2019-12-16 17:50 (UTC)

I've updated the PKGBUILD to install the web folder to /opt/organizr instead of /usr/share/webapps/organizr. That doesn't follow Arch guidelines exactly, but I'm not sure where else to put it. /var/lib doesn't seem appropriate since mostly it's static files.

I've also modernized the build a bit and finally migrated over to the v2-master branch. As of this comment, this means the latest version is a downgrade if you've updated recently, so you'll need to install explicitly if you want the changes right away.

You'll need to migrate your configuration manually. The .install file should display instructions to do this. Briefly, move your config.php file, move any custom tab images you installed, and adjust the organizr path in your webserver and PHP configs. Note that the old installation was /usr/share/webapps/organizr/Organizr. The new one is simply /opt/organizr. I eliminated the pointless Organizr subdir.

SRChiP commented on 2019-07-05 00:20 (UTC)

Now v2-master is out, you can switch to that.

eta-carinae commented on 2019-01-14 16:46 (UTC)

This currently follows the v2-devel branch of organizr. If you have been using v1 of organizr, note that the v2 configuration is incompatible with v1, so you'll have to re-do your setup.