Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Building a static Manila site in 2019 #141
I have Manila running in the OPML Editor.
I tried writing a script to do the static site build, but I don't have good example code. It would be ideal to just run a script and have a folder of static files appear.
I also tried to get the Admin site to show up. The web server is running on port 5337. I tried this URL:
But none produce the admin website.
It's been really interesting, just put in about an hour, and got pretty far.
I've uploaded xmlRpc.root for anyone to have a go at this.
I am running a server which has Manila serving websites (I used one of the websites to teach a class this fall). I was able to load the xmlRpc.root file into Frontier. But when I tried to change the site address to my server, I got an error.
I would really like to solve the static site conversion. I have many photo sites on this server and would like to move them to a static server so if this server dies, I can still have those sites.
I got it to come up somewhat:
with this error:
[Macro error: Can’t call the script because the name “dwWidgetsSuite” hasn’t been defined.]
I am running on a 2.66 GHz Quad-core Intel Xenon with 8 Gb of ram. I have switched the hard drives to SSD in the hopes the server will last longer. It's running Mac OSX 10.6.8 which is the last OS that Frontier will run in.
I posted a note on the Frontier-user list, in the thread you started @kochwilkes in 2014.
I tried, per Ted's clue, to go to this URL.
And the server responded. But none the links across the top of the page work, and I still have no idea how to get to the Manila app page.
Here's a screen shot.
Made progress today. I followed the general instructions in a manual "Manila User's Guide" that I think was written by Brent Simmons. I went to a course he ran in March 24, 2004.
Click on "Static Files"
Check this box to enable static rendering.
File System rendering allows rendered pages to be written to disk or a shared volume.
FTP rendering allows rendered pages to be sent to an FTP server.
Then in the site's Prefs section is a link called Rendering. This page allows you to say "Yes" to enable static rendering. Then you go to the site's Admin link and there is a button to render the whole site. The top item is: Static Rendering: click the Render this Site button. Shows the URL of your static site. Brings up a confirmation page. Click to Render. Brent's comment was that the page will not come back until the whole site is rendered.
I was able to render a very simple 5 page site and get it to show up statically. However, I had to play around with the two settings of the folder to download into and the URL of the static site.
What I am worried about now is how the links will render. When I mounted Dave's xmlrpc root, if you look at the home page, the links in the nav bar are not correct.
notice Home is "course.wilkes.edu" and Spec is "course.wilkes.edu/spec" It's leaving out the "xmlrpc" in each link. I don't know what will happen if I try to render it with the links that way.
@kochwilkes -- I was able to view the xmlRpc site on your server.
I would consider it a big success if I got that far, here. Congratulations. ;-)
I have another approach in mind. I might write a script outside of Manila that renders the pages with their content but not with the original template.
I did something like that for a JS-based site I did a few years back. The code that rendered the site broke, and rather than trying to resurrect it, I just wrote a one-off script to render the site in a simple easier-to-read way. It ended up taking a lot less time than rebooting its CMS would have taken.