{"id":130,"date":"2007-07-31T08:04:07","date_gmt":"2007-07-31T07:04:07","guid":{"rendered":"https:\/\/www.purple-penguin.org\/blog\/?p=130"},"modified":"2007-07-31T08:06:23","modified_gmt":"2007-07-31T07:06:23","slug":"howto-install-tomcat-5-on-centos-4","status":"publish","type":"post","link":"https:\/\/www.purple-penguin.org\/blog\/2007\/07\/31\/howto-install-tomcat-5-on-centos-4\/","title":{"rendered":"Howto install Tomcat 5 on CentOS 4"},"content":{"rendered":"

Howto install tomcat 5 on CentOS 4<\/strong><\/p>\n

This has been taken from serral online instruction and combinded with pritical IT Works \ud83d\ude42<\/strong><\/p>\n

This howto is assuming that you have a working, minimal installation of CentOS. I will repeat that because if not properly understood it will cause you lots of headaches later. A MINIMAL<\/strong> installation of CentOS. This means that when you are doing your installation, you should scroll to the bottom and check that pretty little box that says “minimal” so that only the bare essentials are installed. We will let yum take care of the rest.<\/p>\n

title=”Setting_up_jpackage.org_Enviroment” name=”Setting_up_jpackage.org_Enviroment”><\/p>\n

Setting up jpackage.org Enviroment<\/h2>\n

Steps<\/p>\n

   * Install 'jpackage-utils' (if not already in your system)\r\n\r\n   * Install at least one JDK\r\n\r\n   * Subscribe your system to a repository and install the package you want (dependencies will be brought in automatically)<\/pre>\n
jpackage-utils<\/p>\n
Most Linux distributions now ship with a jpackage-utils RPM installed. If yours doesn’t, you can obtain this RPM using Repoview or the JPackage repository browser. YOU MUST HAVE A ‘jpackage-utils’ RPM INSTALLED ON YOUR SYSTEM BEFORE INSTALLING A JDK. JDK<\/p>\n
Due to different licensing conditions, we only provide nosrc RPMS for the JDKs, or a ‘-compat’ RPM for the Sun JDKs. BEA and IBM provide us with the specifications for their JDKs RPMs, which are JPP compliant. We make them available as nosrc RPMs. The RPM on the Sun web site requires that a corresponding ‘-compat’ RPM from JPackage be installed to become compatible, or alternatively one can also rebuild a nosrc RPM for it.<\/p>\n
YOU MUST HAVE AT LEAST ONE JDK INSTALLED BEFORE INSTALLING ANY OTHER JAVA PACKAGE.<\/p>\n
ATTENTION: Please install (at least) _both_ the java-<version>-<provider> _and_ the java-<version>-<provider>-devel for a complete SDK.<\/p>\n
(the ‘java-<version>-sun-compat’ provides everything for the Sun JDK case, so there is no -devel). Notes<\/p>\n
If the -compat RPM for the latest Sun release is not yet available, you can request an update via the mailing list.<\/p>\n
If the current Sun JDK is not yet packaged, you can find archived releases here.<\/p>\n
For information on building one of the nosrc JDK RPMs from either Sun, BEA or IBM, please see Rebuilding nosrc RPMs Installing the Sun JDK using the ‘-compat’ method<\/p>\n
This step is only necessary if you want to avoid rebuilding the nosrc JDK RPM. Please note that rebuilding the nosrc RPM is the preferred method of obtaining a JPackage JDK.<\/p>\n
repo setup<\/strong><\/p>\n
The first thing that we have to do is set up out yum repositories so that we can find the packages to be downloaded.  The jpackage repository makes this very easy and we will install this one first.  All of the repositories are located in the \/etc\/yum.repos.d directory.  To install the repository for jpackage, which contains all of the java goodies, simply:<\/p>\n\n\n
cd \/etc\/yum.repos.d<\/strong>wget -P \/etc\/yum.repos.d http:\/\/jpackage.org\/jpackage.repo<\/a><\/strong><\/td>\n<\/tr>\n<\/table>\n
Edit the jpackage.repo file you retrieved and enable the repositories appropriate to your distribution.  In the case of CentOS I set
\nenabled=1<\/em> on the jpackage-rhel<\/em> sections.<\/p>\n
The JPackage RPMs are digitally signed using a GPG key, import their key into your RPM keyring<\/p>\n\n\n
rpm –import http:\/\/jpackage.org\/jpackage.asc<\/a><\/strong><\/td>\n<\/tr>\n<\/table>\n
Before adding new stuff make shoure your installed rpms are up to date<\/p>\n\n\n
yum update<\/strong><\/td>\n<\/tr>\n<\/table>\n
 Get the jdk<\/h2>\n
Next, since Sun does not make available its jdk via yum, you have to go to the sun site and download it.  If you point your browser over to:<\/p>\n
http:\/\/java.sun.com\/javase\/downloads\/index.jsp<\/a><\/strong><\/p>\n
  1.<\/pre>\n
     Get the Sun JDK 5.0 from:<\/pre>\n
     http:\/\/java.sun.com\/javase\/downloads\/index.jsp<\/a><\/pre>\n
     by choosing the \"JDK 5.0 Update N\" \"Download\" button, and then choosing \"RPM in self-extracting file\" for Linux on the page that displays after pressing the button.\r\n\r\n     Important: Do NOT install the \"Linux x64\" version of the SDK.<\/pre>\n
     If you prefer the older Java 1.4.2 SDK, get it from:<\/pre>\n
     http:\/\/java.sun.com\/j2se\/1.4.2\/download.html<\/a><\/pre>\n
     by choosing the \"Download J2SE SDK\" link and from there the \"RPM in self-extracting file\" for Linux.<\/pre>\n
You can download the one you see fit.  I downloaded JDK 5.0 Update 12, which at the time of this howto was the current one.  When you see the Sun download page, accept the agreement and pick the “Linux RPM in self-extracting file”  (the one that ends in rpm.bin).<\/p>\n
When your Sun JDK Linux RPM self-extracting file<\/strong> finally arrives you need to execute it, since it is a shell script. It contains the license agreement and the compressed RPM package with Sun JDK. It will ask you if you agree to the long license. Say yes, then it will uncompress the RPM with JDK, and then it will install it. To run it do:<\/p>\n\n\n
chmod 755 jdk-1_5_0_12-linux-i586-rpm.bin
\n.\/jdk-1_5_0_12-linux-i586-rpm.bin<\/strong><\/td>\n<\/tr>\n<\/table>\n
Unfortunately, the Sun RPM package puts files in different locations than the ones required by CentOS. After running the script you will see a new directory \/usr\/java\/jdk1.5.0_07 with JDK files. Note that the actual RPM is left in the directory where you ran the Sun\u00e2\u20ac\u2122s jdk-1_5_0_07-linux-i586-rpm.bin script, however, you do not need to process the RPM, since script already did it.<\/p>\n
You may, however, use the RPM package if you want to install the JDK on another machine or if you erased the JDK at some point with a the RPM\u00e2\u20ac\u2122s rpm -e jdk-1.5.0_07-fcs command. Now, we are ready to install the SUN JDK compatibility RPM from the JPackage.org<\/p>\n
 <\/p>\n
Install compatibility RPM<\/h2>\n
Install java-1.4.2-sun-compat or java-1.5.0-sun-compat, download it your self as the yum install tends to pick up the wrong version.<\/p>\n
Download and install the appropriate -compat RPM from JPackage at:<\/p>\n
     ftp:\/\/jpackage.hmdc.harvard.edu\/JPackage\/1.7\/generic\/RPMS.non-free\/<\/a><\/strong><\/pre>\n
Make sure to match the version of the -compat package to the SDK you’ve installed in the first step. The -compat RPM requires that the RPM self-extracting file from Sun be used in the previous step, not the plain (non-RPM) one.<\/p>\n
 For instance, for a Sun SDK 1.5.0_12 you should get:<\/pre>\n
 ftp:\/\/jpackage.hmdc.harvard.edu\/JPackage\/1.7\/generic\/RPMS.non-free\/java-1.5.0-sun-compat-1.5.0.12-1jpp.i586.rpm<\/a><\/pre>\n
 and for a Sun SDK 1.4.2_12 you should use:<\/pre>\n
 ftp:\/\/jpackage.hmdc.harvard.edu\/JPackage\/1.7\/generic\/RPMS.non-free\/java-1.4.2-sun-compat-1.4.2.12-1jpp.i586.rpm<\/a><\/pre>\n\n\n
rpm -ivh java-1.5.0-sun-compat-1.5.0.12-1jpp.i586.rpm <\/strong><\/td>\n<\/tr>\n<\/table>\n
This will create a bunch of links in the \/etc\/alternatives and \/usr\/lib\/jvm directories and others to the \/usr\/java\/jdk1.5.0_07 directory where the Sun JDK distribution resides. To check which files were affected do:<\/p>\n\n\n
rpm -q -l java-1.5.0-sun-compat<\/strong><\/td>\n<\/tr>\n<\/table>\n
Check if the Sun JDK is really a default by doing:<\/p>\n\n\n
java -version<\/strong><\/td>\n<\/tr>\n<\/table>\n
If you get:<\/p>\n
java version “1.4.2”
\ngij (GNU libgcj) version 4.1.1 20060525 (Red Hat 4.1.1-1)<\/em><\/p>\n
Copyright (C) 2006 Free Software Foundation, Inc.
\nThis is free software; see the source for copying conditions. There is NO
\nwarranty; not even for MERCHANTABILITY or FITNESS FOR A
\nPARTICULAR PURPOSE.<\/em><\/p>\n
(or similar) then something did NOT<\/strong> work. If you get:<\/p>\n
java version “1.5.0_07″Java(TM) 2 Runtime Environment,
\nStandard Edition (build 1.5.0_07-b03)
\nJava HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode, sharing)<\/em><\/p>\n
then the Sun JDK is your default. You can use alternatives to check (or change) the default JDK by:<\/p>\n\n\n
alternatives –config java<\/strong><\/td>\n<\/tr>\n<\/table>\n
Please read the man page for alternatives:<\/p>\n\n\n
man alternatives<\/strong><\/td>\n<\/tr>\n<\/table>\n
It should show something like:<\/p>\n
There are 2 programs which provide \u00e2\u20ac\u2122java\u00e2\u20ac\u2122.<\/em><\/p>\n
Selection Command<\/em>
\n———————————————–<\/em>
\n1 \/usr\/lib\/jvm\/jre-1.4.2-gcj\/bin\/java<\/em>
\n*+ 2 \/usr\/lib\/jvm\/jre-1.5.0-sun\/bin\/java<\/em><\/p>\n

\nEnter to keep the current selection[+], or type selection number:<\/em>
\nHit [Enter] key if you want Sun JDK to be a default, or enter 1 if you want to
\nchange back to GNU Java.<\/p>\n
Now, there will be times, when you want to get rid of Sun JDK and its entries for alternatives. DO NOT TOUCH THESE LINKS WITH YOUR BARE HANDS<\/strong>. Use yum to uninstall the JPackage Java compatibility package first and then erase the Sun JDK with rpm:<\/p>\n\n\n
yum erase java-1.5.0-sun-compat
\nrpm -e jdk-1.5.0_07-fcs<\/strong><\/td>\n<\/tr>\n<\/table>\n
Sometimes yum breaks. A popular situation is when you used rpm to install some package (or the package was installed with an install<\/em> (older package is kept) rather than an update<\/em> (older package is removed). In this case, yum gets confused with dependencies and complains, and it does not want to install a package. To see if this is a case (as it was when installing all of this), list all the installed rpm packages for some package name with a command:<\/p>\n\n\n
bgcolor = “#CCCCCC” rpm -qa | grep “java”<\/strong><\/td>\n<\/tr>\n<\/table>\n
for example. If you see two versions of the same rpm, just erase the old one. Use the<\/p>\n\n\n
rpm -e full_package_name_with_version<\/strong><\/td>\n<\/tr>\n<\/table>\n
(but skip the .rpm) and then try yum update or yum install again. I am telling you this, since we will definitely have more javas<\/em> and compats<\/em> coming, and the mess happens. For example (at this time a hypothetical one), if you got stuck with two compat<\/em> packages when updates to the JDK were processed:<\/p>\n
rpm -qa | grep “java-1.5.0-sun-compat”<\/strong><\/sub><\/p>\n
java-1.5.0-sun-compat-1.5.0.07-1jppjava-1.5.0-sun-compat-1.5.0.08-1jpp<\/em><\/p>\n
remove the older package as:<\/p>\n\n\n
yum erase java-1.5.0-sun-compat-1.5.0.07-1jpp<\/strong><\/td>\n<\/tr>\n<\/table>\n
or, if still no go<\/em>:<\/p>\n\n\n
rpm -e java-1.5.0-sun-compat-1.5.0.07-1jpp<\/strong><\/td>\n<\/tr>\n<\/table>\n
and try again.<\/p>\n
 <\/p>\n
Set Enviroment varibles<\/h2>\n
So… JAVA_HOME.  In your shell, type:<\/p>\n\n\n
JAVA_HOME=\/usr\/lib\/jvm\/java
\nexport JAVA_HOME<\/strong><\/td>\n<\/tr>\n<\/table>\n
or if you are C-shellish:<\/p>\n\n\n
setenv JAVA_HOME \/usr\/lib\/jvm\/java<\/strong><\/td>\n<\/tr>\n<\/table>\n
 <\/p>\n
BIG WORK AROUND FOR USING YUM TO INSTALL<\/h2>\n\n\n
yum install xml-commons <\/strong><\/td>\n<\/tr>\n<\/table>\n
download  the xml-commons-apis rpm from jpackage.org Install by hand using<\/p>\n\n\n
rpm -ivh xml-commons-apis rpm <\/strong><\/td>\n<\/tr>\n<\/table>\n
For some reason yum was bugging out and not recognizing the xml-commons-apis.<\/p>\n
(I guess this may be a case of screwy obsoletes and provides with some of the jpp packages)<\/p>\n
 <\/p>\n
Install tomcat5 and apache<\/h2>\n\n\n
yum install tomcat5 tomcat5-webapps tomcat5-admin-webapps<\/strong><\/td>\n<\/tr>\n<\/table>\n
We will use redhats standard apache2 with mod_jk to talk to Tomcat, so first we install:<\/p>\n\n\n
yum install httpd mod_jk-ap20<\/strong><\/td>\n<\/tr>\n<\/table>\n
 <\/p>\n
Testing the install<\/h2>\n
Check to make sure the default tomcat users are located in \/etc\/tomcat5\/tomcat-users.xml<\/em>.<\/p>\n
[root@centos tomcat5]# cat \/etc\/tomcat5\/tomcat-users.xml
\n<?xml version=\u00e2\u20ac\u21221.0\u00e2\u20ac\u2122 encoding=\u00e2\u20ac\u2122utf-8\u00e2\u20ac\u2122?>
\n<tomcat-users>
\n<role rolename=”tomcat”\/>
\n<role rolename=”role1″\/>
\n<user username=”tomcat” password=”tomcat” roles=”tomcat”\/>
\n<user username=”role1″ password=”tomcat” roles=”role1″\/>
\n<user username=”both” password=”tomcat” roles=”tomcat,role1″\/>
\n<\/tomcat-users>
\n[root@centos tomcat5]#
\nTest tomcat5:<\/p>\n\n\n
\/etc\/rc.d\/init.d\/tomcat5 start<\/strong><\/td>\n<\/tr>\n<\/table>\n
If all is well, you can see the tomcat welcome page on 8080.<\/p>\n
Test apache:<\/p>\n\n\n
\/etc\/rc.d\/init.d\/httpd start<\/strong><\/td>\n<\/tr>\n<\/table>\n
If all is well, you can see the apache welcome page on 80.<\/p>\n
 <\/p>\n
configure apache to work with mod_jk<\/h2>\n
Now we will configure apache to work with mod_jk to grab everything on port 80.<\/p>\n
make enviromet veribles persitant<\/p>\n
edit \/etc\/profile<\/p>\n\n\n
cd \/etc<\/strong>vi profile<\/strong><\/td>\n<\/tr>\n<\/table>\n
add lines<\/p>\n
#Tomcat set up add by Joe 27 07 07\r\n\r\nJAVA_HOME=\/usr\/lib\/jvm\/java\r\n\r\nexport JAVA_HOME\r\n\r\nCATALINA_HOME=\/usr\/share\/tomcat5\r\n\r\nexport CATALINA_HOME<\/pre>\n
 <\/p>\n
Edit tomcat configureation<\/h3>\n
Edit the workers.properties file in \/usr\/share\/tomcat5\/conf\/workers.properties<\/p>\n
Update the entries for workers.tomcat_home and workers.java_home<\/p>\n
workers.tomcat_home=\/usr\/share\/tomcat5\r\n\r\nworkers.java_home=\/usr\/lib\/jvm\/java<\/pre>\n
Change the worker.list from ajp12, ajp13 to just ajp13, or ajp13, inprocess if you want JNI connector. While running the JVM inside the web server gives the best performance, it lacks the stability of the out of process mode.<\/p>\n
workers.list=ajp13<\/pre>\n
Comment out the worker.ajp12 entries if you want, it is not necessary.<\/p>\n
Change worker.ajp13.host from localhost to your fully qualified domain name or IP address<\/p>\n
 worker.ajp13.host=[fully qualified domain name]<\/pre>\n
If you want to cache your connections, uncomment worker.ajp13.cachesize and add a value.<\/p>\n
worker.ajp13.cachesize=20<\/pre>\n
Change worker.loadbalancer.balanced_workers from ajp12, ajp13 to just ajp13.<\/p>\n
worker.loadbalancer.balanced_workers=ajp13<\/pre>\n
If all you need is a simple, straight-forward out of process configuration without load balancing, you can use this as your complete workers.properties file. Again remember to set the host with your fully qualified domain name or IP address<\/p>\n
worker.list=ajp13\r\n\r\nworker.ajp13.type=ajp13\r\n\r\nworker.ajp13.host=[fully qualified domain name]\r\n\r\nworker.ajp13.port=8009<\/pre>\n
Edit the Tomcat server.xml file located in $CATALINA_HOME\/conf\/<\/p>\n
it should be \/usr\/share\/tomcat5\/conf\/server.xml<\/p>\n
Immediately below the entry <Server port=”8005″ shutdown=”SHUTDOWN”> add:<\/p>\n
<Listener className=\"org.apache.jk.config.ApacheConfig\" modJk=\"\/usr\/lib\/httpd\/modules\/mod_jk.so\" workersConfig=\"\/usr\/share\/tomcat5\/conf\/workers.properties\" jkLog=\"\/var\/log\/tomcat5\/logs\/mod_jk.log\" jkDebug=\"info\" \/><\/pre>\n
Find the entry <Host name=”localhost” appBase=”webapps” unpackWARs=”true” autoDeploy=”true” xmlValidation=”false” xmlNamespaceAware=”false”> and change localhost to your fully qualified domain name or IP address.<\/p>\n
<Host name=\"[fully qualified domain name]\" appBase=\"webapps\" unpackWARs=\"true\" autoDeploy=\"true\" xmlValidation=\"false\" xmlNamespaceAware=\"false\"><\/pre>\n
Immidiately following that line add:<\/p>\n
<Listener className=\"org.apache.jk.config.ApacheConfig\" append=\"true\" jkWorker=\"ajp13\" \/><\/pre>\n
Restart Tomcat and verify that the dirctory auto is created and the files mod_jk.conf is created in \/usr\/share\/tomcat5\/conf\/<\/p>\n
By configuring Tomcat to create and recreate the mod_jk.conf on startup, it will automatically add a JkMount for any new webapps you deploy.<\/p>\n
 <\/p>\n
Edit apache configuration<\/h3>\n
Edit \/etc\/httpd\/conf\/httpd.conf and after the last LoadModule entry add an Include for the mod_jk.conf:<\/p>\n
Include \"\/usr\/share\/tomcat5\/conf\/auto\/mod_jk.conf\"<\/pre>\n
Restart Apache<\/p>\n
Browse to http:\/\/localhost\/jsp-examples\/<\/a> or any other webapp you have installed in Tomcat and Apache should send it to Tomcat.<\/p>\n
 <\/p>\n
Make tomcat and apache start at bootup<\/h2>\n
chkconfig –level 234 httpd on<\/strong><\/p>\n
chkconfig –level 234 tomcat5 on<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"
Howto install tomcat 5 on CentOS 4 This has been taken from serral online instruction and combinded with pritical IT Works \ud83d\ude42 This howto is assuming that you have a working, minimal installation of CentOS. I will repeat that because if not properly understood it will cause you lots of headaches later. A MINIMAL installation […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[7,3],"tags":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p4T97-26","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":129,"url":"https:\/\/www.purple-penguin.org\/blog\/2007\/07\/11\/our-first-vip\/","url_meta":{"origin":130,"position":0},"title":"Our First V.I.P.","date":"Wednesday, 11 July 2007","format":false,"excerpt":"Yes folks after many months of hard work at the Hippy Factory (other wise known as the place where i work). We have are fist V.I.P thats Virtual In-house Penguin. Since the start of the year we (in an office IT team) have been trailing and experimenting with visualization using\u2026","rel":"","context":"In "Dyslexic Discourse"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":142,"url":"https:\/\/www.purple-penguin.org\/blog\/2008\/02\/15\/new-toy-olpc-xo\/","url_meta":{"origin":130,"position":1},"title":"New Toy (OLPC XO)","date":"Friday, 15 February 2008","format":false,"excerpt":"So played with the green machine witch looks like it will be called George as its two cute, note i resisted the erge to go tooooooo, but it is. Had some trouble inishaly\u00c2\u00a0 getting it on to a wpa2 net work looks like it ones the pass key in hex\u2026","rel":"","context":"In "Dyslexic Discourse"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":132,"url":"https:\/\/www.purple-penguin.org\/blog\/2007\/08\/23\/so-lime-wire-writen-in-norfolk\/","url_meta":{"origin":130,"position":2},"title":"So Lime wire writen in Norfolk ?","date":"Thursday, 23 August 2007","format":false,"excerpt":"Just upgraded my limewire pro installation witch is a pice of software i have used for meny years. How ever some distebing things on the horizan thay now no longer ship a linux rpm only debts ?. So i had to down load the other linux witch is basical a\u2026","rel":"","context":"In "Dyslexic Discourse"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":44,"url":"https:\/\/www.purple-penguin.org\/blog\/2005\/11\/27\/last-post-before-we-leave\/","url_meta":{"origin":130,"position":3},"title":"Last post before we leave","date":"Sunday, 27 November 2005","format":false,"excerpt":"We are packed and ready - off tomorrow evening. Joe still claims not to know where we are going so hopefully still a surprise. Of course he's pacing about driving me crazy. So it goes. We managed to fit everything into our bags. With minimal sitting on the bag to\u2026","rel":"","context":"In "Travel"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":161,"url":"https:\/\/www.purple-penguin.org\/blog\/2008\/06\/22\/onwards\/","url_meta":{"origin":130,"position":4},"title":"Onwards","date":"Sunday, 22 June 2008","format":false,"excerpt":"Last day in Jamaica and we're off to Trinidad. Being collected at 10.30 and the flight is at 2pm. We're flying off with many of the Caribbean delegates who were at the conference as we're stopping on another couple of islands along the way to Trinidad. So I get to\u2026","rel":"","context":"In "Travel"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":420,"url":"https:\/\/www.purple-penguin.org\/blog\/2010\/09\/01\/more-meetings-in-ghana\/","url_meta":{"origin":130,"position":5},"title":"More meetings in Ghana","date":"Wednesday, 1 September 2010","format":false,"excerpt":"The conference happened and everything seemed to go well, even if it did run late. We had some excursions - one to Cape Coast Castle which was a little depressing but very interesting. We got a guided tour of the castle (more of a fort than a castle) with the\u2026","rel":"","context":"In "Frog Blog"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.purple-penguin.org\/blog\/wp-json\/wp\/v2\/posts\/130"}],"collection":[{"href":"https:\/\/www.purple-penguin.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.purple-penguin.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.purple-penguin.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.purple-penguin.org\/blog\/wp-json\/wp\/v2\/comments?post=130"}],"version-history":[{"count":0,"href":"https:\/\/www.purple-penguin.org\/blog\/wp-json\/wp\/v2\/posts\/130\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.purple-penguin.org\/blog\/wp-json\/wp\/v2\/media?parent=130"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.purple-penguin.org\/blog\/wp-json\/wp\/v2\/categories?post=130"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.purple-penguin.org\/blog\/wp-json\/wp\/v2\/tags?post=130"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}