Github Size of File?

IamJim

Member
I guess I'd like to name this "What's wrong with this picture" (and it is attached.

1) Just re-downloaded core 3.xx whatever it is and going to take another stab with this...and installed it..on a brand new Joomla installation.

2) I then, using the WIKI http://fabrikar.com/forums/index.php?wiki/update-from-github/ grabbed the "latest"..

??? It is 19meg something in file size? In zip? And the whole 3.x.x.x Core Install is 5 something?

Anyway, I extracted it...but not going to do a thing until I hear back "What's wrong with this picture", as I have a GIT zip also as you can see here from 11/13/2012 and it is only 2meg.. Not sure if that is right?

PS..How do I attach an image file here? Without using a http://uploaded link?

h8qlvYo3U06RAAAAABJRU5ErkJggg==
 
A core install doesn't contain all the plugins and libraries, it installs the most common options.

The Github file also contains some build files which you do not need to upload to your server. So you can delete folder fabrik_build.

If you are updating regularly you could probably remove \libraries\dompdf as well as that the biggie at around 13mb. This is for PDF's but the libraries don't update that often so you don't necessarily need to upload them each time.
 
Again, I thank you Felixkat for your prompt replies. I would think "this info" that you just gave me, could also be added as a 'notation' in the wiki > http://fabrikar.com/forums/index.php?wiki/installation-instructions/ or really here> FTP UPDATE area >> http://fabrikar.com/forums/index.php?wiki/update-from-github/

Again, my thanks..

It did have a hic cup on install, I did it again and it was fine. Back end showed an UPDATE so I did that <and I haven't did any GIT action yet, was waiting a reply here> and will upload now...

Thank's to you!! <smile>

Jim
 
Rotten UPDATE.

When it rains, it pours..<sigh>

1) I decided to try, for the first time simply "wget" instructions from http://fabrikar.com/forums/index.php?wiki/update-from-github/ instead...as long as I was "wasting heartbeats" again.

2) They belonged to "root" at that point, so I CHOWN'd -R them to the acct *
Code:
chown -R acctname:acctname *


3) It totally trashed trashed the admin area?

Any suggestions? Now, I am looking at another full clean J! install again..??

Throwing

500 Internal Server Error

The request was not completed. The server met an unexpected condition.
 
Hugh or Rob Please? 21 hours, back at the ranch

Stardate 20121123:18:07CST

1) Another Fresh J! install with 2.5.6 then backend upgrade to 2.5.8

2) Another fresh Fabrik, then used the update and install the little sample date

3) At this point? My admin in Joomla still works.

Stand by please, but don't hold your breath!! :D

4) OK, ran >

wget --no-check-certificate https://github.com/Fabrik/fabrik/tarball/master -O - | tar -zx --strip-components 1

5) File ownership on remote server = root

6) Refresh admin in Joomla =
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.


7) chown -R accountname:accountname * (now)


Same deal, same error...


8) So, can one of the developers [pretty please Hugh] please figure out what is wrong please?



Thanks in advance,


Jim
 
Well, another fresh install...did the update jazz using FTP <and thanks Felix for trimming this down, as I am in the country and use a wireless ISP> and see all but one <below>

Fabrik Package Site
Package 3.0.6.3 September 2012

say

${createdate}

for the date??



ADDED Stardate 20:22CST pc time.. [just to track my time on this] all Plugins now enabled..etc.. I've had enough fun for now.. 10+% of a day <smile> and nothing even started again for this...as I am still curious why the github WGET does not work, and really don't want to do a thing...until that is figured out... as I know I am going to have to re-load this whole thing again... Forgive me, but from being around since before MSFT, and onboard with the beta teams from DOS 3.0 thru 6.22, then onto Windows, and NT teams with Bill and the gang, while also beta for Borland.. Forgive me, as I also suffer from "Bauer Syndrome"..
 
If you are looking to get files directly from github to your server, then wouldn't installing git on the server and creating a repository there make more sense? That way you would be able to rollback/forwards from the servers local repository, and would avoid what ever is causing the issue with wget.

I'm not sure who put the wget info on the wiki and its not something I have any experience with I'm afraid, so I'm unable to comment on that.
 
If you are looking to get files directly from github to your server, then wouldn't installing git on the server and creating a repository there make more sense? That way you would be able to rollback/forwards from the servers local repository, and would avoid what ever is causing the issue with wget.

I'm not sure who put the wget info on the wiki and its not something I have any experience with I'm afraid, so I'm unable to comment on that.

Hi Rob and sorry for such late reply on this...as have not had much time to keep spinning and play with Fabrik.

1) As for "who" put up the wget instructions in the WIKI.. There is no change log or tracking in it? [sorry, it's not my WIKI and not familiar with all of what it has, but I would think so] As a user must be logged in order to post. I made a couple refinements in initial areas this morning, as I am going to attempt this again.

2) BUT? Had a new FRESH J2.5.x in and Fabrik install set up, ran the wget again and now get the below.. The site still display Front end HOME, but Admin is =

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@fab2013-0220.XXXXXX.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.


3) Looking at it, again 'root' is ownership...so did a



chown -R acctname:acctname * and it changed most of them


a) .gitignore file still root - root
b) .tx/ Directory still also root - root

4) Still the same thing, can't get the admin back.


Jim
 
well I could tell you the user who wrote it - but I have never tested it or would think it to be a sensible way to go about things, but as Im not a server guy maybe Im wrong there.

More information about this error may be available in the server error log.
So did you check your error logs? Was there any additional information?

If this is a leased box installing git on the server would still be my preference over this wget method.
 
I believe I was the one who wrote the wget instructions. I hadn't tested them for a while, so I ran a quick test.

I created an empty test dir, logged in as 'joomla' (the user that owns my J! web root) and copied and pasted the wget command from the wiki ...

Code:
-bash-3.2$ mkdir wget_test
-bash-3.2$ cd wget_test
-bash-3.2$ wget --no-check-certificate https://github.com/Fabrik/fabrik/tarball/master -O - | tar -zx --strip-components 1
--2013-02-25 18:13:14--  https://github.com/Fabrik/fabrik/tarball/master
Resolving github.com... 207.97.227.239
Connecting to github.com|207.97.227.239|:443... connected.
WARNING: cannot verify github.com's certificate, issued by `/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance EV CA-1':
  Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 302 Found
Location: https://nodeload.github.com/Fabrik/fabrik/legacy.tar.gz/master [following]
--2013-02-25 18:13:15--  https://nodeload.github.com/Fabrik/fabrik/legacy.tar.gz/master
Resolving nodeload.github.com... 207.97.227.252
Connecting to nodeload.github.com|207.97.227.252|:443... connected.
WARNING: cannot verify nodeload.github.com's certificate, issued by `/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3':
  Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 19312379 (18M) [application/x-gzip]
Saving to: `STDOUT'

100%[======================================>] 19,312,379  1.38M/s   in 12s

2013-02-25 18:13:33 (1.53 MB/s) - `-' saved [19312379/19312379]

-bash-3.2$ ls -l
total 152
drwxr-xr-x  4 joomla joomla  4096 Feb 25 17:55 administrator
-rw-r--r--  1 joomla joomla   372 Feb 25 17:55 build_config.ini
-rw-r--r--  1 joomla joomla  4863 Feb 25 17:55 build_js.xml
-rw-r--r--  1 joomla joomla  3101 Feb 25 17:55 build_one_js.xml
-rw-r--r--  1 joomla joomla  8036 Feb 25 17:55 build_updateserver_xml.xml
-rw-r--r--  1 joomla joomla 38757 Feb 25 17:55 build.xml
drwxr-xr-x  4 joomla joomla  4096 Feb 25 17:55 components
drwxr-xr-x  4 joomla joomla  4096 Feb 25 17:55 fabrik_build
drwxr-xr-x  4 joomla joomla  4096 Feb 25 17:55 libraries
drwxr-xr-x  3 joomla joomla  4096 Feb 25 17:55 media
drwxr-xr-x  5 joomla joomla  4096 Feb 25 17:55 modules
drwxr-xr-x 11 joomla joomla  4096 Feb 25 17:55 plugins
-rw-r--r--  1 joomla joomla  2088 Feb 25 17:55 README.md
-rw-r--r--  1 joomla joomla     0 Feb 25 17:55 test.txt
-bash-3.2$

Apart from the bitching about the cert, it works. I haven't done it into one of my live Fabrik installs, but the default mode for tar -x is to overwrite, so that shouldn't be an issue. You could try adding --overwrite to the tar args, though.

If you just do a wget, without the pipe to tar, does it fetch the file?

-- hugh
 
OBTW, the main thing that adds a potentially "unnecessary" chunk of size to the github ZIP is the DOMPDF library, the 3rd party library we use for generating PDF's, which accounts for about half the total size.

We have considered omitting this from github, and simply providing instructions for obtaining and installing the DOMPDF library if you want PDF support, but having tried this with similar situations in the past with 3rd party libraries, decided the support overhead was not worth omitting it.

-- hugh
 
BTW, Rob ... re ...

I have never tested it or would think it to be a sensible way to go about things

All it is, is a quick way of grabbing and "uploading" the master tarball. End result of the wget/tar thing is exactly the same as downloading the tarball, unzipping it, and ftp'ing all the files up to the server. If you have ssh (command line) access to your server, it makes sense.

Of course, it's "better" to use git itself, especially if you have ssh access to the server and aren't intimidated by the command line. But for some folk, using git isn't possible and/or easy and/or preferable.

So what this does is just give you a one line shortcut for grabbing and installing everything from the latest github files.

BTW, there's a similar one liner you can do in Winders. I just can't remember it off the top of my head.

-- hugh
 
[I'm using 'tarball' incorrectly, as that actually means a .tar.gz, not a a .zip. Which of course is a 'zipball'. All I mean is the compressed archive of current github you get from the standard ZIP button on the main github page]

-- hugh
 
Hello Hugh and thanks [overdue reply from me] for this post....

You mentioning >
(the user that owns my J! web root)
did it...as I logged in as the user, and things went fine. The baffling part was why after trying to change ownership Recursively [which works well in other things] a few did not.

Again, my thanks..

I also sent you you a PM a couple days ago, and was wondering if you could please look into it please? I've been in a holding pattern for 10+ days now...to continue on, as would like to knock one thing down at a time.

Jim
 
I also sent you you a PM a couple days ago, and was wondering if you could please look into it please? I've been in a holding pattern for 10+ days now...to continue on, as would like to knock one thing down at a time.

Jim

IamJim, Mar 9, 2013

2.5 Years now ;)
 
Well, that's why I regularly tell people not to PM me. I delete my PM's once a month, to get rid of all the logins and passwords, and PM's just don't stay on my support radar.

-- hugh
 
We are in need of some funding.
More details.

Thank you.

Members online

Back
Top