Recent Posts

Subscribe to Recent Posts 399 posts found

posted 6 days ago
weilina 1 post

Forum: Heterotic Beast – Topic: Can I view the source text for other people's posts?

Instead of simulating the edit function where content is shown in place, I would preferably show this in a popup. That way users couldn’t mix up the functionality and get confused. You can also add some information like the Format to the popup.

 
posted 5 months ago
distler 100 posts

Forum: Instiki – Topic: Dreamhost installation issues

The whole point of rbenv (or rvm) is to set up your paths correctly so that, when you type ruby, you get the desired executable. I don’t know anything about Dreamhost, and didn’t really read the rbenv installation instructions that you followed, but evidently they didn’t quite achieve the desired result.

 
posted 6 months ago
joelwatsonfish 7 posts

Forum: Instiki – Topic: Dreamhost installation issues

Since I haven’t tried installing Instiki, I don’t have have an Instiki directory, however from my home directory, the following

$ ruby --version

yields

ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

However, from /home/username/.rbenv/versions/2.2.0/bin/ the following

$ ruby --version

yields

ruby 2.2.0p0 (2014-12-25 revision 49005) [x86_64-linux]

 
posted 6 months ago
distler 100 posts

Forum: Instiki – Topic: Dreamhost installation issues

OK. So let’s assume you’ve gotten that far correctly. cd to your Instiki directory and try

ruby --version
ruby bundle install

The first command should return the version of Ruby you’re using (hopefully 2.2). The second should run the included version of Bundler (as opposed to the one you installed via rbenv).

 
posted 6 months ago
joelwatsonfish 7 posts

Forum: Instiki – Topic: Dreamhost installation issues

I tried following the instructions to install rbenv and got stuck at the line

$ bundle install

as it gives the error (in red)

Could not locate Gemfile or .bundle/ directory

I found a Gemfile in a couple of subdirectories of ~/.rbenv/ but it’s not in my ~/websitename/ directory, which is where the script was supposed to be run from. I posted the same question on the forum/comments section there, but it looks like it’s been a year since the guy responded last, so I’m not sure if I’ll get a response. Any thoughts?

[EDIT:] I should add that I was trying to install Ruby 2.2.0

 
posted 6 months ago
distler 100 posts

Forum: Instiki – Topic: Dreamhost installation issues

rbenv is certainly the preferred way to get multi-version Ruby support. So I would go with that, and target Ruby 2.1 or 2.2.

 
posted 6 months ago
joelwatsonfish 7 posts

Forum: Instiki – Topic: Dreamhost installation issues

There aren’t any options that are completely obvious to me (e.g. one click/command install/update etc.). Google searching a bit turns up the following.

  1. Building ruby from source: how to

  2. Another build ruby from source: how to

  3. Installing via RVM how to

  4. Installing via rbenv how to

I think to install RVM I need to run a VPS which increases my monthly costs significantly.

 
posted 6 months ago
distler 100 posts

Forum: Instiki – Topic: Dreamhost installation issues

I think it would be better to start with a more recent version (≥1.9.3) of Ruby.

What are your options for that?

 
posted 6 months ago
joelwatsonfish 7 posts

Forum: Instiki – Topic: Dreamhost installation issues

Okay, I have a fresh account to start with. I set up passenger, backed up all files and folders in ~/BACKUP/ and I’ve done nothing else with the clean account.

$ ruby -v

ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

$ rails -v

Rails 3.0.3

$ bundler -v

-bash: bundler: command not found

What should my next step be? Update Ruby, or follow the hosted services instructions?

 
posted 6 months ago
distler 100 posts

Forum: Instiki – Topic: Dreamhost installation issues

“… although if I want to run Ruby 2.1 or 2.2 I think I’m going to have to build it from source, which I don’t know how to do yet.”

Build Ruby from source? I don’t think you want to do that (unless you really have to). It would be better to have a known-working version of Ruby, so that we don’t have to debug possible problems in your Ruby installation as well (well, OK, technically we are already doing that, since your versions of Ruby and Rubgems aren’t totally compatible).

Instiki should work fine with Ruby 1.9.3, if that’s really the most recent version you have access to. We’d just need to modify a line in config/boot.rb to take care your problem with Rubygems.

 
posted 6 months ago
joelwatsonfish 7 posts

Forum: Instiki – Topic: Dreamhost installation issues

I edited the Gemfile because following the instiki Hosted Services instructions caused an error, and google searching the error for a while turned up the suggestion to make the modification the the Gemfile. It seemed to make progress, but maybe not.

Ruby 1.8.7 seems to be the default version on Dreamhost, and so I think because you wrote

Hmmm. I’m afraid that Maruku no longer supports Ruby 1.8.x (which is EOL). I think you need at least Ruby 1.9.3.

they upgraded me from 1.8.7 to 1.9.3, but not to 2.x (at least, I’m assuming that’s an upgrade). Later today I’ll try to uninstall everything, and start from scratch, although if I want to run Ruby 2.1 or 2.2 I think I’m going to have to build it from source, which I don’t know how to do yet. I’m used to installing via yum/apt-get, so if you could point me to a link to build from source, that would be helpful. If not, I’ll figure try to figure it out on my own, and post the output here.

Thank you very much for your help.

 
posted 6 months ago
distler 100 posts

Forum: Instiki – Topic: Dreamhost installation issues

I’m sorry. I am quite confused as to your configuration.

In your first message, you indicated that

  1. You had willy-nilly modified your Gemfile. Did you revert that modification before trying again?
  2. Your Ruby version was 1.8.7.

Now you tell me that progress was made by downgrading your Ruby version to “<2.0”?!?

That said, I sorta understand the error about Gem.source_index. The version(s) of Rubygems which came with Ruby < 2.0 had that method. Later versions do not. So there’s a monkey-patch in config/boot.rb to supply the missing method for Ruby ≥ 2.0.

Evidently, you have the odd combination of an old (1.9.3) version or Ruby and a recent version of Rubygems.

Maybe you should start again with

  • an unmodified installation of Instiki.
  • a recent version of Ruby: I recommend 2.1 or 2.2.

Run ruby bundle install and see what happens. If that fails, post your errors here. If it succeeds, but then ./instiki fails, post your Gemfile.lock, so we can see what got installed.

 
posted 6 months ago
joelwatsonfish 7 posts

edited 6 months ago

Forum: Instiki – Topic: Dreamhost installation issues

Thanks for the help. I emailed the the folks at Dreamhost (who seem quite helpful), and they sent me this back.

I switched his ruby version to < 2.0 (the error he was getting was an issue with bundler and that ruby version). I then replaced the word string with /w as dictacted in the forum he linked us to and ran d a bundle install with the new ruby version. Now his site is getting this:

App 24716 stdout:   Status: 500 Internal Server Error
App 24716 stdout:   uninitialized constant
Rack::MethodOverride::REQUEST_METHOD
App 24716 stdout:
/home/myusername/mydomainname.org/vendor/rails/activesupport/lib/active_support/dependencies.rb:131:in
`const_missing'

They suggested I bring this error back to the boards here to see if you knew what was going on. When I run

$ ./instiki --daemon

I get the following:

/home/myusername/mydomainname.org/vendor/rails/railties/lib/rails/gem_dependency.rb:21:in `add_frozen_gem_path': undefined method `source_index' for Gem:Module (NoMethodError)
	from /home/myusername/mydomainname.org/config/boot.rb:62:in `load_initializer'
	from /home/myusername/mydomainname.org/config/boot.rb:126:in `run'
	from /home/myusername/mydomainname.org/config/boot.rb:26:in `boot!'
	from /home/myusername/mydomainname.org/config/boot.rb:139:in `<top (required)>'
	from /home/myusername/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /home/myusername/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /home/myusername/mydomainname.org/script/server:3:in `<top (required)>'
	from ./instiki:6:in `load'
	from ./instiki:6:in `<main>'

And again if it’s helpful I have the following.

$ ruby -v

ruby 1.9.3p551 (2014-11-13 revision 48407) [x86_64-linux]

$ rails -v

Rails 4.2.5

$ bundler -v

Bundler version 1.10.6

Again, any help would be appreciated.

 
posted 6 months ago
distler 100 posts

Forum: Instiki – Topic: Dreamhost installation issues

On the other hand, if you’re just using ASCII characters, you can replace [[:word:]] with \w on lines 263 and 267 of vendor/bundle/ruby/1.8/bundler/gems/maruku-aa33367fa89e/lib/maruku/input/parse_span.rb and not run into any problems.

 
posted 6 months ago
distler 100 posts

Forum: Instiki – Topic: Dreamhost installation issues

Hmmm. I’m afraid that Maruku no longer supports Ruby 1.8.x (which is EOL). I think you need at least Ruby 1.9.3.

I guess I should update the documentation accordingly …

 
posted 6 months ago
joelwatsonfish 7 posts

Forum: Instiki – Topic: Dreamhost installation issues

I’m not sure if this is the right place to post this, so my apologies if not.

I’m trying to install instiki on a new Dreamhost account. Since I don’t have super-user access, I can’t follow the usual instructions, and instead tried to follow the hosted services instructions, but I’m having some difficulties.

The first issue is that if I follow the instructions and try

$ ./instiki

I get an error message containing the line

‘ruby_20’ is not a valid platform

I edited the Gemfile replacing the string

[:ruby_20, :ruby_21, :ruby_22]

with the string

[:ruby]

Then when I run

$ ./instiki

I get the following:

NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.
Gem.source_index called from ./config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21.
=> Booting Thin
=> Rails 2.3.18 application starting on http://0.0.0.0:2500
/home/myusername/mydomainname.org/vendor/rails/activesupport/lib/active_support/dependencies.rb:184:in `require': /home/myusername/mydomainname.org/vendor/bundle/ruby/1.8/bundler/gems/maruku-aa33367fa89e/lib/maruku/input/parse_span.rb:263: invalid regular expression; [:word:] is not a character class: /[[:word:]]/ (SyntaxError)
/home/myusername/mydomainname.org/vendor/bundle/ruby/1.8/bundler/gems/maruku-aa33367fa89e/lib/maruku/input/parse_span.rb:267: invalid regular expression; [:word:] is not a character class: /[[:word:]]/
	from /home/myusername/mydomainname.org/vendor/rails/activesupport/lib/active_support/dependencies.rb:184:in `require'
	from /home/myusername/mydomainname.org/vendor/bundle/ruby/1.8/bundler/gems/maruku-aa33367fa89e/lib/maruku.rb:91
	from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:68:in `require'
	from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:68:in `require'
	from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:66:in `each'
	from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:66:in `require'
	from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:55:in `each'
	from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:55:in `require'
	from /usr/lib/ruby/vendor_ruby/bundler.rb:120:in `require'
	from ./config/boot.rb:130:in `load_gems'
	from ./config/../vendor/rails/railties/lib/initializer.rb:164:in `process'
	from ./config/../vendor/rails/railties/lib/initializer.rb:113:in `send'
	from ./config/../vendor/rails/railties/lib/initializer.rb:113:in `run'
	from /home/myusername/mydomainname.org/config/environment.rb:14
	from /home/myusername/mydomainname.org/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in `require'
	from /home/myusername/mydomainname.org/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in `require'
	from /home/myusername/mydomainname.org/vendor/rails/activesupport/lib/active_support/dependencies.rb:547:in `new_constants_in'
	from /home/myusername/mydomainname.org/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in `require'
	from /home/myusername/mydomainname.org/config.ru:3
	from /home/myusername/mydomainname.org/vendor/bundle/ruby/1.8/gems/rack-1.6.4/lib/rack/builder.rb:55:in `instance_eval'
	from /home/myusername/mydomainname.org/vendor/bundle/ruby/1.8/gems/rack-1.6.4/lib/rack/builder.rb:55:in `initialize'
	from /home/myusername/mydomainname.org/config.ru:1:in `new'
	from /home/myusername/mydomainname.org/config.ru:1
	from ./instiki:6:in `eval'
	from ./script/server:86
	from ./instiki:6:in `load'
	from ./instiki:6

If I go to http://mydomainname.org I get the error message:

/home/myusername/mydomainname.org/vendor/bundle/ruby/1.8/bundler/gems/maruku-aa33367fa89e/lib/maruku/input/parse_span.rb:263: invalid regular expression; [:word:] is not a character class: /[[:word:]]/
/home/myusername/mydomainname.org/vendor/bundle/ruby/1.8/bundler/gems/maruku-aa33367fa89e/lib/maruku/input/parse_span.rb:267: invalid regular expression; [:word:] is not a character class: /[[:word:]]/ (SyntaxError)
  /home/myusername/mydomainname.org/vendor/rails/activesupport/lib/active_support/dependencies.rb:184:in `require'
  /home/myusername/mydomainname.org/vendor/rails/activesupport/lib/active_support/dependencies.rb:184:in `require'
  /home/myusername/mydomainname.org/vendor/bundle/ruby/1.8/bundler/gems/maruku-aa33367fa89e/lib/maruku.rb:91
  /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:68:in `require'
  /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:68:in `require'
  /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:66:in `each'
  /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:66:in `require'
  /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:55:in `each'
  /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:55:in `require'
  /usr/lib/ruby/vendor_ruby/bundler.rb:120:in `require'
  ./config/boot.rb:130:in `load_gems'
  ./config/../vendor/rails/railties/lib/initializer.rb:164:in `process'
  ./config/../vendor/rails/railties/lib/initializer.rb:113:in `send'
  ./config/../vendor/rails/railties/lib/initializer.rb:113:in `run'
  ./config/environment.rb:14
  config.ru:3:in `require'
  config.ru:3
  /usr/lib/ruby/vendor_ruby/rack/builder.rb:51:in `instance_eval'
  /usr/lib/ruby/vendor_ruby/rack/builder.rb:51:in `initialize'
  config.ru:1:in `new'
  config.ru:1

I’m not sure what to do at this point. If it helps, I’m using ruby 1.8.7, Rails 3.0.3, bundler 1.10.6

 
posted 10 months ago
distler 100 posts

Forum: Instiki – Topic: HTML/PHP comments?

Short answer: no.

You can try embedding (X)HTML comments in the source, but they get escaped (for a variety of security-related reasons) and hence are “visible” on the page.

Longer answer: Metadata about the page can be placed in a way that does not appear in the rendered output. The syntax is that of email headers (key-value pairs, at the beginning of the page, separated from the main text by a newline):

Author: Me
Subject: My personal musings
Blortnaz: Whatever you want to put here

And now begins the main text ...

This is not quite what you asked for, but it may serve your purpose, depending on what use-case you had in mind.

 
posted 10 months ago
xuinkrbin. 1 post

Forum: Instiki – Topic: HTML/PHP comments?

Is there a way to embed comments in an Instiki page which appear only in the source itself and not to a casual reader?

 
posted about 1 year ago
distler 100 posts

Forum: Instiki – Topic: instiki_session cookie overflows after some editing

I only replaced the /app folder of my current wiki…

Well, since the changeset that I linked to above also involves changes to vendor/plugins/form_spam_protection/lib/form_tag_helper_extensions.rb , just updating files in /app/* won’t actually work.

Moreover, updating all of the files in /app to the latest version(s) drags in other changes. The particular error that you are seeing is due to this changeset, which introduces a nice feature for wikilinks, but required some changes in /lib as well.

I think I will wait for the 19.8 release on this one. This is not a huge problem.

Currently I am awaiting the release of Passenger 5.0.7, to see whether it resolves some issues with Instiki, or whether changes on the Instiki end are also required. If all goes according to plan, I’ll roll another release sometime in the early summer.

For whatever it’s worth, though, this site runs on the latest development version of Instiki (with Passenger 4.0.59) and is perfectly stable.

If you’re having issues with Instiki 0.19.7, I’d recommend updating now.

 
posted about 1 year ago
peter_ljung 2 posts

Forum: Instiki – Topic: instiki_session cookie overflows after some editing

Thanks for your reply !

I made a quick test with the latest source from git. I only replaced the /app folder of my current wiki, but I seem to have some kind of problem.

I got an error (directly in the browser)

ActionView::TemplateError (wrong number of arguments (6 for 3..5)) on line #21 of app/views/wiki/page.rhtml:
18: 
19: <div class="byline">
20: <%= @page.revisions? ? "Revised" : "Created" %> on <%= format_date(@page.revised_at) %> 
21: by <%= author_link(@page) %>
22: <%= "(#{@page.author.ip})" if @page.author.respond_to?(:ip) %>
23: <% if @web.count_pages? %>
24: <% total_chars = @page.content.length %>

lib/url_generator.rb:13:in `make_link'
app/helpers/application_helper.rb:53:in `author_link'
app/views/wiki/page.rhtml:21:in `_run_rhtml_app47views47wiki47page46rhtml'
app/controllers/wiki_controller.rb:368:in `show'
/usr/local/lib/phusion-passenger20/lib/phusion_passenger/rack/thread_handler_extension.rb:74:in `process_request'
/usr/local/lib/phusion-passenger20/lib/phusion_passenger/request_handler/thread_handler.rb:141:in `accept_and_process_next_request'
/usr/local/lib/phusion-passenger20/lib/phusion_passenger/request_handler/thread_handler.rb:109:in `main_loop'
/usr/local/lib/phusion-passenger20/lib/phusion_passenger/request_handler.rb:448:in `block (3 levels) in start_threads'

I think I will wait for the 19.8 release on this one. This is not a huge problem.

 
posted about 1 year ago
distler 100 posts

Forum: Instiki – Topic: instiki_session cookie overflows after some editing

Try using the latest Development Version. (Grab it either from my BZR Repository, from Github or as a tarball.) There are some changes that should fix the problem.

Someday, I’ll get around to releasing 0.19.8 ….

 
posted about 1 year ago
peter_ljung 2 posts

Forum: Instiki – Topic: instiki_session cookie overflows after some editing

The instiki_session cookie seems to increase when I edit my Instiki site.

After a while I reach the 4kB limit and instiki returns an:

Status: 500 Internal Server Error
                  ActionController::Session::CookieStore::CookieOverflow

My web server (http://www.lounge.se) is setup as follows:

  • OpenBSD 5.6
  • ruby 2.0.0p481
  • passenger-4.0.44
  • mysql-server-5.1.7
  • Instiki 1.9.7

When I clear the cookie it start working again for a while until it reached 4k limit agina.

Any suggestions of what could be wrong?

 
posted over 1 year ago
distler 100 posts

Forum: Instiki – Topic: Instiki hyperlinks failures

I did figure out that if I tried to upload a file into instiki (which automatically creates a ‘files’ folder in the Webs directory, and moved the html file to the newly created ‘files’ folder …

Oh. I think I misunderstood your problem.

Of course you can’t create an HTML link to some random file in (a random subdirectory of) the instiki directory. That would be stupid and dangerous.

As you can see from URLs for the CSS and javascript files on your Instiki pages, you can link to files in the public directory. You can also link to files in the webs directory (as you can see from the file links that you created).

I guess also a functionality thing I noticed is that if you click on the hyperlink to an local hosted html page. Instiki calls up a download box within the browser and asks the user if they want to save the html file locally, instead of actually opening the page within the browser as an actual webpage. Is this an issue or just how instiki displays local html files?

That’s for security.

You ought to be able to trust that the content of an Instiki page is safe. Thus (for instance) you can’t edit an Instiki page and add malicious javascript to it. This protection would be vitiated, if you could put the malicious javascript in an HTML file that opened in the user’s browser as if it were just another page on the Instiki wiki.

This restriction does not apply to files in the public directory. Those had to have been placed there by the system administrator and are assumed to be safe.

 
posted over 1 year ago
nkay 8 posts

Forum: Instiki – Topic: Instiki hyperlinks failures

Thanks for the response. Unfortunately the same error occurs. I have tried many different syntax’s each resulting the same error.

I did figure out that if I tried to upload a file into instiki (which automatically creates a ‘files’ folder in the Webs directory, and moved the html file to the newly created ‘files’ folder and update the code I can get it to not error out. If I create additional folders nested in the ‘files’ folder than it errors back out. I checked permissions on the folders and everything is fine.

I guess also a functionality thing I noticed is that if you click on the hyperlink to an local hosted html page. Instiki calls up a download box within the browser and asks the user if they want to save the html file locally, instead of actually opening the page within the browser as an actual webpage. Is this an issue or just how instiki displays local html files?

 
posted over 1 year ago
tanzer 36 posts

Forum: Instiki – Topic: Idle Instiki was using 17% of CPU on a shared host

Problems not related. Sysadmins fixed a server problem. Instiki with high CPU usage has not recurred after that one incident.

Thanks

 
posted over 1 year ago
distler 100 posts

Forum: Instiki – Topic: Instiki hyperlinks failures

How about

"Environment Configuration":/aces/wiki_files/environments/AcesEnvironments.html

?

I don’t know how well Textile handles the “:” in the URL you were using.

 
posted over 1 year ago
nkay 8 posts

edited over 1 year ago

Forum: Instiki – Topic: Instiki hyperlinks failures

I am having an issues with hyperlinks with our WIKI page using the textile markup. Hyperlinks to external webpages work eg. “www.google.com” but any internal html pages within the instiki filesystem end up getting application errors.
We have a folder inside the main Web folder called Wiki_files which has many different HTML files but if we link to any of them e.g…

“Environment Configuration”:http://acesrep:2500/aces/wiki_files/environments/AcesEnvironments.html)

I receive “Internal Error” An application error occurred while processing your request. Looking at the source of the page I get these dumps.

(d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/base.rb:1339:in perform_action' d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:617:in call_filters’ d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:638:in block in run_before_filters' d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:206:in call’ d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:206:in block in around_proc' d:/instiki-d:/0.19.6/vendor/rails/activesupport/lib/active_support/callbacks.rb:182:in call’ d:/instiki-0.19.6/vendor/rails/activesupport/lib/active_support/callbacks.rb:182:in evaluate_method' d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:184:in call’ d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:635:in run_before_filters' d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:615:in call_filters’ d:/instiki-0.19.6/vendor/rails/actionpack/lib/action_controller/filters.rb:638:in `block in run_before_filters')


If I open up the HTML document within the server itself it works fine but not as a link through instiki wiki.

 
posted over 1 year ago
tanzer 36 posts

Forum: Instiki – Topic: How do I bulk-clear the Instiki cache

Thanks, I did that.

It seems to be working fine, but one thing puzzles me. About a day after I cleared everything out as per the above, the full tree under instiki/cache/views/azimuth got repopulated – presumably when the site got crawled.

But the storage folder didn’t get repopulated. Or rather, now there is just a single file in it: azimuth-markdownMML-2015-02-12-11-11-03.zip, with a timestamp of yesterday.

Before I cleared out storage, there were tons of files it in, it looked something like one file per page of the wiki, though I didn’t look closely.

Does this make sense; are there any signs of ill-health here? What is the function of the storage folder?

Thanks.

 
posted over 1 year ago
distler 100 posts

Forum: Instiki – Topic: How do I bulk-clear the Instiki cache

How about:

rm instiki/storage/*

That should be fine.

rm -r instiki/cache/views/azimuth

As should that.

There’s a whole structure of directories and files under the last directory, that’s okay to wipe out?

All of those will be recreated, as needed.

 
posted over 1 year ago
tanzer 36 posts

Forum: Instiki – Topic: How do I bulk-clear the Instiki cache

Can we make the instructions more specific, because I’m cautions about disrupting a structure that I don’t understand.

How about:

rm instiki/storage/*

rm -r instiki/cache/views/azimuth

There’s a whole structure of directories and files under the last directory, that’s okay to wipe out?