satis icon indicating copy to clipboard operation
satis copied to clipboard

Simple static Composer repository generator - For a full private Composer repo use Private Packagist

Results 119 satis issues
Sort by recently updated
recently updated
newest added

An old version of some dependencies depedency uses that pessimistic version constraint, which causes the build to fail completely because the exception isn't caught: ``` [UnexpectedValueException] Could not parse version...

bug

To allow deploying a particular version of Satis it would be very useful if git tags could be utilised for each new release of Satis. This would for instance allow...

question

I have some project in a SVN repository. The directory structure looks like this: ``` $svn-root/project/ - trunk - composer.json - ... - branches (empty) - tags (empty) ``` Now...

support

It would be nice to have a possibility to define some options (for example required packages) pro repository. This would simplify mirroring. Also it would speed up some operations -...

feature

Hi, It would be very helpful if you could show the package version currently in use next to the required by packages. For example: I have the following 2 repos...

feature

Hello, I am trying to diagnose a network connectivity issue with my company's internal-only satis repository when connected via VPN. Everything works fine when plugged into the network directly (I...

support
question

We have two teams - one in a country where internet is fast enough to require a Satis (also they're mostly doing remote-work so there's not one LAN in which...

support
question

For example we have a source of a package: URL: http://github.com/vendor/prj.git reference: "someHashToMasterBranch" But GitHub can generate ZIP archive: http://github.com/vendor/prj/archive/master.zip So, satis can generate "dist" for an archive. GitLab can...

feature

I just run satis on a satis.json file which looks similar to this: ``` javascript { "name": "My Repository", "homepage": "https://satis.somehost.com", "repositories": [ { "type": "vcs", "url": "git@myowngit1host" } ],...

bug
support

We have some already existing package definitions which only need to get added to "includes" of the resulting packages.json Is there a way to archive this?

feature