Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content

Rallly

15 Topics 144 Posts
  • Rallly - Package Updates

    Pinned
    56
    2 Votes
    56 Posts
    8k Views
    Package UpdatesP
    [2.2.0] Update rallly to 4.2.0 Full Changelog Fix issue where wrong start time is shown on event page by @lukevella in https://github.com/lukevella/rallly/pull/1791 Add option to cancel a scheduled event by @lukevella in https://github.com/lukevella/rallly/pull/1800
  • Licensing

    10
    1 Votes
    10 Posts
    509 Views
    andreasduerenA
    @BrutalBirdie Gemini says: Conclusion based purely on this AGPL-3.0 license text: If the Rallly code that implements the user limit and the nag banner is itself licensed under this AGPL-3.0, then: Yes, a user or organization (like Cloudron, if they chose) can legally fork Rallly. Yes, they can modify the AGPL-3.0 licensed source code to remove the multi-user licensing check and the associated nag banner. This would be considered removing a "further restriction" as permitted by Section 7. They must still comply with all other AGPL-3.0 terms when they distribute or provide network access to their modified version: Clearly state that their version is modified (Section 5a). State that their modified version is released under the AGPL-3.0 (Section 5b). Display "Appropriate Legal Notices" (the AGPL ones, not Rallly's proprietary ones) in the UI (Section 5d). Provide the Corresponding Source of their modified version to users interacting with it over a network (Section 13). Keep original copyright notices and AGPL license information intact. The Neo4j precedent mentioned in the forum discussion is less relevant here if Rallly is genuinely distributing the entirety of this V4 code (including the restriction mechanism) under this standard, unmodified AGPL-3.0. The Neo4j case involved a license that was AGPLv3 plus a "Commons Clause," which was a significant alteration/addition to the AGPL terms. If Rallly is just using plain AGPL-3.0, then plain AGPL-3.0 rules apply. In summary: The AGPL-3.0 is designed to prevent exactly this kind of "bait-and-switch" where software is offered as "free" under a strong copyleft license, but then functional restrictions are baked in that users cannot remove. The license explicitly gives users the right to remove such "further restrictions."
  • Any chance to integrate CLOUDRON_OIDC_PROVIDER_NAME in the package?

    7
    1
    1 Votes
    7 Posts
    356 Views
    U
    I've seen the release and I will be testing this shortly. Much appreciation @staff !
  • Custom homepage

    3
    2 Votes
    3 Posts
    693 Views
    A
    @girish said in Custom homepage: @ianhyzy unfortunately not afaik. But I recommend asking upstream. I found https://github.com/lukevella/rallly/discussions/137 when I looked for this earlier. I re-run the post on GitHub
  • Add OIDC support?

    Solved
    5
    1 Votes
    5 Posts
    972 Views
    girishG
    @jdaviescoates agreed, it all depends on the use case. If the goal is to limit the usage of app (create polls in this context) to your org, then it would be nice to have a way to disable registration.
  • Verification codes don't work anymore

    Solved
    5
    0 Votes
    5 Posts
    995 Views
    girishG
    This is fixed with the latest package.
  • Using without registration

    Solved
    9
    1 Votes
    9 Posts
    2k Views
    robiR
    I suppose one could make a public user and tell people to use it for login.
  • No first time set-up instructions.

    3
    1 Votes
    3 Posts
    528 Views
    girishG
    I added a postinstall now to the package and also added https://docs.cloudron.io/apps/rallly/#restrict-sign-up
  • Can't create account on new verison

    Solved
    6
    0 Votes
    6 Posts
    1k Views
    nebulonN
    Also just did a fresh install and it was able to send the mail with the pin fine. Seems like something is off with the email setting on your Cloudron?
  • Rallly 3.0 Pro features missing

    Solved
    9
    2 Votes
    9 Posts
    2k Views
    David 0D
    Great. Everything works fine now.
  • Rally - Invitation links are http://localhost:3000/

    Solved rally configuration
    10
    1 Votes
    10 Posts
    1k Views
    nebulonN
    This is also solved with latest package update.
  • Change language of notifications

    language
    2
    0 Votes
    2 Posts
    573 Views
    girishG
    @hollosch I couldn't find anything obvious. Might be worth asking this upstream at https://github.com/lukevella/rallly/discussions/
  • The language switch does not work

    4
    1 Votes
    4 Posts
    848 Views
    girishG
    This is fixed in the latest package.
  • URL for open graph tag incorrect

    Solved
    9
    1
    1 Votes
    9 Posts
    2k Views
    andreasduerenA
    @girish Nice thanks!
  • Rallly not tagged for New Apps in the App Store

    Solved
    6
    1 Votes
    6 Posts
    1k Views
    RoundHouse1924R
    @nebulon Related to this topic is that Rally is NOT listed in:- Cloudron - Published App Status https://www.cloudron.io/appstatus.html