Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
developer:create_project [2019/02/25 01:40] 127.0.0.1 external edit |
developer:create_project [2019/06/04 01:20] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Creating a Splint Library ===== | + | ====== Creating a Splint Library ====== |
| + | |||
| + | ===== Create Project Directory ===== | ||
| With Splint installed, open terminal at the root of a fresh code-igniter distribution and run the command | With Splint installed, open terminal at the root of a fresh code-igniter distribution and run the command | ||
| Line 34: | Line 36: | ||
| > N.B The ''splint.json'' is necessary for the importation of the package into [[https://splint.cynobit.com|Splint]] and must be created with the same letter case as shown. | > N.B The ''splint.json'' is necessary for the importation of the package into [[https://splint.cynobit.com|Splint]] and must be created with the same letter case as shown. | ||
| + | |||
| + | > N.B All the above tasks (Creating of folders and files) can be done manually without the terminal tool. | ||
| + | |||
| + | >N.B Packages are developed relative to a patched (''MY_Loader.php'' and other files in the ''core'' directory along side dependent packages.) to enable you debug and run them as they would in their target environment. | ||
| Next, initialize the newly created package as a git repository. (''git init'' must be run at the root of the newly created package.)\\ | Next, initialize the newly created package as a git repository. (''git init'' must be run at the root of the newly created package.)\\ | ||
| Line 53: | Line 59: | ||
| > N.B ''README.md'' has to be ''README.md'' before Splint can see it. | > N.B ''README.md'' has to be ''README.md'' before Splint can see it. | ||
| - | === Publishing your Package on Splint === | + | ====== Publishing/Deploying your Package on Splint ====== |
| When you have finished developing your package, push all your commits on your master branch to GitHub. Then head on to the repository page of the package to make a release. See [[https://help.github.com/en/articles/creating-releases|Creating GitHub releases]] on how to go about that.\\ | When you have finished developing your package, push all your commits on your master branch to GitHub. Then head on to the repository page of the package to make a release. See [[https://help.github.com/en/articles/creating-releases|Creating GitHub releases]] on how to go about that.\\ | ||
| - | Log into your account on [[https://splint.cynobit.com|Splint] and go to the [[https://splint.cynobit.com/dashboard/importPackage|Import Package]] page. you should see a page that looks like this.\\ | + | Log into your account on [[https://splint.cynobit.com|Splint]] and go to the [[https://splint.cynobit.com/dashboard/importPackage|Import Package]] page. you should see a page that looks like this.\\ |
| {{ :developer:import_package.png | Splint Import Package}} | {{ :developer:import_package.png | Splint Import Package}} | ||
| Line 77: | Line 83: | ||
| This will quer it's original GitHub repository for new releases or tags. The next time someone runs ''splint install jonas/super-regex'', They'll get the most recent version of your package. | This will quer it's original GitHub repository for new releases or tags. The next time someone runs ''splint install jonas/super-regex'', They'll get the most recent version of your package. | ||
| - | === Related Topics === | + | ===== NEXT ===== |
| + | |||
| + | [[developer:unit_testing|Unit Testing Packages]] => \\ | ||
| + | |||
| + | ===== PREVIOUS ===== | ||
| + | |||
| + | <= [[developer:start|Creating Splint Projects]]\\ | ||
| + | |||
| + | ===== Related Topics ===== | ||
| [[developer:design_guides|Design Guides for Packages]] | [[developer:design_guides|Design Guides for Packages]] | ||