Home Explore Help
Sign In
joker
/
packagist
1
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki

packagist.org网站镜像代码

Tree: 43728ee096
Branches Tags
packagist
ZIP TAR.GZ
Jordi Boggiano 43728ee096 Serialize versions in batches of 100 instead of doing it all at once 6 years ago
app 5c7ac58065 Upgrade to symfony 3.4 and other dep updates, fixes #975 6 years ago
src 43728ee096 Serialize versions in batches of 100 instead of doing it all at once 6 years ago
web 5c7ac58065 Upgrade to symfony 3.4 and other dep updates, fixes #975 6 years ago
.gitignore 5ae0c04d33 Add cs cache to gitignore 10 years ago
.travis.yml 4b63ea15dd Use MySQL service 6 years ago
LICENSE 4c7b8e0226 Initial commit 14 years ago
README.md bcc2e7ca27 Remove all solr related code 8 years ago
composer.json 5c7ac58065 Upgrade to symfony 3.4 and other dep updates, fixes #975 6 years ago
composer.lock 5c7ac58065 Upgrade to symfony 3.4 and other dep updates, fixes #975 6 years ago
phpunit.xml.dist b6588d10de Deps update and fix deprecated stuff 10 years ago

README.md

Packagist

Package Repository Website for Composer, see the about page on packagist.org for more.

This project is not meant for re-use. It is open source to make it easy to contribute but we provide no support if you want to run your own, and will do breaking changes without notice.

Requirements

  • MySQL for the main data store
  • Redis for some functionality (favorites, download statistics)
  • git/svn/hg depending on which repositories you want to support

Installation

  1. Clone the repository
  2. Edit app/config/parameters.yml and change the relevant values for your setup.
  3. Install dependencies: php composer.phar install
  4. Run app/console doctrine:schema:create to setup the DB
  5. Run app/console assets:install web to deploy the assets on the web dir.
  6. Run app/console cache:warmup --env=prod and app/console cache:warmup --env=prod to warmup cache
  7. Make a VirtualHost with DocumentRoot pointing to web/

You should now be able to access the site, create a user, etc.

Day-to-Day Operation

There are a few commands you should run periodically (ideally set up a cron job running every minute or so):

app/console packagist:update --no-debug --env=prod
app/console packagist:dump --no-debug --env=prod
app/console packagist:index --no-debug --env=prod

The latter is optional and only required if you are running a solr server.