Hubzilla core code
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Haakon Meland Eriksen e805f589aa Updated Hubzilla on OpenShift deploy script to include unofficial repos by appending the 'insecure' argument 4 years ago
action_hooks Updated Hubzilla on OpenShift deploy script to include unofficial repos by appending the 'insecure' argument 4 years ago
cron Removed old poller 4 years ago
markers Removed hot_deploy 4 years ago Updated Hubzilla on OpenShift HOWTO with use of logging 4 years ago
pear.txt Creating template 5 years ago

#Hubzilla on OpenShift You will notice a new .openshift folder when you fetch from upstream, i.e. from , which contains a deploy script to set up Hubzilla on OpenShift.

Create an account on OpenShift, then use the registration e-mail and password to create your first Hubzilla instance. Install git and RedHat’s command line tools - rhc - if you have not already done so.

rhc app-create your_app_name php-5.4 mysql-5.5 cron phpmyadmin --namespace your_domain --from-code -l your@email.address -p your_account_password

Make a note of the database username and password OpenShift creates for your instance, and use these at to complete the setup.

NOTE: PostgreSQL is NOT supported by the deploy script yet.

Update To update, consider your own workflow first. I have forked Hubzilla code into my GitHub account to be able to try things out, this remote repo is called origin. Here is how I fetch new code from upstream, merge into my local repo, then push the updated code both into origin and the remote repo called openshift.

git fetch upstream;git checkout master;git merge upstream/master;git push origin;git push openshift HEAD

##Administration Symptoms of need for MySQL database administration are:

  • you can visit your domain and see the Hubzilla frontpage, but trying to login throws you back to login. This can mean your session table is marked as crashed.
  • you can login, but your channel posts are not visible. This can mean your item table is marked as crashed.
  • you can login and you can see your channel posts, but apparently nobody is getting your posts, comments, likes and so on. This can mean your outq table is marked as crashed.

You can check your OpenShift logs by doing

rhc tail -a your_app_name -n your_domain -l your@email.address -p your_account_password 

and you might be able to confirm the above suspicions about crashed tables, or other problems you need to fix.

###How to fix crashed tables in MySQL Using MySQL and the MyISAM database engine can result in table indexes coming out of sync, and you have at least two options for fixing tables marked as crashed.

  • Use the database username and password OpenShift creates for your instance at to login via the web into your phpMyAdmin web interface, click your database in the left column, in the right column scroll down to the bottom of the list of tables and click the checkbox for marking all tables, then select Check tables from the drop down menu. This will check the tables for problems, and you can then checkmark only those tables with problems, and select Repair table from the same drop down menu at the bottom.
  • You can login to your instance with SSH - see OpenShift for details - then
cd mysql/data/your_database
myisamchk -r *.MYI

or if you get

Can't create new tempfile

check your OpenShift’s gear quota with

quota -gus

and if you are short on space, then locally (not SSH) do

rhc app-tidy your_app_name -l your_login -p your_password

to have rhc delete temporary files and OpenShift logs to free space first, then check the size of your local repo dir and execute

git gc

against it and check the size again, and then to minimize your remote repo connect via SSH to your application gear and execute the same command against it by changing to the remote repo directory - your repo should be in


(if not, do find -size +1M to find it), then do

cd ~/mysql/data/yourdatabase
myisamchk -r -v -f*.MYI

and hopefully your database tables are now okay.

##NOTES Note 1: definitely DO turn off feeds and discovery by default if you are on the Free or Bronze plan on OpenShift with a single 1Gb gear by visiting when logged in as administrator of your Hubzilla site. Note 2: DO add the above defaults into the deploy script. Note 3: DO add git gc to the deploy script to clean up git. Note 4: MAYBE DO add myisamchk - only checking? to the end of the deploy script.

The OpenShift php cartridge documentation can be found at:

For information about .openshift directory, consult the documentation: