terramar-labs / packages Goto Github PK

• GitHub

Currently, jquery and bootstrap are still loaded from jsdelivr. This should not be the case. Change references to these resources to use the scripts stored under web/js

Any thoughts on upgrading the Guzzle library to a newer version?

While installing the package I got the notification that: Package guzzle/guzzle is abandoned, you should avoid using it. Use guzzlehttp/guzzle instead.

This can introduce some potential security risks since the old guzzle package is no longer maintained.

Disabling a Remote should also disable all of the Remote's Packages (including disabling webhooks)

Using GitLab 8.3.2 all webhooks fail with message Hook execution failed: Accepted

Hello,

Is there a way to allow only deposited users access to the repository via username and password or a token? If possible, these users / tokens should be managed by means of an API request.

Thanks

Regards
Bjoern

Gitlab allows the creation of project web hooks to trigger external events when an event occurs, including "push events" and "tag push events". Please implement configurable support for these web hooks so I can (almost) immediately see Gitlab updates in Packages.

Please see this page for documentation: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/web_hooks/web_hooks.md

When I run bin/console satis:update --build in the repo I get the this in the output which I expect
"dist": { "type": "zip", "url": "https://gitlab.url.com/api/v3/projects/namespace%2Frepo/repository/archive.zip?sha=hash", "reference": "hash", "shasum": "" },

When it is triggered by the webhook in gitlab that section is always missing but everything else is the same.

Is there any reason why the web hooks cause php bin/console satis:update --build to be run on its own?

Surely it should be running a command to just tell satis to rebuild that individual repository.

As it stands packages ends up being unusable when you've got a lot of repos as it means it's forever performing a full rebuild.

I think it would be good to have open, Satis-like (conceptually, not visually) view with list of available (enabled) packages. It could be available on domain.tld/packages, and it should contain data related to packages.json, but presented in user-friendly way. It should be generated automatically with packages.json.

The Releases on the right side are not sorted.

Just a note for anyone setting this up: if you receive a general error when trying to add entries to the database this is resolvable by allowing the web server write access to the folder the sqlite database is in (as well as write permissions to the database file itself). See https://stackoverflow.com/questions/20364608/pdo-php-sqlite3-database-connection-general-error-14

When a webhook is triggered, validation should be done using the package's remote.

Implement some data validation service that each remote type can implement.

Something like:

<?php

interface WebHookValidatorInterface
{
    public function validate(Request $request, Package $package);
}

For small projects no beeing bound to redis would make live easier.

There is https://github.com/php-enqueue/enqueue-dev which allows to use different backends.

This may make sense for this project as well.

Thanks a lot for considering.

Currently, Packages still supports PHP 5.6. Composer Satis (relatively) recently started work on 2.x line of Satis and are requiring PHP 7+.

We need to change the requirement in Packages' composer.json to use Satis's 1.x branch:

    "composer/satis": "1.0-dev",

Hi, I'm missing some information in the docs.

• What does "Clone this project locally after each code push" mean?
• If I enable the Composer Satis plugin, how do I install the package?
• Where can I access the satis packages page which shows the installable versions, etc.?

And one which I was able to figure out so far:

• Why don't my changes to the twig file show? (hint: delete twig cache in /path...)

Cheers
Markus

After successful install and configuration I got these error in web interface and bin/console orm:schema-tool:create

"SQLSTATE[3D000]: Invalid catalog name: 1046 No database selected"

The database is created and the authentication working and I think the config.yml is correct:

security:
  # Username and password to access the web management interface
  username: admin
  password: xxxx

doctrine:
  mapping:
    default:
      paths: [ '%app.root_dir%/src/Entity', '%app.root_dir%/src/Plugin' ]
      namespace: Terramar

  database:
    # Any Doctrine driver
    driver: pdo_mysql
    host: 127.0.0.1
    database: packages
    user: packages
    password: xxxxxx


resque:
  host:     'unix:/var/run/redis/redis.sock'
  port:     ~
  database: 0

The Version 3.2.0 has a problem with the Webhooks after upgrade from 3.1.5.

Please provide a docker image for instant setup.

Does this tool provide any mechanisms to control auth for consumers of packages provided by satis? The satis documentation mentions using an API-Token in the repository configuration to auth. I'm curious if this gives us a way to manage that.

Hi I have some trouble with Packages, because it does not update Satis if its triggered by a push or manually by GitLab. It updates only if its triggered in the console.

So I just tried to stop the worker and this is what I get:

[root@x composer]# bin/console resque:worker:stop -a
Stopping x.x.ch:10937:*...
PHP Fatal error:  Call to undefined function Terramar\Packages\Console\Command\Worker\posix_kill() in /var/www/x/src/Console/Command/Worker/StopCommand.php on line 61

Fatal error: Call to undefined function Terramar\Packages\Console\Command\Worker\posix_kill() in /var/www/x/src/Console/Command/Worker/StopCommand.php on line 61

Just installed on fresh new server and followed the installation instruction and getting 500 error.

But /index_dev.php is working.

Any insight, how to get started on this packages?

After click on the Sync Button for my GitLab Remote i got an Error 500.

Fatal error: Uncaught PDOException: SQLSTATE[23000]: Integrity constraint violation: 1451 Cannot delete or update a parent row: a foreign key constraint fails (devpackages.packages_gitlab_configurations, CONSTRAINT FK_1FE0005DF44CABFF FOREIGN KEY (package_id) REFERENCES packages (id)) in /var/www/vhosts/mydomain.de/httpdocs/packages/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:105 Stack trace: #0 /var/www/vhosts/mydomain.de/httpdocs/packages/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php(105): PDOStatement->execute(NULL) #1 /var/www/vhosts/mydomain.de/httpdocs/packages/vendor/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(1006): Doctrine\DBAL\Driver\PDOStatement->execute() #2 /var/www/vhosts/mydomain.de/httpdocs/packages/vendor/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(596): Doctrine\DBAL\Connection->executeUpdate('DELETE FROM pac...', Array, Array) #3 /var/www/vhosts/mydomain.de/htt in /var/www/vhosts/mydomain.de/httpdocs/packages/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php on line 60

I use packages 3.1.0 together with gitlab 8.0.2.
After deleting a repository from gitlab, the package is still present inside packages, also if I sync remotes.
There is no delete function inside packages and if I try to deactivate the package I get an error message:

Fatal error: Uncaught exception 'Gitlab\Exception\RuntimeException' with message '404 Project Not Found' in /var/www/vhosts/domain.tld/packages/vendor/m4tthumphrey/php-gitlab-api/lib/Gitlab/HttpClient/Listener/ErrorListener.php:60 Stack trace: #0 /var/www/vhosts/domain.tld/packages/vendor/m4tthumphrey/php-gitlab-api/lib/Gitlab/HttpClient/HttpClient.php(177): Gitlab\HttpClient\Listener\ErrorListener->postSend(Object(Gitlab\HttpClient\Message\Request), Object(Gitlab\HttpClient\Message\Response)) #1 /var/www/vhosts/domain.tld/packages/vendor/m4tthumphrey/php-gitlab-api/lib/Gitlab/HttpClient/HttpClient.php(109): Gitlab\HttpClient\HttpClient->request('projects/121', Array, 'GET', Array) #2 /var/www/vhosts/domain.tld/packages/vendor/m4tthumphrey/php-gitlab-api/lib/Gitlab/Api/AbstractApi.php(50): Gitlab\HttpClient\HttpClient->get('projects/121', Array, Array) #3 /var/www/ in /var/www/vhosts/domain.tld/packages/vendor/m4tthumphrey/php-gitlab-api/lib/Gitlab/HttpClient/Listener/ErrorListener.php on line 60

You should update your package, if it should be longer a solution for gitlab users ...

I did make a fresh install of the package, but the webhook didnt work anymore, if did a test on the gitlab it will show the following message in the log (and a 500 in the webhook site of gitlab)

Uncaught exception 'Symfony\\Component\\HttpKernel\\Exception\\MethodNotAllowedHttpException' with message 'No route found for "GET /webhook/24/receive": Method Not Allowed (Allow: POST)' in /cluster/var/www/site/packagist/vendor/nice/framework/src/Router/RouterSubscriber.php:63\nStack trace:\n#0 [internal function]: Nice\\Router\\RouterSubscriber->onKernelRequest(Object(Symfony\\Component\\HttpKernel\\Event\\GetResponseEvent), 'kernel.request', Object(Symfony\\Component\\EventDispatcher\\ContainerAwareEventDispatcher))\n#1 /cluster/var/www/site/packagist/vendor/symfony/event-dispatcher/EventDispatcher.php(181): call_user_func(Array, Object(Symfony\\Component\\HttpKernel\\Event\\GetResponseEvent), 'kernel.request', Object(Symfony\\Component\\EventDispatcher\\ContainerAwareEventDispatcher))\n#2 /cluster/var/www/site/packagist/vendor/symfony/event-dispatcher/EventDispatcher.php(46): Symfony\\Component\\EventDispatcher\\EventDispatcher->doDispatch(Array, 'kernel.request', Object(Symfony\\Component\\HttpKernel\\Event\\GetResponseEv in /cluster/var/www/site/packagist/vendor/nice/framework/src/Router/RouterSubscriber.php on line 63

And btw ... sami with dev-master is a very bad idea, because they did update and force now php7 (little bit to earlier in my opinion, its not your fault)

Can you please have a look, because your tool is great, but if the webhook doesnt work, it is senseless, because the bin/console satis:update and satis:build didnt work too anymore.

HI I am using the packages with GITLAB. Its working great for us. Except there is a small glitch.
When I do
bin/console satis:update --build I am getting an error.

[RuntimeException]                                                                                                                                                                
  Failed to execute git clone --mirror '[git@https://gitlab.myreposerver.com]:company/limited-testing.git' '/root/.cache/composer/vcs/-git-https---gitlab.myreposerver.com--admin-limited-test  
  ing.git/'                                                                                                                                                                         
  Cloning into bare repository '/root/.cache/composer/vcs/-git-https---gitlab.myreposerver.com--admin-limited-testing.git'...                                                            
  fatal: I don't handle protocol '[git@https'  

Now I understand the URL: [git@https://gitlab.myreposerver.com]:company/limited-testing.git is not a valid URL. I tried in changing that in gitlab but the square brackets [] are coming anyways.

Can you help how I can solve this problem ? Many thanks

I renamed a GitLab repository and then clicked on the sync button. Unfortunately, the repository is still displayed with the old name and path.

Hello,

i used the version 3.1.2 and will now upgrade to 3.2.0 but i have some issues with the new release.
currently i have a issue with the design and all input forms.

The Input forms does not working. I can not create a new repository or package.

Regards,

Bjoern

Currently it just generates docs with default options in a temporary directory.

It should:

• Be able to clone from a remote (Perhaps another package?)
  or generate a new git repositoriy (and publish?)
• Generate the documentation
• Create a new commit
• Push to configured remote, if any

Other deployment tools can take over from there

Please,

update the require restriction for package composer/composer, it is in 1.1.2 version yet.

Am I understanding this right that the worker has to manually be restarted after every web server restart? Is there a good way to automatize this?

Hello,

I keep getting the following message when I run: bin/console orm:schema-tool:create

No Metadata Classes to process.

What am I doing wrong?

Steps to reproduce:

• clone the packages repository
• go inside the repository
• run composer install
• copy config.yml.dist to config.yml
• edit config.yml
• run bin/console orm:schema-tool:create

I even skipped editing of config.yml and tried to use default values and still the same error.

Best regards,
Vladimir

Hello,

after execute the composer install command in to a fresh installation and the execute the command

composer update

i got this error message:

bash-4.1$ composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - composer/satis dev-master requires php ^7.0 -> your PHP version (7.0.27) overridden by "config.platform.php" version (5.6) does not satisfy that requirement.
    - composer/satis dev-master requires php ^7.0 -> your PHP version (7.0.27) overridden by "config.platform.php" version (5.6) does not satisfy that requirement.
    - Installation request for composer/satis dev-master -> satisfiable by composer/satis[dev-master].

i try php 5.6 and 7.0 with the same result.

Regards,

Bjoern

I'm not sure whether this is a bug or that I'm doing something wrong.

I installed packages as per http://docs.terramarlabs.com/packages/3.1/getting-started/installation. All goes well, until I run bin/console orm:schema-tool:create. That command throws a MySQL error (or rather, three times the same one):

[Doctrine\DBAL\Exception\ConnectionException]
  An exception occured in driver: SQLSTATE[28000] [1045] Access denied for user 'root'@'localhost' (using password: NO)

I cannot for the life of me figure out why Doctrine tries to connect using 'root'@'localhost' with no password, as I have another with WITH password specified in config.yml. config.yml is in the project root, same location as config.yml.dist

Here are the contents of my config.yml file:

security:
  # Username and password to access the web management interface
  username: ******
  password: ******

doctrine:
  mapping:
    default:
      paths: [ '%app.root_dir%/src/Entity', '%app.root_dir%/src/Plugin' ]
      namespace: Terramar

  database:
    # Any Doctrine driver
    driver: pdo_mysql

    # Options
    ## path: %app.root_dir%/database.sqlite
    host: 127.0.0.1
    user: packages
    password: ******
    dbname: packages

resque:
  host:     'unix:/tmp/redis.sock'
  port:     ~
  database: 0

Hi

We want to run redis with a password. There doesn't seem to be a way to use the rescue workers with AUTH. How about giving the option in the config to set a password?

Hello,

I'd like to contribute some improvements to packages, but I have a big question upfront.

Is there a specific reason not to use symfony all the way?
Would you be happy if I migrate the code to symfony, or should I start a new project and use packages just as a dependency?

The best,
Simon

The language in the Packages Dashboard for adding remotes does not clearly indicate that the remote URL should be the root of the GitLab installation rather than a remote git repository -- which is generally called a "remote" when using git, hence my confusion.

The result of my confusion is that I added a URL that looked like this: http://gitlab.mydomain.com/web-developers/cms.git (not intended to be an actual link)

This returned non-descript HTTP 500 error responses when attempting to Sync, and I had to dig through vendor packages to find out what it was trying to do. When I saw the "/api/packages..." string appended to the end of my URL, I knew how to fix it. In retrospect, this is obvious, but "remote" is what threw me.

Documentation is not strictly clear, but this blog post hints that the root URL is expected: https://tylersommer.com/managing-private-composer-repositories-with-packages

My suggestion is that some kind of detection/validation be done on GitLab URLs when the form is processed to make sure that the URL does not point to a .git repository.

reference to #73

Hello Tyler,

thank you for the answer. I have now enabled this feature secure_satis: true and has the problem that has nothing changed.
only after i am clear the folder cacheand satisand run /bin/console satis:build finished the securing for satis.

now composer asks to username and password, how can i now manage this users?
the managed user are not working

And now i see that the /packages URI is protected too.
Can i would like to change it separat, please. Can you change this ?

Thank you,

Regards,

Bjoern

Hi @tyler-sommer,

i have seen, that the release date is not correct. It is the current datetime and not the releasedate from the package.

Regards,

Bjoern

The dist url for the packages does not working. The files can't be found and i got a error 404.

Instead of requiring the user private token, use OAuth2 for api calls.

http://doc.gitlab.com/ce/api/oauth2.html

Maybe the best way to add this feature, is to create a new plugin gitlab_oauth...

I can't get access to my private Github repos, even when I allow all options in the personal access token. After syncing, I see only my public repos, but no private ones.

hey folks,
thanks a lot for this awesome project.

I realized that our setup does not do any background jobs. worker is running redis is setup. but since I am quite new to redis and resque i dont know howto debug.

Do you have any tips to find out why i have to call bin/console satis:build manually to get a new packages.json generated?

thanks

• Phil

Not satisfied with the way actions are implemented. Events might be able to be used instead, but I'm unsure how to link the markup rendering to the domain updating in a coherent way.

Any ideas besides adding HTTP_BASIC_AUTH to hide the packages.json and it's respecitve includes from the public?

I'd like to have some Token/Auth based solution but no idea on how to solve this best..

It would be nice if we can filter package by Gitlab groups.

Maybe you can add an optional "group" field in Gitlab config ...

Integrate something like jekyll to generate a site with configurable options when code is pushed.

This will function to automatically generate documentation sites (docs exist within code bases) and should function similarly to the Sami plugin (see #6)