It looks like some people are working very hard out there to try and preserve iFolder for future versions of Opensuse. To those people (the NoFolder crew, Ravi Kumar, etc.), I’m indebted; I simply would be at a loss without iFolder. Yes, I use DropBox, and a couple other things, but there’s just nothing like iFolder for complete control over the server and the sync’d content.
But the sad fact is, it has suffered a bit of neglect as of late. Okay, a LOT of neglect. And you’re probably here because you have an Opensuse 12.1 (or 11.4) server, and you tried to install iFolder 3.8.x on it, and had some trouble.
Notes: I strongly recommend you see my old post about setting up iFolder 3.8 on Opensuse 11.1 for background and additional detail, as this post will be brief and to-the-point without much supporting detail. All the work in this doc was performed on the x86_64 version of Opensuse, and was tested on both 12.1 and 11.4.
First, build up an Opensuse 12.1 box. I tend to build them with “Minimum X Window”, “IPv6 Disabled”, “SSH enabled”, and a dedicated partition for iFolder database and content (like /ifolder); other then that, fairly typical. And I never install patches during installation. So updates are the first thing we do after completion:
zypper ref; zypper up
So first, decide on a single name that you will use for the server for the host configuration, certificate creation, Apache2 configuration, and iFolder service configuration; it is imperative that you use one name! For the following examples, I use “
ifolder.yourLinuxGuy.com“. Let’s configure that critical name and static address:
Now, let’s install all the supporting software we need (of course
findutils isn’t needed for iFolder, but I can’t live without it; but
mono-wcf is the one most people seem to miss):
zypper in apache2-worker findutils-locate apache2-mod_mono log4net mono-core mono-data mono-data-sqlite mono-web mono-winforms mono-wcf xsp libflaim
Next we configure apache2 and related components, starting by generating a certificate (obviously, replace the values to suit):
/usr/bin/gensslcert -c US -s MI -l "City" -o "Your Linux Guy" -e email@yourLinuxGuy.com -d -n ifolder.YourLinuxGuy.com
Add SSL to the APACHE_SERVER_FLAGS section:
Un-comment and change “ServerName” to match the name you put in /etc/hosts, and optionally set “ServerAdmin” to your email address:
cd /etc/apache2/vhosts.d/; cp vhost-ssl.template vhost-ssl.conf; vi vhost-ssl.conf
Now to open ports 80 and 443, set
Next, we install the stars of the show, the iFolder packages:
rpm -Uvh http://download.opensuse.org/repositories/home:/rkumar1:/branches:/network:/ifolder:/server_stable/openSUSE_11.4/x86_64/ifolder3-enterprise-126.96.36.199.11091.1-6.2.x86_64.rpm rpm -Uvh http://download.opensuse.org/repositories/home:/rkumar1:/branches:/network:/ifolder:/server_stable/openSUSE_11.4/x86_64/novell-ifolder-enterprise-plugins-188.8.131.5292.1-6.3.x86_64.rpm
Update: Reader Mike informs me that these links above are no longer in service. In the interim, here’s an alternate download location:
rpm -Uvh http://yourlinuxguy.com/wp-content/uploads/2012/03/ifolder3-enterprise-184.108.40.206.11091.1-6.2.x86_64.rpm rpm -Uvh http://yourlinuxguy.com/wp-content/uploads/2012/03/novell-ifolder-enterprise-plugins-220.127.116.1192.1-6.3.x86_64.rpm
And run all 3 configuration scripts (remember, see my older post for reference and detail, and please note I use an alternative simias datastore location of
simias-server-setup ifolder-admin-setup ifolder-web-setup
A note about the next step: If you just stopped here, you’d be able to pull up the /admin page, but not log in; you’d get a red message saying that your password doesn’t match or whatever. I see this error quite commonly out there… So let’s change the FlaimWrapper softlink pointer to an existing location:
rm /usr/lib64/simias/web/bin/FlaimWrapper.so ln -s /usr/lib64/libFlaimWrapper.so.0 /usr/lib64/simias/web/bin/FlaimWrapper.so
Let’s make sure Apache2 comes up at each boot:
chkconfig apache2 on
And lastly, restart stuff:
rcSuSEfirewall2 restart;rcapache2 stop; rcapache2 start
And that should do it! Log in at /admin, configure some users, etc., etc., etc. I’m guessing you are here because you know already how to *use* iFolder, just got stuck installing and configuring it, so I’ll not go into any usage detail.
By the way, the NoFolder.com page has some good troubleshooting tips, but if you follow these steps accurately, and you use the SAME hostname throughout the configuration, you should be fine.
See, it’s not that bad. And it’s totally worth it. Enjoy!
Update, 20130324: Please see PART 2 of this post and story, after reading through the comments below to see how we arrived there….