Download to read offline
Uploaded byOrtus Solutions, Corp
ITB2016 - ForgeBox 2 Package Management
The document provides an overview of Forgebox 2.0, a ColdFusion (CFML) code directory and package management system, highlighting its features such as a new responsive UI, improved security, and multi-version support. It details the structure of packages, including the required box.json file and various package commands. Additionally, it covers registration and publishing processes for users, including API key management and options for private organizations.
More Related Content
Similar to ITB2016 - ForgeBox 2 Package Management
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
ITB2016 - ForgeBox 2 Package Management
- 1.
- 2. WHO AM I? •Luis Majano • Computer Engineer • Imported from El Salvador • CEO of Ortus Solutions • Adobe Community Professional • Sandals & Beaches -> ESRI -> Ortus
- 3. What is ForgeBox? What’sNew? Creating Packages Maintaining Packages
- 4. ForgeBox 1 releasedin 2010 NPM 1 (2011) Box Centric Code Directory Centralized Packages
- 5. What is ForgeBoxnow! • www.forgebox.io • ColdFusion (CFML) Code Directory • Does not host packages (yet) • Foster Community • Works in Unison with CommandBox • Package Management • But one simple goal….
- 6. Take ColdFusion (CFML) Backto The Future
- 7. ForgeBox 2.0 New ResponsiveUI RSS Feeds Improved Search & Security Multi-Version Support CLI Registration + Publishing UI Registration + Publishing Package Notifications This is just the start….
- 9. How we shouldwork! App#Package# Manager# CLI# REPL# Automa6on# OS#
- 10. Package Manager, REPL,CLI + More
- 11. What’s a package? •A folder or zip/tar file that must contain: • box.json • It must be in the root! init name="My Package" version="1.0.0"
- 13. Package Commands • bugs •clear • documentation • homepage • init • install • list • outdated • set • show • uninstall • update • version init —wizard
- 14. box.json • Package Descriptor •Declares package metadata • Name • Slug • Version • Author • Dependencies • DevDependencies • Installation Details • Custom Metadata
- 15.
- 16. location • ForgeBox 2.0Requires it • ForgeBox 2.0 Only uses your box.json now. • Where is your package • Code Endpoints • HTTP/S • Git • Another ForgeBox slug
- 17. Dynamic Location • CommandBoxInterceptors - Lifecycle events • Execute on pre+post publishing/versions/etc • `` Denotes a dynamic evaluation • Use Package Commands, etc { "scripts" : { "postVersion" : "package set location='gitUser/gitRepo#`package version`'" "postPublish" : "!git push", "onServerStart" : "echo 'Hi, thanks for starting `server show name` on port `server show web.http.port` in directory `pwd`'" } }
- 18.
- 19. ForgeBox Registration • Askyou a few questions • Ready to start publishing • Registers an API Key for you forgebox register
- 20. ForgeBox Login • Askfor username/password • Store your API Key • ~user./CommandBox forgebox login
- 21. ForgeBox Publish • Publishesyour packages • Reads your box.json • Can read readme files, changelogs, instructions forgebox publish
- 22. Bump Command • Bumpmajor, minor or patch placeholder • If using a git repo, it will tag and commit for you bump --patch message="Finalized awesome features."
- 23. ForgeBox Private Organization Support S3Storage Web hooks Package Favorites Analytics Security Analysis Maven Support Package + User Notifications ForgeBox Pro
- 24.