New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document upgrade/installation procedures for Git checkouts (with composer.phar install --no-dev and git submodule update --init --recursive) #8717
Comments
When checking out from git, you might need to do a |
Ah, you mean running However, I've encountered a subproblem now:
Contents of that log file:
Shared hosts (or most locked-down web servers) will not have C compilers lying around, for security reasons. Can we do something about that? |
Try |
Ah yes, that worked... but it seems there's still a bug left to investigate in the process:
Running the DB upgrade script:
But now, the bug is this: when visiting the web interface, no data shows up, and I get this error shown in the Admin settings:
Again, not sure why this would happen, it seems like the file really is missing:
|
Ok. Seems the submodule is missing. Try |
That worked! Woohoo :) I get the overall feeling that it'd be pretty nice to have a "If you're installing/upgrading from Git…" (sub)page in the docs to list all those gotchas... It might others some trouble! |
IIRC there should be a page in the FAQ about deploying Piwik using Git, but
that might be a bit outdated.
Btw. It is not the common use case maintaining Piwik using Git. Normaly it
should be installed using the downloadable build and the built-in auto
update mechanism.
|
I understand it's not the most common/straightforward technique, but it's the "safest" for me as I run on a shared host with a sizeable database (~1.4 GB used by Piwik) so I need to be able to test & revert versions :) |
Here's the FAQ re using Piwik via Git but it's not recommended for security reasons etc http://piwik.org/faq/how-to-install/faq_18271/ |
Closing as I think it's resolved, please reopen or comment if not |
Maybe we should extend our git:pull command, as it only allows pulling the master... For real deployment maybe it would be better to checkout a specific version |
OK reopening... Not sure if our git:pull command can handle this but I presume so. |
Ah that FAQ is interesting! It's missing a few bits that I learned in this bug report though. So instead of:
Maybe it could say:
Complemented by:
Hoping that's useful. |
Thanks @nekohayo this was really useful! I've updated the FAQ to explain the two use cases: using Bleeding edge master, or Deploying a specific release. Also added |
A little bird told me I could upgrade from one version straight to another without going through intermediate version upgrades. However this failed for me today:
And yet I did not make any hacks/modifications to my setup:
So I reverted back to my previous version:
The text was updated successfully, but these errors were encountered: