antonioribeiro / antonioribeiro/tracker

Can't seem to easily install it using the steps provided

Open
#310 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
2.9k
Forks
594
PR merge metrics
No merged PRs in 30d

Description

Could someone please give me the clear instructions on installing the package on Laravel 5. This is the fourth time I am trying to install it and it only worked after using some 'Laravel 4' instructions.

1. Which tracker.php file are you talking about? Do I create a new one in the config directory on project root? Or the one in the package?
2. Vendor:publish Result --> Nothing to publish for tag []
3. Database Connection instructions seem to be misleading, embeded tracker array inside another tracker array does not work --> IMO & from installing it. Clear this if I used the wrong steps.

Thanks.

Would gladly like to contribute in any way?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the Laravel 5 installation instructions, especially the references to tracker.php, the config directory, Vendor:publish, and the database connection tracker array. Compare those steps with the package's current configuration files and verify them in a Laravel 5 project. Done means the documentation clearly identifies the correct file and provides working publishing and database setup instructions.

Written by the indexing model from the issue text.

Assessment

Tech stack
laravel, php
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.