Jump to content
Froxlor Forum
  • 0
tt33tt

composer JSON-RPC PHP

Question

Hallo alle zusammen,

ich würde gerne auf eine API von Limesurvey zurückgreifen. Dafür muss ich installieren: https://github.com/weberhofer/jsonrpcphp

Kann ich in die composer.json einfach so hinzufügen? Ist das mit Froxlor kompatibel?

Das readme zeigt mir diese beiden Möglichkeiten:

To install

composer require weberhofer/jsonrpcphp

or add this to your composer.json, and composer update

{
    "require": {
        "weberhofer/jsonrpcphp": "~2"
    }
}

Share this post


Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 1

Warum sollte es nicht gehen? Es fügt nur das Paket dem vendor/ Ordner und dem autoloader hinzu....dadurch beeinflusst man froxlor nicht

Share this post


Link to post
Share on other sites
  • 1

Öhm, Google bitte erstmal was Composer ist und wie das funktioniert...und k.a. was du da vorhast, aber du brauchst kein Composer um die froxlor api zu nutzen (außer du nutzt die gut version, dann brauchst du das natürlich um Abhängigkeiten zu installieren - im Archiv ist alles vorhanden)

Share this post


Link to post
Share on other sites
  • 0

OK, danke!

Dazu muss ich entsprechend hier einfach die Befehle ausführen https://getcomposer.org/download/

php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php -r "if (hash_file('sha384', 'composer-setup.php') === '48e3236262b34d30969dca3c37281b3b4bbe3221bda826ac6a9a62d6444cdb0dcd0615698a5cbe587c3f0fe57a54d8f5') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
php composer-setup.php
php -r "unlink('composer-setup.php');"

Aber in das root-Directory macht das kein Sinn. Muss ich das in der jeweiligen Domäne ausführen oder in irgendeiner PHP-Bibliothek, damit alle Domänen darauf zugreifen können?

Das kann ich dann sicherlich auch für die Froxlor-API benutzen.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By d00p
      Dear Froxlor Community,
      I am proud to finally release the stable version of a new API based froxlor. Due to massive internal improvements and changes in the core (almost 600 commits since 0.9.40.1) users are now able to list/create/edit/delete resources and entities of froxlor via API (requires activation of api-usage in the settings and a user based API-key). The froxlor frontend itself uses the API backend too.
      Froxlor now uses composer to include some of its requirements like phpMailer, Logger, IdnaConvert and TwoFactorAuth libraries. All required files will be included in the official tarball so you do not need to worry about installing and using composer (only if you are using / testing the git-master, see https://github.com/Froxlor/Froxlor/wiki/Install-froxlor-from-git-sources).
      Most important changes:
      froxlor now requires at least php-7.0 or newer, php-5.6 is no longer supported because of its EOL almost a year ago you can access data via API, for more information see https://api.froxlor.org/doc/. An example can be found here: https://github.com/Froxlor/Froxlor/tree/master/doc/example PHPUnit tested API backend with MySQL 5.6, 5.7 and 8 as well as MariaDB 10.3 and 10.4, see https://travis-ci.com/Froxlor/Froxlor compatibility for MySQL8 2FA (two-factor-authentication) for admins/resellers/customers (email or authenticator app) all froxlor-database tables will automatically be converted to the InnoDB engine added support for Debian 10 (buster) and Ubuntu 18.04 (bionic beaver) implemented Let's Encrypt via acme.sh - Note: all your current Let's Encrypt certificates will be removed and re-created due to another structure customizable error/access log handling for webserver (format, level, pipe-to-script, etc.) deprecated Debian 7 (wheezy) and Ubuntu 14.04 (trusty tahr) support dropped support for Ubuntu 12.04 (precise pangolin) dropped ticketsystem Download: 0.10.1

      Note: Debian packages will be created and released as soon as possible, please be patient
      Attention: The auto-update feature is currently unavailable due to the archive taking a bit longer to extract and froxlor trying to redirect too soon thus leading to an internal server error. A quick reload does "fix" the problem but it's not very clean and therefore I removed the 0.10.0 release from the autoupdate server to avoid that. Please use the manual update options, see https://github.com/Froxlor/Froxlor/wiki

      Visit http://www.froxlor.org or join our IRC channel #froxlor on irc.freenode.net for support, help, participation or just a chat

      Thank you,
      d00p
    • By d00p
      Dear Froxlor Commuity,
      finally - the first release candidate of our new API based version 0.10.0! A lot of work has gone into this, many internal changes (you might miss any frontend-changes, but be patient...) most importantly the API backend which not only is used by froxlor frontend itself but can also be uses from within your website/scripts/etc.
      Froxlor now uses composer to include some of its requirements like phpMailer, Logger, IdnaConvert and TwoFactorAuth libraries.
      Here are some of the new features besides API that found their way in:
      - 2FA / TwoFactor Authentication for accounts - MySQL8 compatibility - new implementation of Let's Encrypt (acme.sh) - customizable error/access log handling for webserver (format, level, pipe-to-script, etc.) - lots and lots of bugfixes and small enhancements You can see all changes on Github at https://github.com/Froxlor/Froxlor/compare/0.9.40.1...0.10.0-rc2
      Download: 0.10.0-rc2

      Note: There will be no Debian packages for release-candidates.

      Visit http://www.froxlor.org or join our IRC channel #froxlor on irc.freenode.net.

      Thank you,
      d00p
    • By H4nSolo
      Hallöchen zusammen,
      ich hätte mal eine Frage bezüglich Froxlor und Cloudflare.
       
      Da einige die Froxlor benutzen, bestimmt auch bei cloudflare ihre domain eingetragen haben, stellt sich mir die Frage ob man dies nicht gleich auch mit cloudflare verbinden kann um so seine subdomains / Domains miteinzurichten, ohne sich immer zusätzlich bei cloudflare anzumelden.

      Cloudflare bringt ja von Haus aus eine API mit womit man sich auch über Scripte und einen Authentifikations Key extern anmelden kann.
      Cloudflare API: https://api.cloudflare.com/
       
      Ich für meinen Teil würde es Prima finden wenn zum Beispiel Kunden ihren Login Key eintragen, und damit bequem auch bei erstellung von subdomains gleichzeitig (sofern sie ihre Domain beim Cloudflare registriert haben) alles in einem abwickeltn können.
       
       
      Was haltet ihr von der Idee und könnte man es überhaubt verwirklichen für Froxlor?
       
      lg H4nSolo
    • By john doe
      Hello,
      I have a couple hundred e-mail accounts to create, is there a better way to do that than creating one account at a time? An API that I can use, or some batch mode?
       
      Thanks.
    • By v1ktor
      Hey guys, I like Froxlor and wanted to ask couple of easy questions to get a better understanding:
       
      1. I noticed in the forums, version 1 has been mentioned to have API as far back as 2010. Do you know when v1 might be coming out?
      2. Is it possible to create client accounts on Froxlor remotely without an API, maybe directly in database? I saw similar question and answer about sessions, but we don't need clients to access panel. Just to provision an account for them.
      3. Can Froxlor manage multiple servers from one panel?
       
      Great job on the platform!
       
      Thanks,
      Viktor




×
×
  • Create New...