danack / bastion

An application to make managing a Satis repository easier.

Bastion

Run your own Packagist server, so that you can do Composer update locally. Oh and it also creates RPM packages for your applications.

Documentation

Please see the documentation at http://bastionrpm.com

Quick setup - satis repo

• Run ./src/bastion.php It will ask you to provide a Github access token

• Edit bastionConfig.php to list the Github repos you want to be available to install.

• Run ./src/bastion.php again. Now that everything is stup it will download the tagged versions of the libraries as zip balls, before uploading them to S3.

You will now have a satis repository uploaded to S3. You can also run this satis provider locally, with the PHP builtin server php -S localhost:8000 -t zipsOutput/ .

Quick setup - setting up S3 static satis DNS

• Setup a bucket in your preferred region, with a name like satis.companyname.com

• Setup a cname to point satis.companyname.com to satis.companyname.com.s3.amazonaws.com

And that's it. The access in this example is done via an ACL to allow certain IP address. If you have the capability I would suggest using an private virtual network to avoid the need for any over the internet access.

Setting up RPM packager

Insert instruction here

bastion's Issues

Find a cli routing library

that doesn't suck.

Check artifacts aren't being downloaded twice.

Download complete of aws/aws-sdk-php/aws_aws-sdk-php_3.0.0-beta.1
Download complete of aws/aws-sdk-php/aws_aws-sdk-php_3.0.0-beta.1
Download complete of aws/aws-sdk-php/aws_aws-sdk-php_2.7.1
Download complete of aws/aws-sdk-php/aws_aws-sdk-php_2.7.1

Need to delete old Satis include files

Currently the include json files are never deleted, and so they accumulate in the output/include directory.

Need to add support for Github's crappy pagination

   if ($repoTags->pager) {
        $newPages = $repoTags->pager->getAllKnownPages();
        foreach ($newPages as $newPage) {
            $pages[$newPage] = false;
        }
    }

For the record, it's crappy because it's a completely different api call to the original listRepoTags call.