furey / tinx

⛔️ Laravel Tinx is archived and no longer maintained.
449 stars 37 forks source link

create .gitignore only in the first run #57

Closed spelcaster closed 5 years ago

spelcaster commented 5 years ago
spelcaster commented 5 years ago
$ sudo -u http php artisan > /dev/null

$ ls -lah storage/tinx/.gitignore 
-rw-r--r-- 1 http http 13 Feb  4 13:55 storage/tinx/.gitignore

$ php artisan                                                                                    

In Local.php line 199:

  file_put_contents(/path/to/project/storage/tinx/.gitignore): failed to open stream: Permission denied 
spelcaster commented 5 years ago

The problem is that now tinx is trying to create .gitignore with my user, but the file already exists and it's owned by apache user... My fix is to create the file only if it does't exist

furey commented 5 years ago

@spelcaster Thank you! πŸ‘

spelcaster commented 5 years ago

Hi @furey, can you push a tag for this in packagist?

furey commented 5 years ago

Hey @spelcaster! πŸ‘‹

You probably saw I pushed a v2.1.8 release 5 days ago.

Our releases sometimes take a while to propagate to Packagist, but 5 days seems a long time.

Unfortunately, I don't have access to Tinx on Packagist (that's @ajthinking's account).

Hey @ajthinking, any ideas?

ajthinking commented 5 years ago

This package is using the legacy GitHub service and will stop being auto-updated in early 2019. Please set up the new GitHub Hook for Packagist so that it keeps working in the future.

Following the guide here: https://packagist.org/about#how-to-update-packages I ran into:

GitHub user has no admin access to the repository, or Packagist was not granted access to the organization

I checked the github repo settings page and it seems you are not allowed to give me admin rights.. so im not sure how to fix it.

For now I updated manually to 2.1.8.

Thank you guys!

ajthinking commented 5 years ago

I sent a question to packagist, hopefully they have some idea what to do.

furey commented 5 years ago

@ajthinking Legend… thanks for looking into this!

furey commented 5 years ago

Following @ajthinking's link, I was able to create a new GitHub webhook for Packagist, and was then able to update Packagist by tagging a new GitHub release:

screen shot 2019-02-12 at 2 23 56 pm

Problem solved!

πŸ€“πŸ‘

ajthinking commented 5 years ago

Awesome furey πŸ˜„

image