1
0
Fork 0
mirror of https://github.com/YunoHost-Apps/ihatemoney_ynh.git synced 2024-09-03 19:26:15 +02:00
Ihatemoney package for YunoHost
Find a file
Jocelyn Delalande c114aa6ac8 Use releases tarballs rather than git master.
- upgrade to ihatemoney 0.9
- refactor some code into a `_common.sh`
2017-06-17 00:22:16 +02:00
conf socket is now in /tmp/ as /var/run/ihatemoney gets rm on each reboot 2015-06-10 00:13:01 +02:00
scripts Use releases tarballs rather than git master. 2017-06-17 00:22:16 +02:00
sources Merge branch 'upstream' 2017-03-18 17:58:12 +01:00
.gitignore Fix some problems related to postgresql and models 2011-10-13 21:27:56 +02:00
LICENSE Add LICENSE file 2017-03-18 19:10:42 +01:00
manifest.json Fix manifest to comply with ynh 2.4 style 2016-06-18 00:33:51 +02:00
README.md added README.md 2015-05-02 17:29:16 +02:00

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 (copied as-is on branch ynh_patched_upstream) as

upstream, waiting for some pull request to enter official code base.

Maintainer

I choose to embed the code in my repo, upstream policy is similar to Debian's.

  • 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