As Hari noted, we now have 1.0.0-beta2 releases for all packages, and (for the first time) a downloadable tarball for the system as a whole.
<https://github.com/auraphp/system>
There are still a couple of "meta" problems with the release process for packages, most notably that when we tag the release, it results in a download of the *master* branch, not of the version branch. I'll remedy that with the beta3 release. There is nothing that impairs package functionality though.
Also, I have yet to update the gh-pages branch of the system; that will come shortly.
Download it, try it out, let us know if you have any troubles.
Thanks everyone!
--
Paul M. Jones
http://paul-m-jones.com/
$ cd /path/to/system/config
I am sure you know this but just in case you don't, the tarball includes
your whole
directory structure, Users/pmjones/Sites/code etc/etc
About to play a bit :)
Jeff
Ah crap. Thanks man, I'll delete that and re-upload.
Just uploaded the "not as deep directory structure" version. Let me know how that works for you. Thanks again!
Now.. back to playing
Got to go to the downloads page:
<https://github.com/auraphp/system/downloads>
How does that one look?
> @Paul , @Jeff ,
>
> the thing is if they have not clicked on the link below
> Download Packages
>
> They will get both tar and zip as in complete one .
>
> Only the files below Download Packages as you have uploaded will work .
Hm, yes. Here's the direct link:
<https://github.com/downloads/auraphp/system/auraphp-system-1.0.0-beta2.tgz>
> @Paul did you forget to tag for system ?
>
> Its not tagged for Beta2 ;) .
Nope, that's correct -- if you tag a branch, the download is for the master, not the branch. Going to figure out something else.
Yeah, the interface on the downloads page is not great. The big buttons for .zip and .tar.gz are for downloading the repository proper, not the file(s) listed underneath.
Playing with your example.package, using a single Aura framework for
multiple
websites, do you see Example.Package as also being a website or just a
package?
Jeff
@Hari
Was not my question exactly, however I think it answers it, at least if I am reading your response correctly?
You are saying:
1. Download a complete system+packages to web root
2. Then for each new project (website), download a skeleton system
3. Then symlink new project skeleton system to packages directory of (1)
If this is correct then it sounds like what I need, however how would I symlink my project
to packages directory?