mirror of
https://github.com/YunoHost-Apps/ihatemoney_ynh.git
synced 2024-09-03 19:26:15 +02:00
added README.md
This commit is contained in:
parent
5d2a476e30
commit
f0a1fb3b29
1 changed files with 41 additions and 0 deletions
41
README.md
Normal file
41
README.md
Normal file
|
@ -0,0 +1,41 @@
|
||||||
|
Yunohost app for Ihatemoney budget web app
|
||||||
|
==========================================
|
||||||
|
|
||||||
|
Backs on MySQL database, the identifiers are per-project, not per-user, so no
|
||||||
|
way to do advanced SSO integration with yunohost accounts.
|
||||||
|
|
||||||
|
The behaviour is either :
|
||||||
|
|
||||||
|
- **non-public app**:
|
||||||
|
- yunohost login required
|
||||||
|
- per-project identifiers required
|
||||||
|
- any yunohost user with authorized access to the app can create a new
|
||||||
|
project).
|
||||||
|
- **public app** :
|
||||||
|
- no yunohost login required
|
||||||
|
- per-project identifiers required
|
||||||
|
- any visitor can create a new project.
|
||||||
|
|
||||||
|
I currently use
|
||||||
|
[my fork](https://github.com/JocelynDelalande/ihatemoney/tree/ynh-patched)
|
||||||
|
(copied as-is on branch *ynh_patched_upstream*) as
|
||||||
|
|
||||||
|
upstream, waiting for some pull request to enter
|
||||||
|
[official code base](https://github.com/spiral-project/ihatemoney).
|
||||||
|
|
||||||
|
|
||||||
|
Maintainer
|
||||||
|
----------
|
||||||
|
|
||||||
|
I choose to embed the code in my repo, upstream policy is similar to
|
||||||
|
[Debian's](https://wiki.debian.org/PackagingWithGit#Using_the_upstream_repo).
|
||||||
|
|
||||||
|
- the *upstream* branch points to a vanilla (tested) upstream commit
|
||||||
|
- the *master* branch includes yunohost specific files and the right files
|
||||||
|
layout (eg: source is in a *sources* subdir).
|
||||||
|
|
||||||
|
Upgrading source code to a further version is a matter of:
|
||||||
|
|
||||||
|
1. pulling the right commit from upstream git in the upstream branch
|
||||||
|
2. merging upstream into master
|
||||||
|
3. adapting the upgrade script if required
|
Loading…
Reference in a new issue