Lipupini is a public domain platform for organizing computer files like images, videos, sounds and writings that you might want to display under your domain on the Internet. Lipupini aims to support RSS and Fediverse protocols.
OTHER License
Published by lipupini 7 months ago
x.y.z => (x+1).0.0
: There is a 100% chance that a git pull (etc) will break the previous iteration
x.y.z => x.(y+1).z
: Allowed to break from the previous release (major release)
x.y.z => x.y.(z+1)
: Almost certainly should not break from the previous release (minor release)
README
Full Changelog: https://github.com/lipupini/lipupini/compare/4.2.0...4.2.1
Published by lipupini 7 months ago
x.y.z => (x+1).0.0
: There is a 100% chance that a git pull (etc) will break the previous iteration
x.y.z => x.(y+1).z
: Allowed to break from the previous release (major release)
x.y.z => x.y.(z+1)
: Almost certainly should not break from the previous release (minor release)
ffmpeg
to be installed and the useFfmeg
option to be enabled.Full Changelog: https://github.com/lipupini/lipupini/compare/4.1.0...4.2.0
Published by lipupini 7 months ago
x.y.z => (x+1).0.0
: There is a 100% chance that a git pull (etc) will break the previous iteration
x.y.z => x.(y+1).z
: Allowed to break from the previous release (major release)
x.y.z => x.y.(z+1)
: Almost certainly should not break from the previous release (minor release)
NOTE: Unless you liked the full path showing from before, nothing else should be affected usability-wise from 4.0.0
. To get the same captions back, they'll need to be specified in files.json
with the full path.
files.json
, for nested collection subfolders. Before, the subfolder path would be displayed as a media file caption. Now it is the filename only. Hovering a nested subfolder itself (not the files) still shows the full path for clarity.Full Changelog: https://github.com/lipupini/lipupini/compare/4.0.0...4.1.0
Published by lipupini 7 months ago
Version 4.x! π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π π
This is the first release of version 4.x. Yay!
As a reminder,
x.y.z => (x+1).0.0
: There is a 100% chance that a git pull (etc) will break the previous iteration
x.y.z => x.(y+1).z
: Allowed to break from the previous release (major release)
x.y.z => x.y.(z+1)
: Almost certainly should not break from the previous release (minor release)
.lipupini
folder. ActivityPub log cache
folder is tucked away for now and should still work if enabled in state settings.useFfmpeg
is enabled and ffmpeg
is installed, video thumbnails can be generated automatically on-request or with new included CLI toolsbin
directorydocker-compose
is added to system/docker/
config/system.php
is renamed to system/config/state.php
with new options
v3.x
Full Changelog: https://github.com/lipupini/lipupini/compare/3.2.1...4.0.0
Published by lipupini 7 months ago
x.y.z - (x+1).0.0 : There is a 100% chance that a git pull (etc) will break the previous iteration
x.y.z - x.(y+1).z : Allowed to break from the previous release (major release)
x.y.z - x.y.(z+1) : Almost certainly should not break from the previous release (minor release)
FolderRequest
Full Changelog: https://github.com/lipupini/lipupini/compare/3.2.0...3.2.1
Published by lipupini 7 months ago
x.y.z - (x+1).0.0 : There is a 100% chance that a git pull (etc) will break the previous iteration
x.y.z - x.(y+1).z : Allowed to break from the previous release (major release)
x.y.z - x.y.(z+1) : Almost certainly should not break from the previous release (minor release)
Full Changelog: https://github.com/lipupini/lipupini/compare/3.1.1...3.2.0
Published by lipupini 7 months ago
x.y.z - (x+1).0.0 : There is a 100% chance that a git pull (etc) will break the previous iteration
x.y.z - x.(y+1).z : Allowed to break from the previous release (major release)
x.y.z - x.y.(z+1) : Almost certainly should not break from the previous release (minor release)
Full Changelog: https://github.com/lipupini/lipupini/compare/3.1.0...3.1.1
Published by lipupini 7 months ago
x.y.z - (x+1).0.0 : There is a 100% chance that a git pull
(etc) will break the previous iteration
x.y.z - x.(y+1).z : Allowed to break from the previous release (major release)
x.y.z - x.y.(z+1) : Almost certainly should not break from the previous release (minor release)
Full Changelog: https://github.com/lipupini/lipupini/compare/3.0...3.1.0
Published by lipupini 10 months ago
x.y.z - x.(y+1).z : Allowed to break from the previous release (major release)
x.y.z - x.y.(z+1) : Almost certainly should not break from the previous release (minor release)
.lipupini
folder are not dotfiles anymorePublished by lipupini 10 months ago
x.y.z - x.(y+1).z : Allowed to break from the previous release (major release)
x.y.z - x.y.(z+1) : Almost certainly should not break from the previous release (minor release)
Published by lipupini 12 months ago
These are the only differences between 2.3.0 and 2.3.1:
2.3.0
2.3.0
This is a breaking change from v2.2.0
. Sorry. The collection and cache directories are moved to root, and storage directory is deleted.
Please, file an issue if that is an issue and we'll try to document a way to solve it (migration guide for 2.2.0-2.3.0).
As a reminder:
x.y.z - x.(y+1).z : Allowed to break from the previous release (major release)
x.y.z - x.y.(z+1) : Almost certainly should not break from the previous release (minor release)
Hopefully I will start publishing minor releases
Full Changelog: https://github.com/instalution/lipupini/compare/2.2.0...2.3.1
Published by lipupini 12 months ago
Please upgrade to version 2.3.1 if you are using Docker.
This is a breaking change. Sorry. The collection and cache directories are moved to root, and storage directory is deleted.
Please, file an issue if that is an issue and we'll try to document a way to solve it (migration guide for 2.2.0-2.3.0
).
As a reminder:
x.y.z - x.(y+1).z : Allowed to break from the previous release (major release)
x.y.z - x.y.(z+1) : Almost certainly should not break from the previous release (minor release)
Hopefully I will start publishing minor releases
Full Changelog: https://github.com/instalution/lipupini/compare/2.2.0...2.3.0
Published by lipupini almost 1 year ago
For immediate future, not long-term:
x.y.z - x.(y+1).z : Allowed to break from the previous release
x.y.z - x.y.(z+1) : Almost certainly should not break from the previous release
No guarantees on the vx.x
branch itself
Published by lipupini about 1 year ago
For immediate future, not long-term:
2.0.0 - 2.1.0 : Allowed to break
2.1.0 - 2.1.1 : Almost certainly should not break
x.y.z - x.(y+1).z : Allowed to break
x.y.z - x.y.(z+1) : Almost certainly should not break
Published by lipupini about 1 year ago
For immediate future, not long-term:
2.0.0 - 2.1.0 : Allowed to break
2.1.1 - 2.1.2 : Almost certainly should not break
x.y.z - x.(y+1).z : Allowed to break
x.y.z - x.y.(z+1) : Almost certainly should not break
Published by lipupini about 1 year ago
Although v1.3
is not likely affected by this potential security issue, should still upgrade or patch
Published by lipupini about 1 year ago
For displaying a media portfolio or posts on the Internet, despite currently limited ActivityPub support Lipupini is considered to be production-ready.
See README for more information: https://github.com/instalution/lipupini/blob/1.3/README.md