Download the PHP package cscart/sdk without Composer
On this page you can find all versions of the php package cscart/sdk. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package sdk
Short Description Command-line tools for CS-Cart & Multi-Vendor developers
License MIT
FAQ
Example:
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 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.
Informations about the package sdk
CS-Cart SDK
CS-Cart & Multivendor Command Line Tools for Developers Pride.
Purposes
We want to provide convenient developer tools for CS-Cart & Multi-Vendor. This SDK is meant to handle complicated and routine tasks related to add-on and theme development.
Usage
Installing
You'll need Composer installed in your system. Check out its installation guide if you haven't done that before.
When the Composer is installed, just execute this command in your console:
Executing commands
Command list
addon:symlink
Creates symlinks for add-on files at the CS-Cart installation directory, allowing you to develop and store add-on files in a separate Git repository.
addon:export
Copies or moves all add-on files to the separate directory, preserving the structure of directories.
addon:sync
Synchronizes add-on files between CS-Cart installation directory and the separate directory storing all add-on files. Calling this command has the same effect as calling the "addon:export" and "addon:symlink" commands simultaneously.
addon:create
Creates addon directory structure and xml/.po files.
addon:build_upgrade
Creates upgrade package between add-on versions
addon:create
Creates addon directory structure and xml/.po files.
Contributing
To contribute to this project, you need to know how to work with Git and GitHub:
- If you haven’t used Git before, check out this tutorial; you can also read Git documentation or find other tutorials on the Internet;
- If you want to learn more about GitHub, check out GitHub Help.
You’ll need a GitHub account to submit an issue or a pull request.
Submitting an Issue
Before you submit an issue, please run a search to see that it wasn’t submitted before. That way we’ll be able to deal with issues faster.
If the issue appears to be a bug, and it hasn’t been reported yet, open a new issue: switch to the Issues tab, press the New Issue button and fill in the form. You’ll need to be logged in to your GitHub account.
When submitting an issue, please provide the following information, so that we can fix it quickly:
-
Short summary of the issue - That helps us to keep things organized.
-
Why is it a problem for you? - Not all issues are bugs. If you have a suggestion on how to improve SDK, please tell us how this improvement would benefit the project.
-
Browsers and operating systems - If we know that the issue appears only in specific browsers or only in some operating systems, we’ll be able to reproduce it faster.
-
Steps to reproduce the issue - We need to see the issue for ourselves to confirm and fix it.
- Suggest a fix - If you know what might be causing the bug, please let us know.
Submitting a Pull Request
GitHub allows you to make a full copy of the SDK and work on it separately. Once you’ve made some changes, you can send us a pull request so that we can include your changes to the main repository.
To contribute to SDK development, do this:
- Register an account at GitHub, if you haven’t done it yet—you’ll need the account to complete the following steps.
- Fork the SDK — get your own copy of the main SDK repository to work on and experiment with.
- Clone your fork to your local machine—a local repository is where all the work is done.
- Create a branch in your local clone—having separate branches for different tasks helps to keep things organized.
- Work on the SDK in this branch. Please make sure to follow PSR coding standards.
- Push your changed branch to your fork in your GitHub account—the changes you made locally will appear in your online repository.
- Create a pull request—submit your changes to us.
That’s it! Our specialists will review the changes and may pull them to the repository.
Preparing local development environment
After cloning the forked repository, you'll want to be able to run the cscart-sdk command to test things locally.
In order to do that, you'll need to install the Composer package from local path.
Add these lines to your global composer configuration file located at ~/.composer/composer.json path:
Don't forget to specify path to the correct directory where you cloned your fork of a repo.
After that, execute this command:
You need to do this only once; there is no need to re-install the local package every time you make a change in code. Directory with forked repository will be symlinked to your globally installed Composer packages directory.
You're now can test your changes by executing globally available cscart-sdk command.
Copyright and License
Code released under the MIT license.
All versions of sdk with dependencies
symfony/filesystem Version ~4.0
symfony/twig-bridge Version ~4.0
ext-mbstring Version *
cscart/upgrade-builder Version ~1.0
ext-simplexml Version *
ext-intl Version *