Download the PHP package linc/nitro-porter without Composer

On this page you can find all versions of the php package linc/nitro-porter. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package nitro-porter

Nitro Porter — free your community! 🚀

Nitro Porter is the only multi-platform community migration tool.

🚀 Mission

Every community deserves the best software for its mission while preserving its unique history. Nitro Porter's goal is 1-hour no-code data migrations for any community with accessible data.

🔍 Why do this?

Community history is vitally important. Platform lock-in stifles competition in the software ecosystem. When everyone owns their own data and can freely choose their platform, everyone wins.

ðŸĪ” How is this possible?

Data is first converted to an intermediary "porter format," reducing the number of code paths from #sources x #targets to #sources + #targets. The result is repeatable results in a single multi-tool rather than myriad low-quality, single-purpose tools.

ðŸŠī How is it extended?

Nitro Porter packages allow anyone with basic programming skills to add any community software (commercial or free) as source or target. Nitro Porter uses the GNU AGPL 3.0 license to ensure it remains freely available to all.

ðŸšĨ Get started

🎟ïļ Get involved

What's Supported?

ðŸ“Ĩ Targets (3)

ðŸ“Ī Sources (37)

...and MORE!

✔ What data gets migrated?

All sources & targets support migrating:

Beyond that, each supports different types of data depending on feature availability, extension choice, and maturity of the source/target package. These include things like badges, reactions, bookmarks, and polls.

Both the source and target must support a data type for it to transfer!

Nitro Porter never transfers permissions. It's not safe to do so automatically due to variations in how platforms implement them. You will always need to reassign permissions after a migration.

Passwords are generally hashed, which means no system can "decrypt" or "convert" them. However, if both the source and target platform support the same hashing algorithm, they should transfer seamlessly. Alternatively, the target system could add support for the source hashing algorithm and convert password hashes as users login next (see Garden/Password). This is beyond the scope of what any migration tool can do in isolation, but we're happy to answer questions about the process should you wish to build that functionality.

🔭 Future support

Don't see your software? Start a discussion to request it and keep an eye on our informal roadmap. We're happy to add a new Source for any software, provided it is not bespoke. For a new Target, we typically require support from the vendor.

Currently, nearly all data sources and targets are based on MySQL-compatible databases. Other storage formats (e.g. mbox, MSSQL, API) require pre-conversion to a MySQL database. The 3.0 rewrite of Nitro Porter[^1] was built with native support for those alternate formats in mind and it will continue to expand.

[^1]: 🚀 Forked 27 Sep 2021 in memory of Kyle

All versions of nitro-porter with dependencies

PHP Build Version
Package Version
Requires php Version >=8.3
ext-gd Version *
ext-json Version *
ext-pdo Version *
ext-zlib Version *
illuminate/database Version ^11
staudenmeir/laravel-cte Version ^1
monolog/monolog Version ^3
adhocore/cli Version ^1
s9e/text-formatter Version 2.15.*
nadar/quill-delta-parser Version ^3
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package linc/nitro-porter contains the following files

Loading the files please wait ...