+
+

Related Products

  • Hightouch
    474 Ratings
    Visit Website
  • Click2Mail
    55 Ratings
    Visit Website
  • Pipedrive
    10,456 Ratings
    Visit Website
  • Notifii Track
    649 Ratings
    Visit Website
  • Building Logistics
    186 Ratings
    Visit Website
  • DNSimple
    74 Ratings
    Visit Website
  • one.com
    32 Ratings
    Visit Website
  • Aesthetic Insight
    10 Ratings
    Visit Website
  • Buildium
    2,544 Ratings
    Visit Website
  • PackageX OCR Scanning
    48 Ratings
    Visit Website

About

Packagist is the main composer repository. It aggregates public PHP packages installable with Composer. Put a file named composer.json at the root of your project, containing your project dependencies. Packagist is the default Composer package repository. It lets you find packages and lets Composer know where to get the code from. You can use Composer to manage your project or libraries' dependencies. First of all, you must pick a package name. This is a very important step since it can not change and it should be unique enough to avoid conflicts in the future. The package name consists of a vendor name and a project name joined by a/. The vendor name exists to prevent naming conflicts. The composer.json file should reside at the top of your package's git/svn/ repository and is the way you describe your package to both packagist and composer. New versions of your package are automatically fetched from tags you create in your VCS repository.

About

Rails Assets is the frictionless proxy between Bundler and Bower. It automatically converts the packaged components into gems that are easily droppable into your asset pipeline and stay up to date. First, make sure you use bundler >= 1.8.4. Add Rails Assets as a new gem source, then reference any Bower components that you need as gems. In development, if you have issues with SSL certificates and security is not a priority, you can use the alternate endpoint instead. During bundle install, if Bundler requests a package like this, Rails Assets’ daemon automatically will fetch the component from Bower’s registry, analyze its manifest file, bower.json, repackage the component as a valid Ruby gem and serve it to your application. Dependencies are handled the same way recursively. Gems created by Rails Assets work great with any Sprockets-based application. It works with Sinatra too!

Platforms Supported

Windows
Mac
Linux
Cloud
On-Premises
iPhone
iPad
Android
Chromebook

Platforms Supported

Windows
Mac
Linux
Cloud
On-Premises
iPhone
iPad
Android
Chromebook

Audience

Individuals and developers looking for a solution to create and manage their package repositories

Audience

Companies and developers in need of a solution to manage their assets and convert their packaged components

Support

Phone Support
24/7 Live Support
Online

Support

Phone Support
24/7 Live Support
Online

API

Offers API

API

Offers API

Screenshots and Videos

Screenshots and Videos

Pricing

No information available.
Free Version
Free Trial

Pricing

Free
Free Version
Free Trial

Reviews/Ratings

Overall 0.0 / 5
ease 0.0 / 5
features 0.0 / 5
design 0.0 / 5
support 0.0 / 5

This software hasn't been reviewed yet. Be the first to provide a review:

Review this Software

Reviews/Ratings

Overall 0.0 / 5
ease 0.0 / 5
features 0.0 / 5
design 0.0 / 5
support 0.0 / 5

This software hasn't been reviewed yet. Be the first to provide a review:

Review this Software

Training

Documentation
Webinars
Live Online
In Person

Training

Documentation
Webinars
Live Online
In Person

Company Information

Packagist
packagist.org

Company Information

Rails Assets
rails-assets.org/#/

Alternatives

Alternatives

CylusOne

CylusOne

Cylus

Categories

Categories

Integrations

Bitbucket
Bower
GitHub
GitLab

Integrations

Bitbucket
Bower
GitHub
GitLab
Claim Packagist and update features and information
Claim Packagist and update features and information
Claim Rails Assets and update features and information
Claim Rails Assets and update features and information